Method and device for reading and writing business database, equipment, medium and program product

Abstract

The invention provides a method and a device for reading and writing a business database, electronic equipment, a medium and a computer program product, which can be applied to the technical field of big data and information security. The method comprises the following steps: in response to a registered secret key acquisition account, sending account information of the secret key acquisition account to a server; responding to the login secret key acquisition account, and sending account information of the secret key acquisition account to a server; caching binding information returned by the server side server; sending the query instruction and the binding information to a service database; in response to the fact that the business database verifies that the binding information is consistent with the filing binding information, receiving a query result returned by the business database; the data change demand and the binding information are sent to the server side server, the data change demand comprises data change content, and when the server side server verifies that the received binding information is consistent with the stored binding information, the data change content is written into the service database.

Description

Technical Field

[0001] The present disclosure relates to the field of big data and information security technology, and more specifically, to a method, device, electronic device, medium and computer program product for reading and writing a business database. Background Art

[0002] In traditional website applications, users usually interact directly with the website server, and the website server interacts directly with the database server. The website server is responsible for security verification and information conversion to ensure that users' access to data is legally authorized; except for some special fields, the data in the database server is usually stored in plain text and is restricted to authorized website servers. Existing query operations rely on the website server to implement forwarding and data conversion, consuming expensive server computing resources and bandwidth resources. Summary of the invention

[0003] In view of this, the present disclosure provides a method, device, electronic device, computer-readable storage medium and computer program product for reading and writing a business database, which saves computing resources and bandwidth resources of a service-side server.

[0004] One aspect of the present disclosure provides a method for reading and writing to a business database, which is applied to a client server and includes: in response to registering a key acquisition account, sending account information of the key acquisition account to a server-side server, wherein the account information includes a unique address of the account, and when the server-side server receives the account information in response to registering the key acquisition account, a unique key is bound to the unique address of the account, and the information is stored as binding information, and the binding information is sent to a business database for filing, and the information is stored in the business database as filed binding information; in response to logging into the key acquisition account, sending the account information of the key acquisition account to the server-side server; caching the binding information returned by the server-side server; sending a query instruction and the binding information to the business database; in response to the business database verifying that the binding information is consistent with the filed binding information, receiving the query result returned by the business database; sending a data change request and the binding information to the server-side server, wherein the data change request includes data change content, and when the server-side server verifies that the received binding information is consistent with the stored binding information, the data change content is written into the business database.

[0005] According to the method for reading and writing business databases in the embodiment of the present disclosure, in response to registering a secret key to obtain an account, the account information of the secret key to obtain an account is sent to the server-side server, wherein the account information includes a unique address of the account, and when the server-side server receives the account information in response to registering a secret key to obtain an account, a unique secret key is bound to the unique address of the account, and the binding information is stored as binding information, and the binding information is sent to the business database for record, and the binding information is stored in the business database as record binding information; in response to logging in to obtain an account with a secret key, the account information of the secret key to obtain an account is sent to the server-side server; the binding information returned by the server-side server is cached; the query instruction and the binding information are sent to the business database; in response to the business database verifying that the binding information is consistent with the record binding information, the query result returned by the business database is received; the data change requirement and the binding information are sent to the server-side server, wherein the data change requirement includes the data change content, and when the server-side server verifies that the received binding information is consistent with the stored binding information, the data change content is written into the business database. It can be understood that the server-side server of the present disclosure stores the binding information when registering, and after registration, the user only needs to log in to the secret key to obtain an account on the client server to obtain the binding information with a unique secret key. Through the unique key, the client server can directly read the data in the business database. Under the premise of ensuring access security, there is no need to rely on the server to implement data forwarding and data conversion, thereby saving the computing resources and bandwidth resources of the server.

[0006] In some embodiments, in response to the business database verifying that the binding information is consistent with the registered binding information, the step of receiving the query result returned by the business database includes: in response to the business database verifying that the binding information is consistent with the registered binding information, receiving the encrypted query result returned by the business database after encrypting the query result using the unique key in the binding information; the method also includes: decrypting the encrypted query result using the unique key in the binding information.

[0007] Another aspect of the present disclosure provides a method for reading and writing to a business database, which is applied to a service-side server, including: in response to registering a key acquisition account, when the account information of the key acquisition account is received, binding a unique key to the account unique address of the account information, storing it as binding information, sending the binding information to the business database for filing, and storing it in the business database as filed binding information; in response to logging into a key acquisition account, when the account information of the key acquisition account is received, sending the binding information to a client server; receiving a data change request and binding information sent by the client server, wherein the data change request includes data change content; and when verifying that the received binding information is consistent with the stored binding information, writing the data change content into the business database.

[0008] According to the method for reading and writing business databases of the embodiments of the present disclosure, in response to registering a key acquisition account, when receiving the account information of the key acquisition account, a unique key is bound to the account unique address of the account information, stored as binding information, and the binding information is sent to the business database for record, and stored in the business database as record binding information; in response to logging in to a key acquisition account, when receiving the account information of the key acquisition account, the binding information is sent to the client server; the data change request and binding information sent by the client server are received, wherein the data change request includes the data change content; when verifying that the received binding information is consistent with the stored binding information, the data change content is written to the business database. The server-side server of the present disclosure binds a unique key to the account information of the key acquisition account and stores it, so that the client server can directly access the business database after caching the unique key, and under the premise of ensuring access security, there is no need to rely on the server-side server to implement data forwarding and data conversion, thereby saving the computing resources and bandwidth resources of the server-side server. The service-side server of the present disclosure can also receive data change requirements and binding information sent by the client server, and when verifying that the received binding information is consistent with the stored binding information, write the data change content into the business database, thereby assisting the client server in writing data into the business database.

[0009] In some embodiments, in response to registering a key acquisition account, when the account information of the key acquisition account is received, a unique key is bound to the account unique address of the account information and stored as binding information, and the binding information is sent to a business database for filing, and stored in the business database as filed binding information. The steps include: in response to registering a key acquisition account, when the account information of the key acquisition account is received, a unique key is bound to the account unique address of the account information as binding information; the binding information is stored in a user authentication database; the binding information is sent to a business database for filing, and stored in the business database as filed binding information; in response to logging in to a key acquisition account, when the account information of the key acquisition account is received, the step of sending the binding information to a client server includes: in response to logging in to a key acquisition account, when the account information of the key acquisition account is received, the binding information is retrieved from the user authentication database, and the binding information is sent to the client server.

