Terminal data secure transmission method and system for cloud computer

Abstract

The invention relates to the technical field of data analysis, in particular to a terminal data secure transmission method and system for a cloud computer. The method comprises the steps of updating a relation graph between files according to operation conditions of the files in a current time period every target duration, and obtaining a current relation graph; the current time period is a time period corresponding to the recently elapsed target duration; respectively taking each file as a target file, and determining the current uploading bias of the target file according to the operation frequency of the target file in the current time period, the association condition performance of the target file in the current relation graph and the association condition change of the associated file of the target file; the associated file is a file associated with the target file in the relation graph in the current time period; and determining whether to upload the target file to the cloud computer or not according to the current uploading weight. Whether each file is uploaded to the cloud computer or not is accurately determined, and accurate and timely file uploading is realized.

Description

Technical Field

[0001] The present invention relates to the field of data analysis technology, and in particular to a method and system for securely transmitting terminal data for cloud computers. Background Art

[0002] Promptly uploading terminal data to cloud computing can significantly improve data security. First, cloud computing data centers employ specialized security measures, such as encrypted transmission and storage, to mitigate the risk of data leaks. Second, they prevent data loss due to device loss or damage, thus providing a backup solution. Furthermore, cloud computing's access controls and security audits effectively prevent unauthorized access, and cloud service providers regularly update security policies to provide ongoing assurance of data security.

[0003] Traditional methods typically use a threshold based on the cumulative number of times files are processed together to determine their associations. This allows for the selection of uploaded data from different time periods and uploads these selected files to cloud computers for storage. However, this method lacks accurate understanding of file associations, making it difficult to upload files accurately and promptly. This can lead to repeated uploads and downloads within a short period of time, potentially causing file loss or theft. Summary of the Invention

[0004] In order to solve the technical problem of difficulty in accurately and timely uploading files, the present invention aims to provide a terminal data secure transmission method and system for cloud computing. The technical solutions adopted are as follows: The present invention provides a method for securely transmitting terminal data for a cloud computer, the method comprising: Every time the target duration passes, the relationship graph between the files is updated according to the operation status of the files in the current time period to obtain a current relationship graph; the current time period is the time period corresponding to the most recently passed target duration; Each of the files is taken as a target file, and the current upload weight of the target file is determined based on the frequency of operations on the target file in the current time period, the association of the target file in the current relationship graph, and changes in the association of the target file's associated files; the associated files are files associated with the target file in the relationship graph in the current time period; Determine whether to upload the target file to the cloud computer based on the current upload preference.

[0005] According to the terminal data secure transmission method for cloud computers provided by the present invention, the method further includes: Obtaining log information of access logs within the current time period; The operation status of each file in the current time period is determined according to the log information.

[0006] According to the terminal data security transmission method for cloud computers provided by the present invention, the updating of the relationship map between the files according to the operation status of the files in the current time period to obtain the current relationship map includes: Determining, based on the operation status of each file in the current time period, the number of occurrences of a file combination that meets the target condition in the current time period and the operation time interval between two files in the file combination during each occurrence; Determining, based on the number of occurrences and the operation time interval, the association strength corresponding to each of the file combinations in the current time period; According to the association strength, the relationship map between the files is updated to obtain a current relationship map.

[0007] According to the terminal data secure transmission method for a cloud computer provided by the present invention, determining the current upload weight of the target file based on the frequency of operations on the target file in the current time period, the association of the target file in the current relationship graph, and the change in the association of the target file's associated files includes: Determining a current storage bias of the target file based on a frequency of operations on the target file within the current time period and a correlation performance of the target file in the current relationship graph; The current upload weight of the target file is determined according to the current storage weight of the target file and the change in the association status of the files associated with the target file.

[0008] According to the terminal data secure transmission method for a cloud computer provided by the present invention, the operation frequency includes the number of operations; and determining the current storage weight of the target file based on the operation frequency of the target file in the current time period and the association of the target file in the current relationship graph includes: Determining the number of associated files of the target file and the maximum value of the association strength between the target file and the associated files according to the current relationship graph; The current storage weight of the target file is determined according to the number of operations, the number of the associated files, and the maximum value of the association strength between the target file and the associated files.

