Task uploading method, system and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a task uploading method, system and device, electronic equipment and a storage medium, and relates to the technical field of cloud storage task uploading. The method comprises the steps that the uploading state of a target task is monitored, whether storage configuration needs to be changed or not is determined, if storage configuration needs to be changed, configuration information corresponding to the target task is determined, the uploading state and the configuration information are uploaded to a cloud storage server, and a next target task is uploaded based on updated storage configuration returned by the cloud storage server. According to the embodiment of the invention, by monitoring the task uploading state, the updating configuration is quickly obtained through the cloud storage server when needed, so that the task can be successfully uploaded, and the task uploading stability is improved.

Description

Technical Field

[0001] This application relates to the technical field of cloud storage task upload. Specifically, this application relates to a task upload method, system, device, electronic device, computer-readable storage medium, and computer program product. Background Art

[0002] With the rapid development of Internet technology, more and more data and files need to be stored. The local storage requires a large amount of storage space and is difficult to maintain. Therefore, scalable, highly available, and highly secure cloud storage has become a mainstream direction, and public clouds, private clouds, enterprise clouds, etc. have emerged one after another, providing cloud storage services to the public or users in small areas.

[0003] In the current cloud storage method, when a task upload fails, it is necessary to screen the configuration information one by one and manually change the relevant files. The response speed is slow, it takes a long time, and it cannot ensure the successful upload of the task. Summary of the Invention

[0004] Embodiments of this application provide a task upload method, system, device, electronic device, computer-readable storage medium, and computer program product, aiming to solve the technical problem that the response and update speeds are slow when cloud storage upload fails, resulting in the task not being successfully uploaded.

[0005] In one aspect of the embodiments of this application, a task upload method is provided, which is applied to the device side. The device side is connected to the cloud storage server through a network. The method includes:

[0006] Monitor the upload status of the target task and determine whether the storage configuration needs to be changed;

[0007] If the storage configuration needs to be changed, determine the configuration information corresponding to the target task;

[0008] Upload the upload status and configuration information to the cloud storage server;

[0009] Based on the updated storage configuration returned by the cloud storage server, upload the next target task.

[0010] Optionally, monitoring the upload status of the target task and determining whether the storage configuration needs to be changed includes:

[0011] Based on the upload status of the target task, determine the upload success rate of the target task;

[0012] Based on the upload success rate, determine whether the storage configuration needs to be changed.

[0013] Optionally, the upload status includes upload success or upload failure;

[0014] Determine the upload success rate of the target task based on the upload status of the target task, including:

[0015] Determine the task type of the target task; the task type includes single tasks and combined tasks;

[0016] If the task type is a single task, determine the upload success rate of the target task based on the number of files successfully uploaded in the target task;

[0017] If the task type is a combined task, determine the upload success rate of the target task based on the number of tasks successfully uploaded in the target task; the combined task includes multiple tasks.

[0018] Optionally, the target task includes multiple tasks;

[0019] Determine the upload success rate of the target task based on the upload status of the target task, including:

[0020] Determine the upload success rate corresponding to each target task based on the upload status of each target task;

[0021] Based on the upload success rate, determine whether to change the storage configuration, including:

[0022] Compare each upload success rate with a preset success rate threshold to determine whether the target task fails;

[0023] Record the consecutive failure count of the target task. If the consecutive failure count meets the preset count threshold, determine that the storage configuration needs to be changed;

[0024] If the consecutive failure count does not meet the preset count threshold, continue to monitor the upload status of each target task.

[0025] Optionally, upload the upload status and configuration information to the cloud storage server, including:

[0026] Determine the scenario information corresponding to the target task;

[0027] Upload the scenario information, upload status, and configuration information to the cloud storage server;

[0028] Based on the updated storage configuration returned by the cloud storage server, upload the next target task, including:

[0029] Receive the updated storage configuration returned by the cloud storage server for the scenario information, upload status, and configuration information;

[0030] Based on the updated storage configuration, upload the next target task.

[0031] Optionally, upload the upload status and configuration information to the cloud storage server, including:

[0032] Determine the certificate information corresponding to the target task;

[0033] Upload the upload status, configuration information, and certificate information to the cloud storage server; the cloud storage server is used to obtain an updated storage configuration based on the upload status, configuration information, and certificate information.

[0034] In another aspect of the embodiments of the present application, a task upload method is provided, which is applied to a cloud storage server. The cloud storage server is connected to the device side through a network. The method includes:

[0035] Receive the upload status and configuration information of the target task sent by the device side; the sending of the upload status and configuration information is determined based on the upload status of the target task; the configuration information is obtained based on the upload status;

[0036] Obtain an updated storage configuration based on the upload status and configuration information;

[0037] Send the updated storage configuration to the device side so that the device side can upload the next target task based on the updated storage configuration.

[0038] Optionally, the configuration information includes the storage bucket information corresponding to the target task;

[0039] Obtaining an updated storage configuration based on the upload status and configuration information includes:

[0040] Determine the updated storage bucket configuration from the storage bucket list based on the upload status and the storage bucket information; the storage bucket list corresponds to the target task one by one;

[0041] Use the updated storage bucket configuration as the updated storage configuration.

[0042] In one aspect of the embodiments of the present application, a task upload system is provided, including a device side and a cloud storage server. The system includes:

[0043] The device side is used to monitor the upload status of the target task, determine whether the storage configuration needs to be changed; if the storage configuration needs to be changed, determine the configuration information corresponding to the target task; upload the upload status and configuration information to the cloud storage server;

[0044] The cloud storage server is used to obtain an updated storage configuration based on the upload status and configuration information and send it to the device side;

[0045] The device side is used to upload the next target task based on the updated storage configuration returned by the cloud storage server.

[0046] In one aspect of the embodiments of the present application, a task upload device is provided, which is applied to the device side. The device includes:

[0047] An update module, configured to monitor the upload status of a target task and determine whether to change the storage configuration;

[0048] An information determination module, configured to determine the configuration information corresponding to the target task if it is necessary to change the storage configuration;

[0049] An upload module, configured to upload the upload status and the configuration information to a cloud storage server;

[0050] A configuration module, configured to upload the next target task based on the updated storage configuration returned by the cloud storage server.

[0051] In one aspect of the embodiments of the present application, a task upload device is provided, which is applied to a cloud storage server. The device includes:

[0052] A receiving module, configured to receive the upload status and the configuration information of the target task sent by the device side; the sending of the upload status and the configuration information is determined based on the upload status of the target task; the configuration information is obtained based on the upload status;

[0053] A configuration acquisition module, configured to obtain an updated storage configuration based on the upload status and the configuration information;

[0054] A sending module, configured to send the updated storage configuration to the device side so that the device side uploads the next target task based on the updated storage configuration.

[0055] In one aspect of the embodiments of the present application, an electronic device is provided. The electronic device includes:

[0056] A memory, a processor, and a computer program stored on the memory. The processor executes the computer program to implement the steps of the task upload method shown in any one of the embodiments of the present application.

