Sensitive rule configuration method, device, storage medium, and computer program product

Abstract

The embodiments of the present disclosure provide a sensitive rule configuration method, a device, a storage medium, and a computer program product, wherein a database system acquires a database operation statement, such as an SQL statement, indicating a data transfer between different data objects within the database system, and searches, according to an object identifier of a first data object before transfer, whether an existing sensitive rule for the first data object exists in an existing sensitive rule base; if the existing sensitive rule for the first data object is found, the database system generates, according to an object identifier of a second data object after transfer and a data protection policy in the existing sensitive rule for the first data object, a new sensitive rule configured for the second data object, and adds the new sensitive rule to the existing sensitive rule base. This allows a database system to effectively fend off an attack by an attacker against sensitive data, thereby ensuring the security of the database system.

Description

[0001] This disclosure relates to the field of database technology, and more particularly to a method, device, storage medium, and computer program product for configuring sensitive rules. Background: To protect sensitive data in a database system, users often configure corresponding sensitive rules. Sensitive rules define the methods for protecting sensitive data in the database system; for example, sensitive rules define de-identification algorithms or encryption algorithms for sensitive data. During the data access phase, the database system uses sensitive rules to protect the sensitive data queried by the user and returns the protected sensitive data to the user. In practical applications, attackers often design specially designed Structured Query Language (SQL) statements. After the attacker triggers the database system to execute the specially designed SQL statements, sensitive data is transferred. For example, sensitive data is copied from one data object to another, such as a database, table, or column. However, the sensitive rules configured by the user for a specific data object are only effective for that specific data object. When sensitive data in a specified data object is copied to other data objects, the sensitive rules become ineffective for those other data objects. This allows an attacker to request the database system to query sensitive data in other data objects. The database system then provides the attacker with the raw, unprotected sensitive data, rendering it outside the scope of the sensitive rules. Consequently, the database system cannot utilize these rules to protect the sensitive data, thus failing to defend against attacks and reducing its security. This invention discloses a method, apparatus, storage medium, and computer program product for configuring sensitive rules to ensure the security of a database system. This disclosure provides a method for configuring sensitive rules, including: obtaining a target database operation statement, which instructs data transfer between different data objects in a database system, the data transfer being used to transfer the data content of a first data object before the transfer to a second data object after the transfer within the database system; searching for existing sensitive rules for the first data object in an existing sensitive rule library based on the object identifier of the first data object before the transfer; if existing sensitive rules for the first data object are found, generating new sensitive rules for the second data object based on the object identifier of the second data object after the transfer and the data protection policy in the existing sensitive rules of the first data object, and adding the new sensitive rules to the existing sensitive rule library.This disclosure provides an electronic device, including: a memory and a processor; the memory for storing a computer program; and a processor coupled to the memory for executing the computer program to perform steps in a sensitive rule configuration method. This disclosure also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to implement steps in a sensitive rule configuration method. Furthermore, this disclosure provides a computer program product, including a computer program / instruction, which, when executed by a processor, enables the processor to implement steps in a sensitive rule configuration method. In this disclosure, a database system, in response to a received database operation statement such as an SQL statement instructing data flow between different data objects in the database system, searches an existing sensitive rule library for an existing sensitive rule for the first data object based on the object identifier of the first data object before the flow. If an existing sensitive rule for the first data object is found, a new sensitive rule is generated for the second data object based on the object identifier of the second data object after the flow and the data protection policy in the existing sensitive rule of the first data object, and the new sensitive rule is added to the existing sensitive rule library. Therefore, even if an attacker designs database operation statements such as SQL statements to initiate data flow requests, as long as the data object before the flow is configured with sensitive rules, the database system can still configure sensitive rules for the data object after the flow. This ensures that sensitive data in the data object after the flow cannot escape the sensitive rules, and the database system can effectively resist attackers' attacks on sensitive data, thus guaranteeing the security of the database system. The accompanying drawings are provided to further illustrate this disclosure and constitute a part of this disclosure. The illustrative embodiments and descriptions of this disclosure are used to explain this disclosure and do not constitute an improper limitation of this disclosure. In the drawings: Figure 1 is a schematic diagram of an application scenario provided by an embodiment of this disclosure; Figure 2 is a flowchart of a sensitive rule configuration method provided by an embodiment of this disclosure; Figure 3 is a flowchart of another sensitive rule configuration method provided by an embodiment of this disclosure; Figure 4 is a structural schematic diagram of a sensitive rule configuration device provided by an embodiment of this disclosure; Figure 5 is a structural schematic diagram of an electronic device provided by an embodiment of this disclosure. Detailed Description To make the objectives, technical solutions, and advantages of this disclosure clearer, the technical solutions of this disclosure will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments.Based on the embodiments in this disclosure, all other embodiments obtained by those skilled in the art without inventive effort are within the scope of protection of this disclosure. In the embodiments of this disclosure, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the access relationship of associated objects, indicating that three relationships may exist, for example, A and / or B. The relationship is as follows. Furthermore, in this embodiment, "first," "second," "third," etc., are merely used to distinguish the content of different objects and have no other special meaning. To protect sensitive data in a database system, users often configure corresponding sensitive rules. Sensitive rules define the methods for protecting sensitive data in the database system; for example, sensitive rules define de-identification algorithms or encryption algorithms for sensitive data. During the data access phase, the database system uses sensitive rules to protect the sensitive data queried by the user and returns the protected sensitive data to the user. In practical applications, attackers often design specially designed Structured Query Language (SQL) statements. After the attacker triggers the database system to execute the specially designed SQL statements, sensitive data is transferred. For example, sensitive data is copied from one data object to another, such as a database, table, or column. However, the sensitive rules configured by the user for a specified data object are only effective for that specified data object. When sensitive data in a specified data object is copied to other data objects, the sensitive rules are ineffective for those other data objects. In this way, attackers can request the database system to query sensitive data in other data objects. The database system provides the attacker with the raw, unprotected sensitive data, causing it to be outside the scope of sensitive rules. The database system cannot use these rules to protect the sensitive data, thus failing to defend against attacks and reducing its security. To address this, this disclosure provides a method, device, storage medium, and computer program product for configuring sensitive rules. In this embodiment, the database system, upon receiving a database operation statement (such as an SQL statement) instructing data transfer between different data objects, searches the existing sensitive rule library for an existing sensitive rule for the first data object based on its object identifier before the transfer. If an existing sensitive rule is found, a new sensitive rule is generated for the second data object based on its object identifier and the data protection policy within the existing sensitive rule of the first data object, and this new rule is added to the existing sensitive rule library.Therefore, even if an attacker designs database operation statements such as SQL statements to initiate data flow requests, as long as the data object before the flow is configured with sensitive rules, the database system can still configure sensitive rules for the data object after the flow. This ensures that sensitive data in the data object after the flow cannot escape the sensitive rules, and the database system can effectively resist attackers' attacks on sensitive data, thus guaranteeing the security of the database system. Figure 1 is a schematic diagram of an application scenario provided by an embodiment of this disclosure. In practical applications, a database system may maintain several databases, each database typically includes multiple tables. A table is usually a two-dimensional data structure, consisting of columns and rows. Each row represents a record, and each column represents a field of data. A field is a data unit of a specific type stored in a database table. Data objects provided by the database system include, for example, databases, tables, and columns. If the data object is a database, its object identifier is the database name (also known as the database name). If the data object is a table, its object identifier can be defined by the database name of the database containing the table and the table name within that database. If the data object is a column, its object identifier is defined by the database name of the database containing the table, the table name within that database, and the column name within that table. For example, a database might be named `Database1`, and a table within that database might be named `Tablet`. The columns in the `Tablet` table might be named `Column1`, `Column2`, `Column3`, etc. If the data object is a database (Database1), its object identifier is denoted as Database1; if the data object is a Tablet, its object identifier is denoted as Database1-Table1, which identifies the Tablet table within the Database1 database; if the data object is Column1, its object identifier is denoted as Database1-Table1-Column1, which identifies Column1 within the Tablet table within the Database1 database. In practical applications, database tables often contain some sensitive fields.For example, in an employee information table, fields such as "Name," "Age," "Gender," "Date of Employment," and "Salary" are all sensitive fields. To reduce the risk of sensitive data leakage, relevant rule configuration personnel, such as database administrators, can configure sensitive rules for these fields. Sensitive rules can be flexibly configured on demand to protect sensitive data. In practical applications, as shown in Figures ① and ② in Figure 1, the rule configuration personnel perform the configuration operation of configuring sensitive rules for data objects on the configuration terminal, triggering the configuration terminal to send the sensitive rules to the database system so that the database system can save the sensitive rules locally. This completes the sensitive rule configuration process. During the data access phase, as shown in Figures ③ and ④ in Figure 1, the attacker's access terminal sends a data transfer request to the database system. For example, the data transfer request might be to copy the field data of a sensitive field in one data table to another data table. Another example is that the data transfer request might be to change the field name of a sensitive field in a data table (i.e., change the column name). In response to a data transfer request, the database system determines whether the data object before the transfer has sensitive rules configured. If so, it needs to configure matching sensitive rules for the transferred data object to ensure that sensitive data remains protected after the transfer. After configuring matching sensitive rules for the transferred data object, the database system executes the data transfer operation, allowing the sensitive data to flow from the original data object to the new one. Referring to Figures 1(⑤) and 1(⑥), an attacker's access terminal sends a query request to the database system to retrieve the transferred data object. The database system confirms that the transferred data object has sensitive rules configured and uses these rules to protect the data content of the transferred data object. The protected data is then returned to the access terminal as the query result. In this way, even if an attacker designs SQL statements to initiate data flow requests, the database system can still configure sensitive rules for the flowed data objects. This ensures that sensitive data within the flowed data objects cannot escape these rules, effectively protecting the database system from attackers' attacks on sensitive data and guaranteeing its security. In practical applications, database systems include, but are not limited to, relational databases, non-relational databases, cloud-native databases, or data warehouses. Which fields in the database tables provided by the database system are sensitive and which are not can be flexibly specified as needed, without any restrictions.In practical applications, an access terminal can be understood as a client of a database system. A client can be any device or application capable of initiating requests and interacting with the database system to access and manipulate data. Access terminals include, but are not limited to, desktop computers, personal computers, smartphones, tablets, in-vehicle devices, or IoT devices. Of course, an access terminal can also be an application installed on a terminal device; there are no limitations on this. Similarly, in practical applications, a configuration terminal can be any device or application capable of initiating requests and interacting with the database system to access and manipulate data. Configuration terminals include, but are not limited to, desktop computers, personal computers, smartphones, tablets, in-vehicle devices, or IoT devices. Of course, a configuration terminal can also be an application installed on a terminal device; there are no limitations on this. It should be noted that the application scenario shown in Figure 1 is merely an exemplary application scenario, and this disclosure does not limit the application scenario. This disclosure does not limit the devices included in Figure 1, nor does it limit the positional relationship between the devices in Figure 1. The technical solutions of this disclosure and how these solutions solve the above-mentioned technical problems will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The technical solutions provided by the embodiments of this disclosure are described in detail below with reference to the accompanying drawings. Figure 2 is a flowchart of a sensitive rule configuration method provided by an embodiment of this disclosure. This method can be executed by a database system. Referring to Figure 2, the method may include the following steps:

[0002] 201. Obtain the target database operation statement. The target database operation statement indicates the data flow between different data objects in the database system.

[0003] 202. Based on the object identifier of the first data object before the transfer, check whether there are existing sensitive rules for the first data object in the existing sensitive rule base.

[0004] 203. If an existing sensitive rule for the first data object is found, a new sensitive rule is generated for the second data object based on its object identifier and the data protection policy in the existing sensitive rule of the first data object. This new sensitive rule is then added to the existing sensitive rule library. In practical applications, database operation statements include, but are not limited to: SQL statements, Object-Relational Mapping (ORM) operation statements, and NoSQL commands. In practical applications, the access terminal can provide various database operation statements to the database system. Basic statement types for database operation statements include, but are not limited to: SELECT statements for retrieving data, INSERT INTO statements for inserting new data into a table, UPDATE statements for updating data in a table, DELETE statements for deleting data from a table, and ALTER statements for modifying the database structure information, etc. The database system analyzes the database operation statements submitted by the access terminal to determine whether they are target database operation statements. Target database operation statements instruct data transfer between different data objects within the database system. This data transfer is used internally within the database system to transfer the data content of a first data object to a second data object. Target database operation statements include, but are not limited to: statements instructing the copying of data content from one data object to another, and statements instructing the renaming of data objects. Using the target database operation statement as the target SQL statement, several exemplary target SQL statements are given below for ease of understanding:

[0005] 1. l< The SQL statement `INSERT INTO table_name2 (column 1 ,column2) SELECT column 1, column2 FROM table_name1` selects all data from columns 1 and 2 of the table `table_name1` and inserts this data into the corresponding columns of the table `table_name2`. In other words, it copies two columns of data from one table to another.

[0006] 2. The SQL statement “INSERT INTO table_name2 FROM table_name1” selects all data from each column of the table_name1 data table and then inserts this data into the corresponding columns of the table_name2 data table. In other words, it copies all the data from all columns of one data table to another data table.

[0007] 3. l< The SQL statement `ALTER TABLE table_namel RENAME COLUMN x TO y` renames the column named `x` in `table_namel` to `y`, thus changing the column name.

[0008] The target SQL statement "RENAME TABLE old_table_name TO new_table_name" modifies the old table name "old_table_name" to the new table name "new_table_name", thus changing the table name. In practical applications, the access terminal may also send relatively complex SQL statements to the database system. If such complex SQL can be broken down into multiple simple SQL statements involving data flow, then the complex SQL statement is also considered the target SQL statement. For example, the complex SQL statement "CREATE TABLE AB as (SELECT(tl.x+ t2.y)as z FROM AC as tl,AD as t2 WHERE tl.id=t2.id)" can be broken down into "INSERT INTO AB (z) SELECT x FROM AC" and "INSERT INTO AB (z) SELECT y FROM AD". oIn this context, `tl` refers to table AC, and `tl.x` refers to column x in table AC; `t2` refers to table AD, and `t2.y` refers to column y in table AD. `tl.id` represents column id in table AC; `t2.id` represents column id in table AD. The statement `INSERT INTO AB (z) SELECT x FROM AC` inserts data from column x in table AC into column z in table AB. Similarly, `INSERT INTO AB (z) SELECT y FROM AD` inserts data from column y in table AD into column z in table AB. In practical applications, after the database system receives the target database operation statement submitted by the access terminal, it can initiate a task to configure sensitive rules for the transferred data objects before, during, or after the execution of the target database operation statement, without any restrictions. In practical applications, database systems can maintain an existing sensitive rule base, which includes one or more existing sensitive rules. An existing sensitive rule can be understood as a sensitive rule already configured for a specific data object. Existing sensitive rules include, but are not limited to, the object identifier of the data object, data protection policies, or user roles. The object identifier in the existing sensitive rules determines which sensitive fields require data protection processing. For example, if the object identifier in an existing sensitive rule is "Database1-Table1", then all columns in the tables of the "Database1" database are sensitive fields. Similarly, if the object identifier in an existing sensitive rule is "Database1-Table1-Column1", then column 1 in the "Table1" table of the "Database1" database is a sensitive field. Data protection policies define the data protection processing methods required for sensitive fields. Data protection policies include, for example, de-identification algorithms or encryption algorithms. Masking algorithms are used to mask sensitive field data. Examples of masking algorithms include, but are not limited to: replacement masking algorithms, mask masking algorithms, hash algorithms, encryption algorithms, etc. Encryption algorithms are used to encrypt sensitive field data before or after masking.Encryption ensures that data flowing from the database system is ciphertext, not plaintext, guaranteeing the security of data transmission from the database system to the access terminal. Replacement anonymization algorithms can replace some or all of sensitive data with non-sensitive content; for example, replacing a real name with "anonymous user" or replacing the last four digits of a phone number with "****". Replacement anonymization algorithms can be user-defined by parameters including, but not limited to: replacement pattern, replacement length, and reserved position. The replacement pattern defines which non-sensitive content to use for replacement, including, but not limited to, asterisks (*), random characters, and fixed characters. The replacement length determines how many digits to replace; for example, a phone number might only display the first three and last four digits, with the middle digits replaced by asterisks. The reserved position determines which characters are not retained and which are replaced. Masking anonymization algorithms can replace some or all of sensitive data with specific characters (such as asterisks *, X) or other placeholders to hide some sensitive information in the data. Masking algorithms are suitable for data with fixed formats, such as phone numbers, credit card numbers, or ID card numbers. Masking algorithms can be user-defined, with parameters including but not limited to: mask pattern, mask length, and reserved bit positions. The mask pattern defines which non-sensitive content is used for masking, such as, but not limited to, asterisks (*), random characters, and fixed characters. The mask length determines the number of digits in the mask; for example, only the first three and last four digits of a phone number are displayed, with the middle portion masked. The reserved bit positions determine which characters are not retained and which are masked. Hash algorithms can use hash functions to convert sensitive data into a fixed-length, irreversible hash value, thereby protecting data privacy. Hash algorithms can be user-defined, with parameters including but not limited to: hash algorithm type, salt value, and number of iterations. Hash algorithm types include, but are not limited to: SHA-1 (Secure Hash Algorithm 1) and SHA-256 (Secure Hash Algorithm 256). Salt can be added to add random strings, improving hash uniqueness; increasing the number of iterations enhances security. When used as a de-identification algorithm, encryption algorithms protect sensitive data by encrypting it. Encryption algorithms can be defined by user-defined parameters, including but not limited to: keys, key derivation functions, encryption algorithm types, etc. Encryption algorithm types include, but are not limited to: symmetric encryption algorithms and asymmetric encryption algorithms.In practical applications, user roles in existing sensitive rules can be flexibly set as needed. User roles include, but are not limited to, management users, ordinary users, temporary access users, data analysis users, developers, etc. It is understood that if existing sensitive rules include user roles, the existing sensitive rules are only effective when the data accessor's user role is one of those roles. If a data accessor with a user role that is one of those roles requests the database system to query sensitive fields, the database system needs to use the data protection strategy in the existing sensitive rules to protect the sensitive fields. It is understood that if existing sensitive rules do not include user roles, the existing sensitive rules apply to any user role. If a data accessor with any user role requests the database system to query sensitive fields, the database system needs to use the data protection strategy in the existing sensitive rules to protect the sensitive fields. In this embodiment, after the database system obtains the target database operation statement, it parses the target database operation statement to obtain the object identifier of the data object undergoing data flow. Here, the data object before flow is referred to as the first data object, and the data object after flow is referred to as the second data object. It is understandable that after executing the target database operation statement, the database system can transfer the data content of the first data object to the second data object. In this embodiment, after obtaining the object identifier of the first data object before the transfer, the database system searches the existing sensitive rule base to see if there are any existing sensitive rules for the first data object. In practical applications, the database system can search the existing sensitive rule base for existing sensitive rules whose object identifier is exactly the same as that of the first data object, and use them as existing sensitive rules for the first data object. For example, the existing sensitive rule base includes existing sensitive rules for Database 1 - Table 1 - Column 1, existing sensitive rules for Database1, and existing sensitive rules for Database1 - Table 1. If the object identifier of the first data object is Database 1 - Table 1 - Column 1, then the existing sensitive rules for Database1 - Table 1 - Column 1 are existing sensitive rules for the first data object.Optionally, the database system can further determine whether existing sensitive rules for the first data object exist in the existing sensitive rule base based on the object identifier of the first data object before the transfer. This can be achieved by: 1) Searching the existing sensitive rule base for candidate existing sensitive rules based on the object identifier of the first data object before the transfer, where the granularity of the object identifier in the candidate existing sensitive rules is greater than or equal to the granularity of the object identifier of the first data object; 2) Determining the existing sensitive rules for the first data object from the candidate existing sensitive rules. Specifically, the granularity of the data object's object identifier may include, but is not limited to, database granularity, table granularity, and column granularity. These are ordered from largest to smallest granularity as follows: database granularity, table granularity, and column granularity. If the object identifier of a data object is at the database level, and the object identifier is the database name, then the data object is a database. If the object identifier is at the table level, and the object identifier consists of the database name and the table name, then the data object is a table. If the object identifier is at the column level, and the object identifier consists of the database name, the table name, and the column name, then the data object is a column. In practical applications, the database system searches for candidate existing sensitive rules in the existing sensitive rule base. The object identifier granularity in the candidate existing sensitive rules is greater than or equal to the object identifier granularity of the first data object. For example, if the object identifier of the first data object is at the column level, but the existing sensitive rule base contains an existing sensitive rule for the column containing the first data object, then the existing sensitive rule for the column containing the first data object can be used as the existing sensitive rule for the first data object. For example, if the object identifier of the first data object is at the column level, but the existing sensitive rule base only contains existing sensitive rules for the table where the first data object resides, then the existing sensitive rules for the table where the first data object resides can be used as the existing sensitive rules for the first data object. Similarly, if the object identifier of the first data object is at the table level, but the existing sensitive rule base only contains existing sensitive rules for the database where the first data object resides, then the existing sensitive rules for the database where the first data object resides can be used as the existing sensitive rules for the first data object. It is worth noting that when there are multiple candidate existing sensitive rules, the candidate existing sensitive rule whose object identifier granularity is closest to that of the object identifier of the first data object is used as the existing sensitive rule for the first data object. It is also worth noting that the object identifier in the candidate existing sensitive rule is related to the object identifier of the first data object. The data object identified by the object identifier in the candidate existing sensitive rule can be the table, database, or column to which the first data object belongs.It is understandable that searching for existing sensitive rules in the existing sensitive rule base of the data table, database, or column to which the first data object belongs, and using these as existing sensitive rules for the first data object, can ensure the reliability of obtaining the existing sensitive rules for the first data object, thereby effectively protecting sensitive data. In this embodiment, after the database system finds the existing sensitive rules for the first data object in the existing sensitive rule base, it can generate new sensitive rules configured for the second data object based on the object identifier of the transferred second data object and the data protection policy in the existing sensitive rules of the first data object, and add the new sensitive rules to the existing sensitive rule base. In practical applications, there are no restrictions on the method of generating new sensitive rules configured for the second data object based on the existing sensitive rules of the first data object. As an example, the data protection policy in the existing sensitive rules of the first data object can be extracted, and new sensitive rules configured for the second data object can be generated based on the object identifier of the transferred second data object and the data protection policy in the existing sensitive rules of the first data object. As another example, data protection policies and user roles can be extracted from the existing sensitive rules of the first data object. Based on the object identifier of the transferred second data object and the data protection policies and user roles in the existing sensitive rules of the first data object, new sensitive rules configured for the second data object can be generated. It is worth noting that adding user roles to the new sensitive rules configured for the second data object allows for better access control based on user roles, thereby effectively protecting sensitive data. As another example, when generating new sensitive rules configured for the second data object, a copy of the existing sensitive rules of the first data object can be obtained. The object identifier in the copy of the existing sensitive rules can be modified to the object identifier of the second data object, resulting in new sensitive rules configured for the second data object. It is worth noting that configuring new sensitive rules for the second data object through rule copying allows for better reuse of the existing sensitive rules of the first data object, ensuring consistency between the second and first data objects in terms of data protection policies and / or user role-based access control, thereby effectively protecting sensitive data. Understandably, the new sensitive rules configured for the second data object are added to the existing sensitive rule library so that when the database system receives a query request for the data content of the second data object, it can use the new sensitive rules of the second data object to perform data protection processing on the queried data content of the second data object, ensuring that the data content of the second data object flowing out of the database system has been processed with data protection, and ensuring the security of sensitive data.The technical solution provided in this disclosure involves a database system that, in response to a received database operation statement such as an SQL statement instructing data transfer between different data objects within the database system, searches the existing sensitive rule base for an existing sensitive rule for the first data object before the transfer, based on the object identifier of the first data object. If an existing sensitive rule for the first data object is found, a new sensitive rule is generated for the second data object based on the object identifier of the second data object after the transfer and the data protection policy in the existing sensitive rule of the first data object, and this new sensitive rule is added to the existing sensitive rule base. Therefore, even if an attacker designs a database operation statement such as an SQL statement to request data transfer, as long as the data object before the transfer has been configured with sensitive rules, the database system can still configure sensitive rules for the data object after the transfer. This ensures that sensitive data in the transferred data object cannot escape the sensitive rules, effectively resisting attacks on sensitive data and guaranteeing the security of the database system. Figure 3 is a flowchart of another sensitive rule configuration method provided in this disclosure. This method can be executed by the database system. Referring to Figure 3, the method may include the following steps:

[0009] 301. Obtain the target database operation statement. The target database operation statement indicates the data flow between different data objects in the database system.

[0010] 302. Based on the object identifier of the first data object before the transfer, check if there are existing sensitive rules for the first data object in the existing sensitive rule base. If existing sensitive rules for the first data object are found, proceed to step 303; if no existing sensitive rules for the first data object are found, end the process. It can be understood that if the database system does not find existing sensitive rules for the first data object in the existing sensitive rule base, it means that the data content of the first data object is not sensitive data. In this case, there is no need to configure sensitive rules for the first data object, and the process of "configuring sensitive rules for the first data object" ends. If the database system finds existing sensitive rules for the first data object in the existing sensitive rule base, it means that the data content of the first data object is sensitive data. Sensitive rules need to be configured for the second data object to ensure that after the data content of the first data object is transferred to the second data object, it is protected using the sensitive rules configured for the second data object.

[0011] 303. Based on the object identifier of the second data object, search the existing sensitive rule base to see if there are any existing sensitive rules for the second data object. If no existing sensitive rules for the second data object are found, proceed to step 304; if existing sensitive rules for the second data object are found, proceed to step 305. In practical applications, the execution order of steps 302 and 303 is not restricted; they can be executed in parallel or sequentially. Specifically, if the database system finds existing sensitive rules for the first data object but not for the second data object, step 304 can be executed to reuse the existing sensitive rules of the first data object to configure new sensitive rules for the second data object. If the database system finds existing sensitive rules for both the first and second data objects, the database system can end the process of "configuring new sensitive rules for the second data object." Further optionally, if the database system finds existing sensitive rules for both the first and second data objects, step 305 can also be executed to more effectively protect sensitive data.

