Cloud Terminal Resource Recycling Method, Device, Equipment, Medium and Product

Abstract

The present disclosure provides a cloud terminal resource recycling method, apparatus, device, medium and product, relating to the field of computer technologies, and particularly to the fields of cloud computing and big data technologies. The specific implementation solution is as follows: search for an identification file in a target path from the initialized cloud terminal resources; in response to the failure to find the identification file, generate a data digest according to the data to be measured of the cloud terminal resources; in response to the data digest matching the expected metric digest, mark the status of the cloud terminal resources as releasable. The cloud terminal resource recycling method of the present disclosure can implement double detection of the initialization performance of the cloud terminal resources and the data to be measured, improve the detection efficiency and detection accuracy of the cloud terminal resources, ensure the recycling efficiency of the cloud terminal resources, and improve the reliability of the released cloud terminal resources.

Description

Technical Field

[0001] This disclosure relates to the field of computer technologies, and particularly to technologies such as cloud computing and big data. Specifically, it relates to a method, apparatus, device, medium, and product for recycling cloud terminal resources. Background Art

[0002] Cloud terminal resources such as cloud phones are recyclable and redistributable resources. After cloud terminal resources are allocated to end users for use and then recycled, before being redistributed to other end users, it is necessary to verify the initialization data of the cloud terminal resources and redistribute the cloud terminal resources that meet the expected requirements. Summary of the Invention

[0003] This disclosure provides a method, apparatus, device, medium, and product for recycling cloud terminal resources, which can effectively improve the accuracy of cloud terminal resource recycling verification.

[0004] According to a first aspect of this disclosure, there is provided a method for recycling cloud terminal resources, including:

[0005] Searching for an identification file in a target path from the initialized cloud terminal resources;

[0006] In response to not finding the identification file, generating a data digest based on the data to be tested of the cloud terminal resources;

[0007] In response to the data digest matching the expected metric digest, marking the status of the cloud terminal resources as releasable.

[0008] According to a second aspect of this disclosure, there is provided a device for recycling cloud terminal resources, including:

[0009] A searching module, configured to search for an identification file in a target path from the initialized cloud terminal resources;

[0010] A generating module, configured to generate a data digest based on the data to be tested of the cloud terminal resources in response to not finding the identification file;

[0011] A first marking module, configured to mark the status of the cloud terminal resources as releasable in response to the data digest matching the expected metric digest.

[0012] According to a third aspect of this disclosure, there is provided an electronic device, including:

[0013] At least one processor; and

[0014] A memory communicatively connected to the at least one processor; wherein,

[0015] The memory stores instructions that can be executed by at least one processor. The instructions are executed by at least one processor, enabling the at least one processor to execute the method provided in the first aspect.

[0016] According to a fourth aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing a computer to execute the method provided in the first aspect.

[0017] According to a fifth aspect of the present disclosure, there is provided a computer program product including a computer program which, when executed by a processor, implements the method provided in the first aspect.

[0018] It should be understood that the content described in this part is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. Description of the Drawings

[0019] The drawings are used to better understand the solution and do not constitute a limitation to the present disclosure. Among them:

[0020] Figure 1 is a schematic diagram of a first embodiment of the cloud terminal resource recovery method according to the present disclosure;

[0021] Figure 2 is a schematic diagram of a second embodiment of the cloud terminal resource recovery method according to the present disclosure;

[0022] Figure 3 is a schematic diagram of a third embodiment of the cloud terminal resource recovery method according to the present disclosure;

[0023] Figure 4 is a schematic diagram of an implementation scenario of the cloud terminal resource recovery method according to the present disclosure;

[0024] Figure 5 is a schematic diagram of an embodiment of the cloud terminal resource recovery device according to the present disclosure;

[0025] Figure 6 is a block diagram of an electronic device for implementing the cloud terminal resource recovery method of the embodiments of the present disclosure. Detailed Embodiments

[0026] The following describes exemplary embodiments of the present disclosure in conjunction with the drawings. Various details of the embodiments of the present disclosure are included to facilitate understanding and should be considered merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, descriptions of well-known functions and structures are omitted below for clarity and conciseness.

[0027] Cloud mobile phone resources can be allocated for end - users. After the end - user unbinds the cloud mobile phone resources, before re - allocating the unbound cloud mobile phone resources, data initialization and resource verification are required to ensure that the initialization data of the cloud mobile phone meets the expectations and satisfies the usage requirements of the end - user, and to ensure the usage performance after the re - allocation of the cloud mobile phone resources.

[0028] Currently, for the detection of cloud mobile phones after recycling and before re - allocation, it is usually to take screenshots of various indicators of the cloud mobile phone resources after being recycled or initialized, and complete the detection based on image recognition and comparison. However, this method can only detect the data indicators directly presented in the interface, with fewer and more fixed detected data types, which is easy to be maliciously bypassed, resulting in lower detection accuracy and success rate. It is difficult to ensure that the re - allocated cloud mobile phone resources fully meet the expectations, and often requires manual intervention for manual verification, with low efficiency.

[0029] The present disclosure provides a method for recycling cloud terminal resources. By pre - writing an identification file to verify the initialization effect of the cloud terminal resources, and by generating a data digest for the data to be tested for verification, various data to be tested in the cloud terminal resources are inspected, effectively ensuring the accuracy of the detection results and improving the efficiency and accuracy of the inspection for recycling cloud terminal resources.

[0030] Figure 1 Fig. 100 shows a flow of an embodiment of the method for recycling cloud terminal resources according to the present disclosure. Referring to Figure 1 as shown, the method for recycling cloud terminal resources includes the following steps:

[0031] Step S101, find the identification file in the target path from the initialized cloud terminal resources.

[0032] In the embodiment of the present disclosure, the execution entity of the method for recycling cloud terminal resources searches for the pre - written identification file from the initialized cloud terminal resources in its target path. The execution entity preliminarily determines the initialization effect of the cloud terminal resources and further determines the initialization performance of the cloud terminal resources by whether the identification file can be found.

[0033] Exemplarily, the above - mentioned execution entity may include a server for recycling management of cloud terminal resources, which can manage processes such as recycling, cleaning, reading, writing, initializing, detecting, and re - allocating cloud terminal resources.

[0034] Among them, the cloud terminal resources include cloud mobile phone resources, and may also include resources such as cloud storage (e.g., cloud disk), which are not limited herein.

[0035] In the embodiment of the present disclosure, the identification file searched by the above - mentioned execution entity is written before the initialization of the cloud terminal resources.

