A database management platform, a file uploading method and device

Abstract

The application relates to a database management and control platform, a file transmission method and device, and belongs to the technical field of computers and the Internet. The method comprises the following steps: after a communication connection with a management and control server is established, a source-end public key is sent to the management and control server; a file transmission request carrying a destination-end public key sent by the management and control server is received; the file transmission request is encrypted by using the destination-end public key and is sent to a destination-end database server; a temporary identity authentication token and a temporary communication port sent by the destination-end database server are received; an abstract value of a source-end file is generated; the source-end file, the temporary identity authentication token and the abstract value are sent to the destination-end database server based on a file transmission process and the temporary communication port, so that the destination-end database server verifies that the temporary identity authentication token is valid and writes the source-end file into a destination-end file when integrity is required. In this way, the file can be simply and safely transmitted, and the risk of account password leakage is reduced.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of computers and the Internet, in particular to a database management platform, a file uploading method and device. BACKGROUND

[0002] With the rapid development of computer software technology, the scale of customers' databases is expanding and the complexity is increasing, and the database management platform has become an indispensable technical platform. Among them, the database management platform is based on advanced cloud computing, big data and artificial intelligence and other technical means, which improves the efficiency, security and stability of managing databases.

[0003] Specifically, the database management platform needs to realize the functions of automatic deployment and cleaning of databases, scaling, backup and recovery, performance optimization, fault detection and recovery, etc. Among them, when the database management platform realizes these functions, a large amount of file transmission needs to be performed between database servers.

[0004] The commonly used file uploading methods in the industry include two types: one is the scp, async and other tools based on point-to-point mode, which has the advantages of open source tools and easy installation and configuration, but requires the use of static identity tickets such as account password, but this method has the risk of server account password leakage; the second is the file and object storage platform based on third-party transfer, to avoid database server account password leakage, but introducing a third-party platform will increase the system complexity.

[0005] Therefore, it is urgent to design a new database management platform and a corresponding file uploading scheme to realize simple and safe file transmission and reduce the risk of database server account password leakage. SUMMARY

[0006] In view of the above deficiencies of the prior art, the purpose of the present application is to provide a database management platform, a file uploading method and device, which can realize simple and safe file transmission and reduce the risk of database server account password leakage.

[0007] In a first aspect of the present application, a database management platform is provided, which includes a source database server, a destination database server and a management server; the management server is in communication connection with the source database server and the destination database server; after establishing the communication connection, the source database server sends a source public key to the management server, and the destination database server sends a destination public key to the management server;

[0008] The management server is configured to: send a file transmission request carrying a destination public key to a source database server, the file transmission request being used to indicate that a source file on the source database server is uploaded to a destination file on a destination database server;

[0009] The source database server is configured to: encrypt the file transmission request using the destination public key, and send the file transmission request to the destination database server.

[0010] The destination database server is configured to: after decrypting the file transmission request using a private key corresponding to the destination public key, generate a temporary identity authentication token, allocate a temporary communication port, and start a file transmission process; and send the temporary identity authentication token and the temporary communication port to the source database server.

[0011] The source database server is further configured to: generate a digest value of the source file; and based on the file transmission process and the temporary communication port, send the source file, the temporary identity authentication token, and the digest value to the destination database server.

[0012] The destination database server is further configured to: when verifying that the temporary identity authentication token is valid, check the integrity of the source file using the digest value; and when the integrity requirement is met, write the source file to the destination file.

[0013] Further, the source database server is configured to: after establishing a first communication connection with the management server, receive an uplink public key sent by the management server; the uplink public key is used to encrypt a file uploaded to the management server; generate a source public key, and encrypt the source public key using the uplink public key to obtain a source encrypted public key; and send the source encrypted public key to the management server; the source public key is valid when the first communication connection is valid.

[0014] The destination database server is configured to: after establishing a second communication connection with the management server, receive an uplink public key sent by the management server; generate a destination public key, and encrypt the destination public key using the uplink public key to obtain a destination encrypted public key; and send the destination encrypted public key to the management server; the destination public key is valid when the second communication connection is valid.

