Data management method, system, computer device and storage medium

Abstract

The application relates to the technical field of data management, and discloses a data management method, a data management system, computer equipment and a storage medium, the method comprising the following steps: when a data uploading instruction is received, an uploading request and an uploading category are sent to a server, and a key from the server is acquired; the uploading category comprises adding data; if the uploading category is adding data, it is judged whether the data in a data column is complete; if the data is complete, the key and the data are bound and locally backed up, and then the data and the key are uploaded to the server. The data can be bound with the key, the server is convenient to manage, and when the data is uploaded, the data is checked locally, so that incomplete data is avoided from being uploaded to the server, the data after uploading is easy to find and complete, and the safety of the data and the convenience of management are improved.

Description

Technical Field

[0001] This invention relates to the field of data management technology, and in particular to a data management method, system, computer equipment, and storage medium. Background Technology

[0002] During the hardware device generation process, data for each device needs to be configured. Since the data for each device is different, data management becomes disorganized when uploading data, and data retrieval is troublesome and insecure. After writing the data for each device, uploading is troublesome, and in the event of data corruption, it is difficult to recover the damaged data. Summary of the Invention

[0003] Firstly, this application provides a data management method applied to a client, the method comprising: When a data upload instruction is received, an upload request and upload type are sent to the server, and a key is obtained from the server; the upload type includes adding data. If the upload type is adding data, determine whether the data in the data column is complete. If it is complete, bind the key and the data and back them up locally, and then upload the data and the key to the server.

[0004] Furthermore, the upload type also includes modified data; the method further includes: If the upload type is data modification, then select the target key that is bound to the data to be modified from all the keys sent by the server; Based on the target key, retrieve the data that needs to be modified from the local backup; The acquired data is entered into the data field, and after receiving the user's input indicating that the modification is complete, it is uploaded to the server according to the upload instruction.

[0005] Furthermore, the method also includes: If the data to be modified is not found in the local backup, a message indicating that the data does not exist will be issued, prompting the user to enter the data. After the data input is complete, it is uploaded to the server.

[0006] Furthermore, the upload type also includes modified data; the method further includes: If the upload type is data modification, then select the target key that is bound to the data to be modified from all the keys sent by the server; Send an inquiry request to the server to verify whether the target key has been bound to the data; If the target key is already bound to the data, then request and obtain the data from the server, and display the data in the data field. After the data is modified, upload it to the server according to the upload instruction. If the key is not bound to the data, then upload the data according to the steps for adding data when the upload type is specified.

[0007] Furthermore, the data column provides value options for the data through a drop-down menu, and the data can be modified in response to the user's selection in the drop-down menu.

[0008] Secondly, this application also provides a data management method applied to a server, the method comprising: Upon receiving an upload request and upload type from the client, a data connection is established with the client; the upload type includes adding data. When the upload type is "add data", a new data row is added to the database, and the data row is encrypted according to its ID to generate a key, which is then sent to the client. Receive the key and data sent by the client, and bind the data and the key into the newly added data row and the specified address.

[0009] Furthermore, the upload type also includes modified data; the method further includes: If the upload type is data modification, then all keys are retrieved from the database and all keys are sent to the client; If an inquiry request is received from the client, then based on the key in the inquiry request, determine whether the key is bound to data; If the key is bound to data, then the data is sent to the client.

[0010] Thirdly, this application also provides a data management system, including: a client and a server; The client is used to send an upload request and upload type to the server when data needs to be uploaded, and to obtain a key from the server; the upload type includes adding data; The server is used to establish a data connection with the client after receiving an upload request and upload type from the client; the upload type includes adding data. When the upload type is "add data", a new data row is added to the database, and the data row is encrypted according to its ID to generate a key, which is then sent to the client. The client is also used to determine whether the data in the data column is complete if the upload type is adding data. If it is complete, the client binds the key and the data and backs them up locally, and then uploads the data and the key to the server. The server is also used to receive the key and data sent by the client, and bind the data and the key into a new data row and a specified address.

[0011] Fourthly, this application also provides a computer device, including a processor and a memory, wherein the memory stores a computer program, and the computer program executes the data management method when it is run on the processor.

[0012] Fifthly, this application also provides a readable storage medium storing a computer program that executes the data management method when run on a processor.

[0013] This invention discloses a data management method, which includes: upon receiving a data upload instruction, sending an upload request and upload type to a server, and obtaining a key from the server; the upload type includes adding data; if the upload type is adding data, determining whether the data in the data field is complete; if complete, binding the key and the data and backing them up locally, and then uploading the data and the key to the server. This allows data to be bound to a key, facilitating server management, and the local check during upload avoids incomplete data being uploaded to the server, ensuring that uploaded data is easy to find and complete, thus improving data security and ease of management. Attached Figure Description