[0036] In some alternative implementations, the content of the identification file is not fixed. For example, it can be randomly generated content such as a random string, so as to ensure the uniqueness of the identification file, facilitate searching for and verifying the identification file, and improve the accuracy of resource detection.

[0037] Exemplarily, when the execution entity writes the identification file into the cloud terminal resource, it can back up the identification file for content verification after finding the identification file from the initialized cloud terminal resource.

[0038] Step S102, in response to not finding the identification file, generate a data digest based on the data to be tested of the cloud terminal resource.

[0039] In the embodiments of the present disclosure, the execution entity of the cloud terminal resource recycling method, such as a server, if it fails to find the pre-written identification file in the initialized cloud terminal resource, determines that the initialization of the cloud terminal resource is successful. At this time, it can test various data to be tested of the cloud terminal resource to determine whether the various data to be tested of the cloud terminal resource meet the expected index requirements.

[0040] Among them, the above-mentioned execution entity generates a corresponding data digest for the data to be tested and determines whether the data to be tested meets the expected requirements by verifying the data digest.

[0041] Exemplarily, the data to be tested of the cloud terminal resource may include at least one of the following: built-in application data, desktop icon data, custom wallpaper data, etc. Among them, the built-in application data may include an application list of installed applications, application data packets, etc.

[0042] In some alternative implementations, the above-mentioned execution entity can generate corresponding data digests for each item of the data to be tested of the cloud terminal resource and then verify them separately. For example, the execution entity can simultaneously generate corresponding data digests for the desktop icon data and the custom wallpaper data and then verify them simultaneously.

[0043] In some alternative implementations, the above-mentioned execution entity can generate corresponding data digests for each item of the data to be tested according to a preset verification order and verify them one by one. For example, the execution entity can first generate a corresponding data digest for the application list of installed applications of the cloud terminal resource and verify it, and then verify the application data packets of each installed application in the application list separately. At this time, the execution entity can simultaneously generate corresponding data digests for the application data packets of each installed application and verify them separately, or generate a summary to be verified after further summarizing the data digests of the application data packets and then verify the summary to be verified.

[0044] In some alternative implementation manners of the embodiments of the present disclosure, the data to be measured includes an application name, the data digest includes a name digest, and generating a data digest according to the data to be measured includes: determining an application list according to the installed applications in the cloud terminal resources; generating a name digest according to the application names in the application list.

[0045] In this implementation manner, the execution entity checks and verifies the installed applications in the cloud terminal resources. For example, it detects whether a preset one or several applications are installed in the initialized cloud terminal resources, or whether the application list of the installed applications in the cloud terminal resources is consistent with the expected installed application list, that is, whether the installed application names in the application list of the cloud terminal resources are consistent with the expected application names in the expected installed application list.

[0046] Among them, the execution entity obtains each installed application in the initialized cloud terminal resources and determines its application list accordingly. The application list includes the application names of each installed application in the cloud terminal resources. Exemplarily, the execution entity obtains the application names of each installed application in the cloud terminal resources in a preset order to obtain the corresponding application list. For example, the preset order can be any one of the installation order, the data packet size order of the installed applications, etc., which is not limited herein.

[0047] Then the execution entity generates a corresponding name digest according to the application names in the application list. Exemplarily, the execution entity calculates the MD5 value of the data composed of all the application names in the application list to obtain the name digest corresponding to all the installed applications in the cloud terminal resources.

[0048] In the embodiments of the present disclosure, the execution entity sorts out the installed applications in the cloud terminal resources to obtain an application list, and calculates the name digest according to the application names in the application list, which can effectively ensure that the generated name digest includes the application names of all the installed applications in the resource, ensure the integrity of the data to be measured and the accuracy of the generated data digest, avoid detection errors caused by malicious bypass of false data, and improve the detection accuracy.

[0049] In some alternative implementation manners of the embodiments of the present disclosure, generating a name digest according to the application names in the application list includes: sorting the application names in the application list to obtain a name sequence; generating a name digest according to the name sequence.

[0050] In this implementation manner, after determining the application list of the installed applications in the cloud terminal resources, the execution entity can directly calculate the MD5 value in the order of the application names in the application list, or re-sort the application names in the application list according to a preset sorting rule to obtain a name sequence, and then calculate the digest of the name sequence to obtain the name digest.

[0051] Among them, the preset sorting rules may include at least one sorting rule such as alphabetical order of names, stroke order of names, application installation order, application usage order, etc.

[0052] Exemplarily, the obtained name sequence may be in the form of an ordered array.

[0053] In this implementation manner, after the above-mentioned execution entity determines the application list corresponding to the cloud terminal resources, it first sorts the application names in the application list to obtain a name sequence, and then calculates the digest of the name sequence, which can effectively ensure that the application names before calculating the digest meet the preset order requirements and improve the accuracy of the name digest.

[0054] In some alternative implementation manners of the embodiments of the present disclosure, the data to be measured includes an application data packet, the data digest includes an application digest, and generating the data digest according to the data to be measured includes: generating a corresponding data packet digest according to the application data packets of the installed applications in the cloud terminal resources; generating an application digest according to the file path and the data packet digest of the application data packet.

[0055] In this implementation manner, the execution entity of the cloud terminal resource recycling method can detect each installed application data packet in the cloud terminal resources.

[0056] For each installed application, the execution entity obtains the corresponding application data packet from its corresponding file path, and then generates a corresponding data packet digest for each application data packet respectively.

[0057] Exemplarily, the execution entity can obtain the file path list corresponding to all installed applications in the application list according to the application list, then obtain the corresponding application data packets according to the file paths in the file path list, and calculate the corresponding data packet digest for each application data packet.

[0058] Then the execution entity generates an application digest according to the file path and the data packet digest of the data packets corresponding to each installed application.

[0059] In some alternative implementation manners, the execution entity can generate corresponding application digests for the file path and the data packet digest of the data packets corresponding to each installed application respectively.

[0060] In some alternative implementation manners, the execution entity can also summarize the file paths and the data packet digests of the data packets corresponding to all installed applications, and then generate a total data packet digest to implement the detection of the application data packets of all installed applications at the same time.

[0061] In this implementation, the execution entity generates a corresponding data packet digest by obtaining the application data packets of the installed applications, and then generates an application digest based on the file paths and data packet digests of the application data packets. By detecting the application digest, this solution can detect both the content and file paths of the application data packets, improving the detection efficiency of the application data packets and ensuring the accuracy and reliability of the detection results of the application data packets.

