# US 12,182,020 B1 · System and method for creating a high-level parameter relational data model for memory configurability solutions > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,182,020 B1 - Document ID: US12182020B1 - Status: Granted - Kind: B1 - Application number: 18/339,290 - Filed: 2023-06-22 - Granted: 2024-12-31 - Earliest claimed: 2023-06-22 - Assignees: Cadence Design Systems, Inc. - Applicants: Cadence Design Systems, Inc. - Inventors: Joseph Bernard Bauer; Shyam Sharma; Vamsi M. Banapuram - Web page: https://patentgrep.com/patent/US12182020B1 ## CPC - G06F 12/0811: with multilevel cache hierarchies - G06N 5/022: Knowledge engineering; Knowledge acquisition - G06N 5/01: Dynamic search techniques; Heuristics; Dynamic trees; Branch-and-bound - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS ## Abstract Embodiments are directed towards a method for creating a relational memory designed for one or more key parameters in at least one memory part configurations library. The method may include identifying one or more high-level parameters (HLPs) within the at least one memory part configurations library, assigning each non-HLP parameter an HLP key, using the assigned HLP keys as a frame of reference to cross-correlate each non-HLP parameter with every other non-HLP parameter in the at least one memory part configurations library. The method may also include extracting a complete relational memory attribute set from the cross-correlated parameters in the at least one memory part configurations library, generating memory configuration metadata equivalent to the at least one memory part configurations library from the complete relational memory attribute set, and providing memory part automation from the generated memory configuration metadata. ## Claims ### Claim 1 A method for creating a relational memory configuration for one or more key parameters in at least one memory part configurations library, the method comprising: identifying one or more high-level parameters (HLPs) within the at least one memory part configurations library; assigning each non-HLP parameter an HLP key; using the assigned HLP keys as a frame of reference to cross-correlate each non-HLP parameter with every other non-HLP parameter in the at least one memory part configurations library; extracting a complete relational memory attribute set from the cross-correlated parameters in the at least one memory part configurations library; generating memory configuration metadata equivalent to the at least one memory part configurations library from the complete relational memory attribute set; and providing memory part automation from the generated memory configuration metadata. ### Claim 2 (depends on 1) The method of claim 1, wherein the one or more HLPs can also be identified from among parameters described in one or more external sources, such as memory specifications or vendor datasheets. ### Claim 3 (depends on 2) The method of claim 2, wherein the complete relational memory attribute set can also be extracted from the cross-correlated parameters in the one or more external sources, such as memory specifications or vendor datasheets. ### Claim 4 (depends on 1) The method of claim 1, wherein each identified HLP has a variable parameter value and all non-HLP parameters have a fixed parameter value, such that each fixed non-HLP parameter value can be mapped onto a unique combination of variable HLP values. ### Claim 5 (depends on 4) The method of claim 4, wherein each HLP key is defined by a unique combination of HLP values corresponding to a specific non-HLP parameter. ### Claim 6 (depends on 1) The method of claim 1, wherein the generated metadata describes the settings and HLP interdependencies of each non-HLP parameter across vendor data sheets. ### Claim 7 (depends on 1) The method of claim 1, further comprising: providing a generic memory protocol interface, wherein a memory model device under test (DUT) interface supports any memory model part in any hardware verification language (HVL). ### Claim 8 (depends on 1) The method of claim 1, further comprising: allowing for memory model creation at simulation runtime per memory part configuration. ### Claim 9 (depends on 1) The method of claim 1, further comprising: exporting compatibility coverage compliance matching and tracking to only real memory parts; and making part compatibility coverage compliance customizable to HLP boundaries. ### Claim 10 (depends on 1) The method of claim 1, further comprising: encrypting vendor, standard body, and memory model provider electronic design automation (EDA) confidential memory information. ### Claim 11 A method for creating a relational memory configuration for one or more key parameters in at least one memory part configurations library, the method comprising: identifying one or more high-level parameters (HLPs) within the at least one memory part configurations library; adding each identified HLP parameter to a set of common parameters that define a memory part, for each memory part included in the at least one memory part configurations library; extracting the complete set of parameter values from each memory part included in the at least one memory part configurations library to create a per parameter set of valid values; for each parameter value within each memory part: capture the set of identified HLP values associated with the parameter; and link the captured set of identified HLP values associated with the parameter back to the parameter itself to create a table of HLP dependencies; interconnecting the per parameter set of valid values with the table of HLP dependencies to create a relational data model of per parameter value HLP dependencies; generating memory configuration metadata equivalent to the at least one memory part configurations library from the complete relational memory attribute set; and providing memory part automation from the generated memory configuration metadata. ### Claim 12 (depends on 11) The method of claim 11, wherein the one or more HLPs can also be identified from among parameters described in one or more external sources, such as memory specifications or vendor datasheets. ### Claim 13 (depends on 12) The method of claim 12, wherein the complete relational memory attribute set can also be extracted from the cross-correlated parameters in the one or more external sources, such as memory specifications or vendor datasheets. ### Claim 14 (depends on 11) The method of claim 11, wherein each identified HLP has a variable parameter value and all other parameters have a fixed parameter value, such that each fixed parameter value can be mapped onto a unique combination of HLP values. ### Claim 15 (depends on 11) The method of claim 11, wherein parameter values that share a common HLP link define a legal/real memory part combination. ### Claim 16 (depends on 11) The method of claim 11, wherein the relational data model of per parameter value HLP dependencies is bi-directional, such that per parameter value the set of HLP dependencies are linked and inversely per HLP table the set of parameters are linked. ### Claim 17 (depends on 11) The method of claim 11, further comprising: providing a generic memory protocol interface, wherein a memory model DUT interface supports any memory model part in any HVL. ### Claim 18 (depends on 11) The method of claim 11, further comprising: providing memory model creation at simulation runtime per memory part configuration. ### Claim 19 (depends on 11) The method of claim 11, further comprising: exporting compatibility coverage compliance matching and tracking to only real memory parts; and making part compatibility coverage compliance customizable to HLP boundaries. ### Claim 20 (depends on 11) The method of claim 11, further comprising: encrypting vendor, standard body, and memory model provider EDA confidential memory information.