[0010] In some embodiments, when verifying that the received binding information is consistent with the stored binding information, the step of writing the data change content into the business database includes: when verifying that the received binding information is consistent with the stored binding information, writing the data change content as plain text data into the business database.

[0011] In some embodiments, when it is verified that the received binding information is consistent with the stored binding information, the step of writing the data change content into the business database also includes: encrypting the data change content using the unique key of the binding information to obtain ciphertext data; and writing the ciphertext data into the business database.

[0012] Another aspect of the present disclosure provides a method for reading and writing to a business database, including: in response to registering a secret key acquisition account, the client server sends the account information of the secret key acquisition account to the server server, wherein the account information includes a unique address of the account; the server receives the account information, binds a unique secret key to the unique address of the account as binding information, sends the binding information to a user authentication database for storage, sends the binding information to a business database for filing, and stores it in the business database as filing binding information; in response to logging in to the secret key acquisition account, the client server sends the account information of the secret key acquisition account to the server server; the server receives the account information, and retrieves the secret key according to the unique address of the account. the corresponding binding information in the authentication database; the server-side server returns the binding information to the client server; the client server caches the binding information returned by the server-side server; the client server sends the query instruction and the binding information to the business database; in response to the business database verifying that the binding information is consistent with the registered binding information, the client server receives the query result returned by the business database; the client server sends the data change request and the binding information to the server-side server, wherein the data change request includes the data change content; when the server-side server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the received data change content is written into the business database.

[0013] According to the method for reading and writing to a business database in an embodiment of the present disclosure, in response to a registration key acquisition account, the client server sends the account information of the key acquisition account to the server-side server, wherein the account information includes a unique address of the account; the server-side server receives the account information, binds a unique key to the unique address of the account, sends the binding information to the user authentication database for storage as binding information, sends the binding information to the business database for filing, and stores it in the business database as filing binding information; in response to a login key acquisition account, the client server sends the account information of the key acquisition account to the server-side server; the server-side server receives the account information, calls the unique address of the account according to the unique address of the account, and sends the binding information to the business database for filing, and stores it in the business database as filing binding information; Get the corresponding binding information in the authentication database; the server returns the binding information to the client server; the client server caches the binding information returned by the server; the client server sends the query instruction and binding information to the business database; in response to the business database verifying that the binding information is consistent with the registered binding information, the client server receives the query result returned by the business database; the client server sends the data change demand and binding information to the server, wherein the data change demand includes the data change content; when the server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the received data change content is written into the business database. It can be understood that the server of the present disclosure stores the binding information when registering. After registration, the user only needs to log in to the client server to obtain the account with the secret key to obtain the binding information with the unique secret key. Through the unique secret key, the client server can directly read the data in the business database. Under the premise of ensuring access security, there is no need to rely on the server to implement data forwarding and data conversion, thereby saving the computing resources and bandwidth resources of the server. The server of the present disclosure can also receive the data change requirements and binding information sent by the client server, and when verifying that the received binding information is consistent with the stored binding information, write the data change content into the business database, thereby assisting the client server to write data into the business database. The present disclosure uses the user authentication database to store the binding information, thereby alleviating the storage pressure of the server of the server, and further saving the computing resources and bandwidth resources of the server of the server.

[0014] In some embodiments, when the service-side server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the step of writing the received data change content into the business database includes: when the service-side server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the step of writing the received data change content into the business database as plain text data.

[0015] In some embodiments, when the service-side server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the step of writing the received data change content into the business database also includes: the service-side server uses the unique key of the binding information to encrypt the data change content to obtain ciphertext data; the service-side server writes the ciphertext data into the business database.

[0016] Another aspect of the present disclosure provides a device for reading and writing a business database, which is applied to a client server, and the device includes: a first sending module, the first sending module is used to execute the acquisition of an account in response to a registration key, and send the account information of the key acquisition account to the server-side server, wherein the account information includes a unique address of the account, and when the server-side server receives the account information in response to the registration key acquisition account, a unique key is bound to the unique address of the account, and the binding information is stored, and the binding information is sent to the business database for filing, and the binding information is stored in the business database as filing binding information; a second sending module, the second sending module is used to execute the acquisition of an account in response to a login key, and send the account information of the key acquisition account to the server-side server. server; a cache module, the cache module is used to execute caching of the binding information returned by the service-side server; a third sending module, the third sending module is used to execute sending the query instruction and the binding information to the business database; a first receiving module, the first receiving module is used to execute in response to the business database verifying that the binding information is consistent with the registered binding information, and receiving the query result returned by the business database; a fourth sending module, the fourth sending module is used to execute sending the data change request and the binding information to the service-side server, wherein the data change request includes data change content, and when the service-side server verifies that the received binding information is consistent with the stored binding information, the data change content is written into the business database.

[0017] Another aspect of the present disclosure provides a read-write device for a business database, which is applied to a service-side server, and the device includes: a binding module, wherein the binding module is used to execute, in response to registering a key acquisition account, when the account information of the key acquisition account is received, bind a unique key to the account unique address of the account information, store the binding information, send the binding information to the business database for filing, and store the binding information in the business database as filed binding information; a fifth sending module, wherein the fifth sending module is used to execute, in response to logging into the key acquisition account, when the account information of the key acquisition account is received, send the binding information to the client server; a second receiving module, wherein the second receiving module is used to execute receiving data change requirements and binding information sent by the client server, wherein the data change requirements include data change content; a writing module, wherein when the writing module is used to verify that the received binding information is consistent with the stored binding information, the data change content is written into the business database.

[0018] Another aspect of the present disclosure provides an electronic device, comprising one or more processors and one or more memories, wherein the memories are used to store executable instructions, and when the executable instructions are executed by the processors, the above-mentioned method is implemented.

[0019] Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the above method when executed.

[0020] Another aspect of the present disclosure provides a computer program product, comprising a computer program, wherein the computer program comprises computer executable instructions, and the instructions are used to implement the method as described above when executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0022] Figure 1 An exemplary system architecture to which the method and apparatus according to an embodiment of the present disclosure can be applied is schematically shown;