[0062] In some alternative implementations of the embodiments of the present disclosure, generating an application digest based on the file path and data packet digest of an application data packet includes: sorting the file path of the application data packet and its data packet digest to obtain a digest sequence; generating an application digest according to the digest sequence.

[0063] In this implementation, before generating the application digest, the execution entity first sorts the file paths of the application data packets and their data packet digests corresponding to each application in the installed application list to obtain a digest sequence, and then generates an application digest based on the digest sequence. It can be seen that the application digest generated in this solution covers the file paths and data packet digests of all installed applications, and can be used to detect the data packets of all installed applications simultaneously.

[0064] In some alternative implementations, the execution entity can obtain a file path sequence according to the order in the file path list of each installed application, and then store the data packet digests corresponding to each installed application into the file path sequence to obtain a digest sequence composed of the file path and the summary data packet, and then calculate the MD5 digest of the digest sequence as the application digest.

[0065] In some alternative implementations, the execution entity can also rearrange the file paths in the file path list of the installed applications in a certain order, and then associate and save each data packet digest with the rearranged file path to obtain a digest sequence, and then calculate the application digest based on this.

[0066] Exemplarily, the data packet digest in the digest sequence can be recorded adjacent to the file path of the corresponding application data packet, either before or after it.

[0067] Among them, the order of rearranging each file path can be any one of the following: file path order, application data packet name, application data packet size, application data packet writing order, etc.

[0068] In this implementation, the execution entity sorts the file path and data packet digest of the application data packet, and then generates an application digest according to the sorting result, which can effectively ensure the order of the file path of the application data packet covered by the application digest and its data packet digest, and thus ensure the orderliness of the content of the application digest, improving the detection efficiency and detection accuracy.

[0069] In some alternative implementation manners of the embodiments of the present disclosure, the data to be measured includes icon field values, the data summary includes icon summaries, and generating a data summary according to the data to be measured includes: obtaining the icon field values of the installed applications in the cloud terminal resources; generating icon summaries according to the icon field values.

[0070] In this implementation manner, the execution subject of the cloud terminal resource recycling method can detect the icons and components of the installed applications in the cloud terminal resources. The detection method is not only to perform image judgment on the shape of the icon, but to improve the detection accuracy by detecting its icon field values.

[0071] Wherein, the above execution subject obtains the icon field value corresponding to its icon through the file path of the installed application, and then performs MD5 digest calculation on the specific icon field value to obtain the icon summary.

[0072] Exemplarily, the icon field values corresponding to the icons of the installed applications include at least one of the field values such as the position value, coordinate value, name, and icon size of the icon.

[0073] This implementation manner obtains the icon field values of the installed applications and calculates the icon field values to obtain icon summaries, effectively ensuring the accuracy of the icon summaries, thereby improving the detection accuracy of the icon field values, and realizing the detection of the icon field values by detecting the icon summaries, thereby improving the accuracy and reliability of the icon detection.

[0074] In some alternative implementation manners of the embodiments of the present disclosure, obtaining the icon field values of the installed applications in the cloud terminal resources includes: in response to the existence of a visualization acquisition tool in the cloud terminal resources, using the visualization acquisition tool to obtain the icon field values from the file paths of the installed applications; in response to the non-existence of a visualization acquisition tool in the resources, executing a connection script to connect to the file paths of the installed applications and obtain the icon field values.

[0075] In this implementation manner, considering the compatibility of the cloud terminal resources, when the execution subject obtains the icon field values of the installed references in the cloud terminal resources, it obtains the icon field values in different ways according to whether the cloud terminal resources are compatible with the visualization acquisition tool.

[0076] In the scenario where the cloud terminal resources are compatible with the visualization acquisition tool, that is, there is a visualization acquisition tool in the cloud terminal resources, such as the sqlite3 tool, the execution subject can directly obtain the corresponding icon field values from the file paths of the installed applications through the visualization acquisition tool.

[0077] In the case where the cloud terminal resources are not compatible with the visualization acquisition tool, the execution entity connects to the file path of the installed application by executing an external script (such as a Python script), then queries and obtains the corresponding icon field value from the file path, and after obtaining the icon field value, closes the access to the file path.

[0078] In this implementation manner, the execution entity obtains the icon field value of the installed application in different ways according to the compatibility of the cloud terminal resources, effectively ensuring the accuracy of the obtained icon field value, thereby ensuring the accuracy of the icon summary, avoiding the inaccuracy brought by only the detection method of image recognition, and improving the reliability of the detection result.

[0079] In some optional implementation manners of the embodiments of the present disclosure, the data to be measured includes custom data, the data summary includes a custom summary, and generating a data summary according to the data to be measured includes: selecting and starting to download custom data in the networked data of the cloud terminal resources; in response to successful download within a preset duration, generating a custom summary according to the downloaded custom data.

[0080] In this implementation manner, the execution entity of the cloud terminal resource recycling method can detect the configurable custom data in the cloud terminal resources. Among them, the custom data may include at least one of the following: custom wallpaper data, custom sound effect data, custom desktop style, etc.

[0081] In this implementation manner, the custom data detected by the execution entity is not the data configured in the cloud terminal resources, but the data that can be selected and configured by the user in its networked database. Therefore, for the detection of custom data, it is necessary to select and download the corresponding custom data from the networked database of the cloud terminal resources and then perform the detection.

[0082] After the execution entity determines that the data to be measured includes custom data, it randomly selects custom data of the type to be detected (such as custom wallpaper data or custom desktop style data) from the networked data of the cloud terminal resources, and then starts to download the custom data. If the custom data is successfully downloaded within the preset duration, a corresponding data summary, that is, a custom summary, is generated for the downloaded custom data.

[0083] Among them, the preset duration is the data download period configured by the cloud terminal resources during the recycling detection process.

[0084] In some optional implementation manners, the custom summary can be calculated and generated only based on the downloaded custom data.

[0085] In some optional implementation manners, the execution entity can comprehensively calculate and generate a corresponding custom summary according to the downloaded custom data in combination with the storage path of the downloaded custom data.

[0086] In this implementation, the execution entity downloads the custom data in the networked database and generates a corresponding custom summary based on the successfully downloaded custom data, so as to detect the custom data by detecting the custom summary, improving the detection accuracy and reliability of the custom data.