[0057] In one aspect of the embodiments of the present application, 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 of the task upload method shown in any one of the embodiments of the present application are implemented.

[0058] In one aspect of the embodiments of the present application, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the steps of the task upload method shown in any one of the embodiments of the present application are implemented.

[0059] The beneficial effects brought by the technical solutions provided by the embodiments of the present application are:

[0060] The task upload method provided by this application can timely obtain the current task upload status of the device side by monitoring the task upload status. When the task upload status fails or other situations occur, the storage configuration can be updated in a timely manner to achieve a timely response to configuration updates. When it is necessary to change the storage configuration, only the upload status and configuration information need to be uploaded to the cloud storage server to obtain the updated storage configuration that needs to be changed. By using the cloud storage server to obtain the updated configuration information, the speed of configuration update is accelerated. When it is found that the upload fails, the storage configuration is changed in a timely manner, improving the stability of task upload. Description of the Drawings

[0061] To more clearly illustrate the technical solutions in the embodiments of this application, the following will briefly introduce the drawings required for the description in the embodiments of this application.

[0062] Figure 1 Schematic diagram of the application scenario of a task upload method provided by an embodiment of this application;

[0063] Figure 2 Schematic diagram of the process of a task upload method applied to the device side provided by an embodiment of this application;

[0064] Figure 3 Another schematic diagram of the process of a task upload method applied to the device side provided by an embodiment of this application;

[0065] Figure 4 Schematic diagram of the process of a task upload method applied to the cloud storage server provided by an embodiment of this application;

[0066] Figure 5 Schematic diagram of the system process of a task upload method provided by an embodiment of this application;

[0067] Figure 6 Schematic diagram of the process of an example of a task upload method provided by an embodiment of this application;

[0068] Figure 7 Schematic diagram of the structure of a task upload device provided by an embodiment of this application;

[0069] Figure 8 Schematic diagram of the structure of a task upload device provided by an embodiment of this application;

[0070] Figure 9 Schematic diagram of the structure of an electronic device applicable to a task upload method provided by an embodiment of this application. Detailed Embodiments

[0071] The embodiments of the present application will be described below with reference to the accompanying drawings in the present application. It should be understood that the embodiments described below in conjunction with the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions of the embodiments of the present application.

[0072] Those skilled in the art of the present technology can understand that, unless specifically stated otherwise, the singular forms "a", "an", "the", and "said" used herein may also include the plural forms. It should be further understood that the terms "comprising" and "including" used in the embodiments of the present application mean that the corresponding features can be implemented as the presented features, information, data, steps, operations, elements, and / or components, but do not exclude the implementation of other features, information, data, steps, operations, elements, components, and / or their combinations, etc. supported by the art of the present technology. It should be understood that when we say an element is "connected" or "coupled" to another element, the one element can be directly connected or coupled to the other element, or it can mean that the one element and the other element establish a connection relationship through an intermediate element. In addition, the "connection" or "coupling" used here can include wireless connection or wireless coupling. The terms "or", "and / or", "including at least one of the following", etc. used in the present application can be interpreted inclusively, or mean any one or any combination.

[0073] In the embodiments of the present application, the term "module" or "unit" refers to a computer program with a predetermined function or a part of a computer program, which works together with other related parts to achieve a predetermined goal, and can be fully or partially implemented by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Similarly, one processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of the overall module or unit that includes the function of the module or unit.

[0074] In the specific implementation of the present application, any data related to an object, such as the data involved in the process of an object using an application program, when the embodiments of the present application are applied to a specific product or technology, object permission or consent needs to be obtained, and the collection, use, and processing of the relevant data need to comply with the relevant laws, regulations, and standards of the relevant countries and regions. That is to say, in the embodiments of the present application, if any of the above data related to an object is involved, these data need to be obtained under the authorization and consent of the object and in compliance with the relevant laws, regulations, and standards of the country and region.

[0075] To make the purpose, technical solutions, and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0076] During the cloud storage upload process, the device side may encounter various problems. For example, the device is online for a long time, the device and the circuit are normal, but during a certain period, tasks or files cannot be uploaded, or they cannot be uploaded all the time. After the device side reports the upload failure problem, in the prior art, the corresponding upload device in the cloud is determined through a specific device identifier, the various configuration information of the device is viewed, and the configuration information of the device is manually edited and changed. The response speed to upload failure is slow, and the firmware does not support multi-certificate updates.

[0077] The task upload method, device, electronic device, computer-readable storage medium and computer program product provided by this application aim to solve at least one of the above technical problems in the prior art.

[0078] In view of at least one of the above technical problems or areas for improvement in the related art, this application proposes a task upload method, system, device, electronic device, computer-readable storage medium and computer program product. The task upload method provided by this solution can timely obtain the current task upload status of the device side by monitoring the task upload status. When the task upload status fails or other situations occur, the storage configuration can be updated in a timely manner to achieve timely response to configuration updates. When the storage configuration needs to be changed, only by uploading the upload status and configuration information to the cloud storage server, the updated storage configuration that needs to be changed can be obtained. By using the cloud storage server to obtain the updated configuration information, the configuration update speed is accelerated, the storage configuration is changed in a timely manner, the task is successfully uploaded, and the stability of the task upload is improved.

[0079] Furthermore, the upload success rate of the target task can be determined based on the upload status of the target task, so as to determine whether the configuration needs to be changed. The target tasks are classified into single tasks and combined tasks according to the type. Different success rate calculation methods are used for different types of tasks, which can more accurately determine the success rate. For multiple target tasks, the upload success rate is compared with the preset success rate threshold to determine the failed target tasks, and then combined with the number of consecutive failures, the situation where the configuration needs to be changed is determined, accurately identifying the situation where the configuration needs to be changed and reducing system resource waste.

[0080] In addition, when uploading the upload status and configuration information to the cloud storage server, the scenario information of the target task can also be uploaded, so that the cloud storage server selects different updated storage configurations based on different scenarios. Uploading the current certificate information together can update the certificate information in a timely manner to ensure the availability of relevant configurations.

[0081] The technical solutions of the embodiments of the present application and the technical effects produced by the technical solutions of the present application will be described below through the description of several exemplary embodiments. It should be noted that the following embodiments can be referenced, borrowed, or combined with each other. For the same terms, similar features, and similar implementation steps in different embodiments, they will not be described repeatedly.

[0082] Figure 1 FIG. is a schematic diagram of the application scenario of the task uploading method provided by the embodiment of the present application. Among them, the application environment may include a device end 100 and a cloud storage server 200, and the device end 100 is connected to the cloud storage server 200 through a network.

[0083] Specifically, the device end 100 monitors the upload status of the target task, determines whether the storage configuration needs to be changed. If the storage configuration needs to be changed, the configuration information corresponding to the target task is determined, and the upload status and the configuration information are uploaded to the cloud storage server 200. The cloud storage server 200 obtains the updated storage configuration based on the upload status and the configuration information and sends it to the device end 100. The device end 100 uploads the next target task based on the updated storage configuration returned by the cloud storage server. By updating the storage configuration, the target task is successfully uploaded, improving the stability of task uploading.

