Data writing method and apparatus for monitoring scenario, storage cluster, and medium

Abstract

The present disclosure provides a data writing method and apparatus for a monitoring scenario, a storage cluster, and a medium, which are applied to the technical field of data storage. The method is specifically applied to a storage cluster that comprises a first data storage pool used for storing data before a data protection policy is changed, and the method comprises: when a write request sent by a service layer is acquired, detecting whether there is a second data storage pool exists in the storage cluster; and if there is a second data storage pool, on the basis of the write request, writing into the second data storage pool data to be written, wherein the second data storage pool is used for storing data after the data protection policy is changed, the write request comprises the data to be written that comprises data of a cycle following full-cycle storage of a current monitoring cycle or data of the current monitoring cycle that has not been stored.

Description

Data writing method and device for monitoring scenario, storage cluster and medium

[0001] Cross-reference to related applications

[0002] The present disclosure claims priority to the Chinese patent application with the application number 2024110837054 and the publication name "Data writing method and device for monitoring scenario, storage cluster and medium", which was filed on August 08, 2024, and is incorporated by reference in its entirety. TECHNICAL FIELD

[0003] The present disclosure relates to the technical field of data storage, and particularly relates to a data writing method and device for a monitoring scenario, a storage cluster and a medium. BACKGROUND

[0004] In a monitoring scenario, if the actual scenario changes, the protection priority of the original data in the monitoring system needs to be adjusted, that is, the data protection strategy is changed (the strategy pool is switched), for some data whose importance increases, the erasure code protection needs to be enhanced, and for some data whose importance decreases, the data protection needs to be reduced. When the data protection strategy is switched, the data migration work is extremely heavy, and has a great impact on the upper real-time business.

[0005] When the actual scenario needs to change the data protection strategy, the prior art adds a data protection pool in the storage cluster, the storage cluster migrates the old data in the old data pool to the data protection pool, at the same time, the read / write of the new data / old data by the business layer needs additional tool support. This method is difficult to realize the online change of the data protection strategy, when the strategy pool is switched, the business layer needs to be reconfigured, which will affect the data, does not support continuous change, and the data migration needs to consume a large amount of resources, which will also affect the upper real-time business. SUMMARY

[0006] The present disclosure provides a data writing method for a monitoring scenario, applied to a storage cluster, the storage cluster comprising a first data storage pool, the first data storage pool being used to store data before a data protection strategy is changed, the method comprising:

[0007] In the case that a write request sent by a business layer is acquired, it is detected whether a second data storage pool exists in the storage cluster; the second data storage pool is used to store data after the data protection strategy is changed, the write request comprising to-be-written data, the to-be-written data comprising data of a next period after full-period storage of a current monitoring period or data not completed storage in the current monitoring period;

[0008] If the second data storage pool exists, the to-be-written data is written into the second data storage pool according to the write request.

[0009] According to the data writing method for a monitoring scenario provided by the present disclosure, the write request includes a to-be-written object corresponding to to-be-written data, and the writing of the to-be-written data into the second data storage pool according to the write request includes:

[0010] If the to-be-written object exists in the first data storage pool, the data corresponding to the to-be-written object is deleted in the first data storage pool;

[0011] The to-be-written object is created in the second data storage pool, and a mapping relationship between the to-be-written object in the first data storage pool and the to-be-written object in the second data storage pool is established;

[0012] According to the mapping relationship, the to-be-written data in the write request is written into the storage space corresponding to the to-be-written object in the second data storage pool.

[0013] According to the data writing method for a monitoring scenario provided by the present disclosure, the method further includes:

[0014] If the to-be-written object does not exist in the first data storage pool, the to-be-written object is created in the first data storage pool;

[0015] The to-be-written object is created in the second data storage pool, and a mapping relationship between the to-be-written object in the first data storage pool and the to-be-written object in the second data storage pool is established;

[0016] According to the mapping relationship, the to-be-written data in the write request is written into the storage space corresponding to the to-be-written object in the second data storage pool.

[0017] According to the data writing method for a monitoring scenario provided by the present disclosure, the write request includes a to-be-written object corresponding to to-be-written data, and the method further includes:

[0018] If the second data storage pool does not exist, it is determined whether the to-be-written object exists in the first data storage pool;

[0019] If the to-be-written object exists, the to-be-written data is overwritten into the storage space corresponding to the to-be-written object in the first data storage pool according to the write request.

[0020] According to the data writing method for a monitoring scenario provided by the present disclosure, the storage cluster further includes a metadata storage pool, and the first command is stored in the metadata storage pool, the first command includes a first identifier of the first data storage pool, and the method further includes:

[0021] If the data in the first data storage pool is completely deleted, and all the second data storage pools mapped by all the objects in the mapping relationship are the same data storage pool, the first data storage pool is released.

[0022] obtain a second identifier of the second data storage pool, and replace the first identifier in the second command with the second identifier.

[0023] According to the data writing method for the monitoring scenario provided by the present disclosure, the storage cluster further includes a second data storage pool and a metadata storage pool, the metadata storage pool stores a second command, the second command includes a first identifier of the first data storage pool, and before detecting whether the second data storage pool exists in the storage cluster, the method further includes:

[0024] obtain a data protection policy change instruction sent by the business layer; the data protection policy change instruction includes a target protection level corresponding to a changed data protection policy;

[0025] determine a second data storage pool matching the target protection level in the storage cluster according to the target protection level; the storage cluster includes data storage pools of different protection levels;

[0026] obtain a second identifier of the second data storage pool, and replace the first identifier in the second command with the second identifier.

[0027] According to the data writing method for the monitoring scenario provided by the present disclosure, the method further includes:

[0028] obtain a read request sent by the business layer; the read request includes a to-be-read object corresponding to to-be-read data;

[0029] if the data corresponding to the to-be-read object in the first data storage pool is not empty, read the data stored in the storage space of the to-be-read object in the first data storage pool;

[0030] if the data corresponding to the to-be-read object in the first data storage pool is empty, find the to-be-read object in the second data storage pool according to the mapping relationship, and read the data stored in the storage space of the to-be-read object in the second data storage pool.

[0031] The present disclosure further provides a data writing device for a monitoring scenario, applied to a storage cluster, the storage cluster including a first data storage pool, the first data storage pool being used for storing data before a data protection policy change, and the device including the following modules:

[0032] a detection module, configured to, in a case where a write request sent by the business layer is obtained, detect whether a second data storage pool exists in the storage cluster; the second data storage pool is used for storing data after a data protection policy change, the write request includes to-be-written data, and the to-be-written data includes data of a next period after full-period storage of a current monitoring period or data not completed for storage in the current monitoring period;

[0033] The data writing module is configured to write the data to be written into the second data storage pool according to the write request if the second data storage pool exists.

[0034] The present disclosure also provides a storage cluster comprising a first data storage pool, a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the first data storage pool is used to store data before a data protection policy is changed, and the processor implements the data writing method for a monitoring scenario as described above when executing the computer program.

[0035] The present disclosure also provides a computer readable storage medium having a computer program stored thereon, wherein the computer program is executable on a processor to implement the data writing method for a monitoring scenario as described above.

[0036] The present disclosure also provides a non-transitory computer program product comprising a computer program, wherein the computer program is executable on a processor to implement the data writing method for a monitoring scenario as described above. BRIEF DESCRIPTION OF DRAWINGS

[0037] FIG. 1 is a flowchart of a data writing method for a monitoring scenario according to the present disclosure.

[0038] FIG. 2 is another flowchart of a data writing method for a monitoring scenario according to the present disclosure.

[0039] FIG. 3 is a third flowchart of a data writing method for a monitoring scenario according to the present disclosure.

[0040] FIG. 4 is a schematic diagram of a data storage pool change according to the present disclosure.

[0041] FIG. 5 is another schematic diagram of a data storage pool change according to the present disclosure.

[0042] FIG. 6 is a third schematic diagram of a data storage pool change according to the present disclosure.

[0043] FIG. 7 is a fourth schematic diagram of a data storage pool change according to the present disclosure.

[0044] FIG. 8 is a fifth schematic diagram of a data storage pool change according to the present disclosure.

[0045] FIG. 9 is a structural schematic diagram of a data writing apparatus for a monitoring scenario according to the present disclosure.

[0046] FIG. 10 is a structural schematic diagram of a storage cluster according to the present disclosure. DETAILED DESCRIPTION

[0047] In order to make the objects, technical solutions and advantages of the present disclosure clearer, the technical solutions in the present disclosure will be clearly and completely described below with reference to the drawings in the present disclosure. Obviously, the described embodiments are only some of the embodiments of the present disclosure, but not all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those of ordinary skill in the art without creative work belong to the scope of protection of the present disclosure.

[0048] At present, in a monitoring scene, due to actual scene changes, the protection priority of original data needs to be adjusted, and there may be some data enhanced erasure copy protection and some data reduced data protection. These situations all need to switch the protection strategy, and when the protection strategy is switched, the data migration work is extremely heavy and has a great impact on real-time business. In the related technology, when the scene needs to change the data protection strategy, the current mainstream solution is to add a data protection pool, migrate the storage to the new data pool, and at the same time, through a tool to ensure the access of old data, monitor the retention period and clean up data, or import data from the old data pool to the new data pool. However, this technology has the following problems: it cannot realize online change of the data protection strategy, the upper-layer business needs to be reconfigured when switching the strategy pool, which will affect the data, and it does not support continuous change; the read and write of the business to the new and old data need additional tool support, and the retention period cannot be managed by the upper-layer business as needed; migrating data needs to consume a lot of resources, and at the same time, it will affect real-time business. Based on this, the present embodiment provides a data writing method and device for a monitoring scene, a storage cluster and a medium, which can solve the above technical problems.

[0049] The data writing method for a monitoring scene in the present embodiment will be described below with reference to FIGS. 1-8.

[0050] It should be noted that the execution subject of the present embodiment can be a data writing device for a monitoring scene, or a storage cluster including the data writing device for a monitoring scene, or other devices or equipment, which are not specifically limited here.

[0051] The following embodiments will be described taking the storage cluster as an example.

[0052] FIG. 1 is a flowchart of a data writing method for a monitoring scene provided by the present disclosure, as shown in FIG. 1, the method includes the following steps:

[0053] S102, in the case of obtaining the write request sent by the service layer, detecting whether there is a second data storage pool in the storage cluster; the second data storage pool is used to store data after the data protection policy is changed, the write request includes to-be-written data, and the to-be-written data includes data of the next period after full-period storage of the current monitoring period or data that has not been stored in the current monitoring period.

[0054] In the method, the storage cluster includes a first data storage pool used to store data before the data protection policy is changed. That is, the first data storage pool refers to a data storage pool configured by the storage cluster for the data protection policy before the data protection policy is changed, and can also be referred to as an old data storage pool. The second data storage pool refers to a data storage pool newly configured by the storage cluster according to received data protection policy change information when the data protection policy is changed, and can also be referred to as a new data storage pool, which can store data after the data protection policy is changed.

[0055] The data protection policy can be a erasure copy policy, such as a 6+1 erasure copy policy, a 6+2 erasure copy policy, etc. For the erasure copy policy, such as the 6+1 erasure copy policy, one data copy is stored in the data storage pool for subsequent data verification, and for the 6+2 erasure copy policy, two data copies are stored in the data storage pool for subsequent data verification.

[0056] In this step, during the process of continuously writing / storing monitoring data by the service layer, it is assumed that the storage cluster learns that the current erasure copy policy / data protection policy is changed, it is determined that the protection policy of the current monitoring data needs to be changed, and the current monitoring data needs to be stored in another storage pool. In this step, it can be detected whether there is a second data storage pool in the storage cluster, and a detection result is obtained.

[0057] It can be understood that the second data storage pool is a data storage pool different from the first data storage pool, and the erasure copy policy / data protection policy for storing data in the two data storage pools is different.

[0058] In addition, for the received write request of the service layer, the write request can include to-be-written data, and can also include a to-be-written object corresponding to the to-be-written data. The to-be-written object can be an identifier of the to-be-written data, such as a date identifier, a data name, etc. For example, the data included in the write request is data of a certain day, and the date of a certain day can be considered as the to-be-written object.