[0087] In some optional implementations of the embodiments of the present disclosure, the cloud terminal resource recovery method further includes: in response to a download failure within a preset duration, determining that the data summary generation fails, and marking the status of the cloud terminal resource as to be recycled.

[0088] In this implementation, if the execution entity fails to successfully download the custom data within the data download cycle of the cloud terminal resource, it determines that there is a problem with the configuration or download of the custom data, thereby determining that the custom data detection fails, and marking the status of the cloud terminal resource as to be recycled.

[0089] In some optional implementations, the "to be recycled" status marked for the cloud terminal resource can be a to-be-detected (to-be-redetected) status, an automatic detection failure status, or can also be understood as a status pending manual intervention.

[0090] In this implementation, after the execution entity determines that the custom data download of the cloud terminal resource fails, it determines that the cloud terminal resource detection fails, and marks the status of the cloud terminal resource as to be recycled, reminding the administrator to pay attention or intervene, effectively preventing the cloud terminal resources that fail the detection from being accidentally released, thereby ensuring the reliability of the released cloud terminal resources and improving the detection efficiency of the cloud terminal resources.

[0091] Step S103, in response to the data summary matching the expected metric summary, mark the status of the cloud terminal resource as releasable.

[0092] In the embodiments of the present disclosure, the execution entity of the cloud terminal resource recovery method, such as a server, after generating a data summary for the data to be tested of the cloud terminal resource, compares the generated data summary with the expected metric summary to determine whether the data to be tested of the cloud terminal resource meets the requirements.

[0093] Among them, the expected metric summary corresponds one-to-one with the generated data summary, including the metric summaries corresponding to the respective expected data metrics that the cloud terminal resource needs to meet for release.

[0094] Exemplarily, there are expected metrics for each item of data in at least one standard cloud terminal resource in the execution entity. For example, the built-in application data metrics, desktop icon data metrics, custom wallpaper data metrics, etc. of at least one standard type of cloud phone resource; and again, the built-in application data metrics, icon metrics, etc. of at least one standard type of cloud disk resource.

[0095] In some alternative implementations, when the above-mentioned execution entity detects each item of data to be tested in the cloud terminal resources, it obtains the corresponding expected data metrics, and generates corresponding expected metric summaries for each of the expected data metrics, and uses them to detect the data summary.

[0096] In some alternative implementations, the execution entity can also pre-generate corresponding expected metric summaries for the expected data metrics of each expected standard and store them. Thus, when detecting the cloud terminal resources, the corresponding metric summaries can be directly obtained and used to detect the data summary.

[0097] In the embodiments of the present disclosure, the execution entity compares the generated data summary with the corresponding metric summary. If the generated data summary conforms to the corresponding metric summary, it is determined that the cloud terminal resources meet the expected requirements and can be released according to the expected requirements. The execution entity marks the status of the cloud terminal resources as releasable.

[0098] Among them, the generated data metrics conforming to the expected metric summary may mean that the content of the data metrics is the same as that of the metric summary, or the content of the data metrics includes all the content of the metric summary and also includes other content.

[0099] In some alternative implementations, when it is determined that the generated data summary conforms to the expected metric summary, the execution entity can determine that the data to be tested of the cloud terminal resources meets the metric requirements, and further determine that the cloud terminal resources can be released according to the metric requirements. In this case, the execution entity can either directly release the cloud terminal resources or mark the status of the cloud terminal resources as releasable to determine whether to release the cloud terminal resources according to the release request.

[0100] Exemplarily, the execution entity can also perform an associated marking on the metric summary compared with the data summary during the process of marking the status of the cloud terminal resources as releasable. For example, while marking the status of the cloud terminal resources as releasable, the number or other identification mark of the metric summary is added.

[0101] According to the cloud terminal resource recovery method provided by the embodiments of the present disclosure, by searching for the identification file in the initialized cloud terminal resources, the initialization process and initialization performance of the cloud terminal resources are detected; by generating a data digest for the data to be tested of the cloud terminal resources and comparing it with the metric digest, it is realized to detect whether the data to be tested of the cloud terminal resources meets the expected metrics, improving the detection accuracy of the data metrics and the scalability of the detected data. The cloud terminal resource recovery method of the present disclosure can realize the dual detection of the initialization performance of the cloud terminal resources and the data to be tested, improve the detection efficiency and detection accuracy of the cloud terminal resources, ensure the recovery efficiency of the cloud terminal resources, and improve the reliability of the released cloud terminal resources. Among them, through the detection of the initialization performance of the cloud terminal resources, the leakage of user information of the cloud terminal resources caused by initialization failure can be effectively avoided.

[0102] It should be noted that in the technical solution of the embodiments of the present disclosure, the user personal information involved is obtained, stored, applied, etc. under the condition of obtaining the user's authorization, all of which comply with the provisions of relevant laws and regulations and do not violate public order and good customs.

[0103] Figure 2 The flowchart 200 of the second embodiment of the cloud terminal resource recovery method according to the present disclosure is shown. Referring to Figure 2 as shown, the cloud terminal resource recovery method includes the following steps:

[0104] Step S201, search for the identification file in the target path from the initialized cloud terminal resources.

[0105] In the embodiments of the present disclosure, the execution subject of the cloud terminal resource recovery method, such as a server, after the cloud terminal resources are initialized, searches for the pre-written identification file in its target path. The execution subject preliminarily determines the initialization effect of the cloud terminal resources by whether the identification file can be found, and further determines the initialization performance of the cloud terminal resources.

[0106] In the embodiments of the present disclosure, the specific implementation process of step S201 has been described in detail in step S101 of the embodiment shown in Figure 1 and will not be elaborated here.

[0107] Step S202, in response to finding the identification file, check whether the current content of the identification file is consistent with the initial content of the identification file.

[0108] In the embodiments of the present disclosure, the execution subject of the cloud terminal resource recovery method, such as a server, if the identification file is found in the target path of the initialized cloud terminal resources, it is necessary to compare the content of the identification file with the pre-written initial content to determine whether they are consistent.

[0109] In this solution, the cloud terminal resource recovery method can be automatically triggered by the server or manually triggered by at least one administrator. Moreover, multiple detection processes can be triggered simultaneously for the same cloud terminal resource. Therefore, during the process of searching for the identification file, it is possible to find the identification files written by other detection processes. Thus, it is necessary to perform a consistency check on the current content of the identification file and the initial content written in the current detection process to determine whether the existence of the identification file is caused by initialization failure or overlap of detection processes.

