Software dependency analysis method, analysis device, and readable storage medium

Abstract

The present invention proposes a software dependency analysis method, an analysis device, and a readable storage medium. The software dependency analysis method includes: obtaining multiple dependency reports corresponding to multiple projects, and multiple software packages corresponding to multiple projects; determining the release dependencies of multiple software packages based on the multiple dependency reports; and generating and displaying the release dependency reports of multiple software packages based on the release dependencies. The software dependency analysis method of the present invention can quickly provide insights into the distribution of a specific software package in various projects, as well as the usage of software packages in various projects, and can quickly understand the release dependencies of various software packages. This provides efficient, convenient, and fast guidance for analyzing the dependencies of large-scale projects and supporting RELEASE versions, thereby improving the work efficiency of the matter.

Description

Technical Field

[0001] The present invention relates to the field of software technology, and in particular to a software dependency analysis method, a software dependency analysis device, and a readable storage medium. Background Art

[0002] Large projects may contain hundreds of projects, and the software development kits (SDKs) in each project may be in different states. There may be different SNAPSHOT versions (versions still under development) and RELEASE versions (released versions). The dependency order of each version is also unclear. Switching to a RELEASE version is even more complicated.

[0003] For scenarios like this, the current approach is to standardize agreements through a unified technology stack and unified second-party packages. However, the versions used in the published services are actually inconsistent. Summary of the Invention

[0004] The present invention aims to solve at least one of the technical problems existing in the prior art or related art.

[0005] To this end, one aspect of the present invention is to propose a software dependency analysis method.

[0006] Another aspect of the present invention is to provide a software dependency analysis device.

[0007] Another aspect of the present invention provides a readable storage medium.

[0008] In view of this, according to one aspect of the present invention, a software dependency analysis method is proposed, where the software includes multiple projects, and the analysis method includes: obtaining multiple dependency reports corresponding to the multiple projects, and multiple software packages corresponding to the multiple projects; determining the release dependencies of the multiple software packages based on the multiple dependency reports; and generating and displaying the release dependency reports of the multiple software packages based on the release dependencies.

[0009] The software dependency analysis method provided by the present invention, wherein the software includes multiple projects. The dependency report and the software package SDK used for each project are obtained respectively, that is, a dependency report is generated for each project, thereby obtaining multiple dependency reports corresponding to multiple projects, and multiple software package SDKs corresponding to multiple projects. According to the multiple dependency reports, the reference relationship in each dependency report is parsed to determine the release dependency of multiple software packages, that is, the order of software package release dependencies. Afterwards, the release dependency reports of multiple software packages are generated and displayed according to the release dependencies, specifically, they can be view reports. Through the software dependency analysis method of the present invention, it is possible to quickly understand the distribution of a specific software package in various projects, as well as the usage of the software packages in various projects, and to quickly understand the release dependencies of each software package, which provides efficient, convenient and fast guidance for analyzing the dependency of large projects and supporting RELEASE versions, thereby improving the work efficiency of this matter.

[0010] The software dependency analysis method according to the present invention may also have the following technical features:

[0011] In the above technical solution, the dependency report includes the dependency relationships of software packages used by any one of the multiple projects.

[0012] In this technical solution, the dependency report includes the dependencies of the software packages used in any project, but is not limited to this. It is understandable that the report may also include basic information of the software package, such as the software package identifier, project identifier, version information, etc. The dependency report reflects the usage of the software package SDK in the project, that is, which software packages are used in the project, and the reference relationship of each software package. For example, project A includes sdk1 and sdk2, sdk1 references sdk3, sdk3 references sdk4 and sdk5, and sdk2 references sdk6. For a single project, this technical solution provides analysis solutions based on different perspectives such as projects and software packages. From the perspective of the project, you can know which software packages are used in the project, the usage status of the software packages, and the versions used. From the perspective of the software package, you can know the dependencies and dependency order of the software packages. This provides a basis for analyzing the dependency situation of large-scale project engineering.

[0013] In any of the above technical solutions, the step of determining the release dependencies of multiple software packages based on multiple dependency reports specifically includes: determining the dependencies of the multiple software packages based on the multiple dependency reports; and sorting the multiple software packages according to the dependency hierarchy based on the dependency relationships to obtain the release dependencies of the multiple software packages.