[0015] The management server is further configured to: decrypt the source encrypted public key and the destination encrypted public key using a private key corresponding to the uplink public key to obtain the source public key and the destination public key.

[0016] Further, the digest value includes MD5, SHA-1, or SHA-256.

[0017] Further, the management and control server is specifically configured to encrypt the file transmission request carrying the destination public key by using the source public key, and send to the source database server.

[0018] Further, the source database server is specifically configured to, when the encrypted file transmission request is successfully decrypted by using the source private key, start a client file transmission process to perform:

[0019] encrypt the unencrypted file transmission request by using the destination public key, and send to the destination database server.

[0020] In a second aspect, an embodiment of the present application provides a file uploading method applied to a source database server in a database management and control platform, the platform comprising: a source database server, a destination database server and a management and control server; the method comprising:

[0021] S1. After establishing a communication connection with the management and control server, sending a source public key to the management and control server;

[0022] S2. Receiving a file transmission request carrying a destination public key sent by the management and control server; after establishing a communication connection with the management and control server, the destination database server sends the destination public key to the management and control server; the file transmission request is used to indicate that a source file on the source database server is uploaded to a destination file on the destination database server;

[0023] S3. Encrypting the file transmission request by using the destination public key, and sending the file transmission request to the destination database server;

[0024] S4. Receiving a temporary identity authentication token and a temporary communication port sent by the destination database server; after the destination database server decrypts the file transmission request by using a private key corresponding to the destination public key, the destination database server generates a temporary identity authentication token, allocates a temporary communication port and starts a file transmission process;

[0025] S5. Generating a digest value of the source file; based on the file transmission process and the temporary communication port, sending the source file, the temporary identity authentication token and the digest value to the destination database server, so that when the destination database server verifies that the temporary identity authentication token is valid, the destination database server verifies the integrity of the source file by using the digest value, and when the integrity requirement is met, the destination database server writes the source file into the destination file.

[0026] Further, the S1 specifically comprises:

[0027] After a first communication connection with a control server is established, an uplink public key sent by the control server is received; the uplink public key is used to encrypt a file uploaded to the control server;

[0028] A source-end public key is generated, and the source-end public key is encrypted by using the uplink public key to obtain a source-end encrypted public key;

[0029] The source-end encrypted public key is sent to the control server; the source-end public key is valid when the first communication connection is valid.

[0030] Further, the source-end database server is specifically used to start a source-end file transmission process to perform:

[0031] The file transmission request is encrypted by using the destination-end public key, and the file transmission request is sent to the destination-end database server.

[0032] In a third aspect, an embodiment of the present application provides a file uploading device applied to a source-end database server in a database control platform, the platform comprising: a source-end database server, a destination-end database server and a control server; the device comprising:

[0033] A first sending module is used to send a source-end public key to the control server after a communication connection with the control server is established;

[0034] A first receiving module is used to receive a file transmission request carrying a destination-end public key sent by the control server; the destination-end database server sends the destination-end public key to the control server after a communication connection with the control server is established; the file transmission request is used to indicate that a source-end file on the source-end database server is uploaded to a destination-end file on the destination-end database server;

[0035] A second sending module is used to encrypt the file transmission request by using the destination-end public key, and send the file transmission request to the destination-end database server;

[0036] A second receiving module is used to receive a temporary identity authentication token and a temporary communication port sent by the destination-end database server; after the destination-end database server decrypts the file transmission request by using a private key corresponding to the destination-end public key, the temporary identity authentication token is generated, the temporary communication port is allocated, and a file transmission process is started;

[0037] The third sending module is configured to generate a digest value of the source file, and send the source file, the temporary identity authentication token and the digest value to the target database server based on the file transmission process and the temporary communication port, so that the target database server verifies the temporary identity authentication token, checks the integrity of the source file by using the digest value when the temporary identity authentication token is verified to be valid, and writes the source file into the target file when the integrity requirement is met.