[0023] Figure 2 A flowchart of a method for reading and writing a business database according to an embodiment of the present disclosure is schematically shown, and a device for reading and writing a business database is applied to a client server;

[0024] Figure 3 A flowchart of a method for reading and writing a business database according to an embodiment of the present disclosure is schematically shown, and a device for reading and writing a business database is applied to a service-side server;

[0025] Figure 4 A flowchart schematically illustrates the steps of, in response to registering a key acquisition account, when receiving account information of the key acquisition account, binding a unique key to the account unique address of the account information, storing it as binding information, sending the binding information to a business database for filing, and storing it in the business database as filing binding information according to an embodiment of the present disclosure;

[0026] Figure 5 A flowchart schematically illustrates the steps of writing data changes into a business database when verifying that received binding information is consistent with stored binding information according to an embodiment of the present disclosure;

[0027] Figure 6 A flowchart of a method for reading and writing a business database according to an embodiment of the present disclosure is schematically shown;

[0028] Figure 7 A block diagram of a device for reading and writing a business database according to an embodiment of the present disclosure is schematically shown, and the device for reading and writing a business database is applied to a client server;

[0029] Figure 8 A block diagram of a device for reading and writing a business database according to an embodiment of the present disclosure is schematically shown, and the device for reading and writing a business database is applied to a service-side server;

[0030] Fig. 9 A block diagram of an electronic device according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0031] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0032] In the technical solution of the present disclosure, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0033] In the scenario of using personal information for automated decision-making, the methods, devices, and systems provided by the embodiments of the present disclosure provide users with corresponding operation portals for users to choose to agree or reject the automated decision-making results; if the user chooses to reject, the expert decision-making process will be entered. The expression "automated decision-making" here refers to the activity of automatically analyzing and evaluating a person's behavioral habits, interests and hobbies, or economic, health, credit status, etc. through computer programs, and making decisions. The expression "expert decision-making" here refers to the activity of making decisions by people who specialize in a certain field, have specialized experience, knowledge and skills, and have reached a certain level of professionalism.

[0034] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0035] When using expressions such as "at least one of A, B or C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B or C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). The terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, features defined as "first" and "second" may explicitly or implicitly include one or more of the said features.

[0036] In traditional website applications, users usually interact directly with the website server, and the website server interacts directly with the database server. The website server is responsible for security verification and information conversion to ensure that users' access to data is legally authorized; except for some special fields, the data in the database server is usually stored in plain text and is restricted to authorized website servers. Existing query operations rely on the website server to implement forwarding and data conversion, consuming expensive server computing resources and bandwidth resources.

[0037] The embodiments of the present disclosure provide a method, device, electronic device, computer-readable storage medium and computer program product for reading and writing a business database. Applied to a client server. The method for reading and writing a business database includes: in response to registering a secret key to obtain an account, sending the account information of the secret key acquisition account to a server-side server, wherein the account information includes a unique address of the account, when the server-side server receives the account information in response to registering a secret key to obtain an account, binding a unique secret key to the unique address of the account, storing it as binding information, sending the binding information to the business database for record, and storing it in the business database as record binding information; in response to logging in to obtain an account, sending the account information of the secret key acquisition account to the server-side server; caching the binding information returned by the server-side server; sending the query instruction and the binding information to the business database; in response to the business database verifying that the binding information is consistent with the record binding information, receiving the query result returned by the business database; sending the data change requirement and the binding information to the server-side server, wherein the data change requirement includes the data change content, and when the server-side server verifies that the received binding information is consistent with the stored binding information, the data change content is written into the business database.

[0038] It should be noted that the reading and writing methods, devices, electronic devices, computer-readable storage media and computer program products of the business database disclosed in the present invention can be used in the fields of big data and information security technology, and can also be used in any field other than the fields of big data and information security technology, such as the financial field. The field of the present invention is not limited here.

[0039] Figure 1 The exemplary system architecture 100 to which the method, device, electronic device, computer-readable storage medium and computer program product for reading and writing business databases according to the embodiments of the present disclosure can be applied is schematically shown. It should be noted that: Figure 1 What is shown is merely an example of a system architecture to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0040] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 is used to provide a medium for a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0041] The user can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client server applications can be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email client servers, social platform software, etc. (only for example).

[0042] The first terminal device 101, the second terminal device 102, and the third terminal device 103 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0043] The server 105 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0044] It should be noted that the method for reading and writing the business database provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the device for reading and writing the business database provided in the embodiment of the present disclosure can generally be set in the server 105. The method for reading and writing the business database provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105. Accordingly, the device for reading and writing the business database provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105.

[0045] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to the implementation requirements.

[0046] The following will be based on Figure 1 The scene described by Figure 2~Figure 6 The method for reading and writing a business database according to an embodiment of the present disclosure is described in detail.

[0047] Figure 2The flowchart of the method for reading and writing a business database according to an embodiment of the present disclosure is schematically shown. The method for reading and writing a business database is applied to a client server.

[0048] like Figure 2 As shown, the method for reading and writing a business database in this embodiment includes operations S210 to S260.

[0049] In operation S210, in response to registering a secret key acquisition account, the account information of the secret key acquisition account is sent to the service-side server, wherein the account information includes the account unique address. When the service-side server receives the account information in response to registering a secret key acquisition account, a unique secret key is bound to the account unique address and stored as binding information. The binding information is sent to the business database for filing and stored in the business database as filed binding information.

[0050] In operation S220, in response to logging into the key acquisition account, the account information of the key acquisition account is sent to the service-side server.

[0051] In operation S230, the binding information returned by the service-side server is cached.

[0052] It is understandable that when you do not have a secret key acquisition account, you need to register a secret key acquisition account first. When registering a secret key acquisition account, the server will store the binding information and send it to the business database for record. When you have a secret key acquisition account, you do not need to perform operation S210, just log in to the secret key acquisition account. When logging in to the secret key acquisition account, the client server will send the account information to the server. The server can retrieve the corresponding binding information based on the account unique address of the account information, and return the retrieved binding information to the client server, so the client server can cache the binding information returned by the server.

[0053] It is understandable that, in the case of not having a key acquisition account, by performing operations S210 to S230, it is possible to cache the client server with unique key binding information. In the case of having a key acquisition account, by performing operations S220 and S230, it is possible to cache the client server with unique key binding information.

[0054] In operation S240, the query instruction and the binding information are sent to the business database.