[0014] This technical solution defines a method for determining the release dependencies of multiple software packages based on multiple dependency reports. Specifically, by statistically analyzing multiple dependency reports for all projects, dependency analysis of a large number of projects is achieved, and the dependency relationships of multiple software packages are output. Analysis schemes based on different perspectives, such as project and software package, are also supported. From the perspective of the software package SDK, the dependency relationships and dependency order of the software package SDKs can be obtained. Dependencies include reference relationships and referenced relationships. For example, SDK2 references SDK6, which is referenced by SDK7 and SDK8. Where SDK7 references SDK8, the dependency order of SDK2 is: SDK7, SDK8, SDK2, SDK6. From the project perspective, the distribution of specific software packages across projects and the usage status of the software packages in each project can be quickly understood. Furthermore, based on the dependency relationships of multiple software packages, the dependency hierarchy of each package can be determined. Multiple software packages are sorted according to the dependency hierarchy to obtain the release dependencies of the multiple software packages. Understandably, for any given level, lower levels are released first, while higher levels are released later. The technical solution of this invention allows for rapid insight into the usage of specific software packages across projects, visually outputs the release dependencies of each package, and standardizes the release dependency order of each package, enabling rapid analysis of second- and third-party packages for large-scale projects.

[0015] In any of the above technical solutions, there is no dependency between multiple software packages in any layer.

[0016] In this technical solution, any level includes at least one software package. When multiple software packages are included, there is no dependency between the multiple software packages, so that software packages at the same level can be released in parallel, providing efficient, convenient and fast guidance for supporting RELEASE versions.

[0017] In any of the above technical solutions, the software dependency analysis method also includes: obtaining multiple software package identifiers and multiple version information corresponding to multiple software packages; based on the inconsistency of the version information corresponding to multiple software packages with the same software package identifier, modifying the versions corresponding to the multiple software packages with the same identifier to specified versions.

[0018] In this technical solution, first, the software package identifier and the corresponding version information corresponding to each software package in all projects are obtained, where the software package identifier is the unique identifier of the software package. Since the same software package may be distributed in different projects and there may be inconsistencies in the versions used in each project, resulting in different versions used in the released services, which is not conducive to subsequent maintenance. Therefore, it is necessary to unify the versions of multiple software packages with the same identifier. If the version information of multiple software packages under the same software package identifier is consistent, no further processing is required. Conversely, if the version information is inconsistent, the versions corresponding to the multiple software packages under the same software package identifier need to be modified to the specified version. Through the technical solution of the present invention, the software package versions used in all projects are made transparent, non-RELEASE analysis of second- and third-party packages of all projects is realized, and the release dependency order of each software package is output in the form of a view, making it easy to switch RELEASE.

[0019] In any of the above technical solutions, the software dependency analysis method also includes: filtering the release dependency report according to preset filtering conditions to generate a corresponding target release dependency report, wherein the preset filtering conditions include any one of the following items or a combination thereof: software package identifier, software package release status, level name, project identifier.

[0020] This technical solution supports filtering release dependency reports according to preset filter conditions, thereby generating target release dependency reports that meet specific criteria. Preset filter conditions can be set based on any one of the following: package identifier, package release status, tier name, and project identifier, or a combination thereof. This allows for analysis of non-RELEASE information within the software and the SDK's use in other projects from different perspectives.

[0021] In any of the above technical solutions, the step of obtaining multiple dependency reports corresponding to multiple projects specifically includes: scanning the compilation file corresponding to each project to determine the dependency report corresponding to each project.

[0022] In this technical solution, by scanning the compiled files corresponding to each project, a dependency report of each project can be obtained, including dependency information, software package identifier, project identifier, version information, and the like.

[0023] In any of the above technical solutions, the format of the dependency report is txt format; the format of publishing the dependency report is excel format.

[0024] In this technical solution, the dependency report is in, but is not limited to, a txt format. When the dependency report format changes, the interface for reading each dependency report will also need to change accordingly when performing a comprehensive analysis of multiple dependency reports. The dependency report is published in, but is not limited to, an Excel format.

