Data management method and device of edge node, storage medium and electronic equipment

By searching and using sqlite files on edge nodes to store and manage resources, the complex system performance problem when edge nodes update resources is solved, and the effect of reducing input and output resource consumption and system load is achieved.

CN119719039APending Publication Date: 2025-03-28BEIJING KINGSOFT CLOUD NETWORK TECH CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311255989.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-09-26
Publication Date
2025-03-28

AI Technical Summary

Technical Problem

When edge nodes update resources, they consume a lot of input and output resources, and the system performance is complex and large.

Method used

Find the sqlite file of the sqlite database on the edge node, and when receiving the file management instructions, store the target data into the sqlite file or delete it from the sqlite file.

Benefits of technology

By configuring sqlite files to store resources of edge nodes, the input and output operations are reduced, the consumption of input and output resources is reduced, and the system performance load is reduced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119719039A_ABST
    Figure CN119719039A_ABST
Patent Text Reader

Abstract

The invention relates to a data management method and device for edge nodes, a storage medium and electronic equipment. The method comprises the steps that under the condition that a file management instruction is received, target data requested to be managed by the file management instruction is determined, and the file management instruction is used for newly adding or deleting the target data; an sqlite file of an sqlite database is searched for on the edge node; and under the condition that the sqlite file is found, storing the target data into the sqlite file or deleting the target data from the sqlite file. The method and the device solve the technical problems of more input and output resource consumption and high system performance complexity during resource updating of the edge node.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a data management method, device, storage medium and electronic device for edge nodes. Background Art

[0002] In the prior art, for edge nodes in a content distribution network, a portion of popular resources can be downloaded from the central node to the edge nodes in advance, so that when edge users access the edge nodes, they can directly obtain popular resources from the edge nodes without waiting for the edge nodes to obtain the resources from the central node.

[0003] In the prior art, for edge nodes composed of routers, routing boxes, etc. in the home, if resources are stored in the edge nodes, every time new resources are to be stored in the edge nodes, all data needs to be written to the disk, which consumes a large amount of input and output resources and places a heavy load on system performance. Summary of the invention

[0004] The present application provides a data management method, device, storage medium and electronic device for edge nodes to solve the technical problems of consuming a lot of input and output resources and complex system performance when updating resources at edge nodes.

[0005] In a first aspect, the present application provides a data management method for an edge node, comprising: upon receiving a file management instruction, determining the target data requested to be managed by the above file management instruction, wherein the above file management instruction is used to add or delete the above target data; searching for an sqlite file of an sqlite database on the above edge node; and upon finding the above sqlite file, storing the above target data in the above sqlite file or deleting the above target data from the above sqlite file.

[0006] In the second aspect, the present application provides a data management device for an edge node, comprising: a determination module, used to determine the target data requested to be managed by the file management instruction when a file management instruction is received, wherein the file management instruction is used to add or delete the target data; a search module, used to search for the sqlite file of the sqlite database on the edge node; a processing module, used to store the target data into the sqlite file or delete the target data from the sqlite file when the sqlite file is found.

[0007] As an optional example, the above-mentioned search module includes: a search unit, which is used to obtain the storage path of the above-mentioned sqlite file stored in advance when the above-mentioned sqlite file is stored in the program folder of the above-mentioned edge node, and determine the file under the above-mentioned storage path as the above-mentioned sqlite file, wherein the above-mentioned program folder is used to store the running program of the above-mentioned edge node; when the above-mentioned sqlite file is stored outside the program folder of the above-mentioned edge node, traverse all folders of the above-mentioned edge node through the file name of the above-mentioned sqlite file until the above-mentioned sqlite file is found.

[0008] As an optional example, the above-mentioned processing module includes: a processing unit, which is used to call the application program interface to locate the first position where the above-mentioned target data should be inserted when the above-mentioned target data is added; and to call the application program interface to locate the second position of the above-mentioned target data in the above-mentioned sqlite file when the above-mentioned target data is deleted.

[0009] As an optional example, the above-mentioned processing unit includes: a first processing sub-unit, used to determine the data type of the above-mentioned target data; determine the position after the last data of the above-mentioned data type in the above-mentioned sqlite file as the above-mentioned first position, or determine the position before the last data of the above-mentioned data type in the above-mentioned sqlite file as the above-mentioned first position, wherein data of the same data type are clustered and distributed in the above-mentioned sqlite file.