[0055] It should be noted that the query instructions include manually constructed query instructions, and the query instructions can be obtained in response to manual input; the query instructions can also include query instructions generated according to the obtained query requirements, and the query requirements can be obtained in response to manual input, and the query requirements can be represented by natural language.

[0056] In operation S250, in response to the business database verifying that the binding information is consistent with the registered binding information, a query result returned by the business database is received.

[0057] In other examples, in response to the business database verifying that the binding information is inconsistent with the registered binding information, the business database will not send the query result to the client server, and the client server cannot obtain the query result returned by the business database.

[0058] It is understandable that, under the premise that the client server caches the unique key binding information, the client server can directly read the data in the business database through operations S240 and S250.

[0059] In operation S260, the data change request and binding information are sent to the service-side server, wherein the data change request includes the data change content. When the service-side server verifies that the received binding information is consistent with the stored binding information, the data change content is written into the business database. It is understandable that the data change content may include new data and / or replacement data. When writing new data into the business database, the new data can be directly added to the business database; when writing replacement data into the business database, the replaced data needs to be deleted, and the replacement data is written in the location of the replaced data. Operation S260 can realize that the client server writes data into the business database.

[0060] According to the method for reading and writing business databases in the embodiment of the present disclosure, in response to registering a secret key to obtain an account, the account information of the secret key to obtain an account is sent to the server-side server, wherein the account information includes a unique address of the account, and when the server-side server receives the account information in response to registering a secret key to obtain an account, a unique secret key is bound to the unique address of the account, and the binding information is stored as binding information, and the binding information is sent to the business database for record, and the binding information is stored in the business database as record binding information; in response to logging in to obtain an account with a secret key, the account information of the secret key to obtain an account is sent to the server-side server; the binding information returned by the server-side server is cached; the query instruction and the binding information are sent to the business database; in response to the business database verifying that the binding information is consistent with the record binding information, the query result returned by the business database is received; the data change requirement and the binding information are sent to the server-side server, wherein the data change requirement includes the data change content, and when the server-side server verifies that the received binding information is consistent with the stored binding information, the data change content is written into the business database. It can be understood that the server-side server of the present disclosure stores the binding information when registering, and after registration, the user only needs to log in to the secret key to obtain an account on the client server to obtain the binding information with a unique secret key. Through the unique key, the client server can directly read the data in the business database. Under the premise of ensuring access security, there is no need to rely on the server to implement data forwarding and data conversion, thereby saving the computing resources and bandwidth resources of the server.

[0061] According to some embodiments of the present disclosure, operation S250, in response to the business database verifying that the binding information is consistent with the registered binding information, the step of receiving the query result returned by the business database includes operation S251.

[0062] In operation S250, in response to the business database verifying that the binding information is consistent with the registered binding information, an encrypted query result returned by the business database after encrypting the query result using a unique key in the binding information is received.

[0063] The method for reading and writing the business database also includes operation S001: decrypting the encrypted query result using the unique key in the binding information.

[0064] It is understandable that before the business database returns the query result to the client server, it can encrypt the query result using the unique key corresponding to the client server and return the encrypted query result to the client server. After the client server obtains the encrypted query result, it can decrypt the encrypted query result using the cached unique key. Through the method disclosed in the present invention, the data returned by the business database to the client server are all encrypted data. If it is a legitimate client server, it can be decrypted with the cached unique key; if it is an illegitimate client server, the data cannot be decrypted. Therefore, it can avoid the storage of a large amount of data in the database server in plain text in the prior art, which may cause large-scale information leakage once a security vulnerability occurs.

[0065] Figure 3 The flowchart of the method for reading and writing a business database according to an embodiment of the present disclosure is schematically shown. The method for reading and writing a business database is applied to a service-side server.

[0066] like Figure 3 As shown, the method for reading and writing a business database in this embodiment includes operations S310 to S340.

[0067] In operation S310, in response to registering a key acquisition account, when account information of the key acquisition account is received, a unique key is bound to the account unique address of the account information, stored as binding information, and the binding information is sent to the business database for filing and stored in the business database as filed binding information.

[0068] In operation S320, in response to logging into the key acquisition account, when account information of the key acquisition account is received, binding information is sent to the client server.

[0069] It is understandable that when you do not have a secret key acquisition account, you need to register a secret key acquisition account first. When registering a secret key acquisition account, the server will store the binding information and send it to the business database for record. When you have a secret key acquisition account, you do not need to perform operation S310, just log in to the secret key acquisition account. When logging in to the secret key acquisition account, the client server will send the account information to the server. The server can retrieve the corresponding binding information based on the account unique address of the account information, and return the retrieved binding information to the client server, so the client server can cache the binding information returned by the server.

[0070] It is understandable that, in the case of not having a key acquisition account, by performing operations S310 and S320, it is possible to cache the client server with unique key binding information. In the case of having a key acquisition account, by performing operation S320, it is possible to cache the client server with unique key binding information.

[0071] In operation S330, a data change request and binding information sent by the client server are received, wherein the data change request includes data change content.

[0072] In operation S340, when it is verified that the received binding information is consistent with the stored binding information, the data change content is written into the business database.

[0073] It is understandable that the data change content may include new data and / or replacement data. When writing new data into the business database, the new data can be directly added to the business database; when writing replacement data into the business database, the replaced data needs to be deleted and the replacement data needs to be written in the location of the replaced data. Through operations S330 and S340, data can be written into the business database while ensuring data security.

[0074] According to the method for reading and writing business databases of the embodiments of the present disclosure, in response to registering a key acquisition account, when receiving the account information of the key acquisition account, a unique key is bound to the account unique address of the account information, stored as binding information, and the binding information is sent to the business database for record, and stored in the business database as record binding information; in response to logging in to a key acquisition account, when receiving the account information of the key acquisition account, the binding information is sent to the client server; the data change request and binding information sent by the client server are received, wherein the data change request includes the data change content; when verifying that the received binding information is consistent with the stored binding information, the data change content is written to the business database. The server-side server of the present disclosure binds a unique key to the account information of the key acquisition account and stores it, so that the client server can directly access the business database after caching the unique key, and under the premise of ensuring access security, there is no need to rely on the server-side server to implement data forwarding and data conversion, thereby saving the computing resources and bandwidth resources of the server-side server. The service-side server of the present disclosure can also receive data change requirements and binding information sent by the client server, and when verifying that the received binding information is consistent with the stored binding information, write the data change content into the business database, thereby assisting the client server in writing data into the business database.