[0110] Step S203: In response to the current content of the identification file being consistent with the initial content, re-initialize the cloud terminal resources.

[0111] In the embodiments of the present disclosure, when the execution entity of the cloud terminal resource recovery method, such as the server, verifies the current content of the identification file, if the current content is consistent with the initial content, it is determined that the initialization of the cloud terminal resource fails this time. Since the initialization failure is not necessarily caused by the performance of the cloud terminal resource itself and may be caused by other non-performance reasons, in this case, the initialization process can be self-healed. Therefore, the cloud terminal resource can be re-initialized.

[0112] In the embodiments of the present disclosure, the execution entity determines whether the initialization process of the cloud terminal resource fails by performing a consistency check on the current content and the initial content of the identification file. When it is determined that the current content is consistent with the initial content, the cloud terminal resource is re-initialized, avoiding manual intervention in unnecessary situations, improving the detection efficiency, and ensuring the detection accuracy at the same time.

[0113] Step S204: In response to the number of initializations of the cloud terminal resource reaching the preset number, mark the status of the cloud terminal resource as to be recycled.

[0114] In the embodiments of the present disclosure, the execution entity of the cloud terminal resource recovery method, such as the server, counts the number of initializations of the cloud terminal resource. When the number of initializations reaches the preset number, the status of the cloud terminal resource is marked as to be recycled, and the automatic detection is stopped, waiting for manual intervention.

[0115] This solution can effectively avoid an endless automatic detection loop while avoiding the low detection efficiency caused by premature manual intervention, and timely wait for manual intervention to ensure the detection efficiency.

[0116] Step S205: In response to the current content of the identification file being inconsistent with the initial content, mark the status of the cloud terminal resource as under verification.

[0117] In an embodiment of the present disclosure, the execution subject of the cloud terminal resource recovery method, such as a server, can determine that the initialization of the cloud terminal resource is successful when it determines that the current content of the identification file is inconsistent with the written initial content. However, there is an overlap in the detection process, so this detection can be terminated, and the status of the cloud terminal resource can be marked as being verified.

[0118] In an embodiment of the present disclosure, the execution subject determines that there is an overlap in the new detection process generated after the start of this detection process for the cloud terminal resource through the inconsistency between the current content and the initial content of the identification file, thereby terminating the previous detection process and marking the status of the cloud terminal resource as being detected, avoiding waste of computing power caused by unnecessary detection and saving resources.

[0119] The cloud terminal resource recovery method provided by the embodiments of the present disclosure, after finding the identification file in the cloud terminal resource after initialization, determines the reason for the existence of the identification file through the consistency check of the current content and the initial content of the identification file, thereby determining whether the initialization performance of the cloud terminal resource is intact, improving the detection accuracy and reliability of the initialization performance of the cloud terminal resource; and, in the case of initialization failure, re-initializing to avoid low detection efficiency caused by premature manual intervention; when the number of initializations reaches the preset number, stop the detection and remind manual intervention to avoid unnecessary waste of computing power. In addition, in the case of determining that there is an overlap in the detection process of the cloud terminal resource, stop the previous detection process to further avoid unnecessary waste of computing power and save resources.

[0120] Figure 3 Flow 300 of the third embodiment of the cloud terminal resource recovery method according to the present disclosure is shown. Referring to Figure 3 as shown, the cloud terminal resource recovery method includes the following steps:

[0121] Step S301, in response to receiving a cloud terminal resource recovery request, generate an identification file and record the initial content of the identification file.

[0122] In an embodiment of the present disclosure, the execution subject of the cloud terminal resource recovery method, such as a server, generates an identification file and records the initial content of the identification file when receiving a cloud terminal resource recovery request.

[0123] In some optional implementation manners, the cloud terminal resource recovery request received by the execution subject may be an automatically triggered recovery request. For example, after detecting that the binding relationship of the cloud terminal resource is released, the execution subject automatically triggers a recovery request for the cloud terminal resource.

[0124] In some alternative implementation manners, the cloud terminal resource recycling request received by the execution entity may also be manually triggered. For example, it may be triggered when an administrator manually detects the discovered cloud terminal resources, or it may be a recycling request triggered when actively manually detecting the cloud terminal resources after the binding relationship is released (which may include but is not limited to the first detection after unbinding, or the first detection after manual repair), or it may also be a recycling request triggered when manually intervening in the cloud terminal resources that have failed in automatic detection.

[0125] In some alternative implementation manners, the content of the identification file is not fixed. For example, it may be randomly generated content such as a random string, so as to ensure the uniqueness of the identification file, facilitate finding and verifying the identification file and its content, ensure the reliability of detecting the initialization performance of the cloud terminal resources, and improve the accuracy of resource detection.

[0126] Exemplarily, after generating the identification file in the cloud terminal resources, the execution entity records the initial content of the identification file, so as to perform content verification after finding the identification file from the initialized cloud terminal resources.

[0127] Step S302: After writing the identification file to the target path of the cloud terminal resources, initialize the cloud terminal resources.

[0128] In the embodiments of the present disclosure, the execution entity of the cloud terminal resource recycling method, such as a server, writes the identification file generated in step S301 to the target path of the cloud terminal resources, and after the writing is completed, initializes the cloud terminal resources.

[0129] The above-mentioned execution entity writes the generated identification file to the target path of the cloud terminal resources, and then initializes the cloud terminal resources, so as to subsequently find and verify the identification file, thereby verifying the initialization performance of the cloud terminal resources.

[0130] Step S303: Find the identification file in the target path from the initialized cloud terminal resources.

[0131] In the embodiments of the present disclosure, the execution entity of the cloud terminal resource recycling method, such as a server, after the cloud terminal resources are initialized, searches for the pre-written identification file in its target path. The execution entity preliminarily determines the initialization effect of the cloud terminal resources by whether the identification file can be found, and further determines the initialization performance of the cloud terminal resources.

[0132] In the embodiments of the present disclosure, the specific implementation process of step S303 has been described in detail in Figure 1 step S101 in the shown embodiments, and will not be elaborated here.

[0133] Step S304, in response to the failure to find the identification file, generate a data digest based on the data to be tested of the cloud terminal resource.

[0134] In the embodiments of the present disclosure, when the execution subject of the cloud terminal resource recovery method, such as a server, fails to find the identification file from the initialized cloud terminal resource, it can generate corresponding data digests for the data to be tested of the cloud terminal resource, so as to further detect the data to be tested.