[0084] The above application scenario is only an example and does not limit the application scenario of the task uploading method of the present application.

[0085] In some possible implementation manners, taking the device end as the execution subject, the embodiment of the present application provides a task uploading method, as Figure 2 shown, which may include the following steps:

[0086] S210, monitor the upload status of the target task, and determine whether the storage configuration needs to be changed.

[0087] Among them, the device end is connected to the cloud storage server through a network.

[0088] Among them, the target task may include at least one, and each target task corresponds to a usage scenario; the usage scenario may include: log upload scenario, cloud storage task upload scenario, one-key panoramic scenario, timed screenshot scenario, cover image upload scenario, etc.

[0089] Specifically, monitor the upload status of the target task, determine whether the upload status is abnormal or failed, so as to determine whether the configuration needs to be changed. When the upload status is failed, it is determined that the configuration needs to be changed. When the upload status is normal, continue to monitor. A preset time period can be set to judge the upload status of the tasks within the preset time period, or the upload status of a preset number of consecutive target tasks can be judged, which is specifically set according to actual needs.

[0090] In the specific implementation process, the upload status includes success or failure. When the target task or file ends and calls back, it is judged whether to change the storage configuration, that is, it is judged whether to change the storage configuration after the task is completed. If the task or file upload fails, it is determined that the storage configuration needs to be changed. For example, when the task scenario is a cloud storage task scenario, after the cloud storage task is completed, it is judged whether the task fails. When the cloud storage task upload fails, the storage bucket can be switched. By switching to a new storage bucket, the next task can be uploaded continuously, and the upload status can be monitored continuously. The above method is executed until the cloud storage task is successfully uploaded, so as to ensure that the device uses the upload function to upload successfully to the greatest extent.

[0091] In the specific implementation process, there can be multiple target tasks, and each target task has a corresponding upload status. The relevant temporary values of the failed target tasks need to be saved in the local cache flash and uploaded to the cloud storage server under certain conditions for updating the storage configuration. Among them, the temporary data includes information related to the configuration and the number of upload failures of the current configuration.

[0092] S220, if the storage configuration needs to be changed, determine the configuration information corresponding to the target task.

[0093] Among them, the configuration information can include storage bucket information. The storage bucket is the basic storage unit in the cloud storage service and is used to organize and manage the data in the cloud storage. In addition to the storage bucket information, it can also include various settings such as access control, storage class, version control, lifecycle management, cross-region replication, data encryption, static website hosting, logging, event notification, custom domain name, multi-factor authentication, resource tags, and interface access control to meet different security, performance, and management requirements.

[0094] Specifically, according to the upload status of the target task, if it is determined that the storage configuration needs to be changed, determine the configuration information corresponding to the target task, and then send it to the cloud storage server, so that the cloud storage server determines to update the storage configuration based on the configuration information corresponding to the current upload status to ensure that the task can be successfully uploaded.

[0095] In the specific implementation process, in different usage scenarios, the configuration information corresponding to the target task can be different. The usage scenarios can include log upload scenarios, cloud storage task upload scenarios, key panorama scenarios, timed screenshot scenarios, and cover image upload scenarios, etc.

[0096] S230, upload the upload status and configuration information to the cloud storage server.

[0097] Specifically, upload the upload status and configuration information corresponding to the target task to the cloud storage server. The cloud storage server selects new configuration information based on the current configuration information and sends the updated storage configuration to the device side so that the device side can successfully upload data.

[0098] In the specific implementation process, the task upload system supports uploading signatures using the policy method, allowing the device side to request a signature policy from the cloud storage server first without uploading the file content, and then uploading the file according to this policy.

[0099] In the specific implementation process, the device side can periodically pull the configuration from the cloud storage server or actively pull the configuration. It can perform multiple configuration update operations, record the failed configurations in the failure list, and upload the failure list of the current configuration to the cloud storage server to request a new configuration. The cloud storage server determines the updated storage configuration according to the preset configuration selection rules. The device side can upload the corresponding scenarios, the failure configuration lists corresponding to each scenario, and the manufacturer (i.e., the cloud storage service provider) list to the cloud storage server together. The cloud storage server allocates a suitable updated storage configuration to the device side.

[0100] In the specific implementation process, the path for the device side to upload information to the cloud storage server can also be selected. The path selection method can include: sending a probe packet from the device side to the endpoint of the cloud storage, collecting data such as the bandwidth, latency, and packet loss of the network path, calculating the comprehensive index of each path based on the collected data. When calculating the index, it can be a simple weighted average, or a more complex scoring, or based on a trained evaluation model. Compare the indexes of all paths, select the optimal path for data upload, upload data according to the selected path, and monitor the actual upload effect. If the actual effect is not good, re-evaluate and select a new path, or adjust the path selection policy according to historical data and real-time feedback.

[0101] In the specific implementation process, monitoring points (logging) can be set to record the status and results of data upload or processing. The device side can upload the detailed information of the failure to the cloud storage server. The detailed information can specifically include: failure type, failure code, occurrence time, impact range, device information, and network status, etc.

[0102] S240, upload the next target task based on the updated storage configuration returned by the cloud storage server.

[0103] Specifically, based on the updated storage configuration returned by the cloud storage server, update the storage configuration of the target task, and then upload the next target task. If the upload is successful, end this update and continuously monitor the upload status of the target task. If the upload fails, continue with the configuration update operation until the target task can be successfully uploaded.

[0104] In the specific implementation process, when the device end receives the updated storage configuration returned by the cloud storage server, before applying the new configuration, the device end can verify the integrity and correctness of the configuration information, including checking the digital signature, checksum or the format of the configuration file. The device end updates the new configuration information to the local storage, replacing the old configuration. After obtaining the updated configuration and applying the new configuration, the device end can send an acknowledgment message back to the cloud storage server indicating that the new configuration has been received and applied, and continue the upload task using the updated configuration, and record the log after the configuration change to ensure the stable operation of the system.

[0105] In some possible implementation manners, in the above steps of monitoring the upload status of the target task and determining whether to change the storage configuration, it includes:

[0106] Based on the upload status of the target task, determine the upload success rate of the target task;

[0107] Based on the upload success rate, determine whether to change the storage configuration.

[0108] Among them, the upload status includes upload success or upload failure.

[0109] Specifically, based on the upload status of the target task, determine the upload success rate of the target task, and determine whether the upload success rate meets the preset condition. If it meets, it is determined that the storage configuration needs to be changed. The method for determining whether the upload success rate meets the preset condition may include: comparing the upload success rate with a preset threshold. When the upload success rate is less than the threshold, it is determined that the storage configuration needs to be changed, or obtain the upload status of multiple target tasks, cluster the upload success rates of multiple tasks to obtain the clustering center point. If the clustering center point meets the threshold, such as the mean point or the mean square deviation, etc.