[0010] As an optional example, the above-mentioned processing unit includes: a second processing sub-unit, used to determine the data type of the above-mentioned target data; determine the position after the first data of the above-mentioned data type in the above-mentioned sqlite file as the above-mentioned first position, or determine the position before the first data of the above-mentioned data type in the above-mentioned sqlite file as the above-mentioned first position, wherein data of the same data type are dispersed in the above-mentioned sqlite file.

[0011] As an optional example, the processing module includes: a deletion unit, used to determine the size of the available storage space of the edge node; when the data size of the target data exceeds the size of the available storage space, prohibiting the target data from being stored in the sqlite file; or, when the data size of the target data exceeds the size of the available storage space, deleting the data with the lowest number of accesses in the sqlite file until the size of the available storage space exceeds the data size of the target data.

[0012] As an optional example, the processing module includes: a storage unit, used to determine the preset storage condition of the edge node; when the target data meets the preset storage condition, storing the target data in the sqlite file.

[0013] In a third aspect, the present application provides an electronic device comprising: at least one communication interface; at least one bus connected to the at least one communication interface; at least one processor connected to the at least one bus; and at least one memory connected to the at least one bus, wherein the memory stores a computer program, and the processor is configured to implement any one of the above-mentioned edge node data management methods when executing the computer program.

[0014] In a fourth aspect, the present application further provides a computer storage medium storing computer executable instructions, wherein the computer executable instructions are used to execute the data management method for edge nodes described in any one of the above items of the present application.

[0015] The above technical solution provided by the embodiment of the present application has the following advantages over the prior art: In the embodiment of the present application, for an edge node, if a file management instruction for adding or deleting target data is received, the sqlite file of the sqlite database is searched on the edge node, and the sqlite file stores the resources stored by the edge node. When the sqlite file is found, the target data is stored in the sqlite file or the target data is deleted from the sqlite file, so that the resources of the edge node can be stored by configuring the sqlite file on the edge node, which reduces input and output operations, reduces the consumption of input and output resources, and reduces the system performance load. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0017] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0018] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0019] Figure 1 A flowchart of a data management method for an edge node provided in an embodiment of the present application;

[0020] Figure 2 A flowchart of another edge node data management method provided in an embodiment of the present application;

[0021] Figure 3 A flowchart of another edge node data management method provided in an embodiment of the present application;

[0022] Figure 4 A flowchart of another edge node data management method provided in an embodiment of the present application;

[0023] Figure 5 A flowchart of another edge node data management method provided in an embodiment of the present application;

[0024] Figure 6 A system flow chart of a data management method for an edge node provided in an embodiment of the present application;

[0025] Figure 7 A schematic diagram of the structure of a data management device for an edge node provided in an embodiment of the present application;

[0026] Figure 8 A schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0028] The disclosure below provides many different embodiments or examples to implement different structures of the present invention. In order to simplify the disclosure of the present invention, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present invention. In addition, the present invention can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0029] In order to solve the technical problems in the prior art that edge nodes consume a lot of input and output resources when updating resources and the system performance is complex, the present application provides a data management method for edge nodes, which can achieve the effect of reducing system load.

[0030] Figure 1 This is a flow chart of a data management method for an edge node provided in an embodiment of the present application. Figure 1 As shown, the data management method of the edge node includes:

[0031] S102, when receiving a file management instruction, determining target data requested to be managed by the file management instruction, wherein the file management instruction is used to add or delete target data;

[0032] S104, searching for the sqlite file of the sqlite database on the edge node;

[0033] S106: When the sqlite file is found, the target data is stored in the sqlite file or the target data is deleted from the sqlite file.

[0034] The above-mentioned lightweight database sqlite database is a lightweight relational database management system that occupies very few resources, and only a few hundred KB of memory is required. The data of the sqlite database is stored in a sqlite file.

[0035] In this embodiment, a sqlite file is added to the edge node. The sqlite file includes a calling interface. By calling the interface, data can be stored in the sqlite file or deleted from the sqlite file.

[0036] The above-mentioned edge nodes can be edge nodes under the content distribution network, and the edge nodes can be routers in household, network data boxes, etc. For household routers and network data boxes, the performance is low and cannot carry a large amount of data input and output. Therefore, the sqlite file of the sqlite database can be configured on the edge node, and the data resources on the edge node can be stored through the sqlite file.

