Report generation method and related device
By extracting table metadata, validation enumeration values, and validation rules from regulatory documents, and combining Java reflection mechanisms and report templates, regulatory reports are automatically generated, solving the problem of low efficiency in existing tools and achieving efficient report generation and flexible system updates.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-01-06
- Publication Date
- 2026-04-10
AI Technical Summary
Existing tools for parsing regulatory documents can only read basic data and cannot automatically extract verification rules and field mapping relationships, resulting in low efficiency in generating regulatory reports.
Based on the business semantics of regulatory documents, extract table metadata, validation enumeration values and validation rules, generate a global validation rule table, and dynamically bind it with business data through Java reflection mechanism, and generate reports in combination with report templates.
It enables the rapid generation of reports that meet regulatory requirements, improves generation efficiency, and supports real-time updates, avoiding system reconstruction due to changes in regulatory requirements.
Smart Images
Figure CN121833707A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of computer, and particularly relates to a report generation method and related device. BACKGROUND
[0002] A regulatory report is a document used to report financial status, business activities or other related information to a regulatory agency, aiming to meet regulatory requirements, help enterprises understand the operation status and assist decision-making.
[0003] At present, a regulatory report meeting regulatory requirements can be generated by parsing a regulatory document. However, the regulatory document involves report fields, verification rules and other information, and the existing tool for parsing the regulatory document can only read basic data, and the information such as verification rules and field mapping relationship still needs to be extracted manually, which reduces the report generation efficiency and is difficult to meet the current regulatory report generation requirements.
[0004] Therefore, an urgent need exists for a solution to solve the above technical problems. SUMMARY
[0005] To solve the above problems, the embodiments of the present application provide a report generation method and related device, aiming to improve the report generation efficiency.
[0006] The embodiments of the present application disclose the following technical solutions:
[0007] In a first aspect, the embodiments of the present application provide a report generation method, comprising:
[0008] Based on the business semantics in the regulatory document, table metadata, verification enumeration values and verification rules are extracted;
[0009] The table metadata, the verification enumeration values and the verification rules are configured into a warehouse to generate a global verification rule table;
[0010] Based on the global verification rule table and the Java reflection mechanism, the verification rules are dynamically bound with the business data to generate the bound verification rules and business data;
[0011] The bound verification rules and business data are input into a report template to generate a report.
[0012] In a possible implementation manner, the extraction of the table metadata, the verification enumeration values and the verification rules based on the business semantics in the regulatory document comprises:
[0013] Based on the business semantics in the regulatory document, multi-level table headers and merged cells in the regulatory document are identified to obtain an identification result;
[0014] Based on the identification result, the table metadata, the verification enumeration values and the verification rules are extracted.
[0015] In a possible implementation, the storing the table metadata, the check enumeration value and the check rule into a database to generate a global check rule table comprises:
[0016] The table metadata, the check enumeration value and the check rule are structured to generate standardized table metadata, a standardized check enumeration file and a standardized check rule file;
[0017] The standardized table metadata, the standardized check enumeration file and the standardized check rule file are stored into a database to generate a global check rule table.
[0018] In a possible implementation, the storing the table metadata, the check enumeration value and the check rule into a database to generate a global check rule table comprises:
[0019] The check enumeration value is stored into a database to generate an enumeration table;
[0020] The check rule is stored into a database to generate a rule table;
[0021] A mapping table is generated based on a mapping relationship between the table metadata and the check rule;
[0022] A global check rule table is generated based on the enumeration table, the rule table and the mapping table.
[0023] In a possible implementation, the inputting the bound check rule and the business data into the report template to generate a report comprises:
[0024] The bound check rule and the business data are inputted into a report template to generate target code;
[0025] A report is generated based on the target code.
[0026] In a possible implementation, the inputting the bound check rule and the business data into the report template to generate target code comprises:
[0027] A report template corresponding to a type of the business data is determined;
[0028] The bound check rule and the business data are inputted into the report template corresponding to the type to generate target code.
[0029] A second aspect: an embodiment of the present application provides a report generation apparatus, comprising:
[0030] An extraction unit, a first generation unit, a second generation unit and a third generation unit;
[0031] The extraction unit is configured to extract table metadata, check enumeration values, and check rules based on business semantics in the regulatory document.
[0032] The first generation unit is configured to configure the table metadata, the check enumeration values, and the check rules into a warehouse to generate a global check rule table.
[0033] The second generation unit is configured to dynamically bind check rules and business data based on the global check rule table and a Java reflection mechanism to generate bound check rules and business data.
[0034] The third generation unit is configured to input the bound check rules and business data into a report template to generate a report.
[0035] In a possible implementation, the extraction unit is specifically configured to:
[0036] identify multi-level table headers and merged cells in the regulatory document based on business semantics in the regulatory document to obtain an identification result;
[0037] extract table metadata, check enumeration values, and check rules based on the identification result.
[0038] In a possible implementation, the first generation unit is specifically configured to:
[0039] perform structural processing on the table metadata, the check enumeration values, and the check rules to generate standardized table metadata, standardized check enumeration files, and standardized check rule files;
[0040] configure the standardized table metadata, the standardized check enumeration files, and the standardized check rule files into a warehouse to generate a global check rule table.
[0041] In a possible implementation, the first generation unit is specifically configured to:
[0042] configure the check enumeration values into a warehouse to generate an enumeration table;
[0043] configure the check rules into a warehouse to generate a rule table;
[0044] generate a mapping table based on a mapping relationship between the table metadata and the check rules;
[0045] generate a global check rule table based on the enumeration table, the rule table, and the mapping table.
[0046] In a possible implementation, the third generation unit is specifically configured to:
[0047] Input the bound check rule and the business data into the report template to generate target code;
[0048] Generate the report based on the target code.
[0049] In a possible implementation, the third generating unit is specifically configured to:
[0050] Determine the report template corresponding to the type of the business data based on the type of the business data;
[0051] Input the bound check rule and the business data into the report template corresponding to the type to generate target code.
[0052] Third aspect: an embodiment of the present application provides a computer device, the computer device comprises a processor and a memory;
[0053] The memory is configured to store program code and transmit the program code to the processor;
[0054] The processor is configured to execute the steps of the report generating method according to the instructions in the program code.
[0055] Fourth aspect: an embodiment of the present application provides a computer readable storage medium, and the computer readable storage medium stores a computer program, and the computer program is executed by a processor to realize the steps of the report generating method.
[0056] Fifth aspect: an embodiment of the present application provides a computer program product, when the computer program product runs on a computer, the computer executes the steps of the report generating method.
[0057] Sixth aspect: an embodiment of the present application provides a chip, comprising a processor, the processor is coupled with a memory, and is configured to execute a computer program or instructions stored in the memory, so that the chip realizes the steps of the report generating method.
[0058] Compared with the prior art, the embodiment of the present application has the following beneficial effects:
[0059] This application provides a report generation method. Based on the business semantics in regulatory documents, it extracts table metadata, validation enumeration values, and validation rules; configures the table metadata, validation enumeration values, and validation rules into a database to generate a global validation rule table; based on the global validation rule table and Java reflection, it dynamically binds the validation rules with business data to generate bound validation rules and business data; and inputs the bound validation rules and business data into a report template to generate a report. This application embodiment can extract table metadata, validation enumeration values, and validation rules based on the business semantics in regulatory documents, and combine business data with dynamic validation rules and templated report templates, enabling rapid generation of reports that meet regulatory requirements and improving report generation efficiency. Attached Figure Description
[0060] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0061] Figure 1 This is a schematic diagram illustrating an application scenario of a report generation method provided in an embodiment of this application;
[0062] Figure 2 A flowchart illustrating a report generation method provided in this application embodiment;
[0063] Figure 3 This is a schematic diagram of the structure of a report generation device provided in an embodiment of this application;
[0064] Figure 4 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation
[0065] The technical solutions in the embodiments of the present application will be described clearly and completely in the following with reference to the drawings in the embodiments of the present application. The terms used in the following embodiments are only for the purpose of describing the specific embodiments and are not intended to be limiting to the present application. As used in the specification and the appended claims of the present application, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “one or more” as used in the embodiments of the present application means one, two or more than two; “and / or” describes the associated relationship of associated objects, which means that there can be three kinds of relationships; for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. The character “ / ” generally represents an “or” relationship between the associated objects.
[0066] In the present specification, the reference to “one embodiment” or “some embodiments” etc. means that a particular feature, structure or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, the statements “in one embodiment”, “in some embodiments”, “in other some embodiments”, “in yet some embodiments” etc. appearing in various places in the present specification are not necessarily all referring to one and the same embodiment, but can mean “one or more but not all embodiments”, unless otherwise specifically stated. The terms “comprising”, “containing”, “having” and their variants mean “including but not limited to”, unless otherwise specifically stated.
[0067] The plurality of embodiments of the present application refers to more than or equal to two. It should be noted that in the description of the embodiments of the present application, the terms “first”, “second” etc. are only used for the purpose of distinguishing the description and cannot be understood as indicating or implying relative importance, nor can it be understood as indicating or implying order.
[0068] Currently, by analyzing the regulatory documents, a regulatory report meeting the regulatory requirements can be generated. However, the information such as report field and verification rule in the regulatory documents, the existing tool for analyzing the regulatory documents can only read the basic data, and the information such as verification rule and field mapping relationship still needs to be extracted manually, which reduces the report generation efficiency and is difficult to meet the current regulatory report generation requirements.
[0069] Based on this, the embodiment of the application provides a report generation method, which extracts table metadata, check enumeration values and check rules based on business semantics in a regulatory document; configures the table metadata, the check enumeration values and the check rules into a warehouse to generate a global check rule table; dynamically binds check rules and business data based on the global check rule table and a Java reflection mechanism to generate bound check rules and business data; and inputs the bound check rules and business data into a report template to generate a report. In the embodiment of the application, table metadata, check enumeration values and check rules can be extracted based on business semantics in a regulatory document, and business data can be combined with dynamic check rules and templated report templates, so that a report meeting regulatory requirements can be quickly generated, and the report generation efficiency is improved.
[0070] As shown in the figure, the figure is an application scenario schematic diagram of a report generation method provided by the embodiment of the application, and the report generation method can be realized based on interaction between a client 101 and a server 102. Figure 1
[0071] The client 101 sends a regulatory document to the server 102. The server 102 extracts table metadata, check enumeration values and check rules based on business semantics in the regulatory document; configures the table metadata, the check enumeration values and the check rules into a warehouse to generate a global check rule table; dynamically binds check rules and business data based on the global check rule table and a Java reflection mechanism to generate bound check rules and business data; and inputs the bound check rules and business data into a report template to generate a report.
[0072] In order to facilitate understanding, the following will be introduced in combination with Figure 2 a report generation method provided by the embodiment of the application, Figure 2 a flowchart of the report generation method provided by the embodiment of the application, which comprises S201-S204.
[0073] S201, extract table metadata, check enumeration values and check rules based on business semantics in a regulatory document.
[0074] In the embodiment of the application, based on business semantics in a regulatory document, natural language or semi-structured content (such as table building statements, check requirements and other information) in the regulatory document can be converted into standardized configurations recognizable by a computer device, and front-end visual operation capabilities are provided for users.
[0075] The table structure in the regulatory document has diversity, and the structure can include one row of table headers corresponding to one row of data, or can include multi-level table headers, merged cells, and complex structures such as cross rows and columns. In the embodiment of the present application, based on the business semantics in the regulatory document, the multi-level table headers and the merged cells can be identified from the regulatory document to obtain an identification result. Based on the identification result, the table metadata, the enumeration value, and the check rule are extracted.
[0076] The table metadata can include but is not limited to table name, field name, and data type.
[0077] For example, the table name can be the name of the table title or the topmost name of the table header; the field name can be the name corresponding to each column in the table, such as "funds amount" and the like; and the data type can be the content identified from the cell content or the annotation, for example, the data type corresponding to the amount can be numerical type, the data type corresponding to the reporting date can be date type, and the data type corresponding to the state information can be string type.
[0078] In a possible implementation, based on the business semantics in the regulatory document, a template document, a table building script, and a front-end form object representation (JavaScript Object Notation, JSON) file can also be generated.
[0079] The template document can include the parsed table metadata, the enumeration value, and the check rule, and subsequent data filling based on the template document can avoid format confusion; the table building script is an automatically generated table building statement, which is used to directly build a table in a database to store the reported data; and the front-end form JSON file is an automatically generated configuration JSON of the front-end form, which supports technicians to view and modify related data.
[0080] S202, the table metadata, the enumeration value, and the check rule are configured into a warehouse to generate a global check rule table.
[0081] In a possible implementation, by configuring the enumeration value into the warehouse, an enumeration table can be generated; by configuring the check rule into the warehouse, a rule table can be generated; based on the mapping relationship between the table metadata and the check rule, a mapping table can be generated; and based on the enumeration table, the rule table, and the mapping table, a global check rule table is generated.
[0082] For example, the enumeration table can include enumeration code, enumeration name, enumeration value list (such as "normal, abnormal, and suspended"), and the like; the check rule table can include rule code, rule type, rule parameter, and error prompt; and the mapping table can include the mapping relationship between the table metadata and the check rule.
[0083] In the embodiments of the present application, the rules are converted from text files to configuration lines in a database, so that the rules can be modified by modifying the configuration lines in the database without changing the codes.
[0084] In a possible implementation, the table metadata, the check enumeration value and the check rule are structured to generate standardized table metadata, standardized check enumeration files and standardized check rule files.
[0085] For example, in the embodiments of the present application, the “required” in the check rule is structured as “required: true”, and the “range 1-100” is structured as min: 1, max: 100.
[0086] The generated standardized table metadata, standardized check enumeration files and standardized check rule files can be in a text (TXT) format. On this basis, the standardized table metadata, the standardized check enumeration files and the standardized check rule files can be configured into a database to generate a global check rule table.
[0087] In S203, the check rule is dynamically bound with the business data based on the global check rule table and a Java reflection mechanism to generate the bound check rule and the business data.
[0088] In the embodiments of the present application, the global check rule table containing the self-defined check capability is created and defined, so that various check rules (for example, built-in rules and self-defined rules) and enumeration data can be uniformly persisted in the database. On this basis, based on the Java reflection mechanism, the dynamic binding and mapping association of the check rule and the business data can be realized, and the standardized check of the business data can be completed.
[0089] In the embodiments of the present application, the Java reflection mechanism is used to dynamically bind the check rule with the business data at runtime without defining the correspondence between a field and a check rule by hard coding.
[0090] For example, the business data contains a first field, the check rule corresponding to the first field is searched in the global check rule table, the first field is obtained by reflection, and the check rule is bound with the business data.
[0091] In the embodiments of the present application, the check rule is dynamically bound with the business data based on the global check rule table and the Java reflection mechanism, so that the decoupling between the check rule and the code can be realized, the real-time update can be supported by the dynamic management of the rule engine, and the system reconstruction caused by the change of regulatory requirements can be avoided.
[0092] S204, input the bound check rule and the business data into the report template to generate a report.
[0093] In the embodiment of the present application, the target code can be generated by inputting the bound check rule and the business data into the report template.
[0094] For example, in the embodiment of the present application, the predefined regulatory report and the business defined report function template contain code skeletons, such as Spring Boot entity classes, front-end forms, etc. The bound check rule and the business data can be input into the report template through the template engine to automatically generate the target code.
[0095] In a possible implementation, based on the type of the business data, a report template corresponding to the type can be determined; the bound check rule and the business data are input into the report template corresponding to the type to generate the target code. After the target code is generated, a report can be generated based on the target code.
[0096] In the embodiment of the present application, the technical personnel can modify the bound check rule and the business data based on the user's custom requirements, or modify the report template, to realize the generation of multiple types of reports.
[0097] In summary, in the embodiment of the present application, the business semantics in the regulatory document can be used to extract table metadata, check enumeration values and check rules, and the business data can be combined with dynamic check rules and template report templates to quickly generate reports that meet regulatory requirements, thereby improving the efficiency of report generation.
[0098] In the embodiment of the present application, the check rule is decoupled from the code, and a rule engine is introduced for dynamic management, which supports real-time updating and avoids system reconstruction caused by changes in regulatory requirements. For different types of business data, corresponding report templates are preset to cover multiple regulatory scenarios. When generating a report, only the template parameters need to be adjusted, which effectively improves the efficiency of report generation.
[0099] The embodiment of the present application provides a report generation device, referring to Figure 3 The figure is a structural schematic diagram of a report generation device provided by the embodiment of the present application, and its specific implementation manner is consistent with the implementation manner and the achieved technical effect recorded in the above-mentioned method embodiment. Some contents will not be repeated.
[0100] The embodiment of the present application provides a report generation device 3100, which comprises:
[0101] The extraction unit 3101, the first generation unit 3102, the second generation unit 3103 and the third generation unit 3104;
[0102] The extraction unit 3101 is configured to extract table metadata, check enumeration values and check rules based on business semantics in the regulatory document.
[0103] The first generation unit 3102 is configured to configure the table metadata, the check enumeration values and the check rules into a warehouse to generate a global check rule table.
[0104] The second generation unit 3103 is configured to dynamically bind the check rules to business data based on the global check rule table and a Java reflection mechanism to generate the bound check rules and business data.
[0105] The third generation unit 3104 is configured to input the bound check rules and business data into a report template to generate a report.
[0106] In a possible implementation, the extraction unit is specifically configured to:
[0107] Identify multi-level table headers and merged cells in the regulatory document based on business semantics in the regulatory document to obtain an identification result.
[0108] Extract table metadata, check enumeration values and check rules based on the identification result.
[0109] In a possible implementation, the first generation unit is specifically configured to:
[0110] Perform structural processing on the table metadata, the check enumeration values and the check rules to generate standardized table metadata, standardized check enumeration files and standardized check rule files.
[0111] Configure the standardized table metadata, the standardized check enumeration files and the standardized check rule files into a warehouse to generate a global check rule table.
[0112] In a possible implementation, the first generation unit is specifically configured to:
[0113] Configure the check enumeration values into a warehouse to generate an enumeration table.
[0114] Configure the check rules into a warehouse to generate a rule table.
[0115] Generate a mapping table based on a mapping relationship between the table metadata and the check rules.
[0116] Generate a global check rule table based on the enumeration table, the rule table and the mapping table.
[0117] In a possible implementation, the third generation unit is specifically configured to:
[0118] Input the bound check rule and the business data into the report template to generate target code;
[0119] Generate the report based on the target code.
[0120] In a possible implementation, the third generating unit is specifically configured to:
[0121] Determine the report template corresponding to the type of the business data based on the type of the business data;
[0122] Input the bound check rule and the business data into the report template corresponding to the type of the business data to generate target code.
[0123] To sum up, in the embodiments of the present application, the business semantics in the regulatory document can be used to extract table metadata, check enumeration values and check rules, and the business data can be combined with dynamic check rules and template-based report templates, so that a report meeting regulatory requirements can be quickly generated, and the report generation efficiency is improved. By decoupling the check rules and the code, real-time updates are supported through dynamic management by the rule engine, and system reconstruction caused by changes in regulatory requirements is avoided. For different types of business data, corresponding report templates are preset to cover multiple regulatory scenarios, and only template parameters need to be adjusted when generating a report, which effectively improves the report generation efficiency.
[0124] The embodiments of the present application provide a computer device, as shown in the accompanying drawings, which is a structural schematic diagram of a computer device provided by the embodiments of the present application. The computer device 410 comprises a processor 411 and a memory 412. Figure 4
[0125] The memory 412 is configured to store program code and transmit the program code to the processor 411.
[0126] The processor 411 is configured to execute the steps of the report generation method according to the instructions in the program code.
[0127] For example, the processor 411 can extract table metadata, check enumeration values and check rules based on the business semantics in the regulatory document, configure the table metadata, the check enumeration values and the check rules into a warehouse to generate a global check rule table, dynamically bind the check rules and the business data based on the global check rule table and the Java reflection mechanism to generate bound check rules and business data, and input the bound check rules and the business data into the report template to generate a report.
[0128] The embodiments of the present application provide a computer readable storage medium, and the computer readable storage medium stores a computer program. When the computer program is executed by a processor, the steps of the report generation method are implemented.
[0129] The embodiment of the present application provides a computer program product, when the computer program product runs on a computer, the computer executes steps of a report generation method.
[0130] The embodiment of the present application provides a chip, comprising a processor coupled with a memory, used for executing a computer program or instructions stored in the memory, so that the chip implements steps of a report generation method.
[0131] It should be noted that each of the embodiments in the present specification adopts a progressive description manner, and the same or similar parts between each embodiment can be referred to each other, and each embodiment mainly describes the difference from other embodiments. Especially, the device and system embodiments are basically similar to the method embodiments, so the description is relatively simple, and the related parts can be referred to the part of the method embodiment. The above described device and system embodiments are only illustrative, and the units described as separate components can be or can not be physically separated, and the components prompted as units can be or can not be physical units, that is, can be located in one place, or can be distributed on multiple network units. According to the actual needs, part or all of the modules can be selected to achieve the purpose of the embodiment scheme. Those skilled in the art can understand and implement without creative labor.
[0132] The above describes only one specific embodiment of the present application, but the protection scope of the present application is not limited to this, any skilled person in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
Claims
1. A report generation method characterized by, The method comprises the following steps: Based on the business semantics in the regulatory document, extract table metadata, check enumeration values and check rules; The table metadata, the check enumeration value and the check rule are configured into the warehouse to generate a global check rule table; Based on the global check rule table and the Java reflection mechanism, the check rule is dynamically bound with the business data to generate the bound check rule and the business data; The bound check rule and the business data are input into the report template to generate a report.
2. The method of claim 1, wherein, The method comprises the following steps: Based on the business semantics in the regulatory document, identify the multi-level table header and the merged cell in the regulatory document to obtain an identification result; Based on the identification result, extract table metadata, check enumeration values and check rules.
3. The method of claim 1, wherein, The method comprises the following steps: The table metadata, the check enumeration value and the check rule are structured to generate standardized table metadata, standardized check enumeration files and standardized check rule files; The standardized table metadata, the standardized check enumeration files and the standardized check rule files are configured into the warehouse to generate a global check rule table.
4. The method of claim 1, wherein, The method comprises the following steps: The check enumeration value is configured into the warehouse to generate an enumeration table; The check rule is configured into the warehouse to generate a rule table; Based on the mapping relationship between the table metadata and the check rule, a mapping table is generated; Based on the enumeration table, the rule table and the mapping table, a global check rule table is generated.
5. The method of claim 1, wherein, The method comprises the following steps: The bound check rule and the business data are input into the report template to generate target code; Based on the target code, a report is generated.
6. The method of claim 5, wherein, The method comprises the following steps: Based on the type of business data, determine the report template corresponding to the type; The bound check rule and the business data are input into the report template corresponding to the type to generate target code.
7. A report generating apparatus characterized by comprising: The method comprises the following steps: An extraction unit, a first generation unit, a second generation unit and a third generation unit are provided. The extraction unit is configured to extract table metadata, check enumeration values and check rules based on the business semantics in the regulatory document. The first generation unit is configured to configure the table metadata, the check enumeration value and the check rule into the warehouse to generate a global check rule table. The second generation unit is configured to dynamically bind the check rule with the business data based on the global check rule table and the Java reflection mechanism to generate the bound check rule and the business data. The third generation unit is configured to input the bound check rule and the business data into the report template to generate a report.
8. A computer device, comprising: The computer device comprises a processor and a memory. The memory is configured to store program code and transmit the program code to the processor. The processor is configured to execute the steps of the report generation method according to any one of claims 1-6 based on instructions in the program code.
9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program is configured to implement the steps of the report generation method according to any one of claims 1-6 when executed by the processor.
10. A computer program product, characterised in that, When the computer program product is run on the computer, the computer executes the steps of the report generation method according to any one of claims 1-6.