[0014] To more clearly illustrate the technical solution of the present invention, the accompanying drawings used in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope of protection of the present invention. In the various drawings, similar components are numbered similarly.

[0015] Figure 1 This paper illustrates a flowchart of a data management method according to an embodiment of this application. Figure 2 A schematic diagram of a data management system according to an embodiment of this application is shown; Figure 3 A schematic diagram of the data upload client interface according to an embodiment of this application is shown; Figure 4 A timing diagram of a data management method according to an embodiment of this application is shown. Detailed Implementation

[0016] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.

[0017] The components of the embodiments of the invention described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0018] In the following, the terms “comprising,” “having,” and their cognates, which may be used in various embodiments of the invention, are intended only to indicate a particular feature, number, step, operation, element, component, or combination thereof, and should not be construed as excluding, firstly, the presence of one or more other features, numbers, steps, operations, elements, components, or combinations thereof, or adding the possibility of one or more features, numbers, steps, operations, elements, components, or combinations thereof.

[0019] Furthermore, the terms "first," "second," and "third" are used only to distinguish descriptions and should not be interpreted as indicating or implying relative importance.

[0020] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of the invention pertain. Terms (such as those defined in commonly used dictionaries) shall be interpreted as having the same meaning as in their contextual meaning in the relevant technical field and shall not be interpreted as having an idealized or overly formal meaning, unless clearly defined in the various embodiments of the invention.

[0021] The technical solution of this application is applied to the uploading of data. The data mentioned in this application is data applied to hardware devices, similar to factory settings or other data that can configure the device.

[0022] By performing different operations on the types of data uploaded and binding a key to each piece of data, the data can be indexed using the key, making the data easier to manage. However, for external personnel, it is difficult to find the data without knowing the key, thus ensuring data security.

[0023] The technical solution of this application will now be described with reference to specific embodiments.

[0024] Example 1 like Figure 1As shown, the data management method of this application includes the following steps: In step S100, when data needs to be uploaded, the client sends an upload request and upload type to the server and obtains a key from the server.

[0025] The data upload in this application is from the client to the server, such as... Figure 2 The diagram shows a data management system. Client 200 can be a computer used by developers, while server 100 is a management server specifically used to store data and project code.

[0026] There are different scenarios when uploading data, specifically adding data and modifying data. In both cases, the data to be added or modified needs to be uploaded from the client. Therefore, when a user needs to upload data, the client sends an upload request to the server, specifying the corresponding upload type.

[0027] Specifically, on the upload interface of the client, different request buttons can be set according to different upload types. Users can press the corresponding button to send the corresponding request message to the server according to the specific situation.

[0028] After the request is sent, the server will return a key to the client based on the request and the type of upload. The upload request and upload type can be sent via the HTTP POST method, requesting the server to return the corresponding data.

[0029] In step S200, the server establishes a data connection with the client after receiving the upload request and upload type from the client.

[0030] When the server receives an upload request and upload type from the client, it establishes a data connection with the client to ensure data transmission. At the same time, it sends the corresponding key to the client based on the upload type.

[0031] Step S300: When the upload type is adding data, add a new data row in the database, encrypt the data row according to its ID, generate a key, and send the key to the client.

[0032] Encryption methods can include DES, AES, or base64.

[0033] When the upload type is "Add Data," it means the server needs to store new data that wasn't originally on the server. Therefore, a new data row needs to be added to the database used to manage the data. Furthermore, in this embodiment, the data is bound to a corresponding key. When a new data row is added, its ID is updated accordingly. Therefore, this ID is necessarily different from the IDs of other data rows, and the key obtained by encrypting this ID is also unique.

[0034] This generates a new key, which can be used to bind to the data to be added later. The bound key then serves as an index for that data. Since keys as indexes are difficult to read, annotations can be generated after the index is created, following a specific annotation logic. For example, in a simulated production environment, data is typically associated with devices, customers, and projects. Therefore, specific annotations can be created based on this information to facilitate user reading and help users identify which key corresponds to which data.

[0035] Understandably, in real-world production environments, multiple clients and projects are involved. Using only row IDs as indexes can easily lead to data mixing between different projects or clients, making data recovery difficult, especially if the database language is misused. Encrypting the IDs prevents this data mixing and makes the data more tamper-proof, preventing human error. Furthermore, different clients and projects can use different encryption keys, ensuring that even the same ID is encrypted with different keys, thus avoiding data mixing issues.