[0009] According to the terminal data secure transmission method for a cloud computer provided by the present invention, determining the current upload weight of the target file based on the current storage weight of the target file and the change in the association status of the associated files of the target file includes: For each of the associated files, determining a difference between the storage weight of the associated file in the current time period and the storage weight of the associated file in the previous time period; The current upload weight of the target file is determined according to the difference values corresponding to the associated files and the current storage weight of the target file.

[0010] According to the terminal data secure transmission method for a cloud computer provided by the present invention, after determining whether to upload the target file to the cloud computer based on the current upload weight, the method further includes: The target duration is updated according to the current remaining terminal storage space size and the size of files uploaded after the current time period.

[0011] According to the terminal data secure transmission method for a cloud computer provided by the present invention, after determining whether to upload the target file to the cloud computer based on the current upload weight, the method further includes: The metadata and upload time of the files to be uploaded are stored in the database; The metadata and the upload time points of the files uploaded at different time points are obtained from the database and are visually displayed on a terminal.

[0012] According to the terminal data secure transmission method for a cloud computer provided by the present invention, determining whether to upload the target file to the cloud computer based on the current upload bias includes: Comparing the current upload bias with an upload bias threshold; If the current upload weight is greater than or equal to the upload weight threshold, uploading the target file to the cloud computer and deleting the target file from the terminal; If the current upload weight is less than the upload weight threshold, the target file is retained.

[0013] The present invention provides a terminal data security transmission system for cloud computers, the system comprising a memory and a processor; the memory is used to store executable program code; the processor is used to call and run the executable program code from the memory to implement the terminal data security transmission method for cloud computers provided by the present invention.

[0014] The present invention has the following beneficial effects: By dynamically establishing the current relationship map between each file in each current time period, we have a clearer understanding of the relationship between files. Then, based on the frequency of operations on individual files in the current time period, the performance of the association in the current relationship map, and the changes in the association of associated files, we can determine the upload weight of individual files. This can accurately determine whether each file has been uploaded to the cloud computer, achieve accurate and timely file upload, and reduce the risk of loss or theft of terminal storage files. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions and advantages of the embodiments of the present invention or the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art descriptions. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0016] Figure 1 A flowchart of a method for securely transmitting terminal data for a cloud computer provided by one embodiment of the present invention; Figure 2 A schematic diagram of the overall process of a method for securely transmitting terminal data for a cloud computer provided by one embodiment of the present invention; Figure 3 A schematic diagram of the structure of a terminal data security transmission system for cloud computing provided by one embodiment of the present invention. DETAILED DESCRIPTION

[0017] To further illustrate the technical means and effects of the present invention to achieve the intended purpose, the following, in conjunction with the accompanying drawings and preferred embodiments, describes in detail a method and system for securely transmitting terminal data for cloud computing according to the present invention, including its specific implementation, structure, features, and effects. In the following description, different references to "one embodiment" or "another embodiment" do not necessarily refer to the same embodiment. Furthermore, specific features, structures, or characteristics of one or more embodiments may be combined in any suitable manner.

[0018] Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.

[0019] The following describes in detail a method and system for securely transmitting terminal data on a cloud computer provided by the present invention in conjunction with the accompanying drawings.

[0020] See also Figure 1 , which shows a flow chart of a method for securely transmitting terminal data for a cloud computer provided by an embodiment of the present invention, comprising the following steps: Step 102 : Every time the target duration passes, the relationship graph between the files is updated according to the operation status of the files in the current time period to obtain the current relationship graph; the current time period is the time period corresponding to the most recently passed target duration.

[0021] In one embodiment, the target duration may be a fixed duration, for example, the target duration may be set to 3 days.

[0022] In another embodiment, the target duration can be adjusted dynamically. For example, the target duration can be adjusted dynamically based on the current storage status of the terminal and the current status of uploaded files.

[0023] In one embodiment, the terminal may determine the association strength corresponding to each file combination that meets the target condition in the current time period based on the operation status of each file in the current time period, determine the maximum association strength corresponding to each file combination based on the association strength corresponding to each file combination in the current time period and the association strength of each file combination in previous time periods, and update the relationship map between each file based on the maximum association strength corresponding to each file combination to obtain the current relationship map. A file combination includes two files.

[0024] In one embodiment, if the maximum association strength corresponding to a file combination is greater than an association strength threshold, the two files included in the file combination are connected in the relationship graph. The association strength threshold can be set according to actual needs, for example, it can be set to 0.7.

