CN116029255A

CN116029255A - Verification platform generation method and device, electronic equipment and storage medium

Info

Publication number: CN116029255A
Application number: CN202310037522.8A
Authority: CN
Inventors: 请求不公布姓名
Original assignee: Shanghai Biren Intelligent Technology Co Ltd
Current assignee: Shanghai Biren Intelligent Technology Co Ltd
Priority date: 2023-01-09
Filing date: 2023-01-09
Publication date: 2023-04-28

Abstract

A method and a device for generating an initial verification platform, a method for generating a target verification platform, electronic equipment and a storage medium. The generation method of the initial verification platform comprises the following steps: reading a template file from a template library; and establishing a common layer and a functional layer of each first verification component based on the template file to obtain a plurality of first verification components. The function layer inherits from the shared layer, the shared layer comprises a corresponding first verification component and a shared sub-component shared by the first verification components except the corresponding first verification component, the function layer comprises a function sub-component of the corresponding first verification component, and configurable parameters are arranged in the function sub-components. The generation method of the initial verification platform can be used for dynamically generating the target verification platform for realizing the specific function, thereby reducing repeated work caused by manual code rewriting, saving the time of verification work and improving the verification reliability.

Description

Verification platform generation method and device, electronic equipment and storage medium

Technical Field

The embodiment of the disclosure relates to a method and a device for generating a verification platform, electronic equipment and a storage medium.

Background

In the field of IC design, mainstream Chip designs are increasingly tending toward System on Chip (SoC, also called System on Chip) designs using reusable IP cores (Intellectual Property core, also called IP modules). IP core refers to the mature design of circuit modules with independent functions in the chip. The speed and quality of the chip are important points in the development of the chip, and in order to ensure the speed and quality of the chip, the functional verification of the chip and the IP core thereof is an important link in the development process of the chip.

Disclosure of Invention

At least one embodiment of the present disclosure provides a method for generating an initial verification platform, wherein the initial verification platform includes a plurality of verification components, the plurality of verification components includes a plurality of first verification components, and each of the plurality of first verification components includes a common layer and a functional layer. The generation method of the initial verification platform comprises the following steps: reading a template file from a template library; and respectively establishing the shared layer and the functional layer of each first verification component based on the template file to obtain the plurality of first verification components, wherein the functional layer of each first verification component is inherited from the shared layer, the shared layer of each first verification component comprises shared sub-components shared by the corresponding first verification component and first verification components except the corresponding first verification component in the plurality of first verification components, the functional layer of each first verification component comprises functional sub-components of the corresponding first verification component, and the functional sub-components are provided with configurable parameters.

For example, the method for generating the initial verification platform provided by at least one embodiment of the present disclosure further includes: the initial verification platform is generated based on inheritance relationships among the plurality of verification components.

For example, in the method for generating the initial verification platform provided in at least one embodiment of the present disclosure, the inheritance relationship includes a first inheritance relationship, and the plurality of verification components includes a parent verification component having the first inheritance relationship and a child verification component that inherits the attribute of the parent verification component from the parent verification component based on the first inheritance relationship.

For example, in the method for generating an initial verification platform provided in at least one embodiment of the present disclosure, each first verification component further includes a user layer, and the method for generating an initial verification platform further includes: and establishing the user layer, wherein the user layer inherits from the functional layer, and a user-defined configuration part is reserved in the user layer for user-defined configuration.

For example, in the method for generating an initial verification platform provided in at least one embodiment of the present disclosure, each first verification component further includes a base layer, and the method for generating an initial verification platform further includes: and establishing the base layer, wherein the shared layer inherits from the base layer, and a corresponding base sub-component of the first verification component is arranged in the base layer.

For example, in the method for generating an initial verification platform provided in at least one embodiment of the present disclosure, the plurality of verification components further includes a second verification component different from the first verification component, and the method for generating an initial verification platform further includes: establishing the second verification component; the initial verification platform is generated based on inheritance relationships between the plurality of first verification components and the second verification component.

For example, in a method for generating an initial verification platform provided in at least one embodiment of the present disclosure, the initial verification platform includes a plurality of verification modules, each of the plurality of verification modules includes at least one first verification component of the plurality of first verification components, and the method for generating an initial verification platform further includes: and carrying out visualization processing on the configurable parameters in the functional sub-components of the at least one first verification component to obtain a visualization interface corresponding to each verification module.

The at least one embodiment of the present disclosure further provides a method for generating a target verification platform, where the method for generating the target verification platform includes: acquiring a parameter configuration table corresponding to the target verification platform; and setting the initial verification platform generated by the initial verification platform generation method provided by at least one embodiment of the present disclosure by using the parameter configuration table so as to generate the target verification platform.

For example, in a method for generating a target verification platform provided in at least one embodiment of the present disclosure, the parameter configuration table includes target parameters corresponding to the plurality of first verification components, and the initial verification platform is set by using the parameter configuration table to generate the target verification platform, including: and setting configurable parameters in the functional sub-components of the first verification components by using the target parameters to obtain a plurality of target first verification components of the target verification platform.

For example, in the method for generating the target verification platform provided in at least one embodiment of the present disclosure, the plurality of verification components further includes a second verification component different from the first verification component, the initial verification platform is set by using the parameter configuration table, so as to generate the target verification platform, and further includes: the target verification platform is generated based on inheritance relationships between the plurality of target first verification components and the second verification components.

For example, in a method for generating a target verification platform provided in at least one embodiment of the present disclosure, the initial verification platform includes a plurality of verification modules, each verification module of the plurality of verification modules includes at least one first verification component of the plurality of first verification components, a visualization interface is provided corresponding to each verification module, the visualization interface has configurable parameters in functional sub-components of the at least one first verification component of the corresponding verification module, and the acquiring a parameter configuration table corresponding to the target verification platform includes: acquiring parameters set by a user on the visual interface by utilizing the visual interface to obtain target parameters corresponding to the plurality of first verification components; and obtaining the parameter configuration table based on the target parameters.

The invention further provides a generating device of the initial verification platform, wherein the initial verification platform comprises a plurality of verification components, the plurality of verification components comprise a plurality of first verification components, and each of the plurality of first verification components comprises a common layer and a functional layer. The generation device of the initial verification platform comprises: a reading module configured to read a template file from a template library; the building module is configured to respectively build the shared layer and the functional layer of each first verification component based on the template file so as to obtain a plurality of first verification components; the function layer of each first verification component inherits from the shared layer, the shared layer of each first verification component comprises shared sub-components shared by the corresponding first verification component and first verification components except the corresponding first verification component, the function layer of each first verification component comprises functional sub-components of the corresponding first verification component, and configurable parameters are arranged in the functional sub-components.

For example, the generating device of the initial verification platform provided in at least one embodiment of the present disclosure further includes: a first generation module configured to generate the initial verification platform based on inheritance relationships between the plurality of verification components.