[0059] For the above to-be-written data, since the data stored in the embodiment is data under monitoring, in order to save storage space, the monitoring data is usually stored periodically according to a storage period, such as a day, a week, a month, etc. as a period, for example, one week is a monitoring period, then the monitoring data of the next week will overwrite the monitoring data of the last week. The above to-be-written data can include data of a new monitoring period after the data of the current monitoring period is completely stored in the first data storage pool, or can also include data that has not been completely stored in the current monitoring period. For example, if a week is taken as a monitoring period, and the monitoring period is from Monday to Sunday, then the to-be-written data can be the monitoring data of Monday of the second week after the first week, or the monitoring data of, for example, Wednesday in the first week that has not been completely stored.

[0060] In S104, if the second data storage pool exists, the to-be-written data in the write request is written into the second data storage pool.

[0061] In this step, as mentioned above, it can be detected whether there is a second data storage pool in the storage cluster, and a detection result is obtained. If the detection result is that there is a second data storage pool in the storage cluster, that is, there is a data storage pool in the storage cluster that can store data after the data protection policy is changed, then the to-be-written data in the write request can be written into the second data storage pool. When writing data, if the to-be-written data includes data of a new monitoring period after the data of the current monitoring period is completely stored in the first data storage pool, then the to-be-written data can be stored in the second data storage pool in sequence according to the attributes such as the identifier of the new monitoring period, for example, the data stored in the first data storage pool is data0~data7, then the to-be-written data can be written in the second data storage pool from data0. If the to-be-written data includes data that has not been completely stored in the current monitoring period, then the to-be-written data can be stored in the second data storage pool in sequence from the attributes such as the identifier of the data that has not been completely stored in the current monitoring period, for example, the data stored in the first data storage pool is not a full coverage period of data, but data0~data1, then the to-be-written data can be written in the second data storage pool from data2.

[0062] In addition, as mentioned above, the write request can also include a to-be-written object corresponding to the to-be-written data, and if the above detection result is that there is no second data storage pool in the storage cluster, then optionally, if there is no second data storage pool, it is judged whether there is a to-be-written object in the first data storage pool; if there is a to-be-written object, then the to-be-written data is overwritten into the storage space corresponding to the to-be-written object in the first data storage pool according to the write request.

[0063] That is, if there is no second data storage pool in the storage cluster, and it is needed to continue writing / storing data in the original first data storage pool, it can be first judged whether there is a to-be-written object in the first data storage pool, that is, whether there is an identifier (such as the identifier data0) of to-be-written data, if there is an identifier of to-be-written data, the data originally stored in the storage space corresponding to the to-be-written object needs to be updated to the to-be-written data carried in the current write request, that is, the to-be-written data can replace / overwrite the data previously stored in the storage space corresponding to the to-be-written object. If there is no to-be-written object in the first data storage pool, a to-be-written object can be directly created through the attribute information of the to-be-written object and the corresponding storage space is allocated, and the to-be-written data is stored in the storage space corresponding to the to-be-written object.

[0064] Here, when there is no second data storage pool in the storage cluster, it can be indicated that the current data protection policy has not changed, at this time, data can continue to be stored in the original first data storage pool, thereby ensuring the continuity of the business and not affecting the normal operation of the business.

[0065] It can be understood that after the data protection policy is changed, the new data of the business layer is stored by using the changed data protection policy.

[0066] The data writing method for the monitoring scenario of the embodiment is applied to a storage cluster, the storage cluster includes a first data storage pool, the first data storage pool is used to store data before the data protection policy is changed, and the method detects whether there is a second data storage pool in the storage cluster in the case that a write request sent by a business layer is acquired, and writes to-be-written data in the write request into the second data storage pool in the case that there is the second data storage pool. The second data storage pool is used to store data after the data protection policy is changed, the write request includes the to-be-written data, and the to-be-written data includes data of a next period after full-period storage of a current monitoring period or data not completed storage in the current monitoring period. In the method, since whether there is a new data storage pool can be detected through the write request of the business layer, and the deduplication copy strategy of the business layer is determined to change when there is a new data storage pool, that is, the data protection policy is changed, at this time, the data after the data protection policy is changed can be stored in the new data storage pool, thereby supporting online continuous change of the data protection policy, without the need to migrate the data in the original old data storage pool to the new data storage pool, so that resource consumption can be effectively reduced, and the upper-layer real-time business is not affected.

[0067] FIG. 2 is a flowchart of a data writing method for a monitoring scenario according to the present disclosure. As shown in FIG. 2, the write request includes a to-be-written object corresponding to the to-be-written data. The step S104 of writing the to-be-written data into the second data storage pool according to the write request can include the following steps:

[0068] S202, if the to-be-written object exists in the first data storage pool, deleting the data corresponding to the to-be-written object in the first data storage pool.

[0069] S204, creating the to-be-written object in the second data storage pool and establishing a mapping relationship between the to-be-written object in the first data storage pool and the to-be-written object in the second data storage pool.

[0070] S206, according to the mapping relationship, writing the to-be-written data in the write request into the storage space corresponding to the to-be-written object in the second data storage pool.

[0071] In the presence of the second data storage pool, before writing data into the second data storage pool, it can be determined whether the to-be-written object corresponding to the to-be-written data exists in the first data storage pool, i.e., whether an object with the same object attribute as the to-be-written data exists in the first data storage pool. If the to-be-written object exists in the first data storage pool, and the storage space of the to-be-written object in the first data storage pool also stores data, the data stored in the storage space of the to-be-written object in the first data storage pool can be deleted to obtain an empty object. Then, a new to-be-written object can be created in the second data storage pool according to the attribute of the to-be-written object. The newly created to-be-written object is initially empty. A mapping relationship, which can also be referred to as a link relationship, can be established between the empty to-be-written object in the first data storage pool and the to-be-written object in the second data storage pool. In this way, if the business layer needs to access data during the data protection policy change, the corresponding object in the new data storage pool (such as the second data storage pool) can be linked from the object in the first data storage pool through the mapping relationship to access the data of the corresponding object, thereby ensuring the continuity of the business.

[0072] After the mapping relationship is established, the to-be-written data newly transmitted by the business layer can be written into the storage space of the to-be-written object in the second data storage pool.