[0036] When the upload type is "modify data," it means the user needs to modify existing data. In this case, the server will not generate a new data row or a new key. Instead, it will send all keys to the client for the user to choose from. Understandably, the aforementioned notes will also be sent to the client along with the keys.

[0037] In step S400, the client is further configured to determine whether the data in the data field is complete if the upload type is adding data. If complete, the client binds the key and the data and backs them up locally, and then uploads the data and the key to the server.

[0038] After sending the upload type and upload request, the client will perform a verification operation on the data to be uploaded, that is, determine whether the data is complete.

[0039] When the upload type is "Add Data", the user needs to enter the data manually in the data box on the operation interface.

[0040] For example, the data for a particular robot device might include various parameters such as model, video encoding, pixel count, horizontal motor direction, and vertical motor direction. Each type of data is written into a corresponding data frame according to a specific format or requirement. When the client performs an upload operation, this data is checked to ensure that all data conforms to the format requirements and is complete before uploading. If incomplete data or other problems are found, the data will not be uploaded, and the user will be prompted to modify the data until it meets the requirements before uploading.

[0041] During upload, a local backup of the newly added data is also created, using the same key as the folder name. This dual backup helps ensure data accuracy to some extent.

[0042] Similarly, if the uploaded data is modified, the above checks will also be performed to prevent the upload of invalid data.

[0043] Furthermore, when uploading data, the client receives all the keys sent by the server. The user needs to select the key corresponding to the data they want to modify from these keys to perform the corresponding data modification. Because notes can be added when the keys are generated, the corresponding data can be selected based on the notes.

[0044] After obtaining the key, you can retrieve data in two ways. One way is to read data from your local machine. As you can understand, when adding data, a copy of the data will be stored locally. When making changes, you can try to retrieve the data from your local machine for modification. After retrieving and modifying the data, upload it according to the steps described above.

[0045] In addition, when retrieving data from the local machine, there may be cases where the data is not available locally. This may be because the client used to add the data and the client used to modify it are not the same client. Therefore, you can prompt the user that the data was not found, wait for the user to enter data in the data box, and then upload the data in the data box according to the steps described above for adding data.

[0046] Alternatively, data can be retrieved from the server. After the user selects a key, a verification message is sent to the server to determine whether the key is bound to data within the server. Once the bound data is found, the corresponding data is sent to the client for the user to modify.

[0047] Similarly, due to network fluctuations or other errors, the key may not be able to match the bound data on the server. In this case, it can be handled by adding data, where the user writes the data on the client and then uploads it.

[0048] like Figure 3The image shows the interface for uploading data on the client side.

[0049] The user interface contains multiple data boxes for inputting data. Since there are multiple different types of data, a separate data box is provided for each type. The "Add" button adds data, the "Modify" button modifies data (corresponding to the upload types), and the "Upload" button performs the final upload operation. The "Key" box displays and allows users to select keys. When the upload type is "Modify Data," the user selects the required key in the key box to retrieve and modify the data. When the upload type is "Add Data," the key box displays the newly generated key from the server.

[0050] To ensure the accuracy of data entered by users in the data frame, the data frame can be set to a non-editable mode. Instead, a drop-down menu can be used to provide data selection. When users need to enter data, they can select the option provided in the drop-down menu to enter the data. This can, to a certain extent, ensure that the entered data meets the format requirements and reduce the likelihood of data errors caused by input mistakes.

[0051] In step S500, the server receives the key and data sent by the client, and binds the data and the key into a newly added data row and a specified address.

[0052] After receiving the key and data sent from the client, the server binds and stores the key and data. The data and key are stored in two places: one is the database mentioned above. In step S100, a new data row is created, and the key and corresponding data are stored in this data row, with the key serving as the index for the data.

[0053] Another point is the directory address specified by the client during upload. When the data is stored in the directory address, it will be stored in the form of a configuration file so that it can be used directly on the device when it is downloaded.

[0054] In other words, the data and keys stored in the database are used to record the addition, modification, and deletion of data; the data here acts as an index. The data stored as configuration files is the final file format that will be distributed to the device; it's a specific application file obtained by transforming the pre-configured data. Understandably, when data needs to be modified, reading data directly from the configuration file is cumbersome for the machine; it's more convenient to read it directly from the database. Recording data in the database allows for effective tracking of the contents of each configuration file, confirming data accuracy, and achieving better data management.

[0055] To better understand Benset's data management system, please refer to the following: Figure 4 The timing diagram shown.

[0056] When a client needs to upload data, it sends an upload request and the upload type to the server. The server then determines the upload type and performs the corresponding operation. When adding data, a new key needs to be generated; when modifying existing data, all keys are retrieved. Once the keys are ready, the server sends them to the client.