[0038] In a fourth aspect, the embodiments of the present application further include a source database server configured to implement the file uploading method of any one of the second aspect.

[0039] The present application has the following advantages:

[0040] By using the database management and control platform and the file uploading scheme provided by the embodiments of the present application, the management and control server can be in communication connection with the source database server and the target database. After the communication connection is established, the source database server can send a source public key to the management and control server, and the target database server can send a target public key to the management and control server. Then, the management and control server can send a file transmission request carrying the target public key to the source database server, and the file transmission request is used to indicate that the source file on the source database server is uploaded to the target file on the target database server. After that, the source database server can encrypt the file transmission request by using the target public key, and send the file transmission request to the target database server. After that, the target database server can generate a temporary identity authentication token and allocate a temporary communication port and start a file transmission process after decrypting the file transmission request by using the private key corresponding to the target public key. Then, the target database server can send the temporary identity authentication token and the temporary communication port to the source database server. After that, the source database server can generate a digest value of the source file, and send the source file, the temporary identity authentication token and the digest value to the target database server based on the file transmission process and the temporary communication port. The target database server can check the integrity of the source file by using the digest value when the temporary identity authentication token is verified to be valid, and write the source file into the target file when the integrity requirement is met. In this way, the authentication and authorization can be implemented without relying on the static identity token, and the illegal reading and writing can be avoided. Furthermore, the file can be transmitted simply and safely, and the risk of database server account password leakage is reduced. BRIEF DESCRIPTION OF DRAWINGS

[0041] The accompanying drawings are included to provide a further understanding of the embodiments of the present application, and are incorporated herein and constitute a part of the detailed description. It should be apparent to those skilled in the art that the accompanying drawings are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art according to the accompanying drawings.

[0042] Figure 1 A structural schematic diagram of a database management platform provided by an embodiment of the present application is shown in FIG. 1.

[0043] Figure 2 A structural schematic diagram of another database management platform provided by an embodiment of the present application is shown in FIG. 2.

[0044] Figure 3 A flowchart of a file uploading method provided by an embodiment of the present application is shown in FIG. 3.

[0045] Figure 4 A structural schematic diagram of a file uploading device provided by an embodiment of the present application is shown in FIG. 4.

[0046] Figure 5 A schematic diagram of a source database server provided by an embodiment of the present application is shown in FIG. 5. DETAILED DESCRIPTION

[0047] In order to make the personnel in the art better understand the technical solutions in the embodiments of the present application, the technical solutions of the present application will be described clearly and completely below in conjunction with the drawings. Obviously, the described embodiments are some embodiments of the present application, rather than all the embodiments of the present application. It should be understood that these descriptions are only exemplary, and are not used to limit the scope of the present application. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor should fall within the scope of protection of the present application.

[0048] In addition, in the following description, the description of the known structures and technologies is omitted to avoid unnecessary confusion of the concepts disclosed in the present application.

[0049] In the description of the present application, it should be noted that, unless otherwise explicitly specified and limited, the orientation or position relationship indicated by the terms “center”, “upper”, “lower”, “left”, “right”, “vertical”, “horizontal”, “inner”, “outer” and the like is based on the orientation or position relationship shown in the drawings, and is only for the convenience of describing the present application and simplifying the description, and therefore cannot be understood as indicating or implying that the indicated device or element must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as limiting the present application. In addition, the terms “first”, “second”, “third” are only for the purpose of description, and cannot be understood as indicating or implying relative importance. The terms “mounting”, “connection”, “connection” should be understood broadly, for example, it can be fixed connection, or detachable connection, or integrally connected; it can be mechanical connection, or electrical connection; it can be directly connected, or indirectly connected through an intermediate medium, or the communication between two elements. For those of ordinary skill in the art, the specific meaning of the above terms in the present application can be understood according to the specific circumstances.

[0050] The exemplary embodiments will be described in detail herein with reference to the attached drawings. In the following description, like reference numerals refer to like elements unless indicated otherwise. The following exemplary embodiments described herein represent the best ways of putting the application into practice and are not to be construed as limiting the scope of the application. Rather, they are presented as examples of the methods and systems consistent with aspects of the present application as detailed in the appended claims.