[0073] In addition, as an optional embodiment, if the to-be-written object does not exist in the first data storage pool, the to-be-written object is created in the first data storage pool; the to-be-written object is created in the second data storage pool, and a mapping relationship between the to-be-written object in the first data storage pool and the to-be-written object in the second data storage pool is established; and according to the mapping relationship, the to-be-written data in the write request is written into the storage space corresponding to the to-be-written object in the second data storage pool.

[0074] That is, if the to-be-written object does not exist in the first data storage pool, it means that the first data storage pool does not have data corresponding to the to-be-written object, and then in order to facilitate the intermediate business layer to access the data of the to-be-written object, the to-be-written object can be newly created in the first data storage pool according to the attributes of the to-be-written object, and the to-be-written object created here is an empty object without stored data. At the same time, a new to-be-written object can also be created in the second data storage pool according to the attributes of the to-be-written object, and the to-be-written object created here is also empty at the beginning. Then a mapping relationship between the empty to-be-written object in the first data storage pool and the to-be-written object in the second data storage pool can be established, and the mapping relationship can also be called a link relationship. In this way, if the business layer needs to access data during the data protection policy change, the corresponding object in the new data storage pool can be linked from the object in the first data storage pool through the mapping relationship to access the data of the corresponding object, thereby ensuring the continuity of the business. After the mapping relationship is established, the newly transmitted to-be-written data of the business layer can also be written into the storage space of the to-be-written object in the second data storage pool.

[0075] In addition, it should be noted that each object in the first data storage pool can establish a mapping relationship of its own data storage pool, and the mapping relationship represents the data storage pool where the data of the object in the first data storage pool is specifically stored.

[0076] In this embodiment, by deleting the data of the to-be-written object in the first data storage pool when the to-be-written object exists in the first data storage pool, and by newly creating the to-be-written object in the second data storage pool and establishing a mapping relationship between the to-be-written objects in the two data storage pools, if the business layer needs to access data during the data protection policy change, the corresponding object in the new data storage pool can be linked from the object in the first data storage pool through the mapping relationship to access the data of the corresponding object, thereby ensuring the continuity of the business. In addition, by newly creating the to-be-written object in the first data storage pool when the to-be-written object does not exist in the first data storage pool, and by newly creating the to-be-written object in the second data storage pool and establishing a mapping relationship between the to-be-written objects in the two data storage pools, the continuity of the business can also be ensured in the case that the to-be-written object does not exist in the first data storage pool.

[0077] Further, for the storage cluster, a data index pool can be pre-configured, the data index pool includes a plurality of objects and mapping relationship of each object, and the data index pool is mainly used to link the object accessed by the business layer to the data storage pool actually storing the data of the object. The data index pool is the first data storage pool at the beginning, that is, the two are consistent, and in the process of continuously changing the data protection strategy, the data storage pool and the data index pool can be continuously replaced according to the storage condition of the data. Based on this, when detecting whether the second data storage pool exists in the storage cluster, it is actually detected whether the data index pool is consistent with the first data storage pool. If consistent, it means that there is no second data storage pool, and if inconsistent, it means that there is a second data storage pool.

[0078] In addition, for the storage cluster, the metadata storage pool can also be included, and the first command is stored in the metadata storage pool. The first command includes the first identifier of the first data storage pool, that is, the identifier of the data index pool is actually stored in the first command, which belongs to the permanent command and will be updated only after the data of the old data storage pool is completely deleted. Since the above is described by taking the first data storage pool as the first data storage pool, the identifier of the first data storage pool is the identifier of the data index pool, which is recorded as the first identifier, such as Data1. Then, in the process of continuously changing the data protection strategy, the first identifier of the data index pool in the metadata storage pool can also be updated according to the storage condition of the data, and the following embodiment describes the process of updating the first identifier of the data index pool.

[0079] In some embodiments, the method can further include the following steps:

[0080] If the data in the first data storage pool is completely deleted, and the second data storage pool mapped by all objects in the mapping relationship is the same data storage pool, the first data storage pool is released; the second identifier of the second data storage pool is obtained, and the first identifier in the first command is replaced by the second identifier.

[0081] In some embodiments, the method can further include the following steps:

[0082] Then an identifier corresponding to the new second data storage pool can be acquired, denoted as a second identifier. The second data storage pool can be used as a new data index pool. Therefore, the identifier of the data index pool in the metadata storage pool can be updated, specifically, the first identifier is replaced by the second identifier, that is, the data index pool is currently the second data storage pool.

[0083] In the embodiment, the first data storage pool is released after all data in the old first data storage pool is deleted. In this way, storage space can be saved. Meanwhile, the identifier of the data index pool is updated to the identifier of the new second data storage pool. In this way, the online continuous change of the data protection policy can be realized, and the normal operation of the business during this period is ensured without being affected.

[0084] Further, the second command can also be stored in the metadata storage pool. The second command includes the first identifier of the first data storage pool. The second command actually stores the identifier of the data storage pool currently storing data, and belongs to a temporary command, which can be updated with the new data storage pool. Since the above is described by taking the first data storage pool as the first data storage pool, the identifier stored in the second command is the identifier of the first data storage pool at the beginning. The identifier can be updated with the new data storage pool. The following embodiments describe how to update the identifier of the data storage pool currently storing data in the second command.

[0085] In some embodiments, before detecting whether the second data storage pool exists in the storage cluster in S102, the method can further include the following steps:

[0086] The data protection policy change instruction sent by the business layer is acquired. The data protection policy change instruction includes the target protection level corresponding to the changed data protection policy.

[0087] The second data storage pool matched with the target protection level is determined in the storage cluster according to the target protection level. The storage cluster includes data storage pools with different protection levels.

[0088] The second identifier of the second data storage pool is acquired, and the first identifier in the second command is replaced by the second identifier.

[0089] Among them, as mentioned above, when the data protection policy changes, the storage cluster can learn that the data protection policy changes, and the specific learning method can be that the business layer sends a data protection policy change instruction to the storage cluster to indicate that the storage cluster data protection policy changes. For this protection policy change instruction, it can not only indicate that the data protection policy changes, but also include the protection level corresponding to the changed data protection policy, denoted as the target protection level. The target protection level can be higher than the protection level of the data protection policy before the change, or the target protection level can be lower than the protection level of the data protection policy before the change. Here, the higher the general protection level, the more / larger the storage space required.