[0037] The above-mentioned file management instruction can be an instruction generated by the content distribution network according to the popularity of the data. If the content distribution network wants to store certain popular data in a certain edge node, it will initiate a file management instruction and require that the data be added to the edge node as target data. The edge node receives the file management instruction and stores the target data in the sqlite file.

[0038] The above sqlite file can be stored in any location of the edge node. Since the edge node is a physical hardware device, the sqlite file can be configured in the physical hardware device. Whether the physical hardware device includes other programs in addition to the sqlite file and the program of the edge node itself is not limited in this embodiment.

[0039] In this application, for edge nodes, if a file management instruction for adding or deleting target data is received, the sqlite file of the sqlite database is searched on the edge node, and the sqlite file stores the resources stored by the edge node. When the sqlite file is found, the target data is stored in the sqlite file or the target data is deleted from the sqlite file, so that the resources of the edge node can be stored by configuring the sqlite file on the edge node, reducing input and output operations, reducing the consumption of input and output resources, and reducing the system performance load.

[0040] The sqlite file is opened synchronously when the edge node is started. After opening, the edge node searches for the location of the sqlite file when receiving the file management instruction. After finding the location of the sqlite file, it records the location. If there is no sqlite file at the location, it creates a sqlite file. When receiving the file management instruction again, it directly performs operations on the sqlite file at the location.

[0041] As an alternative example, Figure 2 As shown, the sqlite files for finding the sqlite database on the edge node include:

[0042] S202-1, when the sqlite file is stored in a program folder of the edge node, obtain a storage path of the pre-stored sqlite file, and determine the file under the storage path as the sqlite file, wherein the program folder is used to store the running program of the edge node;

[0043] S202-2, when the sqlite file is stored outside the program folder of the edge node, traverse all folders of the edge node according to the file name of the sqlite file until the sqlite file is found.

[0044] In this embodiment, since the sqlite file may be stored in any location of the edge node, ideally, the location of the file can be marked when configuring the sqlite file to the edge node. For example, the sqlite file is configured in the program folder where the program of the edge node is located, then the storage path is known, and the sqlite file can be found according to the storage path. If the sqlite file is issued, the storage location may be anywhere in the edge node. Therefore, at this time, all folders of the edge node can be traversed according to the file name of the sqlite file until the sqlite file is traversed or all folders are traversed.

[0045] As an alternative example, Figure 3As shown, when the sqlite file is found, storing the target data into the sqlite file or deleting the target data from the sqlite file includes:

[0046] S302, in the case of newly added target data, calling an application program interface to locate the first position where the target data should be inserted;

[0047] S304, in the case of deleting the target data, calling an application program interface to locate the second position of the target data in the sqlite file.

[0048] In this embodiment, since the file management instruction is used to add target data or delete target data, different positions are to be searched in the sqlite file for different situations. For the case of adding target data, the first position where the target data should be inserted is located, and for the case of deleting target data, the target data is searched in the sqlite file and located at the second position where the target data is located.

[0049] The location can be called by the application program interface, which is an interface directly integrated into the program during compilation, through which operations are performed on the sqlite file.

[0050] As an alternative example, Figure 4 As shown, in the case of adding new target data, calling the application program interface in the sqlite file to locate the first position where the target data should be inserted includes:

[0051] S402, determining the data type of the target data;

[0052] S404, determining the position after the last data of the data type in the sqlite file as the first position, or determining the position before the last data of the data type in the sqlite file as the first position, wherein data of the same data type are aggregated and distributed in the sqlite file.

[0053] In this embodiment, data of different data types can be stored in different locations in the sqlite file. Data of different data types are centrally distributed in the sqlite file. For example, taking two data types as an example, data of data type 1 is stored in the first half of the sqlite file, and data of data type 2 is stored in the second half of the sqlite file. If new data is added, the target data is inserted into the data corresponding to the data type, after the last data. Alternatively, if the last data is template data, the target data is inserted before the last data.

[0054] As an alternative example, Figure 5As shown, in the case of adding new target data, calling the application program interface in the sqlite file to locate the first position where the target data should be inserted includes:

[0055] S502, determining the data type of the target data;

[0056] S504, determining the position after the first data of the data type in the sqlite file as the first position, or determining the position before the first data of the data type in the sqlite file as the first position, wherein the data of the same data type are dispersed in the sqlite file.