[0051] In order to solve the problems existing in the prior art, the embodiment of the present application provides a database management platform, a file transmission method and device. First, a database management platform provided by the embodiment of the present application will be described.

[0052] System embodiment

[0053] Figure 1 The structure diagram of the database management platform provided by the embodiment of the present application is shown in FIG. 1. As shown in FIG. 1, the database management platform comprises a source database server 102, a destination database server 103 and a management server 101. Figure 1

[0054] The management server 101 has a communication connection with the source database server 102 and the destination database server 103. After the communication connection is established, the source database server 102 sends a source public key to the management server 101, and the destination database server 103 sends a destination public key to the management server 101.

[0055] It can be understood that the source database server 102 and the destination database server 103 generate a new pair of RSA certificates after establishing a communication connection with the management server 101, i.e. when the file transmission task is started. RSA is an asymmetric encryption algorithm. Unlike symmetric encryption algorithms, RSA algorithm has two different keys, one is a public key and the other is a private key. Then, the source database server 102 and the destination database server 103 send the source public key and the destination public key to the management server 101 for registration.

[0056] In order to improve the security of data transmission, all data issued by the management server 101 to the source database server 102 and the destination database server 103 can be encrypted with the corresponding public key.

[0057] The management server 101 is configured to send a file transmission request carrying a destination public key to the source database server 102, and the file transmission request is configured to indicate that a source file on the source database server 102 is uploaded to a destination file on the destination database server 103.​

[0058] The source database server 102 is configured to encrypt the file transmission request using the destination public key and send the file transmission request to the destination database server 103.

[0059] The destination database server 103 is configured to decrypt the file transmission request using the private key corresponding to the destination public key, generate a temporary identity authentication token, assign a temporary communication port, and start a file transmission process, and send the temporary identity authentication token and the temporary communication port to the source database server 102.

[0060] It can be understood that the source database server 102 can receive a file transmission request carrying a destination public key, encrypt the file transmission request using the destination public key, and send the file transmission request to the destination database server 103, so that the destination database server can decrypt the file transmission request using the destination private key, and if the decryption is successful, the file transmission request is verified to be secure, and then a temporary identity authentication token can be generated, a temporary communication port can be assigned, and a file transmission process can be started.

[0061] The source database server 103 is further configured to generate a digest value of the source file, and send the source file, the temporary identity authentication token, and the digest value to the destination database server 103 based on the file transmission process and the temporary communication port.

[0062] It can be understood that the digest value includes MD5 (Message-Digest Algorithm 5), SHA-1 (Secure Hash Algorithm 1), or SHA-256 (Secure Hash Algorithm 256), but is not limited thereto.

[0063] The destination database server 103 is further configured to verify the integrity of the source file using the digest value when the temporary identity authentication token is verified to be valid, and write the source file to the destination file when the integrity requirement is met.

[0064] It can be understood that through the platform, authentication and authorization can be achieved without relying on static identity tokens (database server account password, file transmission tool static password), and illegal reading and writing can be avoided. Furthermore, simple and secure file transmission can be achieved, and the risk of database server account password leakage can be reduced.

[0065] In addition, when verifying that the temporary authentication token is valid, the destination database server can check the integrity of the source file using the digest value, and when the integrity requirement is met, the source file is written to the destination file. In this way, after the file is uploaded to the destination database server, the integrity and consistency of the data can also be checked to ensure that the transmission result is consistent with the original content.

[0066] Further, in order to ensure that the data in the file transmission process cannot be stolen and tampered by a third party, the data uploaded by the database server to the management server can also be encrypted. Specifically, the source database server 102 is configured to: after establishing a first communication connection with the management server 101, receive an uplink public key sent by the management server 101; the uplink public key is used to encrypt the file uploaded to the management server; generate a source public key, and encrypt the source public key using the uplink public key to obtain a source encrypted public key; send the source encrypted public key to the management server 101; the source public key is valid when the first communication connection is valid;