[0090] The above storage cluster can include a plurality of different data storage pools, and each data storage pool can correspond to its own protection level, i.e. there can be data storage pools with different protection levels in the storage cluster. Then after obtaining the data protection policy change instruction of the business layer, the target protection level after the change can be parsed, and then the data storage pool corresponding to the protection level (generally equal to or greater than) matching the target protection level can be found in the storage cluster. The matching data storage pool can be denoted as the second data storage pool. Then the second identifier corresponding to the second data storage pool in the storage cluster can be obtained, denoted as the second identifier, such as Data2. Then the first identifier in the second command can be replaced by the second identifier, i.e. the data storage pool of the current stored data is updated from the first data storage pool to the second data storage pool.

[0091] After the steps of the present embodiment, for the detected data index pool whether it is consistent with the first data storage pool, the actual detection is whether the identifier in the first command and the identifier in the second command are consistent. If they are consistent, it means that there is no new data storage pool, and if they are not consistent, it means that there is a new data storage pool.

[0092] In the present embodiment, when the data protection policy changes, the business layer informs the storage cluster and informs the protection level of the changed protection policy, so that the storage cluster can find the second data storage pool matching the level, and update the identifier of the current stored data in the second command according to this. This can facilitate the storage cluster to quickly and accurately detect the new data storage pool to store data when the business layer needs to write data, and improve the efficiency and accuracy of data writing / storage.

[0093] The above embodiment illustrates the process of data writing of the business layer to the data storage pool, and the following embodiment illustrates the process of data reading of the business layer from the data storage pool.

[0094] Figure 3 is a flowchart of a third method for writing data for a monitoring scenario according to the present disclosure. As shown in Figure 3, the method can further include the following steps:

[0095] In step S302, a read request sent by the service layer is obtained. The read request includes a to-be-read object corresponding to the data to be read.

[0096] When the service layer needs to read data in the data storage pool, the data of which object needs to be read can be determined first, i.e., the to-be-read object can be determined first, and then the to-be-read object can be encapsulated in the read request and sent to the storage cluster, so that the storage cluster can obtain the object to be read by the service layer, i.e., the to-be-read object.

[0097] In step S304, if the data corresponding to the to-be-read object in the first data storage pool is not empty, the data stored in the storage space of the to-be-read object in the first data storage pool is read.

[0098] In this step, the first data storage pool can be the current data index pool, and the storage cluster can first find the to-be-read object in the first data storage pool and determine whether the storage space of the to-be-read object stores data. If the storage space of the to-be-read object stores data, i.e., the to-be-read object in the first data storage pool is not an empty object, the corresponding data in the storage space of the to-be-read object in the first data storage pool can be read and sent to the service layer.

[0099] In step S306, if the data corresponding to the to-be-read object in the first data storage pool is empty, the to-be-read object is found in the second data storage pool according to the mapping relationship, and the data stored in the storage space of the to-be-read object in the second data storage pool is read.

[0100] In this step, if the storage cluster finds the to-be-read object in the first data storage pool and determines that the storage space of the to-be-read object does not store data, i.e., the to-be-read object in the first data storage pool is an empty object, the to-be-read object can be linked to the same object in the second data storage pool through the mapping relationship / linkage relationship between the object in the first data storage pool and the same object in the new second data storage pool, and the corresponding data in the storage space of the to-be-read object in the second data storage pool can be read and sent to the service layer.

[0101] In this embodiment, when the service layer needs to read data, the data of the object to be read can be directly read when the data of the object to be read exists in the old first data storage pool, and the read request can be linked to the new second data storage pool through the linkage relationship to read the corresponding data when the data of the object to be read does not exist in the old first data storage pool. In this way, the read request of the service layer can be smoothly executed even if the protection strategy is constantly changed, and the normal reading of the service layer is not affected.

[0102] In order to more specifically describe the technical solutions of the present disclosure, an example scenario is given below for description.

[0103] The scenario is as follows: the original data is stored in the erasure 6+1 policy pool Data1, and then upgraded to the erasure 6+2 policy, and subsequently, due to business needs, a new three-copy data pool is created, and the data protection level is upgraded to the 6+3 policy again.

[0104] Referring to one of the data storage pool change diagrams shown in FIG. 4, the initial configuration data storage pool is Data1, and the erasure 6+2 data storage pool Data2 is switched in the middle. Among them, meta represents the metadata stored in the metadata storage pool. {“dataIdxPol”:“DataX”} is the first command, which represents the information of the data index pool. DataX represents the identification of the data index pool, and X represents the specific identification number. The identification of the data index pool is the identification of the first data storage pool at the beginning, that is, Data1. {“dataPol”:“DataY”} is the second command, which represents the information of the data storage pool. DataY represents the identification of the data storage pool, and Y represents the specific identification number. At the beginning, the identification of the first data storage pool is Data1, and when there is a new second data storage pool, it is updated to the identification Data2 of the new second data storage pool. dataP{“link_pol”:“DataZ”} represents the linkage information or mapping relationship, wherein dataP represents the mapped object, DataZ represents the identification of the data storage pool to which the mapped / linked object is mapped / linked, and P and Z represent the specific identification numbers, respectively.

[0105] The specific data storage pool and data index pool change process is as follows:

[0106] 1. The initial configuration data storage pool of the storage cluster is Data1, at this time, the identification of the data storage pool and the identification of the data index pool recorded in the metadata storage pool are both Data1, that is, the first command {“dataIdxPol”:“Data1”}, the second command {“dataPol”:“Data1”}, and the erasure policy is 6+1.

[0107] 2. After monitoring the data storage for a period of time, refer to one of the data storage pool change diagrams shown in Figure 4, obtain the data protection policy change instruction sent by the business layer, switch the data protection policy from erasure policy 6+1 to erasure policy 6+2, and switch the current data storage pool from the data storage pool Data1 corresponding to erasure policy 6+1 to the data storage pool Data2 corresponding to erasure policy 6+2.

[0108] 3. At this point, update the identifier of the data storage pool recorded in the metadata storage pool to Data2, that is, update the second command {"dataPol":"Data1"} to {"dataPol":"Data2"}. Determine whether Data1 meets the cleanup conditions (i.e., all data in Data1 has been deleted). If the cleanup conditions are not met, continue to use Data1 as the data index pool.

