A method for preventing repeated use of an application system database

Abstract

The present invention discloses a scheme for preventing the reuse of application system databases, which includes the following steps: S1, generating a fingerprint file; S2, program startup verification; S3, configuring and binding fingerprints; S4, runtime verification. The step S1 includes the following sub-steps: A1, reading the machine code of the hospital server; A2, encrypting the server machine code and a random string to generate a fingerprint file; A3, when deploying the background program, it is necessary to manually place the fingerprint file in the program directory. Among them, the encryption method in the step A2 is a reversible algorithm, such as AE. In addition, the fingerprint file is used to decrypt the server machine code and the random string, and the random string is used as the database serial number. Through the settings of the corresponding system, the present invention can technically avoid the situation where implementers copy databases between projects, causing economic losses and adverse effects, standardize the on-site implementation steps, and reduce the error rate of projects.

Description

Technical Field

[0001] The present invention belongs to the technical field of databases, and particularly relates to a method for preventing the reuse of application system databases. Background Art

[0002] A database is a "warehouse for organizing, storing, and managing data according to a data structure", which is a collection of a large amount of data that is long-term stored in a computer, organized, sharable, and uniformly managed. A database does not exist alone. It needs to rely on certain programs. For example, a background program is one of them. A background program is a program that is not directly contacted by users. It can be any program, or it can also be a device that completes corresponding functions. Therefore, the application of background programs is very extensive.

[0003] Among them, background programs are also used in the medical field. To ensure the security of the database, the current background programs are closed-source to implementers. That is, on-site implementers can only obtain the deployment package of the background program and the corresponding database scripts. When on-site implementers successfully deploy the entire background program system in a certain hospital and need to deploy it in other hospitals again, some on-site implementers, for the sake of convenience and speed, will directly reuse the previously successfully deployed background program and database. If the configurations of the previous background program and database are not deleted cleanly, it will cause the information of the used background program system to be directly applied to the new hospital, and then cause the capital flow of the new hospital's transactions to be applied to the hospital account that has used the background program system, which is likely to cause economic losses and adverse effects to the new hospital.

[0004] Therefore, in view of the above technical problems, it is necessary to provide a method for preventing the reuse of application system databases. Summary of the Invention

[0005] The purpose of the present invention is to provide a method for preventing the reuse of application system databases to solve the problem of the reuse of data in the above background program system.

[0006] To achieve the above purpose, the technical solution provided by an embodiment of the present invention is as follows:

[0007] A method for preventing the reuse of application system databases includes the following steps:

[0008] S1. Generate a fingerprint file;

[0009] S2. Perform program startup verification;

[0010] S3. Bind the fingerprint to the configuration;

[0011] S4. Perform runtime verification.

[0012] Further, the step S1 includes the following sub-steps;

[0013] A1. Read the machine code of the hospital server;

[0014] A2. Encrypt the server machine code and the random string to generate a fingerprint file;

[0015] A3. When deploying the background program, the fingerprint file needs to be manually placed in the program directory.

[0016] Among them, the encryption method in step A2 is a reversible algorithm, such as AES.

[0017] In addition, the fingerprint file is used to decrypt the server machine code and the random string, and the random string is used as the database serial number.

[0018] Further, step S2 includes the following sub-steps:

[0019] B1. Start the background program;

[0020] B2. The background program reads and decrypts the fingerprint file, and compares the server machine code in the fingerprint file with the current server. If the match is successful, it jumps to B3; otherwise, the background program is terminated;

[0021] B3. Start the background program and read the random string in the fingerprint file into the memory.

[0022] Further, step S3 includes the following sub-steps:

[0023] C1. Pre-enter the core configuration;

[0024] C2. Enter the random string parsed from the fingerprint file into the database together with this configuration information, and make it act as a field of the configuration information;

[0025] C3. Enter the core configuration into the database.

[0026] Further, step S4 includes the following steps:

[0027] D1. Prepare to use the core configuration information;

[0028] D2. Check whether the database serial number stored in the database of the core configuration is consistent with the random string in the fingerprint file. If they are consistent, jump to D3; if they are inconsistent, prompt and terminate the background program;

[0029] D3. Allow the use of the core configuration, and the background program continues.

[0030] Compared with the prior art, the present invention has the following advantages:

[0031] Through the setting of the corresponding system, the present invention can technically avoid the situation where implementers cause economic losses and adverse effects by copying databases between projects, standardize on-site implementation steps, and reduce the error rate of projects. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0033] Figure 1 It is a block diagram of a fingerprint file generation system for a method of preventing duplicate use of an application system database in an embodiment of the present invention;

[0034] Figure 2 It is a block diagram of a program startup verification system for a method of preventing duplicate use of an application system database in an embodiment of the present invention;

[0035] Figure 3 It is a block diagram of a configuration binding fingerprint system for a method of preventing duplicate use of an application system database in an embodiment of the present invention;