[0025] According to another aspect of the present invention, a software dependency analysis device is proposed, comprising: a memory storing a program; and a processor implementing the software dependency analysis method of any of the above technical solutions when executing the program.

[0026] The software dependency analysis device provided by the present invention implements the steps of the software dependency analysis method of any of the above technical solutions when the processor executes the program. Therefore, the software dependency analysis device includes all the beneficial effects of the software dependency analysis method of any of the above technical solutions.

[0027] According to another aspect of the present invention, a readable storage medium is provided, on which a program is stored. When the program is executed by a processor, the software dependency analysis method according to any of the above technical solutions is implemented.

[0028] The readable storage medium provided by the present invention implements the steps of the software dependency analysis method of any of the above technical solutions when the processor executes the program. Therefore, the readable storage medium includes all the beneficial effects of the software dependency analysis method of any of the above technical solutions.

[0029] Additional aspects and advantages of the invention will become apparent from the description which follows, or may be learned by practice of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the following description of the embodiments with reference to the accompanying drawings, in which:

[0031] Figure 1 A schematic flow chart showing a method for analyzing software dependencies according to a first embodiment of the present invention is shown;

[0032] Figure 2 A schematic flow chart showing a method for analyzing software dependencies according to a second embodiment of the present invention is shown;

[0033] Figure 3 A schematic flow chart showing a software dependency analysis method according to a third embodiment of the present invention is shown;

[0034] Figure 4 A schematic flow chart showing a method for analyzing software dependencies according to a fourth embodiment of the present invention is shown;

[0035] Figure 5 A logical diagram showing a software dependency analysis method according to a fifth embodiment of the present invention is shown;

[0036] Figure 6 A schematic diagram showing a fifth embodiment of the present invention for publishing a dependency report;

[0037] Figure 7 A schematic block diagram of a software dependency analysis device according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0038] In order to more clearly understand the above-mentioned objects, features and advantages of the present invention, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the embodiments of the present invention and the features therein can be combined with each other without conflict.

[0039] In the following description, many specific details are set forth to facilitate a full understanding of the present invention. However, the present invention may also be implemented in other ways different from those described herein. Therefore, the scope of protection of the present invention is not limited to the specific embodiments disclosed below.

[0040] According to an embodiment of one aspect of the present invention, a software dependency analysis method is proposed, and the software dependency analysis method is described in detail through the following embodiments.

[0041] Example 1: Figure 1 The following is a flow chart of a software dependency analysis method according to a first embodiment of the present invention. The software includes multiple projects, and the analysis method includes:

[0042] Step 102: Obtain multiple dependency reports corresponding to multiple projects and multiple software packages corresponding to the multiple projects;

[0043] Step 104: determining release dependencies of multiple software packages based on the multiple dependency reports;

[0044] Step 106: Generate and display a release dependency report of the multiple software packages based on the release dependency.

[0045] The software dependency analysis method provided by this embodiment, wherein the software includes multiple projects. The dependency report and the software packages used for each project are obtained respectively, that is, a dependency report is generated for each project, thereby obtaining multiple dependency reports corresponding to multiple projects, and multiple software package SDKs corresponding to multiple projects. According to the multiple dependency reports, the reference relationships in each dependency report are parsed to determine the release dependencies of multiple software packages, that is, the order of software package release dependencies. Afterwards, the release dependency reports of multiple software packages are generated and displayed based on the release dependencies, specifically, they can be view reports. Through the software dependency analysis method of this embodiment, it is possible to quickly understand the distribution of a specific software package in various projects, as well as the usage of software packages in various projects, and to quickly understand the release dependencies of each software package, which provides efficient, convenient and fast guidance for analyzing the dependency of large projects and supporting RELEASE versions, thereby improving the work efficiency of this matter.

[0046] Example 2: Figure 2 A flowchart of a software dependency analysis method according to a second embodiment of the present invention is shown. The software includes multiple projects, and the analysis method includes:

[0047] Step 202: Obtain multiple dependency reports corresponding to multiple projects and multiple software packages corresponding to the multiple projects;

[0048] Step 204: Determine dependencies among the plurality of software packages based on the plurality of dependency reports;