[0012] 304. Based on the object identifier of the transferred second data object and the data protection policy in the existing sensitive rules of the first data object, generate new sensitive rules for the second data object and add the new sensitive rules to the existing sensitive rule library.

[0013] 305. Determine whether the security level of the existing sensitive rules of the second data object is higher than the security level of the existing sensitive rules of the first data object; if the security level of the existing sensitive rules of the second data object is lower than the security level of the existing sensitive rules of the first data object, then proceed to step 306; if the security level of the existing sensitive rules of the second data object is higher than the security level of the existing sensitive rules of the first data object, then end the process.

[0014] 306. Delete the existing sensitive rules for the second data object from the existing sensitive rule base, and return to step 304. In practical applications, if the database system finds existing sensitive rules for both the first and second data objects, it can determine whether to replace the existing sensitive rules for the second data object in the existing sensitive rule base. Specifically, if the security level of the existing sensitive rules for the second data object is lower than that for the first data object, to ensure that the data protection strength is not reduced after the data content of the first data object is transferred to the second data object, it is necessary to delete the existing sensitive rules for the second data object from the existing sensitive rule base, generate new sensitive rules for the second data object based on the existing sensitive rules for the first data object, and add the new sensitive rules to the existing sensitive rule base. If the security level of the existing sensitive rules for the second data object is higher than that for the first data object, it means that the data protection strength will be enhanced after the data content of the first data object is transferred to the second data object, and the database system can end the process of "configuring new sensitive rules for the second data object". In practical applications, there are no restrictions on how to determine whether the security level of existing sensitive rules for a second data object is higher than that for the first data object. For example, if the security level of the de-identification algorithm in the existing sensitive rules of the second data object is higher than that of the de-identification algorithm in the existing sensitive rules of the first data object, then the security level of the existing sensitive rules for the second data object is higher than that of the first data object. Similarly, if the security level of the encryption algorithm in the existing sensitive rules of the second data object is higher than that of the encryption algorithm in the existing sensitive rules of the first data object, then the security level of the existing sensitive rules for the second data object is higher than that of the first data object. Furthermore, based on the security levels of the de-identification and encryption algorithms in the existing sensitive rules of the second data object, a security score for the existing sensitive rules of the second data object is calculated; based on the security levels of the de-identification and encryption algorithms in the existing sensitive rules of the first data object, a security score for the existing sensitive rules of the first data object is also calculated; if the security score of the existing sensitive rules of the second data object is greater than that of the existing sensitive rules of the first data object, then the security level of the existing sensitive rules of the second data object is higher than that of the first data object. It can be understood that a higher security level generally indicates higher security.Optionally, to more effectively protect sensitive data, if the database system finds existing sensitive rules for the first data object, and assuming the data protection strategy includes de-identification algorithms and encryption algorithms, the method further includes: If existing sensitive rules for the second data object are found, determining whether only one algorithm in the existing sensitive rules for the second data object has a higher security level than the corresponding algorithm in the existing sensitive rules for the first data object; if the determination result is yes, then based on the object identifier of the second data object, the first algorithm with a higher security level in the existing sensitive rules for the second data object, and the second algorithm with a higher security level in the existing sensitive rules for the first data object, generating new sensitive rules configured for the second data object. The first algorithm is one of the de-identification algorithms and the encryption algorithm, and the second algorithm is the other of the de-identification algorithms and the encryption algorithm. It can be understood that a de-identification algorithm with a higher security level is selected from the de-identification algorithms of the existing sensitive rules for the first data object and the de-identification algorithms of the existing sensitive rules for the second data object and configured into the new sensitive rules for the second data object. Similarly, a higher-security encryption algorithm is selected from the encryption algorithms of the existing sensitive rules for the first data object and the encryption algorithms of the existing sensitive rules for the second data object and configured into the new sensitive rules for the second data object. Delete the existing sensitive rules for the second data object from the existing sensitive rule base, and add a new sensitive rule for the second data object with a higher security level to the existing sensitive rule base. In practical applications, there are no restrictions on whether user roles are added to the new sensitive rule for the second data object. For example, user roles from existing sensitive rules of the first data object or existing sensitive rules of the second data object can be added to the new sensitive rule for the second data object.Optionally, to more effectively protect sensitive data, the implementation of generating new sensitive rules for the second data object based on the object identifier of the second data object, the first algorithm with a high security level among the existing sensitive rules of the second data object, and the second algorithm with a high security level among the existing sensitive rules of the first data object is as follows: If the user role level in the existing sensitive rules of the second data object is lower than the user role level in the existing sensitive rules of the first data object, then a new sensitive rule is generated for the second data object based on the object identifier of the second data object, the first algorithm with a high security level among the existing sensitive rules of the second data object, the user role, and the second algorithm with a high security level among the existing sensitive rules of the first data object; if the user role level in the existing sensitive rules of the second data object is higher than the user role level in the existing sensitive rules of the first data object, then a new sensitive rule is generated for the second data object based on the object identifier of the second data object, the first algorithm with a high security level among the existing sensitive rules of the second data object, the second algorithm with a high security level among the existing sensitive rules of the first data object, and the user role. In practical applications, user roles of data visitors can be identified through their accounts, but this is not the only method. Generally, the higher the user role level, the more trustworthy the data visitor and the lower the probability of them launching an attack. For example, sorted from highest to lowest level, the roles could be: administrator user, regular user, etc. If the existing sensitive rules for the second data object specify an administrator user, and the existing sensitive rules for the first data object specify a regular user, then the new sensitive rules for the second data object will specify a regular user. Conversely, if the existing sensitive rules for the second data object specify a regular user, and the existing sensitive rules for the first data object specify an administrator user, then the new sensitive rules for the second data object will specify an administrator user. Since data flows from the first data object to the second data object, controlling the user roles in the new sensitive rules of the second data object with the existing sensitive rules of the first data object ensures that the data protection strength is not weakened after the data flows from the first data object to the second data object.The technical solution provided in this disclosure involves a database system that, upon receiving a database operation statement (such as an SQL statement) instructing data transfer between different data objects within the database system, searches the existing sensitive rule base for an existing sensitive rule for the first data object based on the object identifier of the first data object before the transfer. If an existing sensitive rule for the first data object is found, a new sensitive rule is generated for the second data object based on the object identifier of the second data object after the transfer and the data protection policy in the existing sensitive rule of the first data object, and this new sensitive rule is added to the existing sensitive rule base. Furthermore, if the database system finds both an existing sensitive rule for the first and second data objects, it can determine whether to replace the existing sensitive rule for the second data object in the existing sensitive rule base. Therefore, even if an attacker designs database operation statements such as SQL statements to initiate data flow requests, as long as the data object before the flow is configured with sensitive rules, the database system can still configure sensitive rules for the data object after the flow. This ensures that sensitive data in the data object after the flow cannot escape the sensitive rules, and the database system can effectively resist attackers' attacks on sensitive data, thus guaranteeing the security of the database system. Figure 4 is a schematic diagram of a sensitive rule configuration device provided in an embodiment of this disclosure. This device can be composed of software and / or hardware and can generally be integrated into a database system. Referring to Figure 4, the device may include: an acquisition module 41, configured to acquire a target database operation statement, which instructs data transfer between different data objects in the database system. This data transfer is used within the database system to transfer the data content of a first data object before the transfer to a second data object after the transfer; a search module 42, configured to search the existing sensitive rule base for existing sensitive rules for the first data object based on the object identifier of the first data object before the transfer; and a configuration module 43, configured to, if existing sensitive rules for the first data object are found, generate new sensitive rules configured for the second data object based on the object identifier of the second data object after the transfer and the data protection policy in the existing sensitive rules of the first data object, and add the new sensitive rules to the existing sensitive rule base. Further optionally, when the configuration module 43 generates new sensitive rules configured for the second data object, it is specifically configured to: generate new sensitive rules configured for the second data object based on the object identifier of the second data object after the transfer, the data protection policy in the existing sensitive rules of the first data object, and the user role.Optionally, when the configuration module 43 generates a new sensitive rule configured for the second data object, it is specifically configured to: obtain a copy of the existing sensitive rule obtained by copying the existing sensitive rule of the first data object; modify the object identifier in the copy of the existing sensitive rule to the object identifier of the second data object, thereby obtaining a new sensitive rule configured for the second data object. Optionally, before generating the new sensitive rule configured for the second data object, the configuration module 43 is further configured to: search the existing sensitive rule library for the second data object based on the object identifier of the second data object; if no existing sensitive rule for the second data object is found, then execute the step of generating a new sensitive rule configured for the second data object. Optionally, the configuration module 43 is further configured to: if an existing sensitive rule for the second data object is found, determine whether the security level of the existing sensitive rule for the second data object is higher than the security level of the existing sensitive rule for the first data object; if the security level of the existing sensitive rule for the second data object is lower than the security level of the existing sensitive rule for the first data object, then delete the existing sensitive rule for the second data object from the existing sensitive rule library, and execute the step of generating a new sensitive rule configured for the second data object. Optionally, the data protection strategy includes de-identification algorithms and encryption algorithms. The configuration module 43 is further configured to: when an existing sensitive rule for the second data object is found, determine whether only one algorithm in the existing sensitive rule for the second data object has a higher security level than the corresponding algorithm in the existing sensitive rule for the first data object; if the determination result is yes, then generate a new sensitive rule for the second data object based on the object identifier of the second data object, the first algorithm with a higher security level in the existing sensitive rule for the second data object, and the second algorithm with a higher security level in the existing sensitive rule for the first data object. The first algorithm is one of the de-identification algorithm and the encryption algorithm, and the second algorithm is the other algorithm among the de-identification algorithm and the encryption algorithm.Optionally, when configuration module 43 generates new sensitive rules for the second data object based on the object identifier of the second data object, the first algorithm with a high security level among the existing sensitive rules of the second data object, and the second algorithm with a high security level among the existing sensitive rules of the first data object, it is specifically configured as follows: If the user role level in the existing sensitive rules of the second data object is lower than the user role level in the existing sensitive rules of the first data object, then new sensitive rules are generated for the second data object based on the object identifier of the second data object, the first algorithm with a high security level among the existing sensitive rules of the second data object, the user role, and the second algorithm with a high security level among the existing sensitive rules of the first data object; If the user role level in the existing sensitive rules of the second data object is higher than the user role level in the existing sensitive rules of the first data object, then new sensitive rules are generated for the second data object based on the object identifier of the second data object, the first algorithm with a high security level among the existing sensitive rules of the second data object, the second algorithm with a high security level among the existing sensitive rules of the first data object, and the user role. Further optionally, the lookup module 42 is specifically configured to: based on the object identifier of the first data object before the transfer, search for whether there are candidate existing sensitive rules in the existing sensitive rule base, wherein the granularity of the object identifier in the candidate existing sensitive rules is greater than or equal to the granularity of the object identifier of the first data object; and determine the existing sensitive rule of the first data object from the candidate existing sensitive rules. The device shown in Figure 4 can execute the method shown in the embodiment shown in Figure 2, and its implementation principle and technical effects will not be repeated here. The specific way in which each module and unit of the device shown in Figure 4 in the above embodiments performs operations has been described in detail in the embodiments related to the method, and will not be elaborated here. It should be noted that the execution subject of each step of the method provided in the above embodiments can be the same device, or the method can also be executed by different devices. For example, the execution subject of steps 201 to 203 can be device A; or the execution subject of steps 201 and 202 can be device A, and the execution subject of step 203 can be device B; and so on. Furthermore, in some of the processes described in the above embodiments and accompanying drawings, multiple operations are included that appear in a specific order. However, it should be clearly understood that these operations may not be executed in the order they appear herein, or they may be executed in parallel. The operation numbers, such as 201, 202, etc., are merely used to distinguish different operations, and the numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel.It should be noted that the terms "first" and "second" in this document are used to distinguish different messages, devices, modules, etc., and do not represent a chronological order, nor do they limit "first" and "second" to different types. It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse. Figure 5 is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. As shown in Figure 5, the electronic device includes: a memory 51 and a processor 52; the memory 51 is used to store computer programs and can be configured to store various other data to support operation on a computing platform. Examples of such data include instructions for any application or method operating on a computing platform, contact data, phone book data, messages, pictures, videos, etc. Memory 51 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random-Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. Processor 52, coupled to memory 51, is used to execute the computer program in memory 51 for: performing steps in the configuration method for sensitive rules. Further optionally, as shown in FIG5, the electronic device may also include: communication component 53, display 54, power supply component 55, audio component 56, and other components. FIG5 only schematically shows some components and does not imply that the electronic device includes only the components shown in FIG5. In addition, the components within the dashed boxes in Figure 5 are optional, not mandatory, and their specific requirements depend on the product form of the electronic device.The electronic device in this embodiment can be a terminal device such as a desktop computer, laptop computer, smartphone, or Internet of Things (IoT) device, or a server device such as a conventional server, cloud server, or server array. If the electronic device in this embodiment is a terminal device such as a desktop computer, laptop computer, or smartphone, it may include the components within the dashed box in Figure 5; if the electronic device in this embodiment is a server device such as a conventional server, cloud server, or server array, it may not include the components within the dashed box in Figure 5. Detailed implementation processes of the processor executing each action can be found in the relevant descriptions in the foregoing method embodiments or device embodiments, and will not be repeated here. Accordingly, this disclosure also provides a computer-readable storage medium storing a computer program, which, when executed, can implement the steps that can be executed by the electronic device in the above method embodiments. Accordingly, this disclosure also provides a computer program product, including a computer program / instruction, which, when executed by a processor, causes the processor to implement the steps that can be executed by the electronic device in the above method embodiments. The communication component is configured to facilitate wired or wireless communication between the device containing the communication component and other devices. The device containing the communication component can access wireless networks based on communication standards, such as Wireless Fidelity (WiFi), 2G, 3G, 4G / Long Term Evolution (LTE), 5G, or combinations thereof. In one exemplary embodiment, the communication component receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component also includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be based on Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wide Band (UWB), Bluetooth (BT), and other technologies.The aforementioned display includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touchscreen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. The aforementioned power supply component provides power to various components of the device in which the power supply component resides. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which the power supply component resides. The aforementioned audio component can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC) configured to receive external audio signals when the device in which the audio component resides is in an operating mode, such as a call mode, recording mode, or voice recognition mode. The received audio signals may be further stored in memory or transmitted via a communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals. Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams. These computer program instructions may also be loaded onto a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable device, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams. In a typical configuration, a computing device includes one or more processors (Central Processing Units, CPUs), input / output interfaces, network interfaces, and memory. Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium. Computer-readable media include both permanent and non-permanent, removable and non-removable media, and information storage can be achieved by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data.Examples of computer storage media include, but are not limited to, phase-change RAM (PRAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transient media, such as modulated data signals and carrier waves. It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. The above are merely embodiments of this disclosure and are not intended to limit this disclosure. Various modifications and variations can be made to this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this disclosure should be included within the scope of the claims of this disclosure.