[0067] The destination database server 103 is configured to: after establishing a second communication connection with the management server 101, receive an uplink public key sent by the management server 101; generate a destination public key, and encrypt the destination public key using the uplink public key to obtain a destination encrypted public key; send the destination encrypted public key to the management server 101; the destination public key is valid when the second communication connection is valid;

[0068] The management server 101 is further configured to: use the private key corresponding to the uplink public key to decrypt the source encrypted public key and the destination encrypted public key to obtain the source public key and the destination public key.

[0069] Further, the management server is specifically configured to: encrypt the file transmission request carrying the destination public key using the source public key, and send it to the source database server. In this way, the data can be further encrypted to ensure that the data in the transmission process cannot be stolen and tampered by a third party.

[0070] Further, the source database server is specifically configured to: when the encrypted file transmission request is successfully decrypted using the source private key, start a client file transmission process to perform:

[0071] Encrypt the unencrypted file transmission request using the destination public key, and send it to the destination database server.

[0072] It can be understood that after the source end database server 102 correctly decrypts the file transmission request, that is, after verifying that the file transmission request is legal, a client file transmission process can be started to perform the transmission task in this round.

[0073] Further, the destination end database server 103 is specifically configured to start a file transmission process using the https protocol. It can be understood that when it is a file upload scenario, an https POST call can be used. When it is a file download scenario, an https get call is used, and the destination end database server is responsible for reading the file content, and returns the file content and the file digest value through https.

[0074] Method embodiment

[0075] The file upload method provided by the embodiment of the application will be described below. Figure 2 And Figure 3 The file upload method provided by the embodiment of the application will be described below.

[0076] Referring to Figure 3 The file upload method provided by the embodiment of the application includes:

[0077] S1. After establishing a communication connection with the management and control server, the source end public key is sent to the management and control server;

[0078] It can be understood that the source end database server and the destination end database server generate a new pair of RSA certificates after establishing a communication connection with the management and control server, that is, when the file transmission task is started. RSA is an asymmetric encryption algorithm. Unlike symmetric encryption algorithms, RSA algorithm has two different keys, one is a public key and one is a private key. Then, the source end database server and the destination end database server send the source end public key and the destination end public key to the management and control server for registration.

[0079] In order to improve the security of data transmission, all data issued by the management and control server to the source end database server and the destination end database server can be encrypted by the corresponding public key of the database server.

[0080] S2. Receiving the file transmission request sent by the management and control server and carrying the destination end public key; after the destination end database server establishes a communication connection with the management and control server, the destination end public key is sent to the management and control server; the file transmission request is used to indicate that the source end file on the source end database server is uploaded to the destination end file on the destination end database server;

[0081] S3. encrypt the file transfer request using the destination public key, and send the file transfer request to the destination database server;

[0082] It can be understood that the source database server can receive the file transfer request carrying the destination public key, and then encrypt the file transfer request using the destination public key and send it to the destination database server, so that the destination database server can decrypt the file transfer request by the destination private key, and if the decryption is successful, it verifies that the file transfer request is secure, and then generates a temporary identity authentication token, allocates a temporary communication port and starts a file transfer process.

[0083] S4. receive the temporary identity authentication token and the temporary communication port sent by the destination database server; the destination database server decrypts the file transfer request using the private key corresponding to the destination public key, generates a temporary identity authentication token, allocates a temporary communication port and starts a file transfer process;

[0084] S5. generate the digest value of the source file; based on the file transfer process and the temporary communication port, send the source file, the temporary identity authentication token and the digest value to the destination database server, so that when the destination database server verifies that the temporary identity authentication token is valid, it checks the integrity of the source file using the digest value, and when the integrity requirement is met, it writes the source file to the destination file.

[0085] It can be understood that the digest value includes MD5 (Message-Digest Algorithm 5), SHA-1 (Secure Hash Algorithm 1) or SHA-256 (Secure Hash Algorithm 256), but is not limited thereto.