[0135] In the embodiments of the present disclosure, the specific implementation process of step S304 has been Figure 1 introduced in detail in step S102 of the embodiments shown, and will not be elaborated here.

[0136] Step S305, in response to the data digest matching the expected index digest, mark the status of the cloud terminal resource as releasable.

[0137] In the embodiments of the present disclosure, the specific implementation process of step S305 has been Figure 1 introduced in detail in step S103 of the embodiments shown, and will not be elaborated here.

[0138] According to the cloud terminal resource recovery method provided by the embodiments of the present disclosure, after receiving a cloud terminal resource recovery request, an identification file is randomly generated, and the initial content of the identification file is recorded, and then the identification file is written to the target path of the cloud terminal resource. After the writing is completed, the cloud terminal resource is initialized, and the identification file is searched from the initialized cloud terminal resource. If not found, it is determined that the initialization of the cloud terminal resource is successful, and then the data to be tested of the cloud terminal resource can be detected. This solution randomly generates an identification file and writes it to the target path of the cloud terminal resource before initialization, so as to verify the initialization performance of the cloud terminal resource, effectively avoid the leakage of user information caused by the failure of cloud terminal resource initialization, and improve the use security of cloud terminal resources.

[0139] It should be noted that in the technical solutions of the embodiments of the present disclosure, the acquisition, storage, application, etc. of the user's personal information involved are all carried out under the premise of obtaining the user's authorization, which all comply with the relevant laws and regulations and do not violate public order and good customs.

[0140] Figure 4 Fig. 400 shows an implementation scenario of the cloud terminal resource recovery method according to the present disclosure. Refer to Figure 4As shown, the execution subject of the cloud terminal resource recycling method is server 401. In this scenario, the cloud terminal resource to be recycled is cloud phone 402 to be recycled, and the corresponding standard cloud phone 403 is used. Server 401 uses the data index of standard cloud phone 403 as the recycling and release standard for detecting the recycling of cloud phone 402 to be recycled. Exemplarily, the implementation process of the cloud terminal resource recycling method is as follows:

[0141] Step S4101, the server 401 sends a data indicator acquisition request to the standard cloud phone 403, and the data indicator acquisition request includes at least one expected indicator of the data to be tested;

[0142] Step S4102, receiving the indicator summary sent by the standard cloud phone 403 based on the data indicator acquisition request and saving it.

[0143] Step S4103, receiving a notification of releasing the binding relationship of the cloud phone 402 to be recycled.

[0144] Any cloud phone 402 to be recycled can release the binding relationship and send a binding relationship release notification to the server 401. In response to receiving the binding relationship release notification of the cloud phone to be recycled, the server 401 can automatically trigger the recycling process for the cloud phone 402 to be recycled according to the notification or according to the operation of the administrator.

[0145] In step S4104, the server 401 randomly generates an identification file and writes it into the target path of the cloud phone 402 to be recycled.

[0146] Step S4105, receiving a return result indicating that the file has been written successfully.

[0147] Step S4106, initializing the cloud phone 402 to be recycled.

[0148] Step S4107, receiving notification information that the initialization of the cloud phone 402 to be recycled is completed.

[0149] Step S4108, searching for the written identification file from the target path of the cloud phone 402 to be recycled.

[0150] Step S4109, determining the search result of the identification file.

[0151] Exemplarily, in response to the search result that the identification file is found under the target path of the cloud phone 402 to be recycled, the server 401 can further verify whether the current content of the identification file is consistent with the initial content. If not, the status of the cloud phone 402 to be recycled can be marked as being under detection; if consistent, the cloud phone 402 to be recycled is reinitialized.

[0152] Step S4110: In response to the finding that the identification file is not found, the server 401 sends a request for obtaining test data to the cloud phone 402 to be recycled.

[0153] Step S4111: Receive the data summaries of various pieces of test data returned by the cloud phone 402 to be recycled.

[0154] Step S4112: Compare whether the received data summaries match the metric summaries obtained and stored from the standard cloud phone 403.

[0155] Step S4113: Mark the status of the cloud phone 402 to be recycled according to the comparison result.

[0156] Exemplarily, in response to the received data summaries matching the metric summaries, mark the status of the cloud phone 402 to be recycled as releasable; in response to the received data summaries not matching the metric summaries, mark the status of the cloud phone 402 to be recycled as to-be-recycled, or it can also be marked as to-be-detected or to-be-manually intervened.

[0157] Step S4114: The server 401 can also select and release the cloud phones whose status is marked as releasable according to the received cloud phone release requests.

[0158] As an implementation of the cloud terminal resource recycling method shown in the above figures, Figure 5 An embodiment of a cloud terminal resource recycling device according to the present disclosure is shown. The cloud terminal resource recycling device 500 corresponds to Figure 1 the method embodiment shown, and this device can be applied to various electronic devices.

[0159] Refer to Figure 5 As shown, the cloud terminal resource recycling device 500 provided in the embodiment of the present disclosure includes: a search module 501, a generation module 502, and a first marking module 503. Among them, the search module 501 is configured to search for an identification file in the target path from the initialized cloud terminal resources; the generation module 502 is configured to, in response to not finding the identification file, generate a data summary according to the test data of the cloud terminal resources; the first marking module 503 is configured to, in response to the data summary matching the expected metric summary, mark the status of the cloud terminal resources as releasable.

[0160] In the cloud terminal resource recycling device 500 of the embodiment of the present disclosure, the specific processing of the search module 501, the generation module 502, and the first marking module 503 and the technical effects brought by them can be respectively referred to Figure 1 the relevant descriptions of steps S101 - S103 in the corresponding embodiments, and will not be elaborated here.

[0161] In some alternative implementation manners of the embodiments of the present disclosure, the cloud terminal resource recovery device further includes a verification module and a reset module. Among them, the verification module is configured to verify whether the current content of the identification file is consistent with the initial content of the identification file in response to finding the identification file; the reset module is configured to re-initialize the cloud terminal resources in response to the current content of the identification file being consistent with the initial content.

[0162] In the cloud terminal resource recovery device of the embodiments of the present disclosure, for the specific processing of the verification module and the reset module and the technical effects brought by them, reference can be made to Figure 2 the relevant descriptions of steps S202 - S203 in the corresponding embodiments, which will not be elaborated here.

[0163] In some alternative implementation manners of the embodiments of the present disclosure, the cloud terminal resource recovery device further includes a second marking module, which is configured to mark the status of the cloud terminal resources as to be recycled in response to the number of initializations of the cloud terminal resources reaching a preset number.