[0110] In the specific implementation process, for different usage scenarios, the conditions for determining whether to change the storage configuration are different. When the scenario is cloud storage task upload, when the upload success rate is less than a certain threshold and the continuously satisfied quantity also meets the threshold, the configuration is recorded in the failure list. When the scenario is log upload task, when the upload success rate is less than a certain threshold, the configuration is recorded in the failure list, and the quantity does not need to be concerned about.

[0111] In the specific implementation process, when the upload success rate of a task is greater than or equal to a preset threshold, the corresponding configured failure count is cleared. For example, in the scenario of a log upload task, each time a log upload task is received, the software development kit (SDK) takes the current list of failed storage buckets (buckets) to the cloud to request a new bucket. When any one of the configurations returned by the cloud is equal to the content of the locally cached bucket, the cached list of failed buckets, the current failure count, and other cached variables are cleared. When the upload success rate of a certain bucket is greater than or equal to the preset threshold, the failure count of the corresponding bucket in the failure list is cleared.

[0112] In some possible implementation manners, in the above steps, determining the upload success rate of the target task based on the upload status of the target task includes:

[0113] Determine the task type of the target task;

[0114] If the task type is a single task, determine the upload success rate of the target task based on the number of files successfully uploaded in the target task;

[0115] If the task type is a combined task, determine the upload success rate of the target task based on the number of tasks successfully uploaded in the target task.

[0116] Among them, the task type includes a single task and a combined task. A combined task includes multiple tasks, and one task can include at least one file.

[0117] Specifically, determine the task type of the target task. If the task type is a single task, determine the upload success rate of the target task based on the number of files successfully uploaded in the target task. For example, for a video upload task with many video files, determine the number of successfully uploaded files and determine the upload success rate of the task. If the task type is a combined task, determine the upload success rate of the target task based on the number of tasks successfully uploaded in the target task. For example, a combined task can include upload tasks of multiple pictures, videos, or files. It is necessary to determine the upload status of each task, determine the successfully uploaded tasks, and determine the upload success rate of the combined task based on the number of successfully uploaded tasks.

[0118] In the specific implementation process, for different scenarios or task types, different upload success rate calculation methods can be selected. For example, for multimedia format mp4 tasks, text file format m3u8 tasks, hybrid cloud tasks, one-key panoramic tasks, etc., the success rate can be statistically calculated based on the proportion of successful tasks among multiple tasks. For log files and low-threshold files, etc., one task can include multiple files, and the success rate can be statistically calculated based on the proportion of successful files among multiple files.

[0119] In some possible implementation manners, determining the upload success rate of the target task based on the upload status of the target task in the above steps includes:

[0120] Determining the upload success rate corresponding to each target task based on the upload status of each target task;

[0121] Determining whether to change the storage configuration based on the upload success rate, including:

[0122] Comparing each upload success rate with a preset success rate threshold to determine whether the target task fails;

[0123] Recording the continuous failure count of the target task, and if the continuous failure count meets a preset count threshold, determining that the storage configuration needs to be changed;

[0124] If the continuous failure count does not meet the preset count threshold, continue to monitor the upload status of each target task.

[0125] Among them, there are multiple target tasks.

[0126] Specifically, determining the upload success rate corresponding to each target task based on the upload status of each target task, comparing each upload success rate with a preset success rate threshold to determine whether the target task fails. If the upload success rate is not less than the preset success rate threshold, it is considered that the upload is successful, and then continue to monitor the upload status of each target task. If the upload success rate is less than the preset success rate threshold, it is considered that the task fails, and record the number of continuously failed tasks. A counter can be used to implement this. If the next task is successful, the counter is incremented by one. If the next task is failed, the counter is cleared and recalculated. If the continuous failure count meets the preset count threshold, determine that the storage configuration needs to be changed. If the continuous failure count does not meet the preset count threshold, continue to monitor the upload status of each target task.

[0127] In the specific implementation process, the preset success rate threshold and the preset count threshold corresponding to the target tasks in different scenarios are different, and the continuous failure counts in each scenario are counted separately. When calculating the continuous failure count, it is the number of failure times in the same scenario that is counted. For example, if the recorded failed tasks are cloud storage scenario tasks and one - key panoramic scenario tasks, and if the currently failed task is a cloud storage scenario task, then the continuous failure count of the cloud storage scenario task is 2, and that of the one - key panoramic scenario task is 1.

[0128] In the specific implementation process, the upload status of each target task can be input into the trained task judgment model to obtain a judgment result, that is, to determine whether the storage configuration needs to be changed. When training the task judgment model, a status sample set containing multiple status samples can be obtained first. Each status sample includes the upload status of the corresponding task and is marked with the corresponding result label. The status sample set is input into the task judgment model to obtain a prediction result. Based on the prediction result and the result label, the parameters in the task judgment model are adjusted until the training is completed to obtain the trained task judgment model.

[0129] In the specific implementation process, the success rate threshold can be set to 30%. When the upload success rate of a task is less than 30%, the task is judged as failed. Then, continue to determine the number of continuously failed tasks. If the number of continuously failed tasks reaches the preset number threshold, it is determined that the storage configuration needs to be changed. Among them, for different usage scenarios, the corresponding preset number thresholds are different. The values of the preset success rate threshold and the preset number threshold are configured by the cloud storage server. The preset success rate threshold can be set to 30%, and the preset number threshold can be set to 20, which can be dynamically adjusted according to the actual situation.

[0130] In the specific implementation process, the success rate threshold can be denoted as N, and the continuous number of times can be denoted as X. As Figure 3 shown, the target task is a cloud storage task. When the cloud storage task ends and a callback occurs, determine the success rate of the task, and judge whether the success rate is less than N. If it is greater than N, set the failure count of the cloud storage task recorded in the local cache to 0. If it is less than N, record the failure count and save the failure count in the device-side cache (i.e., the disk write shown in the figure). Then, determine the continuous failure count. If the failure count is less than or equal to X, end the current configuration update and continue to monitor the upload status of the cloud storage task. If the failure count is greater than X, save the failure storage bucket configuration corresponding to the current cloud storage task (i.e., the relevant configuration of the failed cloud storage bucket shown in the figure), determine that the storage configuration needs to be changed, obtain the new storage bucket configuration (i.e., the policy to trigger the re-pull of the cloud storage configuration shown in the figure), and end the current storage configuration update.

[0131] In some possible implementation manners, uploading the upload status and configuration information to the cloud storage server in the above steps includes:

[0132] Determine the scenario information corresponding to the target task;

[0133] Upload the scenario information, upload status, and configuration information to the cloud storage server;

[0134] Based on the updated storage configuration returned by the cloud storage server, uploading the next target task includes:

[0135] Receive the updated storage configuration returned by the cloud storage server for the scenario information, upload status, and configuration information;

[0136] Based on the updated storage configuration, upload the next target task.

[0137] Specifically, determine the scenario information corresponding to the target task, upload the scenario information, upload status, and configuration information to the cloud storage server. The cloud storage server selects the updated storage configuration from multiple configuration information corresponding to the scenario information for the upload status and configuration information and returns it to the device side. The device side uploads the next target task based on the returned updated storage configuration. Among them, the cloud storage server will configure the corresponding configuration information for each scenario. Based on different usage scenarios, different strategies are needed to meet the differentiated requirements and solve the problem of upload failure.