Claims

Claims 1. A method for configuring sensitive rules, comprising: Obtain the target database operation statement, which instructs data transfer between different data objects in the database system. This data transfer is used within the database system to transfer the data content of a first data object before the transfer to a second data object after the transfer. Based on the object identifier of the first data object before the transfer, check if there are existing sensitive rules for the first data object in the existing sensitive rule base. If existing sensitive rules for the first data object are found, generate new sensitive rules for the second data object based on the object identifier of the second data object after the transfer and the data protection policy in the existing sensitive rules of the first data object, and add the new sensitive rules to the existing sensitive rule base.

2. The method according to claim 1, wherein, Generating new sensitive rules for the second data object includes: generating new sensitive rules for the second data object based on the object identifier of the transferred second data object and the data protection policy and user role in the existing sensitive rules of the first data object.

3. The method according to claim 1, wherein, Generating a new sensitive rule configured for the second data object includes: obtaining a copy of the existing sensitive rule obtained by copying the existing sensitive rule of the first data object; modifying the object identifier in the copy of the existing sensitive rule to the object identifier of the second data object, thereby obtaining a new sensitive rule configured for the second data object.

4. The method according to claim 1, wherein, Before generating a new sensitive rule configured for the second data object, the method further includes: based on the object identifier of the second data object, searching the existing sensitive rule library to see if there is an existing sensitive rule for the second data object; if no existing sensitive rule for the second data object is found, then the step of generating a new sensitive rule configured for the second data object is performed.