[0164] In the cloud terminal resource recovery device of the embodiments of the present disclosure, for the specific processing of the second marking module and the technical effects brought by it, reference can be made to Figure 2 the relevant descriptions of step S204 in the corresponding embodiments, which will not be elaborated here.

[0165] In some alternative implementation manners of the embodiments of the present disclosure, the cloud terminal resource recovery device further includes a third marking module, which is configured to mark the status of the cloud terminal resources as being verified in response to the current content of the identification file being inconsistent with the initial content.

[0166] In the cloud terminal resource recovery device of the embodiments of the present disclosure, for the specific processing of the second marking module and the technical effects brought by it, reference can be made to Figure 2 the relevant descriptions of step S205 in the corresponding embodiments, which will not be elaborated here.

[0167] In some alternative implementation manners of the embodiments of the present disclosure, the data to be measured includes an application name, the data summary includes a name summary, and the generation module is configured to: determine an application list according to the installed applications in the cloud terminal resources; generate a name summary according to the application names in the application list.

[0168] In some alternative implementation manners of the embodiments of the present disclosure, generating a name summary according to the application names in the application list includes: sorting the application names in the application list to obtain a name sequence; generating a name summary according to the name sequence.

[0169] In some alternative implementation manners of the embodiments of the present disclosure, the data to be measured includes an application data packet, the data summary includes an application summary, and the generation module is configured to: generate a corresponding data packet summary according to the application data packets of the installed applications in the cloud terminal resources; generate an application summary according to the file path of the application data packet and the data packet summary.

[0170] In some alternative implementation manners of the embodiments of the present disclosure, generating an application summary according to the file path of the application data packet and the data packet summary includes: sorting the file path of the application data packet and its data packet summary to obtain a summary sequence; generating an application summary according to the summary sequence.

[0171] In some alternative implementation manners of the embodiments of the present disclosure, the data to be measured includes an icon field value, the data summary includes an icon summary, and the generation module is configured to: obtain the icon field values of the installed applications in the cloud terminal resources; generate an icon summary according to the icon field values.

[0172] In some alternative implementation manners of the embodiments of the present disclosure, obtaining the icon field values of the installed applications in the cloud terminal resources includes: in response to the existence of a visualization acquisition tool in the cloud terminal resources, using the visualization acquisition tool to obtain the icon field values from the file paths of the installed applications; in response to the non-existence of a visualization acquisition tool in the resources, executing a connection script to connect to the file paths of the installed applications and obtain the icon field values.

[0173] In some alternative implementation manners of the embodiments of the present disclosure, the data to be measured includes custom data, the data summary includes a custom summary, and the generation module is configured to: select and start downloading the custom data in the networked data of the cloud terminal resources; in response to successful download within a preset time period, generate a custom summary according to the downloaded custom data.

[0174] In some alternative implementation manners of the embodiments of the present disclosure, the cloud terminal resource recycling device further includes a fourth marking module, which is configured to, in response to download failure within a preset time period, determine that the data summary generation fails and mark the status of the cloud terminal resources as to be recycled.

[0175] In some alternative implementation manners of the embodiments of the present disclosure, the recycling device of the terminal resources further includes a recording module and an initialization module, wherein the recording module is configured to, in response to receiving a cloud terminal resource recycling request, generate an identification file and record the initial content of the identification file; the initialization module is configured to initialize the cloud terminal resources after writing the identification file to the target path of the cloud terminal resources.

[0176] In the cloud terminal resource recycling device of the embodiments of the present disclosure, the specific processing of the writing module and the initialization module and the technical effects brought by them can be respectively referred to Figure 3The relevant descriptions of steps S301 - S302 in the corresponding embodiments will not be elaborated herein.

[0177] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0178] Figure 6 FIG. shows a schematic block diagram of an exemplary electronic device 600 that can be used to implement the embodiments of the present disclosure. The electronic device is intended to represent various forms of digital computers, such as, for example, a laptop computer, a desktop computer, a workbench, a personal digital assistant, a server, a blade server, a mainframe computer, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as, for example, a personal digital processor, a cellular phone, a smart phone, a wearable device, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely exemplary and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0179] As Figure 6 shown, the device 600 includes a computing unit 601 that can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 602 or a computer program loaded from a storage unit 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 can also be stored. The computing unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0180] A plurality of components in the device 600 are connected to the I / O interface 605, including: an input unit 606, such as a keyboard, a mouse, etc.; an output unit 607, such as various types of displays, speakers, etc.; a storage unit 608, such as a magnetic disk, an optical disk, etc.; and a communication unit 609, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0181] The computing unit 601 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 601 executes the various methods and processes described above, such as the cloud terminal resource recycling method. For example, in some embodiments, the cloud terminal resource recycling method can be implemented as a computer software program tangibly embodied in a machine-readable medium, such as the storage unit 608. In some embodiments, part or all of the computer program can be loaded and / or installed onto the device 600 via the ROM 602 and / or the communication unit 609. When the computer program is loaded into the RAM 603 and executed by the computing unit 601, one or more steps of the cloud terminal resource recycling method described above can be executed. Alternatively, in other embodiments, the computing unit 601 can be configured to execute the cloud terminal resource recycling method by any other suitable means (e.g., by means of firmware).

[0182] Various embodiments of the systems and techniques described above in this document can be implemented in digital electronic circuitry, integrated circuit systems, field-programmable gate arrays (FPGA), application-specific integrated circuits (ASIC), application-specific standard products (ASSP), system-on-a-chip systems (SOC), complex programmable logic devices (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include: implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special or general-purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit the data and instructions to the storage system, the at least one input device, and the at least one output device.

[0183] The program code for implementing the methods of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the program codes are executed by the processor or controller, the functions / operations specified in the flowchart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as an independent software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0184] In the context of this disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0185] To provide for interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can also be used to provide for interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic, speech, or tactile input).

[0186] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer having a graphical user interface or a web browser through which the user can interact with an implementation of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0187] A computer system can include a client and a server. The client and the server are generally remote from each other and typically interact through a communication network. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, a server of a distributed system, or a server incorporating a blockchain.

[0188] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and no limitations are imposed herein.

[0189] The above specific embodiments do not constitute a limitation on the protection scope of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub - combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure shall be included within the protection scope of this disclosure.

Claims