[0138] In the specific implementation process, the device side can request data of multiple scenarios at the same time. The configuration information corresponding to different scenarios is different, and the obtained updated storage configurations are also different. The data of each scenario does not interfere with each other.

[0139] In the specific implementation process, when the device side pulls new configurations regularly or actively, the device side takes the scenario and the failure configuration list of the scenario to the cloud storage server to request new configurations. The cloud storage server selects the updated configuration information from the configuration information corresponding to the scenario according to the preset selection rules and sends it to the device side. For example, the cloud storage server distributes a suitable bucket to the device side according to the multi-bucket polling mechanism.

[0140] In some possible implementation manners, uploading the upload status and configuration information to the cloud storage server in the above step includes:

[0141] Determine the certificate information corresponding to the target task;

[0142] Upload the upload status, configuration information, and certificate information to the cloud storage server.

[0143] Among them, the cloud storage server is used to obtain the updated storage configuration based on the upload status, configuration information, and certificate information.

[0144] Specifically, on the device side, the certificate can be saved in the form of a directory. Determine the certificate information corresponding to the target task, upload the upload status, configuration information, and certificate information to the cloud storage server. The cloud storage server obtains a new updated storage configuration based on the upload status and configuration information, determines the updated certificate based on the uploaded certificate information. If the updated storage configuration matches the updated certificate information, obtain the updated storage configuration and send it to the device side. If not, re-determine the updated storage configuration based on the updated certificate information, ensuring the availability of the task upload method.

[0145] In the specific implementation process, the device side sets fields that support dynamic certificate updates, and new cloud service providers will only issue certificates for versions that support dynamic certificate updates. The certificate information is used to indicate the regions where the task upload system in this application can be used, and different cloud service providers have slightly different implementations of storage buckets.

[0146] In the specific implementation process, the device side supports different manufacturers and multi-certificate updates. The number of simultaneously existing certificates can be set. For example, it can be set to 5 copies. The device side defaults to including 3 copies, and the original logical scheme is retained. When the device is first run, the device-side certificates will be copied to the read-write partition. After the number of certificates is updated to 5 copies and the number of device-side certificates saved exceeds the limit, after deleting certificates through the elimination strategy, new certificates will be downloaded. Among them, the elimination strategy includes: giving priority to deleting the certificates that have been unused for the longest time for internal management. Since the device file system does not support modifying the file access time during access, the earliest modification time of the certificates can also be used as the standard for deleting redundant certificates.

[0147] In the specific implementation process, different certificates correspond to different cloud service providers, and the corresponding configuration information for different manufacturers is also different. After updating the certificate information, the corresponding configuration information also needs to be updated. Specifically, different manufacturers have different storage buckets, and after updating the certificates, the storage buckets also need to be updated.

[0148] In the specific implementation process, for combined tasks, the certificates corresponding to each sub-task of the same target task should be consistent. For example, a task for a one-key panoramic scene can include multiple pictures, multiple m3u8 files, and data transmission stream ts files. Each picture and file corresponds to a sub-task, and the certificates of each sub-task should be consistent.

[0149] In some possible implementation manners, taking the execution entity as a cloud storage server as an example, the embodiments of this application provide a task upload method, as Figure 4 shown, which may include the following steps:

[0150] S410, receive the upload status and configuration information of the target task sent by the device side.

[0151] Among them, the cloud storage server is connected to the device side through a network.

[0152] Among them, the sending of the upload status and configuration information is determined based on the upload status of the target task; the configuration information is obtained based on the upload status.

[0153] Specifically, the device side can pull the configuration from the cloud storage server at regular intervals or actively pull the configuration. It can perform multiple configuration update operations, record the failed configurations in the failure list, and upload the failure list of the current configuration to the cloud storage server to request a new configuration. The cloud storage server receives the upload status and configuration information of the target task sent by the device side, and determines the updated storage configuration according to the preset configuration selection rules. The device side can upload the corresponding scenarios, the failure configuration lists corresponding to each scenario, and the list of manufacturers (i.e., cloud storage service providers) to the cloud storage server, and the cloud storage server allocates a suitable updated storage configuration to the device side.

[0154] S420, obtain the updated storage configuration based on the upload status and configuration information.

[0155] Specifically, based on the upload status and configuration information of the target task uploaded by the device side, the cloud storage server obtains a new configuration from the list of candidate configurations to obtain the updated storage configuration.

[0156] In the specific implementation process, the cloud storage server determines the usage scenario corresponding to the target task, determines the list of candidate configurations corresponding to this usage scenario, and selects a new configuration information from the list of candidate configurations based on the upload status and the current configuration information to obtain the updated storage configuration; among them, each target task corresponds to a usage scenario.

[0157] In the specific implementation process, the device side can upload the corresponding scenarios, the failure configuration lists corresponding to each scenario, and the list of manufacturers (i.e., cloud storage service providers) to the cloud storage server, and the cloud storage server allocates a suitable updated storage configuration to the device side.

[0158] In the specific implementation process, the updated storage configuration can include updated bucket information. The cloud storage server configures multiple buckets for each scenario, determines the corresponding candidate buckets according to the usage scenario of the target task. For example, there are five buckets configured: A, B, C, D, E. Among them, these five buckets can be allocated in sequence. When E is allocated to the device side and still reports failure, then continue to allocate bucket A for cloud storage upload. This is because it takes a certain amount of time to switch buckets, and during this time, the previously failed A has become available; the device side monitors and saves the list of buckets where the task upload fails, for example: A, B. When the number of failures and the failure success rate are less than a certain threshold, the device side requests to switch buckets to the cloud storage server and uploads the list of failed buckets. If the cloud storage server still has unallocated buckets available, such as: C, D, E, it returns a new bucket, such as returning C. If there are no unallocated buckets available, that is, C, D, E have all been allocated and failed, it returns A.

[0159] S430. Send the updated storage configuration to the device side so that the device side uploads the next target task based on the updated storage configuration.

[0160] Specifically, send the updated storage configuration to the device side. The device side clears the original settings, uses the updated storage configuration to upload the next target task, and monitors the upload status of the next target task. If it is determined that the storage configuration needs to be changed, continue with the configuration update steps to update the storage configuration until the target task is successfully uploaded. If successful, continue to upload the task.

[0161] In the specific implementation process, data transmission between the device side and the cloud storage server can be achieved through the cloud service development kit SDK, or through the Hypertext Transfer Protocol HTTP or HTTPS link for data transmission, or through the Transmission Control Protocol TCP or User Datagram Protocol UDP connection for data transmission. The device side can request data by calling the interface API of the cloud storage server, and the cloud storage server returns data in the interface API response. Specifically, it can be flexibly selected according to actual needs.

[0162] In some possible implementation manners, obtaining the updated storage configuration based on the upload status and configuration information in the above steps includes:

[0163] Determine the updated storage bucket configuration from the storage bucket list based on the upload status and the storage bucket information.

[0164] Take the updated storage bucket configuration as the updated storage configuration.

[0165] Among them, the configuration information includes the storage bucket information corresponding to the target task. The storage bucket list corresponds to the target task one by one.

[0166] Specifically, based on the upload status of the target task and the corresponding storage bucket information, determine the new storage bucket configuration from the storage bucket list, and take the new updated storage bucket configuration as the updated storage configuration.

[0167] In the specific implementation process, the device side can pull the configuration from the cloud storage server regularly or actively, and can perform multiple configuration update operations. Record the failed storage buckets in the failed storage bucket list. The device side uploads the failed storage bucket list of the current configuration to the cloud storage server to request a new storage bucket configuration. The cloud storage server allocates a new storage bucket according to the preset configuration selection rules. The device side can upload the corresponding scenarios, the failed storage bucket lists corresponding to each scenario, and the manufacturer (i.e., the cloud storage service provider) list to the cloud storage server together. The cloud storage server allocates a suitable storage bucket to the device side.

[0168] For example, the cloud storage server configures multiple buckets for the current scenario, such as: A, B, C, D, E. The device side saves the list of failed buckets, such as: A, B. When the device side requests to switch buckets from the cloud storage server, it brings the list of failed buckets. If there are new buckets available on the cloud storage server, such as: C, D, E, it returns the new bucket C. If there are no new available buckets, it returns an existing bucket, such as: A.

[0169] In the specific implementation process, if any one of the configurations returned by the cloud storage server is equal to the content of the local cached bucket. For example, if there are A, B, C, D, E locally, and the cloud storage server returns A, the list of abnormal buckets saved on the device side, the current number of abnormal times, and other cached variables will be cleared.

[0170] In the above embodiments, by monitoring the task upload status, the current task upload status of the device side can be timely known. When the task upload status fails or other situations occur, the storage configuration can be timely updated to achieve timely response to configuration updates. When it is necessary to change the storage configuration, only the upload status and configuration information need to be uploaded to the cloud storage server to obtain the updated storage configuration that needs to be changed. By using the cloud storage server to obtain the updated configuration information, the speed of configuration update is accelerated. When it is found that the upload fails, the storage configuration is timely changed to make the task successfully uploaded, improving the stability of task upload.

[0171] Furthermore, the upload success rate of the target task can be determined based on the upload status of the target task, so as to determine whether the configuration needs to be changed. The target tasks are classified into single tasks and combined tasks according to types. Different success rate calculation methods are used for different types of tasks, which can more accurately determine the success rate. For multiple target tasks, the upload success rate is compared with the preset success rate threshold to determine the failed target tasks, and then combined with the number of consecutive failures to determine the situation where the configuration needs to be changed, accurately identifying the situation where the configuration needs to be changed and reducing system resource waste.

[0172] In addition, when uploading the upload status and configuration information to the cloud storage server, the scenario information of the target task can also be uploaded, so that the cloud storage server selects different updated storage configurations based on different scenarios. Uploading the current certificate information together can timely update the certificate information to ensure the availability of relevant configurations.

[0173] In one example, the task upload system of the present application, as Figure 5 shown, includes a device side and a cloud storage server, where:

[0174] The device side is used to monitor the upload status of the target task, determine whether the storage configuration needs to be changed; if the storage configuration needs to be changed, determine the configuration information corresponding to the target task; upload the upload status and configuration information to the cloud storage server;

[0175] The cloud storage server is used to obtain the updated storage configuration based on the upload status and configuration information and send it to the device side;

[0176] The device side is used to upload the next target task based on the updated storage configuration returned by the cloud storage server.

[0177] In the specific implementation process, the device side can be divided into a business development tool (i.e., the business SDK shown in the figure) and basic services. The device-side business SDK monitors the upload status of the target task, determines whether the storage configuration needs to be changed (i.e., whether to pull as shown in the figure), if the storage configuration needs to be changed (i.e., hitting the failure strategy shown in the figure), then determine the configuration information corresponding to the target task (i.e., the failed bucket shown in the figure), upload the upload status and configuration information to the cloud storage server to request new configuration information (i.e., request cloud storage configuration shown in the figure), the configuration information can include bucket information, the cloud storage server determines the updated bucket configuration from the bucket list based on the upload status and bucket information (i.e., remove the failed bucket and return one as shown in the figure), use the updated bucket configuration as the updated storage configuration, send it to the device side (i.e., return cloud storage configuration shown in the figure), the updated storage configuration can include the newly added success rate threshold and continuous number threshold (i.e., N and X shown in the figure), the device side saves the updated storage configuration returned by the cloud storage server, based on the updated storage configuration, upload the next target task (i.e., start cloud storage shown in the figure), continue to detect the upload status of the target task, when the target task ends and calls back, obtain the success rate and continuous failure times, based on the success rate and continuous failure times, determine whether the storage configuration needs to be changed, if so, continue to update the storage configuration, if not, execute the target task normally.

[0178] In the above task upload system, by monitoring the task upload status on the device side, the current task upload status of the device side can be timely known. When the task upload status fails or other situations occur, the storage configuration can be timely updated to achieve timely response to configuration updates. When the storage configuration needs to be changed, just upload the upload status and configuration information to the cloud storage server to obtain the updated storage configuration that needs to be changed. By using the cloud storage server to obtain the updated configuration information, the configuration update speed is accelerated, the storage configuration is timely changed, the task is successfully uploaded, and the stability of task upload is improved.

[0179] In an example, the task upload method of the present application, as Figure 6 shown, may include:

[0180] The device side monitors the upload status of the target task and determines the upload success rate of the target task;

[0181] Based on the upload success rate, the device side determines whether to change the storage configuration;

[0182] If there is no need to change the storage configuration, continue to monitor the upload status of the target task;

[0183] If it is necessary to change the storage configuration, determine the configuration information corresponding to the target task;

[0184] The device side uploads the upload status and configuration information to the cloud storage server;

[0185] The cloud storage server receives the upload status and configuration information of the target task sent by the device side, obtains the updated storage configuration based on the upload status and configuration information, and sends the updated storage configuration to the device side;

[0186] Based on the updated storage configuration returned by the cloud storage server, the device side uploads the next target task;

[0187] If the upload is successful, end this update and continue to monitor the upload status of the target task;

[0188] If the upload fails, continue with the configuration update steps until the task is uploaded successfully.

[0189] In the above task upload method, by monitoring the task upload status, the current task upload status of the device side can be known in a timely manner. When the task upload status fails or other situations occur, the storage configuration can be updated in a timely manner to achieve timely response to configuration updates. When it is necessary to change the storage configuration, only by uploading the upload status and configuration information to the cloud storage server can the updated storage configuration that needs to be changed be obtained. By using the cloud storage server to obtain the updated configuration information, the configuration update speed is accelerated, the storage configuration is changed in a timely manner, the task is successfully uploaded, and the stability of the task upload is improved.