[0075] According to some embodiments of the present disclosure, Figure 4 As shown, operation S310, in response to registering a key acquisition account, when receiving the account information of the key acquisition account, binds a unique key to the account unique address of the account information, stores it as binding information, sends the binding information to the business database for filing, and stores it in the business database as filed binding information, including operations S311 to S313.

[0076] In operation S311, in response to registering a key acquisition account, when account information of the key acquisition account is received, a unique key is bound to an account unique address of the account information as binding information.

[0077] In operation S312, the binding information is stored in a user authentication database.

[0078] In operation S313, the binding information is sent to the business database for filing and is stored in the business database as filed binding information.

[0079] Operation S320, in response to logging into a key acquisition account and receiving account information of a key acquisition account, sends binding information to a client server, including operation S321: in response to logging into a key acquisition account and receiving account information of a key acquisition account, retrieve binding information from a user authentication database and send the binding information to a client server.

[0080] Operations S311 to S313 can facilitate the steps of binding a unique key to the unique address of the account information when receiving the account information of the key acquisition account in response to registering the key acquisition account, storing the binding information, sending the binding information to the business database for record, and storing the binding information in the business database as the record binding information. Operation S321 can facilitate the steps of sending the binding information to the client server when receiving the account information of the key acquisition account in response to logging in the key acquisition account. The user authentication database is used to store the binding information, thereby alleviating the storage pressure of the server on the server side and further saving the computing resources and bandwidth resources of the server on the server side.

[0081] According to some embodiments of the present disclosure, Figure 5 As shown, when operation S340 verifies that the received binding information is consistent with the stored binding information, the step of writing the data change content into the business database includes operation S341: when the received binding information is verified to be consistent with the stored binding information, the data change content is written into the business database as plain text data. Operation S341 can realize writing the data change content into the business database as plain text data under the premise of ensuring data security.

[0082] According to some embodiments of the present disclosure, Figure 5 As shown, when operation S340 verifies that the received binding information is consistent with the stored binding information, the step of writing the data change content into the business database also includes operation S342 and operation S343.

[0083] In operation S342, the data change content is encrypted using the unique key of the binding information to obtain ciphertext data.

[0084] In operation S343, the ciphertext data is written into the business database.

[0085] Through operations S342 and S343, the data change content can be written into the business database as ciphertext data while ensuring data security.

[0086] Figure 6 The flowchart of the method for reading and writing a business database according to an embodiment of the present disclosure is schematically shown.

[0087] like Figure 6 As shown, the method for reading and writing a business database in this embodiment includes operations S401 to S410.

[0088] In operation S401, in response to registering a key acquisition account, the client server sends account information of the key acquisition account to the server, wherein the account information includes a unique address of the account.

[0089] In operation S402, the service-side server receives the account information, binds a unique key to the unique address of the account as binding information, sends the binding information to the user authentication database for storage, sends the binding information to the business database for filing, and stores it in the business database as filing binding information.

[0090] In operation S403, in response to logging into the key acquisition account, the client server sends account information of the key acquisition account to the service server.

[0091] In operation S404, the service-side server receives the account information and retrieves the corresponding binding information in the authentication database according to the unique address of the account.

[0092] In operation S405, the service-side server returns the binding information to the client server.

[0093] In operation S406, the client server caches the binding information returned by the service server.

[0094] It is understandable that when you do not have a secret key acquisition account, you need to register a secret key acquisition account first. When registering a secret key acquisition account, the server will store the binding information and send it to the business database for record. When you have a secret key acquisition account, you do not need to perform operations S401 and S402, just log in to the secret key acquisition account. When logging in to the secret key acquisition account, the client server will send the account information to the server. The server can retrieve the corresponding binding information based on the account unique address of the account information, and return the retrieved binding information to the client server, so the client server can cache the binding information returned by the server.

[0095] It is understandable that, in the case of not having a key acquisition account, by executing operations S401 to S406, it is possible to cache the client server with unique key binding information. In the case of having a key acquisition account, by executing operations S403 to S406, it is possible to cache the client server with unique key binding information.

[0096] In operation S407, the client server sends the query instruction and the binding information to the business database. It should be noted that the query instruction includes a manually constructed query instruction, which can be obtained in response to manual input; the query instruction can also include a query instruction generated according to the obtained query requirements, which can be obtained in response to manual input, and the query requirements can be represented by natural language.

[0097] In operation S408, in response to the business database verifying that the binding information is consistent with the registered binding information, the client server receives the query result returned by the business database.

[0098] In other examples, in response to the business database verifying that the binding information is inconsistent with the registered binding information, the business database will not send the query result to the client server, and the client server cannot obtain the query result returned by the business database.

[0099] It can be understood that, under the premise that the client server caches the unique key binding information, through operations S407 and S408, the client server can directly read data in the business database.

[0100] In operation S409, the client server sends the data change request and binding information to the service server, wherein the data change request includes data change content.

[0101] In operation S410, when the service-side server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the received data change content is written into the business database. It is understandable that the data change content may include new data and / or replacement data. When writing the new data into the business database, the new data can be directly added to the business database; when writing the replacement data into the business database, the replaced data needs to be deleted and the replacement data is written in the location of the replaced data. Operations S409 and S410 can realize that the client server writes data into the business database.