[0025] In one embodiment, the maximum association strength value corresponding to each file combination may be stored accordingly.

[0026] In step 104, each file is taken as a target file, and the current upload weight of the target file is determined based on the frequency of operations on the target file in the current time period, the association of the target file in the current relationship graph, and the change in the association of the target file's associated files; the associated file is a file that is associated with the target file in the relationship graph in the current time period.

[0027] Among them, upload bias is used to measure the tendency to upload the target file to the cloud computer.

[0028] In one embodiment, the associated files of the target file may be determined based on the current relationship graph, for example, files connected to the target file in the current relationship graph may be used as the associated files of the target file.

[0029] In one embodiment, the change in the association status of the associated files is determined based on the current relationship graph and the previous relationship graph.

[0030] In one embodiment, the previous relationship map may be the last relationship map. In other embodiments, the previous relationship map may be multiple previous relationship maps.

[0031] Step 106: Determine whether to upload the target file to the cloud computer based on the current upload preference.

[0032] In one embodiment, the current upload weight can be compared with the upload weight threshold, and whether to upload the target file to the cloud computer is determined based on the comparison result. The upload weight threshold can be set according to actual needs, for example, the upload weight threshold can be set to 0.8.

[0033] In one embodiment, if it is determined that the target file needs to be uploaded to the cloud computer, the target file is uploaded to the cloud computer and the target file is deleted from the terminal. The target file can be downloaded from the cloud computer when it is needed again. If it is determined that the target file does not need to be uploaded to the cloud computer, the target file is retained.

[0034] In one embodiment, the terminal can display the metadata and upload time of each uploaded file. In one embodiment, the display can be performed in the form of a table.

[0035] In the above-mentioned terminal data security transmission method for cloud computers, by dynamically establishing the current relationship map between each file in each current time period, a clearer understanding of the relationship between files is obtained. Then, based on the frequency of operations on a single file in the current time period, the performance of the association in the current relationship map, and the changes in the association of associated files, the upload weight of a single file is determined. It can accurately determine whether each file is uploaded to the cloud computer, thereby achieving accurate and timely file upload and reducing the risk of loss or theft of terminal stored files.

[0036] In one embodiment, the method further includes: obtaining log information of access logs in the current time period; and determining the operation status of each file in the current time period according to the log information.

[0037] The access log is a log used to record operations on files.

[0038] In one embodiment, the log information may include information such as the file name, path, file size, and modification time point.

[0039] In one embodiment, during file operations, the terminal can use an auditing tool to record the file operation type and timestamp. A process monitoring tool can then associate the process identifier (PID) with the user identifier (UID) to record the specific process and user performing the operation. Keyboard events can then be captured and a timestamped access log generated. For example, the auditing tool can be Linux's auditd. File operation types can include read, write, move, and copy. The process monitoring tool can be, for example, ps or lsof. The logkeys tool can be used to capture keyboard events and generate a timestamped access log.

[0040] In one embodiment, file metadata can be obtained through system commands or file monitoring tools. Access logs are named according to the file metadata and stored locally or in a shared directory for unified management. For example, system commands can be commands such as stat. Access logs can be named "server name_log identifier_character set_YYYYMMDD.log." In one embodiment, file metadata can include information such as the file name, path, file size, and modification time.

[0041] In one embodiment, the log type and date range can be selected through a management interface, and the access logs can be packaged into a compressed file and stored in a designated database. For example, the management interface can be Symantec DLP.

[0042] In one embodiment, the collection path may be configured using regular expressions or wildcards according to the storage path and naming rules of the access logs.

[0043] In one embodiment, SQL (Structured Query Language) query statements may be used to obtain files and log information in a database that have access logs within a current time period from a collection path.

[0044] In one embodiment, a log collection tool can be used to automatically match directories and subdirectories and continuously monitor changes in access logs that meet the rules. For example, the log collection tool can be LogListener.

[0045] In the above embodiment, log information of the access log in the current time period is obtained, and the operation status of each file in the current time period can be determined efficiently and accurately based on the log information.