[0036] Figure 4 It is a block diagram of an operation verification system for a method of preventing duplicate use of an application system database in an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0037] The present invention will be described in detail below in conjunction with the embodiments shown in the drawings. However, these embodiments do not limit the present invention, and any structural, methodical, or functional changes made by those of ordinary skill in the art based on these embodiments are included in the protection scope of the present invention.

[0038] The present invention discloses a method for preventing duplicate use of an application system database. Referring to Figures 1 - 4 as shown, it includes the following steps:

[0039] S1. Provide a tool that can obtain the server information code to on-site implementers, add a function in the company's internal system to generate a fingerprint file (encrypted) based on the server information code, and add a function in the background program to read the fingerprint file at startup and compare it with the server information code;

[0040] S2. Implementers use the tool to read the hospital server machine code, and use the company's internal system to encrypt the server machine code and a random string to generate a fingerprint file. The fingerprint file is mainly used to decrypt the server machine code and the random string, and this random string is used as the database serial number;

[0041] Among them, the encryption method is a reversible algorithm, such as AES or other methods.

[0042] S3. When the implementer deploys the background program, this fingerprint file needs to be manually placed in the background program directory;

[0043] S4. When the background program needs to be started, the background program reads and decrypts the fingerprint file, and compares the server machine code in the fingerprint file with the current server to check if they match;

[0044] Among them, if the server machine code matches the current server successfully, the background program can smoothly read the random string in the fingerprint file into the memory;

[0045] If the server machine code does not match the current server, the background program will automatically terminate.

[0046] S5. When the background program needs to operate on the key configuration information and store it in the database, the random string parsed from the fingerprint file is stored in the database together with this configuration information, making it act as a field of the configuration information, and performing core configuration binding and storage;

[0047] S6. When the background program needs to use the key configuration information, it will automatically compare whether the database serial number (random string) stored in the database for this configuration information is the same as the random string in the fingerprint file;

[0048] Among them, if the database serial number (random string) is the same as the random string in the fingerprint file, the background system is allowed to use the core configuration, and the background program continues to run;

[0049] If the database serial number (random string) is not the same as the random string in the fingerprint file, the background program will automatically terminate.

[0050] For those skilled in the art, it is obvious that the present invention is not limited to the details of the above exemplary embodiments, and without departing from the spirit or basic characteristics of the present invention, the present invention can be implemented in other specific forms. Therefore, from any point of view, the embodiments should be regarded as exemplary and non-limiting. The scope of the present invention is defined by the appended claims rather than the above description. Therefore, all changes falling within the meaning and scope of the equivalent elements of the claims are intended to be encompassed within the present invention. Any reference signs in the claims should not be regarded as limiting the claimed rights.

[0051] In addition, it should be understood that although this specification is described in terms of embodiments, not every embodiment contains only one independent technical solution. This narrative manner of the specification is only for clarity. Those skilled in the art should regard the specification as a whole, and the technical solutions in each embodiment can also be appropriately combined to form other implementations that can be understood by those skilled in the art.

Claims

1. A method for preventing repeated use of an application system database, characterized in that, it includes the following steps: S1. Generate a fingerprint file; S2. Perform program startup verification; S3. Configure and bind fingerprints; S4. Perform runtime verification; The step S1 includes the following sub-steps; A1. Read the hospital server machine code; A2. Encrypt the server machine code and a random string to generate a fingerprint file; A3. When deploying the background program, manually place the fingerprint file in the program directory; The encryption method in the step A2 is a reversible algorithm. The fingerprint file is used to decrypt the server machine code and the random string. The random string is used as the database serial number and is used to verify the consistency with the random string in the fingerprint file when performing step S4.

2. The method for preventing repeated use of an application system database according to claim 1, characterized in that, the step S2 includes the following sub-steps: B1. Start the background program; B2. The background program reads and decrypts the fingerprint file, and compares whether the server machine code in the fingerprint file matches the current server. If the match is successful, jump to B3; otherwise, terminate the background program; B3. Start the background program and read the random string in the fingerprint file into memory.

3. The method for preventing repeated use of an application system database according to claim 1, characterized in that, the step S3 includes the following sub-steps: C1. Pre-enter the core configuration information into the database; C2. Enter the random string parsed from the fingerprint file into the database together with this core configuration information, making it act as a field of the core configuration information; C3. Enter the core configuration information into the database.

4. The method for preventing repeated use of an application system database according to claim 1, characterized in that, the step S4 includes the following steps: D1. Prepare to use the core configuration information; D2. Verify whether the database serial number stored in the database of the core configuration information is consistent with the random string in the fingerprint file. If it is consistent, jump to D3; if it is inconsistent, prompt and terminate the background program; D3. Allow the use of the core configuration information, and the background program continues.

Images