[0109] 4. When writing data at the business layer, the information of the data index pool and data storage pool is sent to Data1. If the storage cluster detects that the current data storage pool is not Data1 but Data2, an empty object is created in Data1, and the attribute information of the empty object, i.e. the mapping / association / link information, is recorded as {"link_pol":"Data2"}, and data is written to Data2.

[0110] 5. After writing data for a period of time, the data protection strategy is switched from erasure policy 6+2 to erasure policy 6+3, and the data storage pool is switched to the data storage pool Data3 corresponding to erasure policy 6+3. See the second schematic diagram of data storage pool change in Figure 5. After writing for a period of time, the data protection strategy is changed back to erasure policy 6+3. The identifier update strategy of the data storage pool in the metadata storage pool is the same as the initial change, and is changed to {"dataPol":"Data3"}. The data index pool is still Data1. When writing data to the new data storage pool, the corresponding empty object is still created in the data index pool and the mapping relationship / association relationship / link relationship is recorded.

[0111] 6. At any time, refer to the third schematic diagram of data storage pool change shown in Figure 6 to check whether the data index pool meets the update conditions, that is, whether the data index pool is full of empty objects. If it is detected that the data index pool does not meet the update conditions, empty objects are still created, and the mapping relationship / association relationship / link relationship of the empty objects are recorded.

[0112] 7. Write data from the current data storage pool, count a monitoring period after full coverage, see Figure 7 for the fourth data storage pool change schematic diagram, when full coverage is completed, at this time all data is saved in the data storage pool Data3, only empty objects and mapping relationship / correlation / linking relationship data are left in the original data index pool Data1. It should be noted that the storage space occupied by the mapping relationship / correlation / linking relationship data is negligible compared to the actual data occupied space.

[0113] 8. When it is detected that the data index pool no longer contains objects storing data (i.e. all empty objects), and there is no associated data storage pool (i.e. the data storage pool information mapped / correlated / linked by the empty objects is inconsistent), (for processing multiple change scenarios), clean up the mapping relationship / correlation / linking relationship data in the current data index pool, and update the identification information in the metadata storage pool. See Figure 8 for the fifth data storage pool change schematic diagram, which can be specifically judged that the original data index pool Data1 has no abnormal items (i.e. only empty objects are left in the Data1 pool, and the data storage pool mapped / correlated / linked by the empty objects is consistent, such as being mapped / correlated / linked to Data3), then notify the metadata storage pool to update the identification of the data storage pool and the identification of the data index pool to Data3, i.e. update the first command in the metadata storage pool from the identification of the first data storage pool {“dataIdxPol”:“Data1”} to the identification of the third data storage pool {“dataIdxPol”:“Data3”}, and release the original data storage pool Data1 and the intermediate data storage pool Data2, by which the original data storage pool Data1 and the intermediate data storage pool Data2 are released from the business, thereby completing the continuous online change of the data protection policy without affecting the real-time business background.

[0114] From the above description of the embodiments, it can be known that the technical scheme of the present disclosure has the following technical effects:

[0115] 1. Continuous data protection policy online change service can be provided.

[0116] 2. The mapping relationship / correlation / linking relationship data uses a database space that is negligible compared to the actual data occupied space. Since the actual data space is cleaned up, if the evaluation of the amount of data written does not exceed the amount of data migrated, the original data storage pool can provide complete storage services before the data protection policy change is completed.

[0117] 3. During the data protection policy change, the new data of the business layer uses the new protection policy, which can be combined with object attributes as secondary index correlation to realize transparent access of the business layer to the cluster cross-pool data, that is, the old data storage pool can also support business access to ensure the continuity of the business and be transparent to the upper layer business.

[0118] 4. In the actual monitoring system, the data in the original data storage pool will be written by the business layer and gradually cleaned and replaced by the full coverage process. There is no additional data cleaning and migration work, the resource consumption is low, and the real-time business is not affected.

[0119] 5. The configuration is simplified, that is, the actual occupied space of the original data storage pool and the intermediate data storage pool can be released, and the storage space is saved.

[0120] The data writing device for a monitoring scenario provided by the present disclosure is described below. The data writing device for a monitoring scenario described below can be mutually corresponding with the data writing method for a monitoring scenario described above.

[0121] FIG. 9 is a structural schematic diagram of the data writing device for a monitoring scenario provided by the present disclosure. As shown in FIG. 9, the device can be applied to a storage cluster. The storage cluster includes a first data storage pool. The first data storage pool is used to store data before a data protection policy is changed. The device can include:

[0122] The detection module 410 is configured to detect whether a second data storage pool exists in the storage cluster when the write request sent by the business layer is acquired. The second data storage pool is used to store data after the data protection policy is changed. The write request includes to-be-written data. The to-be-written data includes data of a next period after full-period storage of a current monitoring period or data that is not completed for storage in the current monitoring period.

[0123] The write data module 420 is configured to write the to-be-written data into the second data storage pool according to the write request if the second data storage pool exists.

[0124] In some embodiments, the write request includes a to-be-written object corresponding to the to-be-written data. The write data module 420 is specifically configured to delete data corresponding to the to-be-written object in the first data storage pool if the to-be-written object exists in the first data storage pool. The to-be-written object is created in the second data storage pool, and a mapping relationship between the to-be-written object in the first data storage pool and the to-be-written object in the second data storage pool is established. According to the mapping relationship, the to-be-written data in the write request is written into a storage space corresponding to the to-be-written object in the second data storage pool.

[0125] Optionally, the write data module 420 is further configured to, if the to-be-written object does not exist in the first data storage pool, create the to-be-written object in the first data storage pool; create the to-be-written object in the second data storage pool, and establish a mapping relationship between the to-be-written object in the first data storage pool and the to-be-written object in the second data storage pool; and write the to-be-written data in the write request into a storage space corresponding to the to-be-written object in the second data storage pool according to the mapping relationship.

[0126] In some embodiments, the write request includes a to-be-written object corresponding to the to-be-written data, and the write data module 420 is further configured to, if the second data storage pool does not exist, determine whether the to-be-written object exists in the first data storage pool; if the to-be-written object exists, overwrite the to-be-written data into a storage space corresponding to the to-be-written object in the first data storage pool according to the write request.