The at least one embodiment of the present disclosure further provides a generating device of a target verification platform, where the generating device of the target verification platform includes: the acquisition module is configured to acquire a parameter configuration table corresponding to the target verification platform; and the second generation module is configured to set an initial verification platform generated by the generation method provided by at least one embodiment of the present disclosure by using the parameter configuration table so as to generate the target verification platform.

At least one embodiment of the present disclosure also provides an electronic device. The electronic device includes: a processor; a memory including one or more computer program modules; wherein the one or more computer program modules are stored in the memory and configured to be executed by the processor, the one or more computer program modules configured to implement the method of generating an initial verification platform provided by any embodiment of the present disclosure or the method of generating a target verification platform provided by any embodiment of the present disclosure.

At least one embodiment of the present disclosure also provides a storage medium storing non-transitory computer readable instructions that, when executed by a computer, implement a method for generating an initial verification platform provided by any embodiment of the present disclosure or a method for generating a target verification platform provided by any embodiment of the present disclosure.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments will be briefly described below, and it is apparent that the drawings in the following description relate only to some embodiments of the present disclosure, not to limit the present disclosure.

FIG. 1A is a schematic diagram of a UVM verification platform;

FIG. 1B is a schematic diagram of a tree structure of the UVM verification platform of FIG. 1A;

FIG. 2 is an exemplary flow chart of a method of generating an initial verification platform provided by at least one embodiment of the present disclosure;

FIG. 3 is a schematic diagram of one example of a first validation component provided by at least one embodiment of the present disclosure;

FIG. 4 is a schematic diagram of one example of a visualization interface for a plurality of verification modules provided in accordance with at least one embodiment of the present disclosure;

FIG. 5 is an exemplary flow chart of a method of generating a target verification platform provided by at least one embodiment of the present disclosure;

FIG. 6 is another exemplary flow chart of a method of generating a target verification platform provided by at least one embodiment of the present disclosure;

fig. 7A is a schematic diagram of one example of implementing function 1 in a UVM verification platform;

FIG. 7B is a schematic diagram of one example of an initial verification platform implementation function 1 generated using methods provided by at least one embodiment of the present disclosure;

fig. 8A is a schematic diagram of another example of implementing function 1 in a UVM verification platform;

FIG. 8B is a schematic diagram of another example of implementing function 1 using an initial authentication platform generated by a method provided by at least one embodiment of the present disclosure;

fig. 9A is a schematic diagram of one example of implementing function 2 in a UVM verification platform;

FIG. 9B is a schematic diagram of one example of implementing function 2 using an initial authentication platform generated by a method provided by at least one embodiment of the present disclosure;

FIG. 10 is a schematic block diagram of a generating device of an initial verification platform provided by at least one embodiment of the present disclosure;

FIG. 11 is a schematic block diagram of a generating device of a target verification platform provided by at least one embodiment of the present disclosure;

FIG. 12 is a schematic block diagram of an electronic device provided in accordance with at least one embodiment of the present disclosure;

FIG. 13 is a schematic block diagram of another electronic device provided by at least one embodiment of the present disclosure; and

fig. 14 is a schematic diagram of a storage medium according to at least one embodiment of the present disclosure.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present disclosure. It will be apparent that the described embodiments are some, but not all, of the embodiments of the present disclosure. All other embodiments, which can be made by one of ordinary skill in the art without the need for inventive faculty, are within the scope of the present disclosure, based on the described embodiments of the present disclosure.

Unless defined otherwise, technical or scientific terms used in this disclosure should be given the ordinary meaning as understood by one of ordinary skill in the art to which this disclosure belongs. The terms "first," "second," and the like, as used in this disclosure, do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. Likewise, the terms "a," "an," or "the" and similar terms do not denote a limitation of quantity, but rather denote the presence of at least one. The word "comprising" or "comprises", and the like, means that elements or items preceding the word are included in the element or item listed after the word and equivalents thereof, but does not exclude other elements or items. The terms "connected" or "connected," and the like, are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", etc. are used merely to indicate relative positional relationships, which may also be changed when the absolute position of the object to be described is changed.

The present disclosure is illustrated by the following several specific examples. Detailed descriptions of known functions and known components may be omitted for the sake of clarity and conciseness in the following description of the embodiments of the present disclosure. When any element of an embodiment of the present disclosure appears in more than one drawing, the element is identified by the same or similar reference numeral in each drawing.

With the improvement of chip performance, the scale of chip design is larger and larger, and the dependence on verification is higher and higher. The UVM verification platform established based on the UVM (Universal Verification Methodology ) verification methodology is widely applied to chip verification to perform functional verification on a chip to be tested and an IP core thereof. UVM verification is a mainstream verification method, provides a reusable and layered verification platform framework, has the characteristics of clear layers, flexibility, easiness in use, expandability and the like, and is currently becoming a standard for chip industry verification.

For example, the verification environment of the device under test (Device Under Test, DUT, which may be, for example, an integrated circuit, chip, IP, etc.) may be built hierarchically according to grammatical requirements, or based on UVM and virtual machine monitors (Virtual Machine Monitor, simply VMM) of a particular programming language. For example, a DUT interface requires a separate verification environment, different verification environments are established according to the DUT's different needs, and then the environment is connected to the DUT in the verification top layer. After the environment is established, the verification environment can be applied to RTL of the same interface in the form of software or script, and then the verification environment is operated through the script. For example, when a new DUT needs to build a new verification environment, the verification environment script needs to be rewritten.

Fig. 1A is a schematic structural diagram of a UVM verification platform.

For example, as shown in fig. 1A, the UVM verification platform may include the following verification components: verification top layer 110 (test top), environment 120/121/122, input agent 130 (in_agent), output agent 140 (out_agent), monitor 131/141 (monitor), driver 132 (driver), sequencer 133 (sequence), reference model 150 (reference model), scoreboard 160 (scoreboard), and so forth. For example, to ensure the universality of the UVM verification platform, functional verification is split into separate sub-flows in UVM verification, and different sub-flows can be implemented by different verification components. Thus, when the verification environment 120 (or 121 or 122, etc.) for verifying different DUTs is established, a verification component may be selected from the UVM verification platform for corresponding sub-flow verification.

For example, verification top layer 110 is used to encapsulate environments 120/121/122 (hereinafter, environment 120 is all examples) that are used to functionally verify a DUT. In addition, the verification top layer 110 may also have encapsulated therein instantiated DUTs and interfaces of the DUTs with virtual interfaces of the environment 120 so that individual verification components in the environment 120 interact with the DUTs (e.g., data transfer, etc.).