[0049] Step 206: Based on the dependency relationships, the multiple software packages are sorted according to the dependency hierarchy to obtain release dependency relationships of the multiple software packages.

[0050] Step 208: Generate and display a release dependency report of the multiple software packages based on the release dependency.

[0051] In this embodiment, by statistically analyzing multiple dependency reports across all projects, dependency analysis is performed on a large number of projects, and the dependency relationships of multiple software packages are output. Analysis schemes based on different perspectives, such as project and software package, are also supported. From the perspective of the software package SDK, the dependency relationships and dependency order of the software package SDKs can be obtained. Dependencies include reference relationships and referenced relationships. For example, SDK2 depends on SDK6, which is dependent on SDK7 and SDK8. Where SDK7 depends on SDK8, the dependency order of SDK2 is: SDK7, SDK8, SDK2, SDK6. From a project perspective, the distribution of specific software packages across projects and the usage status of the software packages in each project can be quickly understood. Furthermore, based on the dependency relationships, the dependency hierarchy of each software package can be determined. Multiple software packages are sorted according to the dependency hierarchy to obtain the release dependency relationships of the multiple software packages. It is understandable that for any hierarchy, lower levels are released first, and higher levels are released later. Through the software dependency analysis method of this embodiment, it is possible to quickly understand the usage of specific software packages in various projects, and to output the release dependencies of each software package in a visual manner, standardize the release dependency order of each software package, thereby realizing the rapid analysis of second- and third-party packages in large-scale project engineering.

[0052] Example 3, Figure 3 A flowchart of a software dependency analysis method according to a third embodiment of the present invention is shown. The software includes multiple projects, and the analysis method includes:

[0053] Step 302: Obtain multiple dependency reports corresponding to multiple projects and multiple software packages corresponding to the multiple projects;

[0054] Step 304: Determine dependencies among the plurality of software packages based on the plurality of dependency reports;

[0055] Step 306: Based on the dependency relationships, the multiple software packages are sorted according to the dependency hierarchy to obtain release dependency relationships of the multiple software packages.

[0056] Step 308: Generate and display a release dependency report of multiple software packages based on the release dependency;

[0057] Step 310: Obtain multiple software package identifiers and multiple version information corresponding to multiple software packages;

[0058] Step 312: If the version information corresponding to the multiple software packages with the same software package identifier is inconsistent, the versions corresponding to the multiple software packages with the same identifier are modified to a specified version.

[0059] In this embodiment, first, the software package identifier and corresponding version information corresponding to each software package in all projects are obtained, where the software package identifier is the unique identifier of the software package. Since the same software package may be distributed in different projects and there may be inconsistencies in the versions used in each project, resulting in different versions used in the released services, which is not conducive to subsequent maintenance. Therefore, it is necessary to unify the versions of multiple software packages with the same identifier. If the version information of multiple software packages under the same software package identifier is consistent, no further processing is required. Conversely, if the version information is inconsistent, the versions corresponding to the multiple software packages under the same software package identifier need to be modified to the specified version. Through the software dependency analysis method of this embodiment, the software package versions used in all projects are made transparent, non-RELEASE analysis of second- and third-party packages of all projects is achieved, and the release dependency order of each software package is output in the form of a view, making it easy to switch RELEASE.

[0060] Example 4: Figure 4 The following is a flow chart of a software dependency analysis method according to a fourth embodiment of the present invention. The software includes multiple projects, and the analysis method includes:

[0061] Step 402: Obtain multiple dependency reports corresponding to multiple projects and multiple software packages corresponding to the multiple projects;

[0062] Step 404: Determine dependencies among the plurality of software packages based on the plurality of dependency reports;

[0063] Step 406: Based on the dependency relationships, the multiple software packages are sorted according to the dependency hierarchy to obtain release dependency relationships of the multiple software packages.

[0064] Step 408: Generate and display a release dependency report of the plurality of software packages based on the release dependency;

[0065] Step 410: Obtain multiple software package identifiers and multiple version information corresponding to multiple software packages;

[0066] Step 412: If the version information corresponding to the multiple software packages with the same software package identifier is inconsistent, the versions corresponding to the multiple software packages with the same identifier are modified to a specified version;