1. A cloud terminal resource recovery method, comprising: In response to receiving a cloud terminal resource recovery request, generating an identification file and recording initial content of the identification file; After writing the identification file into the target path of the cloud terminal resource, initializing the cloud terminal resource; Searching for the identification file under the target path from the initialized cloud terminal resources; In response to not finding the identification file, generating a data summary according to the data to be tested of the cloud terminal resource; In response to the data summary being consistent with the expected indicator summary, marking the state of the cloud terminal resource as releasable.

2. The method according to claim 1, further comprising: In response to finding the identification file, verifying whether the current content of the identification file is consistent with the initial content of the identification file; In response to the current content being consistent with the initial content, the cloud terminal resources are reinitialized.

3. The method according to claim 2, further comprising: In response to the number of initializations of the cloud terminal resource reaching a preset number, the state of the cloud terminal resource is marked as to be recycled.

4. The method according to claim 2, further comprising: In response to the current content being inconsistent with the initial content, marking the state of the cloud terminal resource as being in verification.

5. The method according to any one of claims 1 to 4, wherein: The data to be tested includes an application name, the data summary includes a name summary, and The step of generating a data summary according to the data to be tested includes: Determine an application list according to installed applications in the cloud terminal resources; Generate a name summary according to the application name in the application list.

6. The method according to claim 5, wherein: The generating a name summary according to the application name in the application list includes: Sort the application names in the application list to obtain a name sequence; A name digest is generated according to the name sequence.

7. The method according to any one of claims 1 to 4, wherein: The data to be tested includes an application data packet, the data summary includes an application summary, and The step of generating a data summary according to the data to be tested includes: Generate a corresponding data packet digest based on the application data packets of the installed applications in the cloud terminal resources; An application summary is generated according to the file path of the application data packet and the data packet summary.

8. The method according to claim 7, wherein: The step of generating an application summary according to the file path of the application data packet and the data packet summary includes: Sorting the file paths of the application data packets and the data packet summaries thereof to obtain a summary sequence; An application summary is generated according to the summary sequence.

9. The method according to any one of claims 1 to 4, wherein: The data to be tested includes an icon field value, the data summary includes an icon summary, and The step of generating a data summary according to the data to be tested includes: Obtaining the icon field value of the installed application in the cloud terminal resource; An icon summary is generated according to the icon field value.

10. The method according to claim 9, wherein: The obtaining of the icon field value of the installed application in the cloud terminal resource includes: In response to the presence of a visualization acquisition tool in the cloud terminal resource, using the visualization acquisition tool to acquire the icon field value from the file path of the installed application; In response to the absence of a visualization acquisition tool in the resource, a connection script is executed to connect to the file path of the installed application and obtain the icon field value.

11. The method according to any one of claims 1 to 4, wherein: The data to be tested includes custom data, the data summary includes a custom summary, and The step of generating a data summary according to the data to be tested includes: Select and start downloading custom data from the networked data of the cloud terminal resource; In response to successful downloading within the preset time period, a custom summary is generated according to the downloaded custom data.

12. The method according to claim 11, further comprising: In response to a download failure within a preset time period, it is determined that the data summary generation fails, and the state of the cloud terminal resource is marked as to be recycled.

13. A cloud terminal resource recovery device, comprising: a recording module configured to generate an identification file and record initial content of the identification file in response to receiving a cloud terminal resource recovery request; an initialization module, configured to initialize the cloud terminal resources after writing the identification file into the target path of the cloud terminal resources; A search module, configured to search for the identification file under the target path from the initialized cloud terminal resources; A generating module, configured to generate a data summary according to the data to be tested of the cloud terminal resource in response to failure to find the identification file; The first marking module is configured to mark the state of the cloud terminal resource as releasable in response to the data summary being consistent with the expected indicator summary.

14. The apparatus according to claim 13, further comprising: a verification module, configured to verify whether the current content of the identification file is consistent with the initial content of the identification file in response to finding the identification file; The reset module is configured to reinitialize the cloud terminal resources in response to the current content being consistent with the initial content.

15. The apparatus according to claim 14, further comprising: The second marking module is configured to mark the state of the cloud terminal resource as to be recycled in response to the number of initialization times of the cloud terminal resource reaching a preset number.

16. The apparatus according to claim 14, further comprising: The third marking module is configured to mark the state of the cloud terminal resource as being in the process of being verified in response to the inconsistency between the current content and the initial content.

17. The device according to any one of claims 13 to 16, wherein: The data to be tested includes an application name, the data summary includes a name summary, and The generation module is configured to: Determine an application list according to installed applications in the cloud terminal resources; Generate a name summary according to the application name in the application list.

18. The device according to claim 17, wherein: The generating a name summary according to the application name in the application list includes: Sort the application names in the application list to obtain a name sequence; A name digest is generated according to the name sequence.

19. The device according to any one of claims 13 to 16, wherein: The data to be tested includes an application data packet, the data summary includes an application summary, and The generation module is configured to: Generate a corresponding data packet digest based on the application data packets of the installed applications in the cloud terminal resources; An application summary is generated according to the file path of the application data packet and the data packet summary.

20. The device according to claim 19, wherein The step of generating an application summary according to the file path of the application data packet and the data packet summary includes: Sorting the file paths of the application data packets and the data packet summaries thereof to obtain a summary sequence; An application summary is generated according to the summary sequence.

21. The device according to any one of claims 13 to 16, wherein: The data to be tested includes an icon field value, the data summary includes an icon summary, and The generation module is configured to: Obtaining the icon field value of the installed application in the cloud terminal resource; An icon summary is generated according to the icon field value.

22. The device according to claim 21, wherein The obtaining of the icon field value of the installed application in the cloud terminal resource includes: In response to the presence of a visualization acquisition tool in the cloud terminal resource, using the visualization acquisition tool to acquire the icon field value from the file path of the installed application; In response to the absence of a visualization acquisition tool in the resource, a connection script is executed to connect to the file path of the installed application and obtain the icon field value.

23. The device according to any one of claims 13 to 16, wherein: The data to be tested includes custom data, the data summary includes a custom summary, and The generation module is configured to: Select and start downloading custom data from the networked data of the cloud terminal resource; In response to successful downloading within the preset time period, a custom summary is generated according to the downloaded custom data.

24. The apparatus according to claim 23, further comprising: The fourth marking module is configured to determine that the data summary generation fails in response to a download failure within a preset time period, and mark the state of the cloud terminal resource as to be recycled.

25. An electronic device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 12.

26. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-12.

27. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 12.

Images