For example, the input agent 130 and the output agent 140 are used to layer and connect portions of the authentication component. The input agent 130 may have monitor 131 and driver 132 encapsulated therein and the output agent 140 may have monitor 141 encapsulated therein. The driver 132 may be used to apply stimulus signals to the sequencer 133 and drive the stimulus signals onto ports of the DUT as specified by the bus protocol. Monitor 131 may be used to monitor the stimulus signal driven on the DUT and send the monitored stimulus signal to reference model 150. The reference model 150 may be used to perform the same functions as the DUT. Score board 160 may be used to compare data sent by reference model 150 and monitor 141, respectively, to obtain a comparison result, and to determine if the DUT is operating properly based on the comparison result. The monitor 241 is used to monitor the response signal generated by the DUT for the stimulus signal and send the response signal to the scoreboard 160.

For example, according to the manner in which the individual authentication components of the UVM authentication platform are packaged in fig. 1A, the individual authentication components are divided into different levels and thus may be represented by a tree structure. Fig. 1B is a schematic tree structure diagram of the UVM verification platform of fig. 1A.

For example, as shown in fig. 1B, the verification top layer 110 may serve as a root of the tree structure, and other verification components may serve as nodes of different levels in the tree structure based on different encapsulation manners. In the tree structure shown in FIG. 1B, a parent node (e.g., authentication top layer 110) may operate to manage connected child nodes (e.g., environment 120) to enable orderly management of authentication components, avoiding omission and errors. The function and packaging manner of each verification component have been described in detail in fig. 1A, and thus will not be described in detail.

For example, based on the UVM verification platform in fig. 1A or 1B, a verifier manually writes code for implementing a specific function for a DUT as an instantiated target verification platform; the target verification platform interacts with the DUT through the interface signal agent and applies test stimulus to the DUT for corresponding functional verification. For example, specifically, for an IP module, after a certain IP module is designed, an IP module verifier may manually write a specific code according to the IP module function and the interface signal to instantiate the UVM verification platform to serve as a target verification platform for the IP module, and perform corresponding function verification on the IP module by using the target verification platform.

Therefore, in order to generate the target verification platform, handwriting codes are required, the handwriting codes have strong specialization, and migration among modules is difficult to achieve, so that time and energy are wasted greatly. Or, codes can be generated through scripts, however, most of the codes generated by the scripts are command line interaction, so that the use is inconvenient, and once the functions needing verification are increased, the codes can not be used basically; furthermore, the code generated by the script is static, that is, the code can only be rewritten manually once it needs to be modified, so that a large amount of repetitive work is required, and thus automatic verification cannot be realized.

At least one embodiment of the present disclosure provides a method for generating an initial verification platform, where the initial verification platform includes a plurality of verification components, the plurality of verification components includes a plurality of first verification components, and each of the plurality of first verification components includes a common layer and a functional layer. The generation method of the initial verification platform comprises the following steps: reading a template file from a template library; and respectively establishing a common layer and a functional layer of each first verification component based on the template file to obtain a plurality of first verification components. The function layer of each first verification component inherits from the shared layer, the shared layer of each first verification component comprises a shared sub-component shared by the corresponding first verification component and the first verification components except the corresponding first verification component, the function layer of each first verification component comprises a function sub-component of the corresponding first verification component, and configurable parameters are arranged in the function sub-components.

At least one embodiment of the present disclosure further provides a method for generating a target verification platform, where the method for generating a target verification platform includes: acquiring a parameter configuration table corresponding to a target verification platform; and setting the initial verification platform generated by the initial verification platform generation method provided by at least one embodiment of the present disclosure by using the parameter configuration table so as to generate the target verification platform.

At least one embodiment of the present disclosure also provides a generating device of the initial verification platform, a generating device of the target verification platform, an electronic device and a storage medium.

The method, the device, the equipment and the storage medium provided by at least one embodiment of the present disclosure separate the shared part from the part requiring user definition by layering the verification component and reserving the configurable parameter in the functional layer, so that the user can configure the configurable parameter to modify the initial verification platform, thereby being capable of being used for dynamically generating the target verification platform for realizing the specific function, thereby reducing the repeated work caused by manually rewriting the code, saving the time of the verification work, and improving the verification reliability.

It should be noted that, the "initial verification platform" in the disclosure may also be referred to as a "general verification platform" and the "target verification platform" may also be referred to as a "special verification platform", and other naming manners may also be selected according to actual needs, which is not limited in the embodiments of the disclosure; furthermore, the purposes and functions of the "initial verification platform" and the "target verification platform" are not limited by the manner of naming, and are described in detail in this disclosure.

Hereinafter, at least one embodiment of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that the same reference numerals in different drawings will be used to refer to the same elements already described.

Fig. 2 is an exemplary flowchart of a method for generating an initial verification platform according to at least one embodiment of the present disclosure.

For example, as shown in fig. 2, at least one embodiment of the present disclosure provides a method of generating an initial authentication platform including a plurality of authentication components including a plurality of first authentication components, each of the plurality of first authentication components including a common layer and a functional layer. For example, the method for generating the initial verification platform includes the following steps S110 to S120.

Step S110: reading a template file from a template library;

step S120: and respectively establishing a common layer and a functional layer of each first verification component based on the template file to obtain a plurality of first verification components.

For example, embodiments of the present disclosure utilize a selected programming language to generate an initial verification platform; in step S110, an appropriate type may be selected from a template library of the programming language, as a template library, and a template file is a code file in the template library required for generating the initial verification platform, for example, a reusable portion of the code required for generating the initial verification platform.

In some examples, the initial verification platform may be a UVM verification platform; accordingly, the programming language may be SV (SystemVerilog), python, etc.; for example, when the programming language python, the template library may be the jinja2 library of python, the Mako library, or the Genshi library, etc.; it should be noted that the selection of the verification platform, the programming language, and the template library is not limited to the above description, and other selections may be made as desired, which is not limited by the embodiments of the present disclosure.