[0086] Through this method, authentication and authorization can be achieved without relying on static identity tickets (database server account password, file transfer tool static password), avoiding illegal reading and writing. Furthermore, it realizes simple and safe file transfer, reducing the risk of database server account password leakage.

[0087] In addition, when the destination database server verifies that the temporary identity authentication token is valid, it can check the integrity of the source file using the digest value, and when the integrity requirement is met, it writes the source file to the destination file. In this way, after the file is uploaded to the destination database server, the integrity and consistency of the data can also be checked to ensure that the transmission result is consistent with the original content.

[0088] It can be understood that a microservice is deployed in the management server, which is responsible for interacting with the database server for distributing operation tasks to the database server and collecting summary task execution results.

[0089] Referring to Figure 2 , a resident process is deployed on the database server, specifically, a client task process (referred to as a client task) is deployed on the source database server, and a client task process is also deployed on the destination database server, which is used to receive the tasks issued by the management server, execute the tasks, and report the task results. Specifically, the process is as follows:

[0090] 1. When each task is started, a new pair of RSA certificates is generated, and the public key is registered to the management server. All data subsequently issued by the management server to the client task needs to be encrypted using the public key of the database server corresponding to the client task. The registration process is an RSA channel handshake process between the client task and the management server microservice, and the specific process is as follows:

[0091] a. After the client task establishes a TCP network link to the management server successfully, the client task receives the RSA public key returned by the management server in plaintext, which is used for subsequent encryption of data from the client task to the management server, hereinafter referred to as the uplink public key;

[0092] b. The client task uses the uplink public key to encrypt the newly generated public key (i.e., the source public key or the destination public key) and sends it to the management server;

[0093] c. The public key generated by the client task is bound to the network link, and is invalidated synchronously after the connection is disconnected or invalid.

[0094] 2. The management server issues a file transfer task to the source client task carrying the destination public key, requiring the source file to be uploaded to the destination file;

[0095] 3. After the source client task obtains the read-write permission, a client file transfer process is started;

[0096] 4. The client file transfer process uses the destination public key to encrypt the file transfer request and calls the interface of the destination client task to request to upload the file;

[0097] 5. After the destination client task verifies the read-write permission, a temporary identity authentication token is generated, a temporary communication port is allocated, and a server file transfer process using the https protocol is started;

[0098] 6. The destination client task returns the temporary communication port and the one-time temporary identity authentication token to the client file transfer process;

[0099] 7. The client file transfer process reads the source file content, carries a one-time temporary identity authentication token, and calls the https upload interface of the client file transfer process of the destination to complete the file content upload;

[0100] 8. The client file transfer process of the destination is responsible for file writing and checking file integrity and consistency. After the task is completed, the client file transfer process and the server file transfer process.

[0101] Further, in order to ensure that the data in the file transmission process cannot be stolen and tampered by a third party, the data uploaded by the database server to the management server can also be encrypted, and the S1 specifically includes:

[0102] After establishing a first communication connection with the management server, receive the uplink public key sent by the management server; the uplink public key is used to encrypt the file uploaded to the management server;

[0103] Generate a source public key, and encrypt the source public key using the uplink public key to obtain a source encrypted public key;

[0104] Send the source encrypted public key to the management server; the source public key is valid when the first communication connection is valid.

[0105] Further, the source database server is specifically configured to start a source file transfer process to perform:

[0106] Encrypt the file transfer request using the destination public key and send the file transfer request to the destination database server.

[0107] In this way, the data can be further encrypted to ensure that the data in the transmission process cannot be stolen and tampered by a third party.

[0108] Apparatus embodiment

[0109] Corresponding to the above method embodiment, the embodiment of the application also provides a file upload device applied to a source database server in a database management platform, the platform comprising: a source database server, a destination database server and a management server; see Figure 4 , the device comprises:

[0110] The first sending module 401 is configured to send a source public key to the management server after establishing a communication connection with the management server;

[0111] The first receiving module 402 is used for receiving a file transmission request carrying a destination public key sent by the management server; after the destination database server establishes a communication connection with the management server, the destination public key is sent to the management server; the file transmission request is used for indicating that a source file on a source database server is uploaded to a destination file on a destination database server.