5. The method according to claim 4, wherein, Also includes: If an existing sensitive rule for the second data object is found, then determine whether the security level of the existing sensitive rule for the second data object is higher than the security level of the existing sensitive rule for the first data object. If the security level of the existing sensitive rules for the second data object is lower than the security level of the existing sensitive rules for the first data object, then delete the existing sensitive rules for the second data object from the existing sensitive rule library, and perform the step of generating new sensitive rules configured for the second data object.

6. The method according to claim 5, wherein, The data protection strategy includes an anonymization algorithm and an encryption algorithm, and further includes: when existing sensitive rules for the second data object are found, determining whether only one algorithm in the existing sensitive rules of the second data object has a higher security level than the corresponding algorithm in the existing sensitive rules of the first data object; if the determination result is yes, then generating a new sensitive rule for the second data object based on the object identifier of the second data object, the first algorithm with a higher security level in the existing sensitive rules of the second data object, and the second algorithm with a higher security level in the existing sensitive rules of the first data object, wherein the first algorithm is one of the anonymization algorithm and the encryption algorithm, and the second algorithm is the other algorithm of the anonymization algorithm and the encryption algorithm.

7. The method according to claim 6, wherein, Based on the object identifier of the second data object, the first algorithm with a high security level among the existing sensitive rules of the second data object, and the second algorithm with a high security level among the existing sensitive rules of the first data object, a new sensitive rule is generated and configured for the second data object. This includes: if the user role level in the existing sensitive rules of the second data object is lower than the user role level in the existing sensitive rules of the first data object, then based on the object identifier of the second data object, the first algorithm with a high security level among the existing sensitive rules of the second data object, the user role, and the second algorithm with a high security level among the existing sensitive rules of the first data object, a new sensitive rule is generated and configured for the second data object. If the level of the user role in the existing sensitive rules of the second data object is higher than the level of the user role in the existing sensitive rules of the first data object, then a new sensitive rule is generated and configured for the second data object based on the object identifier of the second data object, the first algorithm with a higher security level in the existing sensitive rules of the second data object, the second algorithm with a higher security level in the existing sensitive rules of the first data object, and the user role.

8. The method according to claim 1, wherein, Based on the object identifier of the first data object before the transfer, search the existing sensitive rule base to see if there are any existing sensitive rules for the first data object. This includes: based on the object identifier of the first data object before the transfer, searching the existing sensitive rule base to see if there are any candidate existing sensitive rules, where the granularity of the object identifier in the candidate existing sensitive rules is greater than or equal to that of the first data object. The granularity of the object identification; determining the existing sensitive rules for the first data object from the candidate existing sensitive rules.

9. An electronic device, comprising: Memory and processor; The memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program to perform the steps of the method according to any one of claims 1-8.

10. A computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to perform the steps of the method according to any one of claims 1-8.

11. A computer program product comprising a computer program / instructions that, when executed by a processor, cause the processor to perform the steps of the method according to any one of claims 1-8.

Images