For example, in step S120, the common layer of each first verification component includes a common sub-component shared by the corresponding first verification component and the other first verification components except for the first verification component; the functional layer of each first verification component comprises a functional sub-component of the corresponding first verification component, and in particular, the functional sub-component is provided with configurable parameters. For example, taking a driver (driver) in the UVM verification platform as the first verification component, a common layer of the driver may be denoted as a base_driver by using a pseudo code, a functional layer of the driver may be denoted as { { { name } -shadow_driver by using a pseudo code, where { { { name } } -is an example of a configurable parameter, and a user may replace or modify "name" according to actual needs.

In some examples, the inheritance relationship includes a first inheritance relationship. For example, the plurality of verifying components includes a parent verifying component having a first inheritance relationship and a child verifying component that inherits properties of the parent verifying component from the parent verifying component based on the first inheritance relationship.

For example, the functional layer of each first verification component inherits from the common layer, i.e., the functional layer is a child verification component, the common layer is a parent verification component, and the functional layer may relay the properties of the common layer from the common layer based on the first inheritance relationship. For example, taking a driver (driver) in the UVM verification platform as an example of the first verification component, one example of the pseudo code of the inheritance relationship between the functional layer and the common layer may be { { { name } } -shadow_ drver extends base _driver, where "extensions" may represent the first inheritance relationship.

In some examples, the method for generating the initial verification platform may further include step S130:

step S130: an initial verification platform is generated based on inheritance relationships between the plurality of verification components.

For example, in step S130, the plurality of authentication components have respective inheritance relationships (e.g., first inheritance relationships) therebetween; in the process of establishing each verification component of the initial verification platform, inheritance relationships among a plurality of verification components also need to be established, so as to generate the initial verification platform. For example, taking the initial verification platform as the UVM verification platform shown in fig. 1A or fig. 1B as an example, multiple verification components may be divided into different levels based on the encapsulation manner between each other, so as to be nodes of different levels in the tree structure, where a parent node and a child node have corresponding inheritance relationships.

For example, in some examples, the plurality of verification components may further include a second verification component that is different from the first verification component. For example, taking the initial verification platform as a UVM verification platform, a second verification component, such as a reference model, is used to receive stimulus signals to perform the same function as the DUT. For example, when the second validation component is a reference model, no common or functional layers may be included.

For example, the method for generating the initial verification platform provided by the embodiment of the present disclosure further includes: establishing a second verification component; an initial verification platform is generated based on inheritance relationships between the plurality of first verification components and the second verification components. For example, taking the initial verification platform as the UVM verification platform shown in fig. 1A or 1B as an example, the second verification component is, for example, a reference model 150, the reference model 150 inherits from the environment 120. For example, in step S130, an initial verification platform may be generated based on inheritance relationships between the plurality of first verification components in the above example, and based on inheritance relationships between the second verification component and the corresponding first verification component in the above example.

Fig. 3 is a schematic diagram of one example of a first validation component provided in accordance with at least one embodiment of the present disclosure. For example, the first verification component of FIG. 3 may be established by the generation method of the initial verification platform of FIG. 2.

For example, as shown in FIG. 3, each first validation component includes a common layer and a functional layer. For example, the common layer comprises common sub-components which can be fully shared between different first verification components, the common sub-components being obtained, for example, by means of a template file. For example, the common sub-components in the common layer of each first verification component are identical, and configurable parameters do not need to be set, so that the problem that the common sub-components need to be manually duplicated once when each first verification component is established is avoided.

For example, the functional layer includes a functional sub-component of the corresponding first verification component, which may be used to implement a specific function or instantiation and connection of functional portions, e.g., stimulus driven, response collection, etc. For example, the configurable parameters are arranged in the functional sub-assembly, and a user can configure the configurable parameters to modify the functional sub-assembly, so that the functional layer has stronger modification; and other parts of the functional sub-components than the configurable parameters may also be obtained from the template file, which may be used to dynamically generate the target functional layer for implementing a particular function.

For example, in some examples, a common sub-component may be code required to establish a common layer, a functional sub-component may be code required to establish a functional layer, and embodiments of the present disclosure are not limited to a specific form of common sub-component or functional sub-component.

For example, as shown in FIG. 3, each first validation component may also include a base layer. For example, the base layer is provided with a base sub-component of the corresponding first verification component. For example, taking the initial verification platform as a UVM verification platform as an example, the base sub-component may be a base sub-component based on UVM standards, such as UVM _driver, uvm_monitor, and the like.

For example, as shown in FIG. 3, each first authentication component may also include a user layer. For example, a user layer is reserved with a custom configuration part for user to perform custom configuration. For example, the user may add the required code at the user layer as needed; because these codes are difficult to integrate into the template file, the user can customize the configuration in the user layer. In addition, the user-defined codes are separated from the template files, so that the universality of the template files can be improved, and the reusability of the template files can be improved. For example, taking the initial Verification platform as a UVM Verification platform as an example, the user layer may be used to process the Verification top layer or the differentiated features between different DUTs, such as whether a C language digital programming Model (C-Model), verification IP (VIP), etc. are needed, including a file list (file) required for Verification, test cases (testcases), regression configuration (regression), etc.; in addition, the user can add the required codes at the user layer through custom configuration, so that new functions can be added.

For example, the method for generating the initial verification platform provided by the embodiment of the present disclosure may further include: a base layer is established (when each first authentication component comprises a base layer), and a user layer is established (when each first authentication component comprises a user layer). For example, as shown in fig. 3, the common layer may inherit from the base layer, i.e., there is a first inheritance relationship between the common layer and the base layer; the user layer may inherit from the functional layer, i.e. there is a first inheritance relationship between the user layer and the functional layer. For example, taking a drive (driver) in the UVM verification platform as the first verification component, the base layer of the drive may be denoted as UVM _driver with a pseudo code, and the user layer of the drive may be denoted as user_driver with a pseudo code; one example of the pseudo code of the inheritance relationship between the common layer and the base layer may be base_ drver extends uvm _river, and one example of the pseudo code of the inheritance relationship between the user layer and the function layer may be user_river extensions { { { name } -shadow_river, wherein "extensions" may represent the first inheritance relationship.

According to the method for generating the initial verification platform, the verification component is layered, the configurable parameters are reserved in the functional layer, the shared part is separated from the part requiring user definition, so that the user can configure the configurable parameters to modify the initial verification platform, and the method can be used for dynamically generating the target verification platform for realizing the specific function, repeated work caused by manually rewriting codes is reduced, verification time is saved, and verification reliability is improved.

In some examples, the initial verification platform includes a plurality of verification modules, each verification module including at least one of a plurality of first verification components of the initial verification platform. For example, the method for generating the initial verification platform further comprises the following steps: and carrying out visualization processing on the configurable parameters in the functional sub-components of at least one first verification component to obtain a visual interface corresponding to each verification module.

For example, since each first verification component of each verification module includes a functional layer, and the functional sub-components in the functional layer are provided with configurable parameters, the configurable parameters of each verification module may be subjected to a visualization process, so as to obtain a visualization interface corresponding to each verification module.

Fig. 4 is a schematic diagram of one example of a visualization interface for a plurality of verification modules provided in accordance with at least one embodiment of the present disclosure.

For example, as shown in fig. 4, taking the example that the initial authentication platform is the UVM authentication platform shown in fig. 1A or fig. 1B, the initial authentication platform may include a plurality of authentication modules: top layer module, environment module, agency module, score board module. For example, the top-level module includes a first verification component (i.e., verifying the top-level 110), the environment module includes a first verification component (i.e., environment 120), and the scoreboard module includes a first verification component (i.e., scoreboard 160); when the agent module corresponds to an input agent, the environment module includes 4 first validation components (i.e., input agent 130, monitor 131, driver 132, sequencer 133); when the agent module corresponds to an output agent, the environment module includes 2 first validation components (i.e., output agent 140, monitor 141).

For example, as shown in fig. 4, taking a top module as an example, the top module includes a configurable parameter 01, a configurable parameter 02 and a configurable parameter 03 and …, and a visual interface of the top module is obtained through visual processing. For example, the user may set the configurable parameters 01, 02 and 03 … by selecting "yes" or "no" through the visual interface of the top module, so as to select which parameters are specifically needed to be included in the top module, so that the instantiated top module may be obtained.

For example, as shown in fig. 4, taking a proxy module as an example, the proxy module includes configurable parameters 11, 12 and 13 …, and a visual interface of the proxy module is obtained through visual processing. For example, the user may input the required parameters in the blank of the configurable parameters 11, 12 and 13 and … through the visual interface of the proxy module, so as to obtain the instantiated proxy module. For example, specifically, taking the function layer { { { name } -shadow_driver as an example, where { { name } -is the configurable parameter 12, the user may replace "{ name }" by inputting the required parameter "test_if_1" at the blank of the configurable parameter 12 through the visual interface, and the function layer of the driver is instantiated as the target function layer test_if_1_shadow_driver.

For example, as shown in fig. 4, the user may further create a verification module according to the actual requirement to obtain a corresponding visual interface, so as to set parameters of the verification module to be instantiated. For example, when a new DUT needs to be verified, a new verification environment needs to be established, an environment module can be newly built; for another example, when the proxy module in fig. 4 corresponds to the input proxy, a proxy module corresponding to the output proxy needs to be established, and then the proxy module may be newly built.

For example, as shown in FIG. 4, a "generate" button is also included in the visual interface. For example, after the user has set all the parameters on the visualization interface of all the verification modules, a parameter configuration table for a specific function may be obtained in the background, where the parameter configuration table includes target parameters corresponding to a plurality of first verification components. For example, the user may click a "generate" button to set the initial verification platform using the parameter configuration table so that the initial verification platform may be instantiated as a target verification platform for implementing a particular function. For example, the "generate" button may be implemented by a Code generation tool such as "Code Gen", to which embodiments of the present disclosure are not limited.

For example, the visual interface as shown in FIG. 4 may be a graphical user interface (Graphical User Interface, GUI) developed using a visual development tool. For example, the visual development tool may be a tkinter, pyqt, pyside, wxpython tool in Python language, an adwt tool, a swing tool in Java language, or a FLTK, QT, MFC tool in c++ language, or other programming languages and other visual development tools according to actual needs, which is not limited by the embodiments of the present disclosure.

It should be noted that, the visual interfaces of the plurality of verification modules shown in fig. 4 are only an example, and the plurality of verification modules may be divided into other types according to actual needs, or may be set in other configuration manners according to actual needs, which is not limited in the embodiments of the present disclosure.

For example, in the initial verification platform generation method provided by the embodiment of the disclosure, by setting the visual interfaces of the multiple verification modules, a user can directly configure the configurable parameters on the visual interfaces without writing codes in the code editing interface, thereby improving the operation convenience. In addition, by setting a 'generate' button shown in fig. 4 on the visual interface, after the visual interface is configured with all parameters, a user can click the 'generate' button to generate a target verification platform for realizing a specific function in a one-click manner, so that automatic verification is further realized.

Fig. 5 is an exemplary flowchart of a method for generating a target verification platform according to at least one embodiment of the present disclosure. For example, the target verification platform in fig. 5 may be obtained by instantiating the generated initial verification platform of the generation method of the initial verification platform in fig. 2.

For example, the target verification platform is used to verify a specific function of the target DUT, and the generation method of the target verification platform includes the following steps S210 to S220.

Step S210: acquiring a parameter configuration table corresponding to a target verification platform;

step S220: and setting the initial verification platform generated by the initial verification platform generation method by using the parameter configuration table so as to generate the target verification platform.

For example, in step S210, the parameter configuration table includes target parameters corresponding to the plurality of first verification components. In some examples, a visualization interface of multiple verification modules in an initial verification platform may be utilized to obtain a parameter configuration table corresponding to a target verification platform. For example, step S210 may include: acquiring parameters set by a user on a visual interface by utilizing the visual interface to obtain target parameters corresponding to a plurality of first verification components; and obtaining a parameter configuration table based on the target parameters.

For example, in step S220, the configurable parameters in the functional sub-components of the plurality of first verification components may be set using the target parameters to obtain a plurality of target first verification components of the target verification platform. In some examples, the initial verification platform may be set through a parameter configuration table obtained through visual interfaces of multiple verification modules in the initial verification platform, such that the initial verification platform may be instantiated as a target verification platform for implementing a particular function.

For example, taking the visual interface shown in fig. 4 as an example, the visual interface may be used to collect all parameters set by the user on the visual interface, so as to obtain target parameters corresponding to a plurality of first verification components; based on the target parameters, a parameter configuration table for a specific function can be obtained in the background. For example, as shown in FIG. 4, after obtaining the parameter configuration table, the user may click on the "generate" button to set the initial verification platform using the parameter configuration table, so that the target verification platform for implementing the specific function may be dynamically generated.

For example, in some examples, the plurality of verification components may further include a second verification component that is different from the first verification component. For example, taking the initial verification platform as a UVM verification platform, a second verification component, such as a reference model, is used to receive stimulus signals to perform the same function as the DUT. For example, when the second validation component is a reference model, the common layer or the functional layer may not be included; accordingly, the second verification component can be directly used to generate the target verification platform without setting configurable parameters.

For example, step S220 may further include: a target verification platform is generated based on inheritance relationships between the plurality of target first verification components and the second verification components. For example, the inheritance relationship between the plurality of target first and second verification components is the same as the inheritance relationship between the plurality of first and second verification components in the initial verification platform.

For example, taking the initial verification platform as the UVM verification platform shown in fig. 1A or 1B as an example, the second verification component is, for example, a reference model 150, the reference model 150 inherits from the environment 120. For example, in step S220, a target verification platform may be generated based on inheritance relationships between a plurality of first verification components, such as described in step S130 in fig. 2, and inheritance relationships between a second verification component and a corresponding first verification component.

Fig. 6 is another exemplary flowchart of a method for generating a target verification platform according to at least one embodiment of the present disclosure. For example, in FIG. 6, a target verification platform is generated using the visualization interface shown in FIG. 4.

For example, as shown in fig. 6, in S1, a visual interface is started. For example, the home page of the visual interface may be used to input the name of the verification module for which parameter configuration is desired, and then enter the parameter configuration interface of that verification module. For example, in S2, the configurable parameters set by the user on the visual interface are collected using the visual interface as shown in fig. 4, so as to obtain target parameters corresponding to the plurality of first verification components. For example, in S3, a parameter configuration table for a specific function may be obtained in the background based on the target parameter. For example, after obtaining the parameter configuration table, in S4, the initial verification platform is set using the parameter configuration table (e.g., by clicking on a "generate" button as shown in fig. 4). For example, in S5, after setting the initial verification platform using the parameter configuration table, the target verification platform for implementing the specific function may be dynamically generated.

For example, specific processes for executing the method for generating the initial verification platform and the method for generating the target verification platform provided in the embodiments of the present disclosure are detailed in fig. 2 to 5, and are not described herein again.

For example, by using the initial verification platform generation method and the target verification platform generation method provided in fig. 2 to 6, the DUT can be subjected to corresponding function verification. In the following, taking fig. 7A-9B as examples, several specific examples of implementing different verification functions using an initial verification platform generated by a method provided by at least one embodiment of the present disclosure are described.

Fig. 7A is a schematic diagram of one example of implementing function 1 in a UVM verification platform; fig. 7B is a schematic diagram of one example of an initial verification platform implementation function 1 generated using a method provided by at least one embodiment of the present disclosure. For example, function 1 may be a function (non-valid cycle drive X) of invalid loop driver X implemented in a driver verification component, as well as other functions implemented in a driver verification component, as embodiments of the present disclosure are not limited in this regard.

For example, as shown in fig. 7A, in the UVM verification platform, function 1 is implemented in drive a and drive B, respectively, with corresponding function codes. For example, the function codes of the drive a and the drive B are different in identification names of variables, that is, a variable corresponding to the drive a is a_if.a_data and a variable corresponding to the drive B is b_if.b_data. Accordingly, it is necessary to manually input the corresponding function codes in the driver a and the driver B, respectively.

For example, as shown in fig. 7B, with the initial verification platform generated by the method provided by the embodiment of the present disclosure, the drive is used as a first verification component of the initial verification platform, and a functional sub-component (e.g., functional code) for implementing the function 1 is included in a functional layer of the initial verification platform. For example, a configurable parameter "< if >" is set in a function sub-component of the driver, and is used for representing the identification name of a variable in the function code; the user need only replace the configurable parameter "< if >" with the identification name "a" or "B" corresponding to drive a or drive B. For example, further, the verification platform may automatically generate, through the function sub-component, the function code corresponding to driver a or driver B, respectively, and may dynamically generate the target verification platform for implementing function 1 corresponding to driver a and driver B, respectively.

Fig. 8A is a schematic diagram of another example of implementing function 1 in a UVM verification platform; fig. 8B is a schematic diagram of another example of implementing function 1 using an initial authentication platform generated by a method provided by at least one embodiment of the present disclosure. For example, the UVM verification platform of fig. 8A is the same as that of fig. 7A, and the verification platform of fig. 8B is the same as that of fig. 7B, and the same parts are not repeated.

For example, as shown in fig. 8A, in the UVM verification platform, in order to change the function 1 implementation drive "X" to the implementation drive "rand", it is necessary to manually input the corresponding function codes in the driver a and the driver B, respectively, and to manually change "drive X" in the function codes to "drive rand".

For example, as shown in fig. 8B, with the initial verification platform generated by the method provided by the embodiment of the present disclosure, "X" in the functional subcomponent of the drive may also be set as a configurable parameter, and the user need only replace the configurable parameter "X" with "rand" and replace the configurable parameter "< if >" with the identification name "a" or "B" corresponding to the drive a or the drive B. For example, further, the verification platform may automatically generate, through the function sub-component, the function code corresponding to driver a or driver B, respectively, and may dynamically generate the target verification platform for implementing function 1 corresponding to driver a and driver B, respectively.

For example, as shown in fig. 7B and 8B, by configuring the configurable parameters to modify the initial verification platform, the target verification platform for implementing the function 1 may be dynamically generated, thereby reducing repetitive work caused by manually rewriting the code in fig. 7A and 8A, saving time of verification work, and improving verification reliability. For example, the user can also configure the configurable parameters in the functional sub-components by using the visual interface as shown in fig. 4, without writing codes in the code editing interface, thereby improving the convenience of operation.

Fig. 9A is a schematic diagram of one example of implementing function 2 in a UVM verification platform; fig. 9B is a schematic diagram of one example of implementing function 2 using an initial authentication platform generated by a method provided by at least one embodiment of the present disclosure. For example, function 2 may be a function of verifying a performance counter (performance counter) in an environment verification component, or may be other functions implemented in an environment verification component, as embodiments of the present disclosure are not limited in this regard.

For example, as shown in fig. 9A, in the UVM verification platform, in order to implement the function 2 in the environment a, the environment B, …, and the environment C, it is necessary to set a corresponding function 2 agent (agent) and a corresponding function 2 functional unit in the environment a, the environment B, …, and the environment C, respectively. For example, the function 2 agent contains the code necessary to establish the agent authentication component, and the function 2 functional unit contains a large amount of functional code for implementing the function 2.

For example, as shown in fig. 9A, in order to establish an a_functionally 2 agent and an a_functionally 2 functional unit in the environment a, establish a b_functionally 2 agent and a b_functionally 2 functional unit in the environment B, …, and establish a c_functionally 2 agent and a c_functionally 2 functional unit in the environment C, it is necessary to manually input corresponding codes in the environment a, the environment B, …, and the environment C, respectively.

For example, as shown in fig. 9B, with the initial verification platform provided by the embodiment of the present disclosure, the environment is used as a first verification component of the initial verification platform, and the functional layer thereof includes a functional sub-component 1 and a functional sub-component 2 for implementing the function 2; the function sub-assembly 1 contains the code required for establishing the function 2 agent, and the function sub-assembly 2 contains the code required for establishing the function 2 function unit.

For example, as shown in FIG. 9B, the user need only modify the configurable parameters in function sub-assembly 1 and function sub-assembly 2. For example, further, the verification platform may automatically generate an a_functionally 2 agent, a b_functionally 2 agent, …, and a c_functionally 2 agent through the functional sub-component 1, automatically generate an a_functionally 2 unit, a b_functionally 2 unit, …, and a c_functionally 2 unit through the functional sub-component 2, have instantiated the functional sub-component 1 and the functional sub-component 2 in the environment a, the environment B, …, and the environment C, respectively, and may dynamically generate the target verification platform for implementing the function 2 corresponding to the environment a, the environment B, …, and the environment C, respectively.

For example, as shown in fig. 9B, by configuring the configurable parameters to modify the initial verification platform, the target verification platform for the verification function 2 may be dynamically generated, so that repeated operations caused by manually inputting corresponding codes in the environment a, the environment B, … and the environment C in fig. 9A are reduced, time for verification operations is saved, and verification reliability is improved. For example, the user can configure the configurable parameters in the function sub-assembly 1 and the function sub-assembly 2 by using the visual interface as shown in fig. 4, without writing codes in the code editing interface, thereby improving the operation convenience.

It should be noted that, the implementation of different verification functions by using the initial verification platform generated by the method provided by at least one embodiment of the present disclosure in fig. 7A to fig. 9B is only a few examples, and other verification functions may also be implemented by selecting according to actual needs, which is not limited by the embodiments of the present disclosure. In addition, specific processes of the method for generating the initial verification platform and the method for generating the target verification platform provided in the embodiments of the present disclosure are detailed in fig. 2 to 5, and are not described herein again.

According to the method for generating the initial verification platform and the method for generating the target verification platform, provided by at least one embodiment of the disclosure, the verification component is layered, the configurable parameters are reserved in the functional layer, and the shared part is separated from the part requiring user definition, so that the user can configure the configurable parameters to modify the initial verification platform, and the method can be used for dynamically generating the target verification platform for realizing the specific function, thereby reducing repeated work caused by manual code rewriting, saving the time of verification work, and improving the verification reliability.

Fig. 10 is a schematic block diagram of a generating device of an initial verification platform according to at least one embodiment of the present disclosure. For example, the initial verification platform includes a plurality of verification components including a plurality of first verification components, each first verification component of the plurality of first verification components including a common layer and a functional layer.

For example, as shown in fig. 10, the generating device 200 of the initial verification platform includes a reading module 210, a setting-up module 220, and a first generating module 230.

For example, the reading module 210 is configured to read a template file from a template library. That is, the reading module 210 may be configured to perform, for example, step S110 shown in fig. 2.

For example, the creation module 220 is configured to create a common layer and a functional layer of each first verification component, respectively, based on the template file, to obtain a plurality of first verification components. For example, the functional layer of each first verification component inherits from the common layer, the common layer of each first verification component includes a common sub-component shared by the corresponding first verification component and the first verification components except for the corresponding first verification component in the plurality of first verification components, the functional layer of each first verification component includes a functional sub-component of the corresponding first verification component, and the functional sub-component is provided with a configurable parameter. That is, the setup module 220 may be configured to perform, for example, step S120 shown in fig. 2.

For example, the first generation module 230 is configured to generate an initial verification platform based on inheritance relationships between multiple verification components. That is, the first generation module 230 may be configured to perform, for example, step S130 shown in fig. 2.

Fig. 11 is a schematic block diagram of a generating device of a target verification platform according to at least one embodiment of the present disclosure.

For example, as shown in fig. 11, the generating device 300 of the target verification platform includes an obtaining module 310 and a second generating module 320.

For example, the acquisition module 310 is configured to acquire a parameter configuration table corresponding to the target verification platform. That is, the acquisition module 310 may be configured to perform, for example, step S210 shown in fig. 5.

For example, the second generation module 320 is configured to set an initial verification platform generated according to a generation method such as shown in fig. 2 using a parameter configuration table to generate a target verification platform. That is, the second generation module 320 may be configured to perform, for example, step S220 shown in fig. 5.

Since details of the operations of the initial authentication platform generating apparatus 200 and the target authentication platform generating apparatus 300 have been described in the above description of the initial authentication platform generating method such as that shown in fig. 2 and the target authentication platform generating method such as that shown in fig. 5, the details thereof will not be repeated here, and thus, the related details may be referred to the above description of fig. 1 to 9B for brevity.

In the initial verification platform generating apparatus 200 shown in fig. 10 and the target verification platform generating apparatus 300 shown in fig. 11, each of the above modules may be configured as software, hardware, firmware, or any combination thereof that performs a specific function. For example, these modules may correspond to application specific integrated circuits, to pure software code, or to a combination of software and hardware. By way of example, the devices described with reference to fig. 10 and 11 may be, but are not limited to, PC computers, tablet devices, personal digital assistants, smartphones, web applications, or other devices capable of executing program instructions.

In addition, although the generation apparatus 200 of the initial authentication platform and the generation apparatus 300 of the target authentication platform are divided into the modules for respectively performing the respective processes in the above description, it is apparent to those skilled in the art that the processes performed by the respective modules may be performed without any specific division of the modules in the apparatus or without explicit demarcation between the respective modules. Further, the generation apparatus 200 of the initial verification platform described above with reference to fig. 10 and the generation apparatus 300 of the target verification platform described in fig. 11 are not limited to include the above-described modules, but some other modules (e.g., a writing module, a control module, etc.) may be added as needed, or the above modules may be combined as well.

At least one embodiment of the present disclosure also provides an electronic device including a processor and a memory; the memory includes one or more computer program modules; one or more computer program modules are stored in the memory and configured to be executed by the processor, the one or more computer program modules comprising a method for implementing the generation of an initial verification platform or a method for generating a target verification platform provided by embodiments of the present disclosure as described above.

FIG. 12 is a schematic block diagram of an electronic device provided in accordance with at least one embodiment of the present disclosure

For example, as shown in fig. 12, the electronic device 400 includes a processor 410 and a memory 420. For example, memory 420 is used to store non-transitory computer-readable instructions (e.g., one or more computer program modules). The processor 410 is configured to execute non-transitory computer readable instructions that when executed by the processor 410 may perform one or more steps in accordance with the initial verification platform generation method or target verification platform generation method described above. The memory 420 and the processor 410 may be interconnected by a bus system and/or other form of connection mechanism (not shown).

For example, the processor 410 may be a Central Processing Unit (CPU), a Digital Signal Processor (DSP), or other form of processing unit having data processing and/or program execution capabilities, such as a Field Programmable Gate Array (FPGA), or the like; for example, the Central Processing Unit (CPU) may be an X86 or ARM architecture, or the like. The processor 410 may be a general-purpose processor or a special-purpose processor that may control other components in the electronic device 400 to perform the desired functions.

For example, memory 420 may include any combination of one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. Volatile memory can include, for example, random Access Memory (RAM) and/or cache memory (cache) and the like. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, erasable programmable read-only memory (EPROM), portable compact disc read-only memory (CD-ROM), USB memory, flash memory, and the like. One or more computer program modules may be stored on the computer readable storage medium and executed by the processor 410 to implement various functions of the electronic device 400. Various applications and various data, as well as various data used and/or generated by the applications, etc., may also be stored in the computer readable storage medium.

It should be noted that, in the embodiments of the present disclosure, specific functions and technical effects of the electronic device 400 may refer to the description of the method for generating the initial verification platform and the method for generating the target verification platform provided in at least one embodiment of the present disclosure, which are not repeated herein.

Fig. 13 is a schematic block diagram of another electronic device provided in at least one embodiment of the present disclosure.

For example, as shown in fig. 13, the electronic device 500 is suitable for implementing, for example, a method for generating an initial verification platform or a method for generating a target verification platform provided by an embodiment of the present disclosure. It should be noted that the electronic device 500 shown in fig. 13 is only one example and does not impose any limitation on the functionality and scope of use of the disclosed embodiments.

For example, as shown in fig. 13, the electronic device 500 may include a processing means (e.g., a central processor, a graphics processor, etc.) 51 that may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 52 or a program loaded from a storage means 58 into a Random Access Memory (RAM) 53. In the RAM 53, various programs and data required for the operation of the electronic device 500 for cache system simulation are also stored. The processing device 51, the ROM 52, and the RAM 53 are connected to each other via a bus 54. An input/output (I/O) interface 55 is also connected to bus 54. In general, the following devices may be connected to the I/O interface 55: input devices 56 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 57 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage devices 58 including, for example, magnetic tape, hard disk, etc.; and a communication device 59. The communication means 59 may allow the electronic device 500 to communicate wirelessly or by wire with other electronic devices to exchange data.

While fig. 13 shows electronic device 500 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided, and that electronic device 500 may alternatively be implemented or provided with more or fewer means.

Regarding the detailed description and technical effects of the electronic device 500, reference may be made to the above related description regarding the generation method of the initial verification platform or the generation method of the target verification platform, which are not repeated herein.

For example, as shown in FIG. 14, the storage medium 600 stores non-transitory computer readable instructions 610. For example, the non-transitory computer readable instructions 610, when executed by a computer, perform one or more steps in accordance with the initial verification platform generation method or the target verification platform generation method described above.

For example, the storage medium 600 may be applied to the electronic device 400 shown in fig. 12. For example, the storage medium 600 may be the memory 420 in the electronic device 400. For example, the relevant description of the storage medium 600 may refer to the corresponding description of the memory 420 in the electronic device 400 shown in fig. 12, which is not repeated here.

For the purposes of this disclosure, the following points are to be described:

(1) In the drawings of the embodiments of the present disclosure, only the structures related to the embodiments of the present disclosure are referred to, and other structures may refer to the general design.

(2) Features of the same and different embodiments of the disclosure may be combined with each other without conflict.

The foregoing is merely a specific embodiment of the disclosure, but the protection scope of the disclosure is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the disclosure, and it should be covered in the protection scope of the disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims

1. A method of generating an initial authentication platform, wherein the initial authentication platform comprises a plurality of authentication components including a plurality of first authentication components, each of the plurality of first authentication components including a common layer and a functional layer,

the generation method of the initial verification platform comprises the following steps:

reading a template file from a template library;

based on the template file, the common layer and the functional layer of each first verification component are respectively established to obtain a plurality of first verification components,

Wherein said functional layer of each said first authentication component inherits from said common layer,

the common layer of each first verification component comprises a common sub-component shared by the corresponding first verification component and first verification components except the corresponding first verification component in the plurality of first verification components,

the functional layer of each first verification component comprises a functional sub-component of the corresponding first verification component, and configurable parameters are arranged in the functional sub-components.

2. The method for generating an initial verification platform according to claim 1, further comprising:

the initial verification platform is generated based on inheritance relationships among the plurality of verification components.

3. The method of generating an initial verification platform according to claim 2, wherein the inheritance relationship comprises a first inheritance relationship, the plurality of verification components comprising a parent verification component having the first inheritance relationship and a child verification component that inherits properties of the parent verification component from the parent verification component based on the first inheritance relationship.

4. The method for generating an initial authentication platform as recited in claim 1, wherein each of said first authentication components further comprises a user layer,

The generation method of the initial verification platform further comprises the following steps:

the user layer is established in such a way that,

the user layer inherits from the functional layer, and a user-defined configuration part is reserved in the user layer for user-defined configuration.

5. The method for generating an initial verification platform as recited in claim 1, wherein each of said first verification components further comprises a base layer,

the base layer is established in such a way that,

the shared layer inherits from the base layer, and a corresponding base sub-component of the first verification component is arranged in the base layer.

6. The method of generating an initial verification platform as recited in claim 1, wherein the plurality of verification components further comprises a second verification component different from the first verification component,

establishing the second verification component;

the initial verification platform is generated based on inheritance relationships between the plurality of first verification components and the second verification component.

7. The method of generating an initial authentication platform as claimed in claim 1, wherein the initial authentication platform comprises a plurality of authentication modules, each of the plurality of authentication modules comprising at least one of the plurality of first authentication components,

and carrying out visualization processing on the configurable parameters in the functional sub-components of the at least one first verification component to obtain a visualization interface corresponding to each verification module.

8. A method of generating a target verification platform, comprising:

acquiring a parameter configuration table corresponding to the target verification platform;

setting an initial verification platform generated by the initial verification platform generation method according to any one of claims 1 to 7 by using the parameter configuration table to generate the target verification platform.

9. The method of generating a target verification platform according to claim 8, wherein the parameter configuration table includes target parameters corresponding to the plurality of first verification components,

setting the initial verification platform by using the parameter configuration table to generate the target verification platform, including:

and setting configurable parameters in the functional sub-components of the first verification components by using the target parameters to obtain a plurality of target first verification components of the target verification platform.

10. The method of generating a target verification platform according to claim 9, wherein the plurality of verification components further comprises a second verification component different from the first verification component,

Setting the initial verification platform by using the parameter configuration table to generate the target verification platform, and further comprising:

the target verification platform is generated based on inheritance relationships between the plurality of target first verification components and the second verification components.

11. The method of generating a target verification platform as recited in claim 8, wherein the initial verification platform comprises a plurality of verification modules, each verification module of the plurality of verification modules comprising at least one first verification component of the plurality of first verification components,

a visual interface is arranged corresponding to each verification module, the visual interface is provided with configurable parameters in the functional sub-components of the at least one first verification component in the corresponding verification module,

the obtaining a parameter configuration table corresponding to the target verification platform comprises the following steps:

acquiring parameters set by a user on the visual interface by utilizing the visual interface to obtain target parameters corresponding to the plurality of first verification components;

and obtaining the parameter configuration table based on the target parameters.

12. A generation device of an initial verification platform, wherein the initial verification platform comprises a plurality of verification components, the plurality of verification components comprise a plurality of first verification components, each first verification component in the plurality of first verification components comprises a common layer and a functional layer,

The generation device of the initial verification platform comprises:

a reading module configured to read a template file from a template library;

the building module is configured to respectively build the shared layer and the functional layer of each first verification component based on the template file so as to obtain a plurality of first verification components;

13. The generation apparatus of an initial verification platform of claim 12, further comprising:

a first generation module configured to generate the initial verification platform based on inheritance relationships between the plurality of verification components.

14. A generation apparatus of a target verification platform, comprising:

the acquisition module is configured to acquire a parameter configuration table corresponding to the target verification platform;

A second generation module configured to set an initial verification platform generated according to the generation method of any one of claims 1 to 7 using the parameter configuration table to generate the target verification platform.

15. An electronic device, comprising:

a processor;

a memory including one or more computer program modules;

wherein the one or more computer program modules are stored in the memory and configured to be executed by the processor, the one or more computer program modules being configured to implement the method of generating an initial verification platform of any one of claims 1-7 or the method of generating a target verification platform of any one of claims 8-11.

16. A storage medium storing non-transitory computer readable instructions which, when executed by a computer, implement the method of generating an initial verification platform of any one of claims 1 to 7 or the method of generating a target verification platform of any one of claims 8 to 11.