[0127] In some embodiments, the storage cluster further includes a metadata storage pool, the metadata storage pool stores a first command, the first command includes a first identifier of the first data storage pool, and the apparatus further includes a first update module configured to, if all data in the first data storage pool is completely deleted and all second data storage pools mapped by all objects in the mapping relationship are the same data storage pool, release the first data storage pool; obtain a second identifier of the second data storage pool, and replace the first identifier in the first command with the second identifier.

[0128] In some embodiments, the storage cluster further includes a second data storage pool and a metadata storage pool, the metadata storage pool stores a second command, the second command includes a first identifier of the first data storage pool, and before detecting whether the second data storage pool exists in the storage cluster, the apparatus further includes:

[0129] a second update module configured to obtain a data protection policy change instruction sent by the business layer, the data protection policy change instruction includes a target protection level corresponding to a changed data protection policy; determine a second data storage pool matching the target protection level in the storage cluster according to the target protection level, the storage cluster includes data storage pools of different protection levels; obtain a second identifier of the second data storage pool, and replace the first identifier in the second command with the second identifier.

[0130] In some embodiments, the apparatus further includes:

[0131] a read request obtaining module configured to obtain a read request sent by the business layer, the read request including a to-be-read object corresponding to to-be-read data;

[0132] The read data module is configured to read data stored in the storage space of the to-be-read object in the first data storage pool if the data corresponding to the to-be-read object in the first data storage pool is not empty.

[0133] The read data module is further configured to find the to-be-read object in the second data storage pool according to the mapping relationship and read data stored in the storage space of the to-be-read object in the second data storage pool if the data corresponding to the to-be-read object in the first data storage pool is empty.

[0134] It should be noted that the above device provided by the embodiments of the present disclosure can realize all the method steps achieved by the above method embodiments and achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiments will not be described in detail.

[0135] FIG. 10 illustrates an entity structure diagram of a storage cluster. As shown in FIG. 10, the storage cluster can include a first data storage pool, a processor 510, a communications interface 520, a memory 530, and a communications bus 540. The first data storage pool is configured to store data before a data protection policy change. The processor 510, the communications interface 520, and the memory 530 can complete mutual communication through the communications bus 540. The processor 510 can invoke a logical instruction in the memory 530 to execute a data writing method for a monitoring scenario. The method includes: in a case where a write request sent by a business layer is acquired, detecting whether a second data storage pool exists in the storage cluster. The second data storage pool is configured to store data after the data protection policy change. The write request includes to-be-written data. The to-be-written data includes data of a next period after full-period storage of a current monitoring period or data that has not been stored in the current monitoring period. If the second data storage pool exists, the to-be-written data is written into the second data storage pool according to the write request.

[0136] In addition, the logic instructions in the memory 530 described above can be implemented in the form of a software function unit and sold or used as an independent product, which can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present disclosure essentially or the part that contributes to the prior art or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions for making a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in each embodiment of the present disclosure. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and each kind of medium that can store program codes.

[0137] In another aspect, the present disclosure also provides a computer program product, which includes a computer program, the computer program can be stored on a computer readable storage medium, and the computer program is executed by a processor, so that the computer can execute the data writing method for a monitoring scenario provided by each method described above, and the method includes: in the case that a write request sent by a business layer is acquired, detecting whether a second data storage pool exists in a storage cluster; the second data storage pool is used to store data after a data protection policy is changed, the write request includes to-be-written data, and the to-be-written data includes data of a next period after full-period storage of a current monitoring period or data that is not completed for storage in the current monitoring period; and if the second data storage pool exists, the to-be-written data is written into the second data storage pool according to the write request.

[0138] In another aspect, the present disclosure also provides a computer program product, which includes a computer program, the computer program can be stored on a computer readable storage medium, and the computer program is executed by a processor, so that the computer can execute the data writing method for a monitoring scenario provided by each method described above, and the method includes: in the case that a write request sent by a business layer is acquired, detecting whether a second data storage pool exists in a storage cluster; the second data storage pool is used to store data after a data protection policy is changed, the write request includes to-be-written data, and the to-be-written data includes data of a next period after full-period storage of a current monitoring period or data that is not completed for storage in the current monitoring period; and if the second data storage pool exists, the to-be-written data is written into the second data storage pool according to the write request.

[0139] The device embodiments described above are merely illustrative, wherein the units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed to multiple network units. Part or all of the modules can be selected to achieve the purposes of the embodiments according to actual needs. Those skilled in the art can understand and implement without creative labor.

[0140] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be realized by means of software plus a necessary general hardware platform, and of course can also be realized by hardware. Based on such understanding, the above technical solutions can be embodied in the form of a software product, which can be stored in a computer readable storage medium, such as a ROM / RAM, a magnetic disk, an optical disk, etc., and includes a plurality of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute the methods described in each embodiment or some parts of the embodiments.

[0141] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present disclosure, and not to limit them; although the present disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in each of the foregoing embodiments, or make equivalent replacement for part of the technical features; and these modifications or replacements do not make the corresponding technical solutions deviate from the spirit and scope of the technical solutions of each embodiment of the present disclosure.

Claims

1. A data writing method for monitoring scenarios, applied to a storage cluster, the storage cluster including a first data storage pool, the first data storage pool being used to store data prior to changes in data protection policies, the method comprising: Upon receiving a write request from the business layer, detect whether a second data storage pool exists in the storage cluster; The second data storage pool is used to store data after the data protection policy has been changed. The write request includes data to be written, which includes data in the next cycle after the current monitoring cycle is fully stored or data that has not been fully stored in the current monitoring cycle. If the second data storage pool exists, the data to be written is written to the second data storage pool according to the write request.

2. The data writing method for monitoring scenarios according to claim 1, wherein, The write request includes the object to be written corresponding to the data to be written, and the step of writing the data to be written to the second data storage pool according to the write request includes: If the object to be written exists in the first data storage pool, then delete the data corresponding to the object to be written in the first data storage pool; Create the object to be written in the second data storage pool, and establish a mapping relationship between the object to be written in the first data storage pool and the object to be written in the second data storage pool; According to the mapping relationship, the data to be written in the write request is written to the storage space corresponding to the object to be written in the second data storage pool.