[0067] Step 414 , filtering the release dependency report according to preset filtering conditions to generate a corresponding target release dependency report, wherein the preset filtering conditions include any one of the following or a combination thereof: software package identifier, software package release status, level name, and project identifier.

[0068] In this embodiment, the release dependency report can be filtered according to preset filter conditions, thereby generating a target release dependency report that meets specific conditions. The preset filter conditions can be set based on any one of the following: package identifier, package release status, layer name, project identifier, or any combination thereof. This allows for analysis of non-RELEASE information in the software and the SDK's use in other projects from different perspectives.

[0069] In any of the above embodiments, the step of obtaining multiple dependency reports corresponding to multiple projects specifically includes: scanning the compilation file corresponding to each project to determine the dependency report corresponding to each project.

[0070] In this embodiment, by scanning the compiled files corresponding to each project, a dependency report of each project can be obtained, including dependency information, software package identifier, project identifier, version information, and the like.

[0071] In any of the above embodiments, the dependency report includes dependencies of software packages used by any of the multiple projects.

[0072] In this embodiment, the dependency report includes the dependencies of the software packages used in any project, but is not limited to this. It is understandable that the report may also include basic information of the software packages, such as software package identification, project identification, version information, etc. The dependency report reflects the usage of the software package SDK in the project, that is, which software packages are used in the project, and the reference relationship of each software package. For example, project A includes sdk1 and sdk2, sdk1 references sdk3, sdk3 references sdk4 and sdk5, and sdk2 references sdk6. For a single project, this embodiment provides an analysis solution based on different perspectives such as projects and software packages. From the perspective of the project, it is possible to know which software packages are used in the project, the usage status of the software packages, and the versions used. From the perspective of the software packages, it is possible to know the dependencies and dependency order of the software packages. This provides a basis for analyzing the dependency situation of large-scale project engineering.

[0073] In any of the above embodiments, there is no dependency between multiple software packages in any layer.

[0074] In this embodiment, any level includes at least one software package. When multiple software packages are included, there is no dependency between the multiple software packages, so that software packages at the same level can be released in parallel, achieving efficient, convenient, and fast guidance for supporting RELEASE versions.

[0075] In any of the above embodiments, the format of the dependency report is txt format; the format for publishing the dependency report is excel format.

[0076] In this embodiment, the dependency report is in txt format, but is not limited thereto. When the dependency report format changes, the interface for reading each dependency report will also need to change accordingly when performing a comprehensive analysis of multiple dependency reports. The dependency report is published in excel format, but is not limited thereto.

[0077] Example 5 proposes a software dependency analysis method. Figure 5 FIG. 5 shows a logic diagram of a software dependency analysis method according to a fifth embodiment of the present invention. Figure 5 As shown in the figure, the two core tools of this analysis method are: a Maven-based plug-in that outputs a report on the SDK usage in each project, and a project-sdk-analyze plug-in that performs statistical analysis on the collected reports of all projects to analyze a large number of projects and output analysis from different perspectives. Specifically:

[0078] 1. Based on Maven plug-in, it can scan the dependency relationship report in the project and also support retrieval of those that meet specific conditions.

[0079] 2. Project-sdk-analyze: used to parse all generated reports, calculate the reference relationships and statistics in each report, and output the corresponding view report.

[0080] Figure 6 A schematic diagram of a release dependency report according to a fifth embodiment of the present invention is shown. The release dependency report displays the release dependencies of multiple software packages in batches (i.e., hierarchical). It is understandable that the first level (i.e., the first batch) to the tenth level are released in sequence, the second level depends on the first level, the third level depends on the first level and / or the second level, and so on. The tenth level can depend on any one of the previous nine levels or a combination thereof.

[0081] In addition, the release dependency report also displays the main project ID, sub-project ID, version information and status (i.e., software package release status), as well as the using projects (i.e., used software packages). Preset filtering conditions can be set based on the main project ID, sub-project ID, version information, software package release status, and software package ID. The release dependency report is then filtered based on the preset filtering conditions to generate the corresponding target release dependency report.