[0057] The client operates differently depending on the type of upload. For adding data, the client waits for the user to finish entering the data before proceeding with the upload. For modifying data, the client selects the key associated with the data to be modified from all the keys sent by the server. Then, using that key, the client retrieves the data from either its local machine or the server. After retrieving the data, the client modifies it before proceeding with the upload.

[0058] Before uploading, the client will also check the data to ensure that the data format conforms to the specifications and that the data is complete. During the upload, the client will bind and save the key and data locally and upload it to the server. The server will also bind and save the data and key to ensure that the key serves as an index that can point to the data.

[0059] This application's data management method uses a key as an index, avoiding the vulnerability of plaintext IDs to tampering and increasing the difficulty of malicious data destruction. Furthermore, the unique key allows for locating the corresponding data within the system. Different operations are performed for different upload types to ensure correct data modification and addition. Upload checks are performed locally on the client side to prevent incomplete data from being uploaded to the server, ensuring that uploaded data is easy to find and complete. This improves data security and management convenience, preventing chaotic data management.

[0060] This application also provides a computer device, including a processor and a memory, wherein the memory stores a computer program, and the computer program executes the data management method described above when it is run on the processor.

[0061] This application also provides a readable storage medium storing a computer program that executes the data management method when run on a processor.

[0062] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative; for example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that, as an alternative implementation, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0063] In addition, the functional modules or units in the various embodiments of the present invention can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0064] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a smartphone, personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0065] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention.

Claims

1. A data management method, characterized in that, Applied to the client, the method includes: When a data upload instruction is received, an upload request and upload type are sent to the server, and a key is obtained from the server; the upload type includes adding data; wherein when the upload type is adding data, the server adds a new data row to the database in the server, and the key is generated by encrypting the ID of the data row; If the upload type is adding data, determine whether the data in the data column is complete. If it is complete, bind the key and the data and back them up locally, and then upload the data and the key to the server. After uploading, bind the key and the data, with the key serving as the index for the data. The data and the key binding are stored in the newly added data row and the specified address. The types of uploads also include modified data; If the upload type is data modification, then select the target key that is bound to the data to be modified from all the keys sent by the server; Send an inquiry request to the server to verify whether the target key has been bound to the data; If the target key is already bound to the data, then request and obtain the data from the server, and display the data in the data field. After the data is modified, upload it to the server according to the upload instruction. If the target key is not bound to the data, then upload the data according to the steps for adding data when the upload type is specified.

2. The data management method according to claim 1, characterized in that, The upload type also includes modified data; the method also includes: If the upload type is data modification, then select the target key that is bound to the data to be modified from all the keys sent by the server; Based on the target key, obtain the data that needs to be modified from the local backup on the client. The acquired data is entered into the data field, and after receiving the user's input indicating that the modification is complete, it is uploaded to the server according to the upload instruction.

3. The data management method according to claim 2, characterized in that, The method further includes: If the data to be modified is not found in the local backup of the client, a message indicating that the data does not exist will be issued, prompting the user to enter the data. After the data input is complete, the data is uploaded to the server according to the upload command.

4. The data management method according to claim 1, characterized in that, The data column provides value options for the data through a drop-down menu, and the data can be modified in response to the user's selection in the drop-down menu.

5. A data management method, characterized in that, Applied to a server, the method includes: Upon receiving an upload request and upload type from the client, a data connection is established with the client; the upload type includes adding data. When the upload type is "add data", a new data row is added to the database in the server, and the data row is encrypted according to its ID to generate a key, which is then sent to the client; wherein, when the data row is added, the ID of the data row will be updated as the data row is added; The system receives a key and data sent by the client, binds the data and the key, and stores them in a newly added data row and a specified address; the key serves as an index for the data; the upload type also includes modifying data; If the upload type is data modification, then all keys are retrieved from the database and all keys are sent to the client; If an inquiry request is received from the client, it is determined whether the key is bound to data based on the key in the inquiry request; the key is the target key selected by the client from all keys sent by the server and bound to the data that needs to be modified. If the key is bound to data, then the data is sent to the client; Receive the modified data uploaded by the client according to the upload instruction.

6. A data management system, characterized in that, include: Client and server; The client is used to execute the data management method according to any one of claims 1 to 4; The server is used to execute the data management method according to claim 5.

7. A computer device, characterized in that, It includes a processor and a memory, the memory storing a computer program that, when executed on the processor, performs the data management method according to any one of claims 1 to 5.

8. A readable storage medium, characterized in that, It stores a computer program that, when run on a processor, executes the data management method according to any one of claims 1 to 5.

Images