[0112] The second sending module 403 is used for encrypting the file transmission request by using the destination public key and sending the file transmission request to the destination database server.

[0113] The second receiving module 404 is used for receiving a temporary identity authentication token and a temporary communication port sent by the destination database server; after the destination database server decrypts the file transmission request by using a private key corresponding to the destination public key, the temporary identity authentication token is generated, the temporary communication port is allocated, and a file transmission process is started.

[0114] The third sending module 405 is used for generating an digest value of the source file; based on the file transmission process and the temporary communication port, the source file, the temporary identity authentication token and the digest value are sent to the destination database server, so that when the destination database server verifies that the temporary identity authentication token is valid, the integrity of the source file is checked by using the digest value, and when the integrity requirement is met, the source file is written into the destination file.

[0115] In addition, the embodiment of the present application also provides a source database server for implementing any one of the above file uploading methods. The source database server comprises a memory and one or more processors.

[0116] The memory stores one or more application programs, and the one or more application programs are adapted to be executed by the one or more processors to implement the scientific and technological big data element construction method of the first aspect.

[0117] Specifically, as shown in the figure, Figure 5 The source database server comprises a processor 501 and a memory 502. The processor 501 and the memory 502 are connected, for example, by a bus.

[0118] The structure of the source database server does not constitute a limitation on the embodiments of the present application.

[0119] The processor 501 can be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the present disclosure. The processor 501 can also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

[0120] The bus can include a path that transmits information between the above-mentioned components. The bus can be a PCI bus or an EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For convenience of representation, Figure 5 In the figure, only one thick line is used to represent the bus, but it does not mean that there is only one bus or only one type of bus.