[0102] According to the method for reading and writing to a business database in an embodiment of the present disclosure, in response to a registration key acquisition account, the client server sends the account information of the key acquisition account to the server-side server, wherein the account information includes a unique address of the account; the server-side server receives the account information, binds a unique key to the unique address of the account, sends the binding information to the user authentication database for storage as binding information, sends the binding information to the business database for filing, and stores it in the business database as filing binding information; in response to a login key acquisition account, the client server sends the account information of the key acquisition account to the server-side server; the server-side server receives the account information, calls the unique address of the account according to the unique address of the account, and sends the binding information to the business database for filing, and stores it in the business database as filing binding information; Get the corresponding binding information in the authentication database; the server returns the binding information to the client server; the client server caches the binding information returned by the server; the client server sends the query instruction and binding information to the business database; in response to the business database verifying that the binding information is consistent with the registered binding information, the client server receives the query result returned by the business database; the client server sends the data change demand and binding information to the server, wherein the data change demand includes the data change content; when the server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the received data change content is written into the business database. It can be understood that the server of the present disclosure stores the binding information when registering. After registration, the user only needs to log in to the client server to obtain the account with the secret key to obtain the binding information with the unique secret key. Through the unique secret key, the client server can directly read the data in the business database. Under the premise of ensuring access security, there is no need to rely on the server to implement data forwarding and data conversion, thereby saving the computing resources and bandwidth resources of the server. The server of the present disclosure can also receive the data change requirements and binding information sent by the client server, and when verifying that the received binding information is consistent with the stored binding information, write the data change content into the business database, thereby assisting the client server to write data into the business database. The present disclosure uses the user authentication database to store the binding information, thereby alleviating the storage pressure of the server of the server, and further saving the computing resources and bandwidth resources of the server of the server.

[0103] According to some embodiments of the present disclosure, when the service-side server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the step of writing the received data change content into the business database includes operation S411: when the service-side server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the data change content is written into the business database as plain text data. Operation S411 can be used to write the data change content into the business database as plain text data while ensuring data security.

[0104] According to some embodiments of the present disclosure, when the service-side server verifies in operation S410 that the received binding information is consistent with the binding information stored in the user authentication database, the step of writing the received data change content into the business database also includes operation S412 and operation S413.

[0105] In operation S412, the server-side server encrypts the data change content using the unique key of the binding information to obtain ciphertext data.

[0106] Operation S413: The service-side server writes the ciphertext data into the business database.

[0107] Through operations S412 and S413, it is possible to write the data change content as ciphertext data into the business database while ensuring data security.

[0108] The following describes in detail a method for reading and writing a business database according to an embodiment of the present disclosure. It is worth noting that the following description is only an exemplary description and is not a specific limitation of the present disclosure.

[0109] The present disclosure provides a secure and open method for reading and writing business databases, which can improve the utilization rate of computing resources and bandwidth resources of the service-side server, and quickly realize data sharing and transparency on the client server under the premise of ensuring data security. In order to control access security and ensure data consistency, the user registration and login of the website application and the write operation to the database still use the traditional website application architecture, that is, the user (browser) directly interacts with the website service-side server, and the website service-side server directly interacts with the business database; but for the read operation of business data, the user (browser) can directly interact with the business database and parse the user's data by using the symmetric encryption key created during user registration (or subsequently allocated). The specific scheme is described as follows.

[0110] 1. After the user successfully registers, a unique symmetric encryption key will be created and stored in the user authentication database. Each subsequent time the user logs in, the key will be obtained and cached in the user's browser.

[0111] 2. Except for public data, the website server uses the corresponding user's symmetric encryption key to encrypt each data field when writing user data to the business database, writes plaintext data into the plaintext table, and writes ciphertext data into the ciphertext table. The data in the plaintext table and the ciphertext table correspond one-to-one through a unique address.

[0112] 3. Users (browsers) can generate query instructions for accessing the database according to actual access needs and directly query the business database. Business data uses the plaintext table to execute query instructions to query data and returns the ciphertext table data corresponding to the query results.

[0113] 4. The user (browser) uses the cached encryption key to decrypt the returned query results (ciphertext table data) and obtain the plaintext query results, which can be used for subsequent business data processing.

[0114] 5. Under normal business processes, users will only query user data (public data is not encrypted), so the user's secret key can decrypt all returned data; if a malicious user constructs a query statement to query other users' data, since the query result is encrypted by the corresponding user's secret key, the malicious user will not be able to use his own secret key to decrypt it, and the query result is meaningless to the malicious user.

[0115] 6. After obtaining their own encryption keys, advanced users can directly construct query instructions to query user data as needed. Advanced users can directly obtain structured data and organize and analyze data according to their own needs.

[0116] Through the present disclosure, a readable access service of a business database directly open to customers can be realized based on the traditional architecture mode under the premise of ensuring the security of user data. The effects are mainly reflected in: users can directly query and access the database, and a large number of complex data analysis and processing can directly use the computing resources on the user side, thereby improving the utilization rate of server computing resources and bandwidth resources; website applications developed based on this invention all natively support advanced user-defined queries, highly support plug-in secondary development, and the development of edge derivative applications, which is also conducive to information sharing and transparency under the current wave of big data and artificial intelligence; the data security of the business database is based on modern public encryption algorithms and the user's unique encryption key, and the architecture is direct and simple. As long as the user key is not leaked, the user data security can be guaranteed and unauthorized access can be effectively prevented.

[0117] Based on the above-mentioned method for reading and writing a business database, the present disclosure also provides a device for reading and writing a business database. The device for reading and writing a business database is applied to an application client server. Figure 7 The reading and writing devices of the business database are described in detail.

[0118] Figure 7 The structural block diagram of the device for reading and writing a business database according to an embodiment of the present disclosure is schematically shown.

[0119] The device 10 for reading and writing a business database comprises a first sending module 11 , a second sending module 12 , a buffer module 13 , a third sending module 14 , a first receiving module 15 and a fourth sending module 16 .

[0120] The first sending module 11 is used to execute a response to registering a secret key to obtain an account, and send the account information of the secret key obtaining account to the service-end server, wherein the account information includes the account unique address. When the service-end server receives the account information in response to registering a secret key to obtain an account, it binds a unique secret key to the account unique address, stores it as binding information, sends the binding information to the business database for filing, and stores it in the business database as filed binding information.

[0121] The second sending module 12 is used to execute, in response to logging into the key acquisition account, sending the account information of the key acquisition account to the service end server.

[0122] The cache module 13 is used to execute the binding information returned by the cache service server.

[0123] The third sending module 14 is used to execute and send the query instruction and the binding information to the business database.

[0124] The first receiving module 15 is used for receiving the query result returned by the business database in response to the business database verifying that the binding information is consistent with the registered binding information.

[0125] The fourth sending module 16 is used to execute sending the data change request and binding information to the service server, wherein the data change request includes the data change content. When the service server verifies that the received binding information is consistent with the stored binding information, the data change content is written into the business database.