3. The data writing method for monitoring scenarios according to claim 2, wherein, The method further includes: If the object to be written does not exist in the first data storage pool, then the object to be written is created in the first data storage pool; Create the object to be written in the second data storage pool, and establish a mapping relationship between the object to be written in the first data storage pool and the object to be written in the second data storage pool; According to the mapping relationship, the data to be written in the write request is written to the storage space corresponding to the object to be written in the second data storage pool.

4. The data writing method for monitoring scenarios according to claim 1, wherein, The write request includes the object to be written corresponding to the data to be written, and the method further includes: If the second data storage pool does not exist, then determine whether the object to be written exists in the first data storage pool; If the object to be written exists, then according to the write request, the data to be written is overwritten into the storage space corresponding to the object to be written in the first data storage pool.

5. The data writing method for monitoring scenarios according to any one of claims 2 to 4, wherein, The storage cluster further includes a metadata storage pool, which stores a first command, the first command including a first identifier of the first data storage pool, and the method further includes: If all data in the first data storage pool has been deleted, and all objects in the mapping relationship are mapped to the same second data storage pool, then the first data storage pool is released. Obtain the second identifier of the second data storage pool, and replace the first identifier in the first command with the second identifier.

6. The data writing method for monitoring scenarios according to any one of claims 1 to 4, wherein, The storage cluster further includes a second data storage pool and a metadata storage pool. The metadata storage pool stores a second command, which includes a first identifier of the first data storage pool. Before detecting whether the second data storage pool exists in the storage cluster, the method further includes: Obtain the data protection policy change instruction sent by the service layer; the data protection policy change instruction includes the target protection level corresponding to the changed data protection policy; A second data storage pool matching the target protection level is determined in the storage cluster; the storage cluster includes data storage pools with different protection levels. Obtain the second identifier of the second data storage pool, and replace the first identifier in the second command with the second identifier.

7. The data writing method for monitoring scenarios according to claim 2 or 3, wherein, The method further includes: Obtain the read request sent by the business layer; the read request includes the object to be read corresponding to the data to be read; If the data corresponding to the object to be read in the first data storage pool is not empty, then the data stored in the storage space of the object to be read is read from the first data storage pool; If the data corresponding to the object to be read in the first data storage pool is empty, then the object to be read is found in the second data storage pool according to the mapping relationship, and the data stored in the storage space of the object to be read is read in the second data storage pool.

8. A data writing device for monitoring scenarios, applied to a storage cluster, the storage cluster including a first data storage pool, the first data storage pool being used to store data prior to a change in data protection policy, the device comprising: The detection module is configured to detect whether a second data storage pool exists in the storage cluster when a write request is received from the business layer. The second data storage pool is used to store data after the data protection policy has been changed. The write request includes data to be written, which includes data in the next cycle after the current monitoring cycle is fully stored or data that has not been fully stored in the current monitoring cycle. The write data module is configured to write the data to be written to the second data storage pool according to the write request if the second data storage pool exists.

9. The data writing device for monitoring scenarios according to claim 8, wherein, The write request includes the object to be written corresponding to the data to be written. The write data module is specifically configured to delete the data corresponding to the object to be written in the first data storage pool if the object to be written exists in the first data storage pool. Create the object to be written in the second data storage pool, and establish a mapping relationship between the object to be written in the first data storage pool and the object to be written in the second data storage pool; According to the mapping relationship, the data to be written in the write request is written to the storage space corresponding to the object to be written in the second data storage pool.

10. The data writing device for monitoring scenarios according to claim 9, wherein, The write data module is further configured to create the object to be written in the first data storage pool if the object to be written does not exist in the first data storage pool. Create the object to be written in the second data storage pool, and establish a mapping relationship between the object to be written in the first data storage pool and the object to be written in the second data storage pool; According to the mapping relationship, the data to be written in the write request is written to the storage space corresponding to the object to be written in the second data storage pool.

11. The data writing device for monitoring scenarios according to claim 8, wherein, The write request includes the object to be written corresponding to the data to be written. The write data module is also configured to determine whether the object to be written exists in the first data storage pool if the second data storage pool does not exist. If the object to be written exists, then according to the write request, the data to be written is overwritten into the storage space corresponding to the object to be written in the first data storage pool.

12. The data writing device for monitoring scenarios according to any one of claims 9 to 11, wherein, The storage cluster further includes a metadata storage pool, which stores a first command, the first command including a first identifier of the first data storage pool. The device further includes: The first update module is configured to release the first data storage pool if all data in the first data storage pool has been deleted and all objects in the mapping relationship are mapped to the same second data storage pool; obtain the second identifier of the second data storage pool and replace the first identifier in the first command with the second identifier.

13. The data writing device for monitoring scenarios according to any one of claims 8 to 11, wherein, The storage cluster further includes a second data storage pool and a metadata storage pool. The metadata storage pool stores a second command, which includes a first identifier of the first data storage pool. Before the detection module detects whether the second data storage pool exists in the storage cluster, the device further includes: The second update module is configured to: obtain a data protection policy change instruction sent by the service layer; the data protection policy change instruction includes a target protection level corresponding to the changed data protection policy; determine a second data storage pool in the storage cluster that matches the target protection level according to the target protection level; the storage cluster includes data storage pools with different protection levels; obtain a second identifier of the second data storage pool, and replace the first identifier in the second command with the second identifier.

14. The data writing device for monitoring scenarios according to claim 9 or 10, wherein, The device further includes: The read request acquisition module is configured to acquire read requests sent by the business layer; the read request includes the object to be read corresponding to the data to be read. The data reading module is configured to read the data stored in the storage space of the object to be read in the first data storage pool if the data corresponding to the object to be read in the first data storage pool is not empty; The data reading module is further configured to, if the data corresponding to the object to be read in the first data storage pool is empty, find the object to be read in the second data storage pool according to the mapping relationship, and read the data stored in the storage space of the object to be read in the second data storage pool.

15. A storage cluster, the storage cluster comprising a first data storage pool, a memory, a processor, and a computer program stored on the memory and executable on the processor, the first data storage pool being used to store data prior to a change in a data protection policy, and the processor executing the program implementing the data writing method for a monitoring scenario as described in any one of claims 1 to 7.

16. A non-transitory computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the data writing method for a monitoring scenario as described in any one of claims 1 to 7.

Images