[0046] In one embodiment, based on the operation status of each file in the current time period, the relationship map between each file is updated to obtain the current relationship map, including: determining the number of occurrences of file combinations that meet the target conditions in the current time period and the operation time interval between two files in the file combination each time the combination occurs based on the operation status of each file in the current time period; determining the association strength corresponding to each file combination in the current time period based on the number of occurrences and the operation time interval; and updating the relationship map between each file based on the association strength to obtain the current relationship map.

[0047] In one embodiment, the target condition may be that the operation time interval between two files in the file combination is less than a preset time interval, wherein the preset time interval can be set according to actual needs, for example, the preset time interval can be set to 10 minutes.

[0048] In one embodiment, the association strength corresponding to a file combination is positively correlated with the number of occurrences of the file combination within the current time period. The association strength corresponding to a file combination is negatively correlated with the time interval between the two files each time the file combination appears within the current time period. That is, the greater the number of occurrences, the greater the association strength. The shorter the time interval, the greater the association strength.

[0049] In one embodiment, the maximum value of the number of occurrences of all file combinations in the current time period can be determined to obtain the maximum number of occurrences, and then, for each file combination, the first proportion of the number of occurrences of the file combination in the current time period in the maximum number of occurrences can be determined, and the first sum of the operation time intervals each time the file combination appears in the current time period can be determined. Based on the ratio between the first proportion and the first sum, the association strength of the file combination in the current time period is determined.

[0050] In one embodiment, the association strength of the file combination j in the current time period m can be determined according to the following formula: : in, Indicates the association strength of file combination j in the current time period m. Indicates the number of occurrences of file combination j in the current time period m. Indicates the maximum number of occurrences of all file combination j in the current time period m (i.e., the maximum number of occurrences). Indicates the proportion of the occurrence count of file combination j in the current time period m to the maximum occurrence count. Indicates the operation time interval when file combination j appears for the i-th time in the current time period m. It represents the sum of the operation time intervals each time the file combination j appears in the current time period m.

[0051] In one embodiment, for each file combination, the maximum association strength of the file combination can be determined based on the association strength of the file combination in the current time period and the association strength of the file combination in previous time periods. Then, the relationship map can be updated based on the maximum association strength corresponding to each file combination to obtain the current relationship map.

[0052] In one embodiment, the maximum association strength can be normalized to obtain a normalized association strength, and the relationship graph can be updated based on the normalized association strength to obtain the current relationship graph. Specifically, if the normalized association strength of a file combination is greater than an association strength threshold, the two files included in the file combination are connected in the relationship graph. The normalization process can utilize a sigmoid function.

[0053] In the above embodiment, based on the operation status of each file in the current time period, the number of occurrences of the file combination that meets the target conditions in the current time period and the operation time interval between the two files in the file combination each time are determined. Based on the number of occurrences and the operation time interval, the corresponding association strength of each file combination in the current time period is determined. Based on the association strength, the relationship map between each file is updated to obtain the current relationship map, which realizes the dynamic establishment of the current relationship map of the files in each current time period, thereby having a clearer understanding of the relationship between the files, and then being able to accurately determine whether each file is currently uploaded to the cloud computer based on the current relationship map.

[0054] In one embodiment, the current upload bias of the target file is determined based on the frequency of operations on the target file in the current time period, the association performance of the target file in the current relationship graph, and the change in the association of the target file's associated files, including: determining the current storage bias of the target file based on the frequency of operations on the target file in the current time period and the association performance of the target file in the current relationship graph; determining the current upload bias of the target file based on the current storage bias of the target file and the change in the association of the target file's associated files.

[0055] Among them, storage bias is used to measure the tendency to keep the target file on the terminal for storage.

[0056] In one embodiment, the frequency of operations may be measured by the number of operations.

[0057] In one embodiment, the association status of the target file in the current relationship graph may include the number of associated files of the target file and the maximum association strength between the target file and the associated files.

[0058] In the above embodiment, the current storage bias of the target file is determined based on the frequency of operations on the target file in the current time period and the association performance of the target file in the current relationship graph. Then, based on the current storage bias of the target file and the changes in the association status of the target file's associated files, the current upload bias of the target file can be accurately determined.

[0059] In one embodiment, the operation frequency includes the number of operations; determining the current storage bias of the target file based on the operation frequency of the target file in the current time period and the association performance of the target file in the current relationship graph includes: determining the number of associated files of the target file and the maximum association strength between the target file and the associated files based on the current relationship graph; determining the current storage bias of the target file based on the number of operations, the number of associated files, and the maximum association strength between the target file and the associated files.