[0190] Furthermore, the upload success rate of the target task can be determined based on the upload status of the target task, so as to determine whether to change the configuration. The target tasks are divided into single tasks and combined tasks according to the type. Different success rate calculation methods are used for different types of tasks, which can more accurately determine the success rate. For multiple target tasks, the upload success rate is compared with the preset success rate threshold to determine the failed target tasks, and then combined with the number of consecutive failures to determine the situation where the configuration needs to be changed, accurately identifying the situation where the configuration needs to be changed and reducing system resource waste.

[0191] In addition, when uploading the upload status and configuration information to the cloud storage server, the scenario information of the target task can also be uploaded, so that the cloud storage server selects different updated storage configurations based on different scenarios, and uploads the current certificate information together, which can update the certificate information in a timely manner and ensure the availability of relevant configurations.

[0192] An embodiment of the present application provides a task uploading device, which is applied to the device side, such as Figure 7 shown, the task uploading device 70 may include: an update module 701, an information determination module 702, an upload module 703, and a configuration module 704, where

[0193] The update module 701 is configured to monitor the upload status of the target task and determine whether the storage configuration needs to be changed;

[0194] The information determination module 702 is configured to determine the configuration information corresponding to the target task if the storage configuration needs to be changed;

[0195] The upload module 703 is configured to upload the upload status and configuration information to the cloud storage server;

[0196] The configuration module 704 is configured to upload the next target task based on the updated storage configuration returned by the cloud storage server.

[0197] As an alternative embodiment, in this device, the update module 701 is specifically configured to:

[0198] Based on the upload status of the target task, determine the upload success rate of the target task;

[0199] Based on the upload success rate, determine whether the storage configuration needs to be changed.

[0200] As an alternative embodiment, in this device, the update module 701 is specifically configured to:

[0201] Determine the task type of the target task; the task type includes a single task and a combined task;

[0202] If the task type is a single task, determine the upload success rate of the target task based on the number of successfully uploaded files in the target task;

[0203] If the task type is a combined task, determine the upload success rate of the target task based on the number of successfully uploaded tasks in the target task; the combined task includes multiple tasks.

[0204] As an alternative embodiment, in this device, the update module 701 is specifically configured to:

[0205] Based on the upload status of each target task, determine the upload success rate corresponding to each target task;

[0206] Compare each upload success rate with a preset success rate threshold to determine whether the target task fails;

[0207] Record the consecutive failure count of the target task. If the consecutive failure count meets the preset count threshold, determine that the storage configuration needs to be changed;

[0208] If the consecutive failure count does not meet the preset count threshold, continue to monitor the upload status of each target task.

[0209] As an alternative embodiment, in this device, the upload module 703 is specifically configured to:

[0210] Determine the scenario information corresponding to the target task;

[0211] Upload the scenario information, upload status, and configuration information to the cloud storage server;

[0212] Receive the updated storage configuration returned by the cloud storage server for the scenario information, upload status, and configuration information;

[0213] Based on the updated storage configuration, upload the next target task.

[0214] As an alternative embodiment, in this device, the upload module 703 is specifically configured to:

[0215] Determine the certificate information corresponding to the target task;

[0216] Upload the upload status, configuration information, and certificate information to the cloud storage server; the cloud storage server is used to obtain the updated storage configuration based on the upload status, configuration information, and certificate information.

[0217] An embodiment of this application provides a task upload device, which is applied to a cloud storage server. As Figure 8 shown, this task upload device 80 may include: a receiving module 801, a configuration acquisition module 802, and a sending module 803, where

[0218] The receiving module 801 is configured to receive the upload status and configuration information of the target task sent by the device side; the sending of the upload status and configuration information is determined based on the upload status of the target task; the configuration information is obtained based on the upload status;

[0219] The configuration acquisition module 802 obtains the updated storage configuration based on the upload status and configuration information;

[0220] The sending module 803 sends the updated storage configuration to the device side so that the device side uploads the next target task based on the updated storage configuration.

[0221] As an alternative embodiment, in this device, the configuration acquisition module 802 is specifically configured to:

[0222] Determine an updated bucket configuration from a list of buckets based on the upload status and bucket information; the list of buckets corresponds one-to-one with the target tasks;

[0223] Use the updated bucket configuration as the updated storage configuration.

[0224] The task upload device provided by this application can timely obtain the current task upload status of the device end by monitoring the task upload status. When the task upload status fails or other situations occur, the storage configuration can be updated in a timely manner to achieve a timely response to configuration updates. When the storage configuration needs to be changed, only the upload status and configuration information need to be uploaded to the cloud storage server to obtain the updated storage configuration that needs to be changed. By using the cloud storage server to obtain the updated configuration information, the configuration update speed is accelerated, the storage configuration is changed in a timely manner, the task is successfully uploaded, and the stability of task upload is improved.

[0225] Furthermore, the upload success rate of the target task can be determined based on the upload status of the target task, so as to determine whether the configuration needs to be changed. The target tasks are classified into single tasks and combined tasks according to the type. Different success rate calculation methods are used for different types of tasks, which can more accurately determine the success rate. For multiple target tasks, the upload success rate is compared with a preset success rate threshold to determine the failed target tasks, and then combined with the number of consecutive failures to determine the situation where the configuration needs to be changed, accurately identifying the situation where the configuration needs to be changed and reducing system resource waste.

[0226] In addition, when uploading the upload status and configuration information to the cloud storage server, the scenario information of the target task can also be uploaded, so that the cloud storage server selects different updated storage configurations based on different scenarios. Uploading the current certificate information together can update the certificate information in a timely manner to ensure the availability of relevant configurations.

[0227] The device of the embodiment of this application can execute the method provided by the embodiment of this application, and its implementation principle is similar and has corresponding technical effects. The actions performed by each module in the device of each embodiment of this application correspond to the steps in the method of each embodiment of this application. For the detailed function description of each module of the device, reference can be specifically made to the description in the corresponding method shown above, and details are not described herein again.

[0228] An embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory. The processor executes the above computer program to implement the steps of the method provided in any optional embodiment of the present application. Compared with the prior art, it can be achieved that by monitoring the task upload status, the current task upload status of the device side can be timely known. When the task upload status fails or other situations occur, the storage configuration can be timely updated to achieve timely response to configuration updates. When the storage configuration needs to be changed, only the upload status and configuration information need to be uploaded to the cloud storage server to obtain the updated storage configuration that needs to be changed. By using the cloud storage server to obtain the updated configuration information, the configuration update speed is accelerated, the storage configuration is timely changed, the task is successfully uploaded, and the stability of task upload is improved.

[0229] In an optional embodiment, an electronic device is provided, as Figure 9 shown. Figure 9 The electronic device 9000 shown includes: a processor 9001 and a memory 9003. Among them, the processor 9001 and the memory 9003 are connected, such as through a bus 9002. Optionally, the electronic device 9000 may further include a transceiver 9004, and the transceiver 9004 may be used for data interaction between this electronic device and other electronic devices, such as data sending and / or data receiving, etc. It should be noted that in practical applications, the transceiver 9004 is not limited to one, and the structure of the electronic device 9000 does not constitute a limitation to the embodiments of the present application.