[0057] In this embodiment, data distribution of different data types can be stored in different locations in the sqlite file. For example, data of one data type is dispersed in the sqlite file and adjacent to data of other data types. Taking two data types as an example, the sqlite file starts from the beginning of the data part, and the order can be data of data type 1, data of data type 2, data of data type 2, data of data type 1, data of data type 2, data of data type 1, data of data type 2, data of data type 1, and so on. The data of the two data types are not obviously concentrated together, but are dispersed.

[0058] At this time, if new target data is added, the target data can be inserted into the data of the data type, before or after the first data, or inserted into the data of the data type, before or after a selected data. The selected data can be data with the same data length as the target data.

[0059] As an optional example, when a sqlite file is found, storing the target data in the sqlite file includes: determining the size of the available storage space of the edge node; when the data size of the target data exceeds the size of the available storage space, prohibiting the target data from being stored in the sqlite file; or, when the data size of the target data exceeds the size of the available storage space, deleting the data with the lowest number of accesses in the sqlite file until the size of the available storage space exceeds the data size of the target data.

[0060] In this embodiment, considering that the edge node is a local device, the storage space has an upper limit. Therefore, when adding new target data, it is possible to check whether the available storage space of the edge node is sufficient. The sqlite file will become larger after storing the target data, so it is necessary to ensure that the sqlite file can still be stored in the edge node after storing the target data, and will not hesitate to store the sqlite file in the edge node due to the increase in size. If the available storage space is insufficient, it is possible to prohibit the storage of the target data or delete some data in the sqlite file until the available space is sufficient.

[0061] As an optional example, when a sqlite file is found, storing the target data in the sqlite file includes: determining a preset storage condition of the edge node; and storing the target data in the sqlite file when the target data meets the preset storage condition.

[0062] In this embodiment, the storage requirements of the sqlite file can be set, such as what type of data to store, when the data is generated, how much data to store, etc. If the target data does not meet the preset storage conditions, the target data may not be stored, and only the data that meets the preset storage conditions will be stored in the sqlite file.

[0063] Figure 6 This is a system diagram of this embodiment. On the edge node, when the edge node is started, the relevant file information must be loaded, that is, the information of the data shared by the central node must be loaded. The sqlite management module calls the application program interface in the sqlite file to operate the sqlite file, takes out the data information and returns it to the edge node management module. When adding or deleting data, the edge node management module calls the application program interface in the sqlite file through the sqlite management module to add or delete data, and receives the result returned by the sqlite management module.

[0064] Figure 7 This is a schematic diagram of the structure of a data management device for an edge node provided in an embodiment of the present application. Figure 7 As shown, the data management device of the edge node includes:

[0065] A determination module 702 is used to determine the target data requested to be managed by the file management instruction when a file management instruction is received, wherein the file management instruction is used to add or delete the target data;

[0066] A search module 704 is used to search for a sqlite file of a sqlite database on an edge node;

[0067] The processing module 706 is used to store the target data into the sqlite file or delete the target data from the sqlite file when the sqlite file is found.

[0068] The above-mentioned lightweight database sqlite database is a lightweight relational database management system that occupies very few resources, and only a few hundred KB of memory is required. The data of the sqlite database is stored in a sqlite file.

[0069] In this embodiment, a sqlite file is added to the edge node. The sqlite file includes a calling interface. By calling the interface, data can be stored in the sqlite file or deleted from the sqlite file.

[0070] The above-mentioned edge nodes can be edge nodes under the content distribution network, and the edge nodes can be routers in household, network data boxes, etc. For household routers and network data boxes, the performance is low and cannot carry a large amount of data input and output. Therefore, the sqlite file of the sqlite database can be configured on the edge node, and the data resources on the edge node can be stored through the sqlite file.

[0071] The above-mentioned file management instruction can be an instruction generated by the content distribution network according to the popularity of the data. If the content distribution network wants to store certain popular data in a certain edge node, it will initiate a file management instruction and require that the data be added to the edge node as target data. The edge node receives the file management instruction and stores the target data in the sqlite file.

[0072] The above sqlite file can be stored in any location of the edge node. Since the edge node is a physical hardware device, the sqlite file can be configured in the physical hardware device. Whether the physical hardware device includes other programs in addition to the sqlite file and the program of the edge node itself is not limited in this embodiment.