[0126] According to the reading and writing device 10 for the business database of the embodiment of the present disclosure, in response to registering a secret key acquisition account, the account information of the secret key acquisition account is sent to the server-side server, wherein the account information includes a unique address of the account, and when the server-side server receives the account information in response to registering a secret key acquisition account, a unique secret key is bound to the unique address of the account, and stored as binding information, and the binding information is sent to the business database for record, and stored in the business database as record binding information; in response to logging in to the secret key acquisition account, the account information of the secret key acquisition account is sent to the server-side server; the binding information returned by the server-side server is cached; the query instruction and the binding information are sent to the business database; in response to the business database verifying that the binding information is consistent with the record binding information, the query result returned by the business database is received; the data change requirement and the binding information are sent to the server-side server, wherein the data change requirement includes the data change content, and when the server-side server verifies that the received binding information is consistent with the stored binding information, the data change content is written into the business database. It can be understood that the server-side server of the present disclosure stores the binding information when registering, and after registration, the user only needs to log in to the secret key acquisition account on the client server to obtain the binding information with the unique secret key. Through the unique key, the client server can directly read the data in the business database. Under the premise of ensuring access security, there is no need to rely on the server to implement data forwarding and data conversion, thereby saving the computing resources and bandwidth resources of the server.

[0127] In addition, according to an embodiment of the present disclosure, any multiple modules among the first sending module 11, the second sending module 12, the buffer module 13, the third sending module 14, the first receiving module 15 and the fourth sending module 16 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module.

[0128] According to an embodiment of the present disclosure, at least one of the first sending module 11, the second sending module 12, the cache module 13, the third sending module 14, the first receiving module 15 and the fourth sending module 16 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or can be implemented in any one of the three implementation methods of software, hardware and firmware, or in an appropriate combination of any of them.

[0129] Alternatively, at least one of the first sending module 11, the second sending module 12, the cache module 13, the third sending module 14, the first receiving module 15 and the fourth sending module 16 can be at least partially implemented as a computer program module, and when the computer program module is executed, the corresponding function can be executed.

[0130] Based on the above-mentioned method for reading and writing a business database, the present disclosure also provides a device for reading and writing a business database. The device for reading and writing a business database is applied to a server at the service end. Figure 8 The reading and writing devices of the business database are described in detail.

[0131] Figure 8 The structural block diagram of the device for reading and writing a business database according to an embodiment of the present disclosure is schematically shown.

[0132] The reading and writing device 20 for the business database includes a binding module 21 , a fifth sending module 22 , a second receiving module 23 and a writing module 24 .

[0133] The binding module 21 is used to execute, in response to registering a secret key acquisition account, when receiving the account information of the secret key acquisition account, binding a unique secret key to the account unique address of the account information, storing it as binding information, sending the binding information to the business database for filing, and storing it in the business database as filed binding information.

[0134] The fifth sending module 22 is used to execute, in response to logging into the secret key acquisition account and receiving the account information of the secret key acquisition account, sending the binding information to the client server.

[0135] The second receiving module 23 is used to receive the data change request and binding information sent by the client server, wherein the data change request includes data change content.

[0136] The writing module 24 is used to write the data change content into the business database when verifying that the received binding information is consistent with the stored binding information.

[0137] According to the reading and writing device 20 for the business database of the embodiment of the present disclosure, in response to the registration of the key acquisition account, when the account information of the key acquisition account is received, a unique key is bound to the account unique address of the account information, and the binding information is stored as binding information, and the binding information is sent to the business database for record, and the binding information is stored in the business database as the record binding information; in response to the login of the key acquisition account, when the account information of the key acquisition account is received, the binding information is sent to the client server; the data change request and binding information sent by the client server are received, wherein the data change request includes the data change content; when verifying that the received binding information is consistent with the stored binding information, the data change content is written into the business database. The server of the present disclosure binds a unique key to the account information of the key acquisition account and stores it, so that the client server can directly access the business database after caching the unique key, and under the premise of ensuring access security, there is no need to rely on the server server to implement data forwarding and data conversion, thereby saving the computing resources and bandwidth resources of the server server. The service-side server of the present disclosure can also receive data change requirements and binding information sent by the client server, and when verifying that the received binding information is consistent with the stored binding information, write the data change content into the business database, thereby assisting the client server in writing data into the business database.

[0138] In addition, according to an embodiment of the present disclosure, any multiple modules among the binding module 21, the fifth sending module 22, the second receiving module 23 and the writing module 24 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module.

[0139] According to an embodiment of the present disclosure, at least one of the binding module 21, the fifth sending module 22, the second receiving module 23 and the writing module 24 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or can be implemented in any one of the three implementation methods of software, hardware and firmware, or in an appropriate combination of any of them.

[0140] Alternatively, at least one of the binding module 21, the fifth sending module 22, the second receiving module 23 and the writing module 24 may be at least partially implemented as a computer program module, and when the computer program module is executed, a corresponding function may be executed.

[0141] Fig. 9A block diagram of an electronic device suitable for implementing the above method according to an embodiment of the present disclosure is schematically shown.

[0142] like Fig. 9 As shown, the electronic device 900 according to an embodiment of the present disclosure includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage part 908 to a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a dedicated microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include an onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0143] In RAM 903, various programs and data required for the operation of electronic device 900 are stored. Processor 901, ROM 902 and RAM 903 are connected to each other via bus 904. Processor 901 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 902 and / or RAM 903. It should be noted that the program can also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0144] According to an embodiment of the present disclosure, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to the bus 904. The electronic device 900 may further include one or more of the following components connected to the input / output (I / O) interface 905: an input portion 906 including a keyboard, a mouse, etc.; an output portion 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 908 including a hard disk, etc.; and a communication portion 909 including a network interface card such as a LAN card, a modem, etc. The communication portion 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output (I / O) interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed, so that a computer program read therefrom is installed into the storage portion 908 as needed.

[0145] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0146] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 902 and / or RAM 903 described above and / or one or more memories other than ROM 902 and RAM 903.

[0147] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the method provided by the embodiment of the present disclosure.