[0060] In one embodiment, the terminal may use SQL query statements to count the number of operations on each file in the database within the current time period.

[0061] In one embodiment, the terminal may traverse the current relationship graph, determine the number of associated files of the target file, and obtain the maximum association strength between the target file and the associated files.

[0062] It is understandable that the greater the relationship between the projects executed by the user in a certain period of time and the target file, the more times the target file is operated within this period of time, and the more frequently the target file is used in the future. Therefore, the target file should be stored in the terminal for easy access. The more projects the target file involves, the greater the maximum value of the association strength between the target file and other multiple files in the relationship map, and the longer the target file should be retained and stored in the terminal. Therefore, the more associated files the target file has, the greater the maximum value of the association strength between the target file and the associated files, indicating that the relationship between the target file and other files is closer, and therefore the target file should be stored in the terminal. Therefore, in one embodiment, the current storage bias of the target file is positively correlated with the number of operations on the target file in the current period of time. The current storage bias of the target file is positively correlated with the number of associated files of the target file. The current storage bias of the target file is positively correlated with the maximum value of the association strength.

[0063] In one embodiment, the terminal can determine a second proportion of the number of operations on the target file in the current time period to the maximum number of operations on each file in the current time period, and determine a second sum of the maximum values of the association strength between the target file and each associated file, and then determine the current storage bias of the target file based on the product of the second proportion, the second sum, and the number of associated files.

[0064] In one embodiment, the current storage bias of the target file can be determined according to the following formula: in, Indicates that the storage of the kth file in the mth time period is biased. Indicates the number of operations on the k-th file in the m-th time period. Indicates the maximum number of operations on all files in the mth time period. Indicates file k and associated files The maximum strength of the correlation between . Represents file k and each associated file The sum of the maximum correlation strengths between . Indicates the number of associated files of file k.

[0065] In the above embodiment, the more times the target file is operated in the current time period, the more frequently the target file may be used in the next time. Therefore, the target file should be stored in the terminal for easy access. The more associated files the target file has, the greater the maximum value of the association strength between the target file and the associated files, indicating that the relationship between the target file and the other files is closer. Therefore, the target file should be stored in the terminal. Therefore, according to the current relationship map, the number of associated files of the target file and the maximum value of the association strength between the target file and the associated files are determined. According to the number of operations, the number of associated files, and the maximum value of the association strength between the target file and the associated files, the current storage bias of the target file can be accurately determined.

[0066] In one embodiment, the current upload weight of the target file is determined based on the current storage weight of the target file and the change in the association status of the associated files of the target file, including: determining, for each associated file, the difference between the storage weight of the associated file in the current time period and the previous time period; and determining the current upload weight of the target file based on the difference corresponding to each associated file and the current storage weight of the target file.

[0067] In one embodiment, the previous time period may be a previous time period. In other embodiments, the previous time period may also be a plurality of time periods before the current time period.

[0068] It is understandable that the consideration of whether a single file should be uploaded to the cloud computer for storage is not only related to the operation of the single file itself and its performance in the relationship map, but also to the associated files of the file. When the project related to the target file may have ended, the storage bias of the multiple associated files associated with the target file will be significantly reduced, and the storage bias of the target file itself will also be reduced. The target file will not be used in other projects temporarily and can be uploaded to the cloud computer for storage. Therefore, in one embodiment, the current upload bias of the target file is negatively correlated with the current storage bias of the target file. The current upload bias of the target file is positively correlated with the difference corresponding to the associated files of the target file.

[0069] In one embodiment, the sum of the difference values corresponding to the associated files of the target file may be determined, and then the current upload bias of the target file may be determined based on the ratio between the sum of the difference values and the current storage bias of the target file.

[0070] In one embodiment, the current upload weight of the target file can be determined according to the following formula: in, Indicates that the upload of file k in the mth time period is heavy. Indicates the storage bias of file k in the mth time period. Indicates the storage weight of the associated file p of file k in the m-1th time period. Indicates the storage bias of the associated file p of file k in the mth time period. Indicates the difference in storage weight between the current time period and the previous time period for the associated file p. It represents the sum of the differences corresponding to each associated file p of file k. Indicates the number of associated files p of file k.