[0073] In this application, for edge nodes, if a file management instruction for adding or deleting target data is received, the sqlite file of the sqlite database is searched on the edge node, and the sqlite file stores the resources stored by the edge node. When the sqlite file is found, the target data is stored in the sqlite file or the target data is deleted from the sqlite file, so that the resources of the edge node can be stored by configuring the sqlite file on the edge node, reducing input and output operations, reducing the consumption of input and output resources, and reducing the system performance load.

[0074] For other examples of this embodiment, please refer to the above examples and will not be described in detail here.

[0075] like Figure 8 As shown, an embodiment of the present application provides an electronic device, including a processor 111, a communication interface 112, a memory 113 and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.

[0076] Memory 113, used for storing computer programs;

[0077] In one embodiment of the present application, the processor 111 is configured to implement the edge node data management method provided by any one of the aforementioned method embodiments when executing the program stored in the memory 113 .

[0078] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of providing a data management method for an edge node as in any of the aforementioned method embodiments are implemented.

[0079] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0080] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0081] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0082] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A data management method for an edge node, characterized in that: include: In the case of receiving a file management instruction, determining target data requested to be managed by the file management instruction, wherein the file management instruction is used to add or delete the target data; Searching for a sqlite file of a sqlite database on the edge node; When the sqlite file is found, the target data is stored in the sqlite file or the target data is deleted from the sqlite file.

2. The method according to claim 1, characterized in that The sqlite file for searching the sqlite database on the edge node includes: In the case where the sqlite file is stored in a program folder of the edge node, obtaining a storage path of the pre-stored sqlite file, and determining the file under the storage path as the sqlite file, wherein the program folder is used to store the running program of the edge node; In the case where the sqlite file is stored outside the program folder of the edge node, all folders of the edge node are traversed by the file name of the sqlite file until the sqlite file is found.

3. The method according to claim 1, characterized in that When the sqlite file is found, storing the target data into the sqlite file or deleting the target data from the sqlite file comprises: In the case of adding the target data, calling an application program interface to locate the first position where the target data should be inserted; In the case of deleting the target data, an application program interface is called to locate the second position of the target data in the sqlite file.

4. The method according to claim 3, characterized in that In the case where the target data is newly added, calling the application program interface in the sqlite file to locate the first position where the target data should be inserted includes: Determine the data type of the target data; The position after the last piece of data of the data type in the sqlite file is determined as the first position, or the position before the last piece of data of the data type in the sqlite file is determined as the first position, wherein data of the same data type are clustered and distributed in the sqlite file.

5. The method according to claim 3, characterized in that: In the case where the target data is newly added, calling the application program interface in the sqlite file to locate the first position where the target data should be inserted includes: Determine the data type of the target data; The position after the first data of the data type in the sqlite file is determined as the first position, or the position before the first data of the data type in the sqlite file is determined as the first position, wherein data of the same data type are dispersed in the sqlite file.

6. The method according to claim 1, characterized in that When the sqlite file is found, storing the target data into the sqlite file includes: Determining the size of available storage space of the edge node; If the data size of the target data exceeds the size of the available storage space, it is prohibited to store the target data in the sqlite file; or In the case where the data size of the target data exceeds the size of the available storage space, the data with the lowest access times in the sqlite file is deleted until the size of the available storage space exceeds the data size of the target data.

7. The method according to claim 1, characterized in that When the sqlite file is found, storing the target data into the sqlite file includes: Determining a preset storage condition of the edge node; When the target data meets the preset storage condition, the target data is stored in the sqlite file.

8. A data management device for an edge node, characterized in that: include: a determination module, configured to determine, upon receiving a file management instruction, target data requested to be managed by the file management instruction, wherein the file management instruction is used to add or delete the target data; A search module, used to search for a sqlite file of a sqlite database on the edge node; A processing module is used to store the target data into the sqlite file or delete the target data from the sqlite file when the sqlite file is found.

9. An electronic device, characterized in that: include: at least one communication interface; at least one bus connected to the at least one communication interface; at least one processor coupled to the at least one bus; At least one memory connected to the at least one bus, wherein a computer program is stored in the memory, and when the processor executes the computer program, the method described in any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, wherein the storage medium stores computer-executable instructions, wherein the computer-executable instructions are used to execute the method described in any one of claims 1 to 7 of the present application.