[0148] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 901. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0149] In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of a signal on a network medium, and downloaded and installed through the communication part 909, and / or installed from a removable medium 911. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0150] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0151] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0152] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0153] It will be appreciated by those skilled in the art that the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations or combinations are not explicitly described in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0154] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A method for reading and writing a business database, applied to a client server, characterized in that: include: In response to registering a secret key acquisition account, sending account information of the secret key acquisition account to a service-side server, wherein the account information includes a unique address of the account, and in response to registering a secret key acquisition account, when the service-side server receives the account information, it binds a unique secret key to the unique address of the account, stores it as binding information, sends the binding information to a business database for record, and stores it in the business database as record binding information; In response to logging into the key acquisition account, sending account information of the key acquisition account to the service-side server; Cache the binding information returned by the server; Sending the query instruction and the binding information to the business database; In response to the business database verifying that the binding information is consistent with the registered binding information, receiving a query result returned by the business database; The data change request and the binding information are sent to the service-side server, wherein the data change request includes data change content. When the service-side server verifies that the received binding information is consistent with the stored binding information, the data change content is written into the business database.

2. The method for reading and writing a business database according to claim 1, characterized in that: In response to the business database verifying that the binding information is consistent with the registered binding information, the step of receiving the query result returned by the business database includes: In response to the business database verifying that the binding information is consistent with the registered binding information, receiving an encrypted query result returned by the business database after encrypting the query result using a unique key in the binding information; The method further includes: decrypting the encrypted query result using a unique key in the binding information.

3. A method for reading and writing a business database, applied to a service-side server, characterized in that: include: In response to registering a key acquisition account, upon receiving account information of the key acquisition account, binding a unique key to a unique address of the account information, storing the binding information as binding information, sending the binding information to a business database for record, and storing the binding information in the business database as record binding information; In response to logging into the key acquisition account, upon receiving account information of the key acquisition account, sending the binding information to the client server; Receiving a data change request and binding information sent by a client server, wherein the data change request includes data change content; When it is verified that the received binding information is consistent with the stored binding information, the data change content is written into the business database.

4. The method for reading and writing a business database according to claim 3, characterized in that: In response to registering a key acquisition account, when receiving account information of the key acquisition account, binding a unique key to the account unique address of the account information, storing it as binding information, sending the binding information to a business database for filing, and storing it in the business database as filing binding information, the steps include: In response to registering a key acquisition account, upon receiving account information of the key acquisition account, binding a unique key to a unique account address of the account information as binding information; Storing the binding information in a user authentication database; Sending the binding information to a business database for filing, and storing it in the business database as filing binding information; In response to logging into a key acquisition account, when receiving account information of the key acquisition account, the step of sending the binding information to the client server comprises: In response to logging into the key acquisition account, when the account information of the key acquisition account is received, the binding information is retrieved from the user authentication database and the binding information is sent to the client server.

5. The method for reading and writing a business database according to claim 3, characterized in that: When verifying that the received binding information is consistent with the stored binding information, the step of writing the data change content into the business database comprises: When it is verified that the received binding information is consistent with the stored binding information, the data change content is written into the business database as plain text data.

6. The method for reading and writing a business database according to claim 5, characterized in that: When verifying that the received binding information is consistent with the stored binding information, the step of writing the data change content into the business database further includes: Encrypt the data change content using the unique key of the binding information to obtain ciphertext data; The ciphertext data is written into the business database.

7. A method for reading and writing a business database, characterized in that: include: In response to registering a key acquisition account, the client server sends account information of the key acquisition account to the server, wherein the account information includes a unique address of the account; The service-side server receives the account information, binds a unique key to the unique address of the account as binding information, sends the binding information to the user authentication database for storage, sends the binding information to the business database for filing, and stores it in the business database as filing binding information; In response to logging into the key acquisition account, the client server sends account information of the key acquisition account to the service server; The service-side server receives the account information and retrieves the corresponding binding information in the authentication database according to the unique address of the account; The service-side server returns the binding information to the client server; The client server caches the binding information returned by the server; The client server sends the query instruction and the binding information to the business database; In response to the business database verifying that the binding information is consistent with the registered binding information, the client server receives the query result returned by the business database; The client server sends the data change request and the binding information to the service server, wherein the data change request includes the data change content; When the service-side server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the received data change content is written into the business database.

8. The method for reading and writing a business database according to claim 7, characterized in that: When the service-side server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the step of writing the received data change content into the business database includes: When the service-side server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the data change content is written into the business database as plain text data.

9. The method for reading and writing a business database according to claim 8, characterized in that: When the service-side server verifies that the received binding information is consistent with the binding information stored in the user authentication database, the step of writing the received data change content into the business database also includes: The service-side server uses the unique key of the binding information to encrypt the data change content to obtain ciphertext data; The service-side server writes the ciphertext data into the business database.

10. A device for reading and writing a business database, applied to a client server, characterized in that: include: A first sending module, the first sending module is used to execute in response to the registration key acquisition account, send the account information of the key acquisition account to the service-end server, wherein the account information includes the account unique address, the server responds to the registration key acquisition account, when receiving the account information, binds the unique key to the account unique address, stores it as binding information, sends the binding information to the business database for record, and stores it in the business database as record binding information; A second sending module, the second sending module is used to execute in response to logging into the secret key acquisition account, sending the account information of the secret key acquisition account to the service-end server; A cache module, the cache module is used to cache the binding information returned by the service-side server; A third sending module, the third sending module is used to execute and send the query instruction and the binding information to the business database; A first receiving module, the first receiving module is used to execute, in response to the business database verifying that the binding information is consistent with the registered binding information, receiving a query result returned by the business database; A fourth sending module, the fourth sending module is used to execute the sending of the data change request and the binding information to the service-side server, wherein the data change request includes the data change content, and when the service-side server verifies that the received binding information is consistent with the stored binding information, the data change content is written into the business database.

11. A device for reading and writing a business database, applied to a service-side server, characterized in that: include: A binding module, the binding module being used to execute, in response to registering a secret key acquisition account, upon receiving account information of the secret key acquisition account, binding a unique secret key to a unique account address of the account information, storing the binding information as binding information, sending the binding information to a business database for filing, and storing the binding information in the business database as filing binding information; a fifth sending module, configured to send the binding information to the client server when receiving the account information of the key acquisition account in response to logging into the key acquisition account; A second receiving module, the second receiving module is used to receive a data change requirement and binding information sent by a client server, wherein the data change requirement includes data change content; A writing module is used to write the data change content into the business database when verifying that the received binding information is consistent with the stored binding information.

12. An electronic device comprising: one or more processors; a storage device for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 9.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

14. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

Images