[0071] In the above embodiment, the smaller the storage weight of the multiple associated files associated with the target file, and the smaller the storage weight of the target file itself, the more likely it is that the project associated with the target file has ended, and the target file will not be used in other projects for the time being. Therefore, the target file should be uploaded to the cloud computer for storage. Therefore, for each associated file, the difference between the storage weight of the associated file in the current time period and the previous time period is determined. Based on the difference corresponding to each associated file and the current storage weight of the target file, the current upload weight of the target file can be accurately determined.

[0072] In one embodiment, after determining whether to upload the target file to the cloud computer based on the current upload bias, the method further includes: updating the target duration based on the current remaining terminal storage space size and the file size uploaded after the current time period.

[0073] In one embodiment, the df command may be used to obtain the current remaining terminal storage space size.

[0074] In one embodiment, an adjustment weight can be determined based on the current remaining terminal storage space and the size of files uploaded after the current time period. The current target duration is adjusted based on the adjustment weight, resulting in an updated target duration that serves as the target duration for the next use. The adjustment weight is used to control the degree to which the target duration is reduced. That is, a larger adjustment weight indicates a greater degree of reduction in the target duration.

[0075] It is understandable that if the window size of the target duration T is set too large, some pending file data may not be uploaded to the cloud computer in a timely manner. If it is set too short, it may cause some files that are still in use to be mistransmitted. To avoid the above situation, the judgment should be made based on the current amount of uploaded files. When the amount of uploaded files after the current time period is large, in order to upload the files in time and save the terminal's storage space, the window size of the target duration should be shortened. At the same time, the storage space situation in the current terminal should also be considered when uploading. When the terminal's available storage space is small, the window size of the target duration should be appropriately shortened.

[0076] In one embodiment, the adjustment weight is negatively correlated with the size of the currently remaining terminal storage space. That is, the smaller the currently remaining terminal storage space, the greater the adjustment weight, and the greater the degree of reduction in the target duration.

[0077] In one embodiment, the adjustment weight is positively correlated with the size of files uploaded after the current time period. That is, the larger the size of files uploaded after the current time period, the larger the adjustment weight, and the greater the degree of reduction in the target duration.

[0078] In one embodiment, the target duration may be updated according to the following formula: in, Indicates the target duration analyzed after the mth time period, that is, the updated target duration after the mth time period. Indicates the target duration analyzed after the m-1th time period, that is, the target duration before the update after the mth time period. Indicates adjustment weight. Indicates that normalization is performed using the hyperbolic tangent function. Indicates the size of file s uploaded after the mth time period. Indicates the total number of files uploaded after the mth time period. Indicates the total size of files uploaded after the mth time period. Indicates the remaining terminal storage space after the mth time period.

[0079] In the above embodiment, the target duration is updated according to the current remaining terminal storage space size and the file size uploaded after the current time period, and the window size for analyzing the upload bias of files can be dynamically adjusted, thereby effectively avoiding the impact of excessive storage on the terminal operation speed and the problem of large amounts of data loss due to terminal damage, while avoiding the problem of data packet loss and file leakage caused by congestion when transferring large amounts of files.

[0080] In one embodiment, after determining whether to upload the target file to the cloud computer based on the current upload bias, the method also includes: storing the metadata and upload time points of the files determined to be uploaded in a database; obtaining the metadata and upload time points of the files uploaded at different time points from the database, and visually displaying them on the terminal.

[0081] In one embodiment, the file number, file size and upload time of files uploaded at different time points can be obtained from the database, and the file number, file size and upload time point can be visually displayed on the terminal.

[0082] In one embodiment, as shown in the following table, it can be visualized in the form of a table: In the above embodiment, the metadata and upload time points of the files to be uploaded are stored in a database; the metadata and upload time points of the files uploaded at different time points are obtained from the database and visually displayed on the terminal, so that a brief description of the uploaded files can be clearly displayed on the terminal.

[0083] In one embodiment, based on the current upload bias, determining whether to upload the target file to the cloud computer includes: comparing the current upload bias with an upload bias threshold; if the current upload bias is greater than or equal to the upload bias threshold, uploading the target file to the cloud computer and deleting the target file from the terminal; if the current upload bias is less than the upload bias threshold, retaining the target file.