[0230] The processor 9001 may be a CPU (Central Processing Unit, central processor), a general-purpose processor, a DSP (Digital Signal Processor, data signal processor), an ASIC (Application Specific Integrated Circuit, application-specific integrated circuit), an FPGA (Field Programmable Gate Array, field programmable gate array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in combination with the disclosure of the present application. The processor 9001 may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0231] The bus 9002 may include a path for transmitting information between the above components. The bus 9002 can be a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus 9002 can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 9 only a thick line is used in Figure 9 to represent it, but it does not mean that there is only one bus or one type of bus.

[0232] The memory 9003 can be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory), or other types of dynamic storage devices that can store information and instructions. It can also be an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium that can be used to carry or store computer programs and can be read by a computer, which is not limited here.

[0233] The memory 9003 is used to store the computer program for implementing the embodiments of the present application and is controlled by the processor 9001 to execute. The processor 9001 is used to execute the computer program stored in the memory 9003 to implement the steps shown in the foregoing method embodiments.

[0234] Among them, the electronic device includes but is not limited to: a device side and a cloud server capable of implementing the above task uploading method.

[0235] The embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps and corresponding contents of the foregoing method embodiments can be implemented.

[0236] It should be noted that the computer-readable storage medium described above in this application can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of a computer-readable storage medium can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0237] The embodiments of this application also provide a computer program product, including a computer program, which when executed by a processor can implement the steps and corresponding contents of the foregoing method embodiments.

[0238] The terms "first", "second", "third", "fourth", "1", "2", etc. (if any) in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily have to be used to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of this application described here can be implemented in an order other than the one illustrated or described in words.

[0239] The flowcharts and block diagrams in the drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in the flowchart or block diagram can represent a module, a program segment, or a part of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than marked in the drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0240] It should be understood that although the flowchart of the embodiments of the present application indicates each operation step by arrows, the execution order of these steps is not limited to the order indicated by the arrows. Unless otherwise clearly stated herein, in some implementation scenarios of the embodiments of the present application, the implementation steps in each flowchart may be executed in other orders according to requirements. In addition, some or all of the steps in each flowchart may include multiple sub-steps or multiple stages based on the actual implementation scenario. Some or all of these sub-steps or stages may be executed at the same time, and each sub-step or stage among these sub-steps or stages may also be executed at different times respectively. In the scenario where the execution times are different, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and the embodiments of the present application do not limit this.

[0241] The above are only optional implementation manners of some implementation scenarios of the present application. It should be noted that for those of ordinary skill in the art, without departing from the technical concept of the solution of the present application, adopting other similar implementation means based on the technical idea of the present application also belongs to the protection scope of the embodiments of the present application.

Claims

1. A task uploading method, characterized in that: Applied to a device end, the device end is connected to a cloud storage server via a network, including: Monitor the upload status of the target task to determine whether the storage configuration needs to be changed; If the storage configuration needs to be changed, the configuration information corresponding to the target task is determined; Uploading the upload status and the configuration information to the cloud storage server; Based on the updated storage configuration returned by the cloud storage server, the next target task is uploaded.

2. The task uploading method according to claim 1, characterized in that: The monitoring of the upload status of the target task and determining whether the storage configuration needs to be changed includes: Determining the upload success rate of the target task based on the upload status of the target task; Based on the upload success rate, it is determined whether storage configuration needs to be changed.

3. The task uploading method according to claim 2, characterized in that: The upload status includes upload success or upload failure; The determining the upload success rate of the target task based on the upload status of the target task includes: Determine the task type of the target task; the task type includes a single task and a combined task; If the task type is a single task, determining the upload success rate of the target task based on the number of files successfully uploaded in the target task; If the task type is a combined task, the upload success rate of the target task is determined based on the number of successfully uploaded tasks in the target task; the combined task includes multiple tasks.

4. The task uploading method according to claim 2, characterized in that: The target tasks include multiple; The determining the upload success rate of the target task based on the upload status of the target task includes: Determine the upload success rate corresponding to each target task based on the upload status of each target task; The determining whether the storage configuration needs to be changed based on the upload success rate includes: Compare each upload success rate with a preset success rate threshold to determine whether the target task has failed; Recording the number of consecutive failures of the target task, and if the number of consecutive failures meets a preset number threshold, determining that the storage configuration needs to be changed; If the number of consecutive failures does not meet the preset number threshold, the upload status of each target task continues to be monitored.

5. The task uploading method according to claim 1, characterized in that: The uploading the upload status and the configuration information to the cloud storage server includes: Determining scene information corresponding to the target task; Uploading the scene information, the upload status and the configuration information to the cloud storage server; The uploading of the next target task based on the updated storage configuration returned by the cloud storage server includes: Receiving an updated storage configuration returned by the cloud storage server in response to the scene information, the upload status, and the configuration information; Based on the updated storage configuration, the next target task is uploaded.

6. The task uploading method according to claim 1, characterized in that: The uploading the upload status and the configuration information to the cloud storage server includes: Determine the certificate information corresponding to the target task; The upload status, the configuration information and the certificate information are uploaded to the cloud storage server; the cloud storage server is used to obtain the updated storage configuration based on the upload status, the configuration information and the certificate information.

7. A task uploading method, characterized in that: Applied to a cloud storage server, the cloud storage server is connected to a device via a network, including: Receiving the upload status and configuration information of the target task sent by the device end; sending the upload status and the configuration information is determined based on the upload status of the target task; and the configuration information is obtained based on the upload status; Based on the upload status and the configuration information, obtaining an updated storage configuration; The updated storage configuration is sent to the device end, so that the device end uploads the next target task based on the updated storage configuration.

8. The task uploading method according to claim 7, characterized in that: The configuration information includes storage bucket information corresponding to the target task; The obtaining, based on the upload status and the configuration information, an updated storage configuration, comprises: Based on the upload status and the bucket information, determine to update the bucket configuration from the bucket list; the bucket list corresponds to the target task one by one; The updated storage bucket configuration is used as the updated storage configuration.

9. A task uploading system, characterized in that: It includes the device side and cloud storage server, where: The device is used to monitor the upload status of the target task and determine whether the storage configuration needs to be changed; if the storage configuration needs to be changed, determine the configuration information corresponding to the target task; and upload the upload status and the configuration information to the cloud storage server; The cloud storage server is used to obtain an updated storage configuration based on the upload status and the configuration information and send the updated storage configuration to the device end; The device end is used to upload the next target task based on the updated storage configuration returned by the cloud storage server.

10. A task uploading device, characterized in that: Applied to the device side, including: The update module is used to monitor the upload status of the target task and determine whether the storage configuration needs to be changed; An information determination module, used to determine the configuration information corresponding to the target task if the storage configuration needs to be changed; An uploading module, used for uploading the upload status and the configuration information to the cloud storage server; The configuration module is used to upload the next target task based on the updated storage configuration returned by the cloud storage server.

Images