[0121] The memory 502 can be a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, an optical disk storage (including a compact disk, a laser disk, an optical disk, a digital versatile disk, a Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but not limited to this.

[0122] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, the computer program being capable of being loaded and executed by a processor to perform the method steps of the above-mentioned method embodiments.

[0123] The applicant of the present application has made a detailed description and explanation of the embodiments of the present application in combination with the accompanying drawings of the specification, but those skilled in the art should understand that the above embodiments are only preferred embodiments of the present application, and the detailed description is only to help the reader better understand the spirit of the present application, and is not a limitation on the protection scope of the present application. On the contrary, any improvement or modification made on the basis of the spirit of the present application should fall within the protection scope of the present application.

[0124] It should be pointed out finally that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present application, but not to limit them. Although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those skilled in the art that the technical solutions recorded in the foregoing embodiments can be modified, or some technical features can be replaced equivalently; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application. Any changes or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed by the present application should be covered within the protection scope of the present application.

Claims

1. A database management and control platform, characterized in that, The platform includes: a source database server, a destination database server, and a management server; the management server establishes a communication connection with the source database server and the destination database server; after the communication connection is established, the source database server sends a source public key to the management server, and the destination database server sends a destination public key to the management server. The control server is used to: send a file transfer request carrying the destination public key to the source database server, the file transfer request being used to instruct: to upload the source file on the source database server to the destination file on the destination database server; The source database server is configured to: encrypt the file transfer request using the destination public key, and send the file transfer request to the destination database server; The destination database server is configured to: decrypt the file transfer request using the private key corresponding to the destination public key, generate a temporary authentication token, allocate a temporary communication port, and start the file transfer process; and send the temporary authentication token and the temporary communication port to the source database server. The source database server is further configured to: generate a digest value of the source file; and send the source file, the temporary authentication token, and the digest value to the destination database server based on the file transfer process and the temporary communication port. The destination database server is further configured to: when verifying the validity of the temporary authentication token, use the digest value to verify the integrity of the source file; and when the integrity requirements are met, write the source file into the destination file.

2. The database management platform according to claim 1, characterized in that, The source database server is configured to: after establishing a first communication connection with the management server, receive an uplink public key sent by the management server; the uplink public key is used to encrypt files uploaded to the management server; generate a source public key, and encrypt the source public key using the uplink public key to obtain a source encryption public key; and send the source encryption public key to the management server. The source public key is valid while the first communication connection is valid; The destination database server is used to: receive the uplink public key sent by the management server after establishing a second communication connection with the management server; Generate the destination public key, and encrypt the destination public key using the uplink public key to obtain the destination encrypted public key; Send the destination encryption public key to the management server; The destination public key is valid while the second communication connection is valid; The control server is also used to: use the private key corresponding to the uplink public key to decrypt the source encryption public key and the destination encryption public key to obtain the source public key and the destination public key.

3. The database management platform according to claim 1, characterized in that, The digest value includes: MD5, SHA-1, or SHA-256.

4. The database management platform according to claim 1, characterized in that, The control server is specifically used to: encrypt the file transfer request carrying the destination public key using the source public key, and send it to the source database server.

5. The database management platform according to claim 4, characterized in that, The source database server is specifically used to: when a file transfer request that has been successfully decrypted using the source private key is executed, start a client file transfer process to perform the following: The unencrypted file transfer request is encrypted using the destination public key and sent to the destination database server.

6. A file upload method, characterized in that, A source database server is used in a database management platform, the platform comprising: a source database server, a destination database server, and a management server; the method includes: S1. After establishing a communication connection with the management server, send the source public key to the management server; S2. Receive a file transfer request sent by the management server, carrying the destination public key; after the destination database server establishes a communication connection with the management server, it sends the destination public key to the management server; the file transfer request is used to indicate: upload the source file on the source database server to the destination file on the destination database server; S3. Encrypt the file transfer request using the destination public key and send the file transfer request to the destination database server; S4. Receive a temporary authentication token and a temporary communication port sent by the destination database server; after the destination database server decrypts the file transfer request using the private key corresponding to the destination public key, it generates a temporary authentication token, allocates a temporary communication port, and starts the file transfer process. S5. Generate a digest value for the source file; based on the file transfer process and the temporary communication port, send the source file, the temporary authentication token, and the digest value to the destination database server, so that when the destination database server verifies the validity of the temporary authentication token, it uses the digest value to verify the integrity of the source file, and when the integrity requirements are met, it writes the source file into the destination file.

7. The method according to claim 6, characterized in that, S1 specifically includes: After establishing the first communication connection with the management server, the system receives the uplink public key sent by the management server; the uplink public key is used to encrypt files uploaded to the management server. Generate a source public key and encrypt the source public key using the uplink public key to obtain a source encrypted public key; The source-side encryption public key is sent to the management server; the source-side public key is valid when the first communication connection is valid.

8. The method according to claim 6, characterized in that, The source database server is specifically used to initiate a source file transfer process to execute: The file transfer request is encrypted using the destination public key and then sent to the destination database server.

9. A file upload device, characterized in that, A source database server used in a database management platform, the platform comprising: a source database server, a destination database server, and a management server; the device comprising: The first sending module is used to send the source public key to the management server after establishing a communication connection with the management server; The first receiving module is used to receive a file transfer request sent by the management server, which carries the destination public key; after the destination database server establishes a communication connection with the management server, it sends the destination public key to the management server; the file transfer request is used to indicate: to upload the source file on the source database server to the destination file on the destination database server; The second sending module is used to encrypt the file transfer request using the destination public key and send the file transfer request to the destination database server. The second receiving module is used to receive a temporary authentication token and a temporary communication port sent by the destination database server; after the destination database server decrypts the file transfer request using the private key corresponding to the destination public key, it generates a temporary authentication token, allocates a temporary communication port, and starts the file transfer process. The third sending module is used to generate a digest value of the source file; based on the file transfer process and the temporary communication port, it sends the source file, the temporary authentication token, and the digest value to the destination database server, so that when the destination database server verifies the validity of the temporary authentication token, it uses the digest value to verify the integrity of the source file, and when the integrity requirements are met, it writes the source file into the destination file.

10. A source-end database server, characterized in that, Used to implement the file upload method according to any one of claims 6 to 8.

Images