[0084] In one embodiment, the current upload weight can be normalized to obtain a current normalized upload weight, which is then compared with an upload weight threshold. If the current normalized upload weight is greater than or equal to the upload weight threshold, the target file is uploaded to the cloud computer and deleted from the terminal. If the current normalized upload weight is less than the upload weight threshold, the target file is retained. For example, the upload weight threshold can be set to 0.8.

[0085] In the above embodiment, the current upload bias is compared with the upload bias threshold. If the current upload bias is greater than or equal to the upload bias threshold, the target file is uploaded to the cloud computer and the target file is deleted from the terminal; if the current upload bias is less than the upload bias threshold, the target file is retained, and the file can be uploaded accurately.

[0086] See also Figure 2 , which shows an overall flow chart of a terminal data security transmission method for a cloud computer provided by an embodiment of the present invention, comprising the following steps: first, obtaining log information of access logs of various files in the terminal, and then analyzing the connections between files based on the usage relationships between the files, thereby obtaining a relationship graph; and then dynamically correcting the upload degree (i.e., upload bias) of the current file through the frequency of operations on a single file over a period of time, the distribution performance in the relationship graph (i.e., the performance of the association in the relationship graph), and the changes in the association with other related files (i.e., associated files); then, adjusting the window size of the time interval (target duration) for file connection analysis based on the speed of changes in the connections of the multiple files currently in use; and finally, visually displaying the files to be transferred and stored on the cloud computer.

[0087] See also Figure 3 , which shows a structural diagram of a terminal data security transmission system for a cloud computer provided by an embodiment of the present invention, the system includes a memory and a processor; the memory is used to store executable program code; the processor is used to call and run the executable program code from the memory to implement the following steps: every time a target time period passes, the relationship map between each file is updated according to the operation status of each file in the current time period to obtain the current relationship map; the current time period is the time period corresponding to the most recently passed target time period; each file is used as a target file, and the current upload weight of the target file is determined according to the frequency of operation of the target file in the current time period, the association performance of the target file in the current relationship map, and the change in the association of the associated files of the target file; the associated file is a file associated with the target file in the relationship map in the current time period; according to the current upload weight, it is determined whether to upload the target file to the cloud computer.

[0088] In one embodiment, the processor further implements the following steps: obtaining log information of access logs within the current time period; and determining the operation status of each file within the current time period according to the log information.

[0089] In one embodiment, the processor further implements the following steps: determining the number of occurrences of file combinations that meet the target conditions in the current time period and the operation time interval between two files in the file combination each time the combination occurs, based on the operation status of each file in the current time period; determining the association strength corresponding to each file combination in the current time period based on the number of occurrences and the operation time interval; and updating the relationship map between each file based on the association strength to obtain the current relationship map.

[0090] In one embodiment, the processor also implements the following steps: determining the current storage bias of the target file based on the frequency of operations on the target file in the current time period and the association performance of the target file in the current relationship graph; determining the current upload bias of the target file based on the current storage bias of the target file and the changes in the association status of the target file's associated files.

[0091] In one embodiment, the processor further implements the following steps: determining the number of associated files of the target file and the maximum value of the association strength between the target file and the associated files based on the current relationship map; determining the current storage bias of the target file based on the number of operations, the number of associated files, and the maximum value of the association strength between the target file and the associated files.

[0092] In one embodiment, the processor further implements the following steps: determining, for each associated file, the difference between the storage weight of the associated file in the current time period and the previous time period; and determining the current upload weight of the target file based on the difference corresponding to each associated file and the current storage weight of the target file.

[0093] In one embodiment, the processor further implements the following steps: updating the target duration according to the current remaining terminal storage space size and the size of files uploaded after the current time period.

[0094] In one embodiment, the processor further implements the following steps: storing the metadata and upload time points of the files to be uploaded in a database; obtaining the metadata and upload time points of the files uploaded at different time points from the database, and visually displaying them on the terminal.

[0095] In one embodiment, the processor also implements the following steps: comparing the current upload bias with the upload bias threshold; if the current upload bias is greater than or equal to the upload bias threshold, uploading the target file to the cloud computer and deleting the target file from the terminal; if the current upload bias is less than the upload bias threshold, retaining the target file.

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

[0097] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person skilled in the art may make various modifications and improvements without departing from the scope of the present application, and all such modifications and improvements fall within the scope of protection of the present application.