[0082] Compared with traditional solutions, this embodiment has the following advantages in the scenario of second- and third-party analysis of large-scale project engineering:

[0083] 1. Ability to quickly understand the distribution of specific SDKs in various projects;

[0084] 2. Ability to quickly know the usage status of SDK in a project;

[0085] 3. Be able to quickly understand the release dependencies and order of each SDK.

[0086] According to another embodiment of the present invention, a software dependency analysis device is provided. Figure 7 A schematic block diagram of a software dependency analysis device 700 according to an embodiment of the present invention is shown. The software dependency analysis device 700 includes a memory 702 storing a program and a processor 704 executing the program to implement the software dependency analysis method according to any of the above embodiments.

[0087] The software dependency analysis device 700 provided in this embodiment implements the steps of the software dependency analysis method of any of the above embodiments when the processor 704 executes the program. Therefore, the software dependency analysis device 700 includes all the beneficial effects of the software dependency analysis method of any of the above embodiments.

[0088] According to an embodiment of yet another aspect of the present invention, a readable storage medium is provided, on which a program is stored. When the program is executed by a processor, the software dependency analysis method according to any of the above embodiments is implemented.

[0089] The readable storage medium provided in this embodiment implements the steps of the software dependency analysis method of any of the above embodiments when the processor executes the program. Therefore, the readable storage medium includes all the beneficial effects of the software dependency analysis method of any of the above embodiments.

[0090] In this specification, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance, unless otherwise expressly specified or limited. Terms such as "connect," "install," and "fix" should be interpreted broadly. For example, "connect" can refer to a fixed connection, a detachable connection, or an integral connection; and can be directly connected or indirectly connected through an intermediary. Those skilled in the art will understand the specific meanings of these terms in the present invention based on specific circumstances.

[0091] Throughout this specification, terms such as "one embodiment," "some embodiments," and "specific embodiments" mean that the specific features, structures, materials, or characteristics described in conjunction with that embodiment or example are included in at least one embodiment or example of the present invention. In this specification, schematic representations of these terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0092] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A software dependency analysis method, wherein the software includes multiple projects, characterized in that: The analysis method comprises: Obtaining a plurality of dependency reports corresponding to the plurality of projects and a plurality of software packages corresponding to the plurality of projects; determining release dependencies of the plurality of software packages according to the plurality of dependency reports; generating and displaying a release dependency report of the plurality of software packages according to the release dependency; The step of determining the release dependencies of the multiple software packages based on the multiple dependency reports specifically includes: determining dependencies among the plurality of software packages according to the plurality of dependency reports; Based on the dependency relationship, the plurality of software packages are sorted according to the dependency order to obtain the release dependency relationship of the plurality of software packages; For any of the levels, the lower the level, the earlier it will be published, and the higher the level, the later it will be published; Obtaining multiple software package identifiers and multiple version information corresponding to the multiple software packages; When the version information corresponding to the multiple software packages based on the same software package identifier is inconsistent, the versions corresponding to the multiple software packages based on the same software package identifier are modified to a specified version.

2. The software dependency analysis method according to claim 1, wherein: The dependency report includes dependencies of software packages used by any one of the multiple projects.

3. The software dependency analysis method according to claim 1, wherein: There are no dependencies between packages in any of the described levels.

4. The software dependency analysis method according to claim 1, wherein: Also includes: Filter the release dependency report according to the preset filtering conditions to generate the corresponding target release dependency report, where The preset filtering condition includes any one of the following items or a combination thereof: software package identifier, software package release status, level name, and project identifier.

5. The software dependency analysis method according to claim 1, wherein: The step of obtaining multiple dependency reports corresponding to the multiple projects specifically includes: Scan the compiled files corresponding to each project to determine the dependency report corresponding to each project.

6. The software dependency analysis method according to claim 1, wherein: The dependency report is in txt format; The release dependency report is in Excel format.

7. A software dependency analysis device, characterized in that: include: a memory storing a program; A processor, wherein when executing the program, the processor implements the software dependency analysis method according to any one of claims 1 to 6.

8. A readable storage medium having a program stored thereon, characterized in that: When the program is executed by a processor, the software dependency analysis method according to any one of claims 1 to 6 is implemented.

Images