[0098] It should be noted that the order in which the embodiments of the present invention are described above is for illustrative purposes only and does not necessarily represent the superiority or inferiority of the embodiments. The processes depicted in the accompanying drawings do not necessarily require the specific order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0099] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments.

Claims

1. A terminal data security transmission method for cloud computers, characterized in that: The method comprises: Every time the target duration passes, the relationship graph between the files is updated according to the operation status of the files in the current time period to obtain a current relationship graph; the current time period is the time period corresponding to the most recently passed target duration; Each of the files is taken as a target file, and the current upload weight of the target file is determined based on the frequency of operations on the target file in the current time period, the association of the target file in the current relationship graph, and changes in the association of the target file's associated files; the associated files are files associated with the target file in the relationship graph in the current time period; Determine whether to upload the target file to the cloud computer based on the current upload preference.

2. The terminal data security transmission method for cloud computers according to claim 1 is characterized in that: The method further comprises: Obtaining log information of access logs within the current time period; The operation status of each file in the current time period is determined according to the log information.

3. The terminal data security transmission method for cloud computers according to claim 1 is characterized in that: The updating of the relationship map between the files according to the operation status of the files in the current time period to obtain the current relationship map includes: Determining, based on the operation status of each file in the current time period, the number of occurrences of a file combination that meets the target condition in the current time period and the operation time interval between two files in the file combination during each occurrence; Determining, based on the number of occurrences and the operation time interval, the association strength corresponding to each of the file combinations in the current time period; According to the association strength, the relationship map between the files is updated to obtain a current relationship map.

4. The terminal data security transmission method for cloud computers according to claim 1 is characterized in that: The determining the current upload weight of the target file according to the frequency of operations on the target file in the current time period, the association of the target file in the current relationship graph, and the change in association of the target file's associated files includes: Determining a current storage bias of the target file based on a frequency of operations on the target file within the current time period and a correlation performance of the target file in the current relationship graph; The current upload weight of the target file is determined according to the current storage weight of the target file and the change in the association status of the files associated with the target file.

5. The terminal data security transmission method for cloud computers according to claim 4 is characterized in that: The operation frequency includes the number of operations; and determining the current storage bias of the target file according to the operation frequency of the target file in the current time period and the association of the target file in the current relationship graph includes: Determining the number of associated files of the target file and the maximum value of the association strength between the target file and the associated files according to the current relationship graph; The current storage weight of the target file is determined according to the number of operations, the number of the associated files, and the maximum value of the association strength between the target file and the associated files.

6. The terminal data security transmission method for cloud computers according to claim 4 is characterized in that: The determining the current upload weight of the target file according to the current storage weight of the target file and the change in the association of the associated files of the target file includes: For each of the associated files, determining a difference between the storage weight of the associated file in the current time period and the storage weight of the associated file in the previous time period; The current upload weight of the target file is determined according to the difference values corresponding to the associated files and the current storage weight of the target file.

7. The terminal data secure transmission method for cloud computers according to any one of claims 1 to 6, characterized in that: After determining whether to upload the target file to the cloud computer based on the current upload preference, the method further includes: The target duration is updated according to the current remaining terminal storage space size and the size of files uploaded after the current time period.

8. The terminal data secure transmission method for cloud computers according to any one of claims 1 to 6, characterized in that: After determining whether to upload the target file to the cloud computer based on the current upload preference, the method further includes: The metadata and upload time of the files to be uploaded are stored in the database; The metadata and the upload time points of the files uploaded at different time points are obtained from the database and are visually displayed on a terminal.

9. The terminal data secure transmission method for cloud computers according to any one of claims 1 to 6, characterized in that: The step of determining whether to upload the target file to the cloud computer according to the current upload bias includes: Comparing the current upload bias with an upload bias threshold; If the current upload weight is greater than or equal to the upload weight threshold, uploading the target file to the cloud computer and deleting the target file from the terminal; If the current upload weight is less than the upload weight threshold, the target file is retained.

10. A terminal data security transmission system for cloud computers, characterized in that: The system includes a memory and a processor; the memory is used to store executable program code; the processor is used to call and run the executable program code from the memory to implement the terminal data security transmission method for cloud computers described in any one of claims 1 to 9.

Images