Method and apparatus for production control of memory sticks

Abstract

The present disclosure relates to a memory stick production control method and device, and relates to the technical field of semiconductor production and manufacturing. The method comprises: in response to a production event trigger instruction of a to-be-processed memory stick, determining a target production link of the to-be-processed memory stick; determining a target processing rule matched with the target production link, the target processing rule comprising a plurality of first-level rule groups, each first-level rule group corresponding to at least one second-level sub-rule; according to a rule group entering operation of the first-level rule group, acquiring the second-level sub-rule, and determining a matching result of the second-level sub-rule; according to the matching result of the second-level sub-rule, determining a rule matching result of the target processing rule; and based on the rule matching result, performing a production operation on the to-be-processed memory stick to obtain a processed memory stick. The present disclosure triggers the matching and execution of a plurality of independent rule groups through a memory stick production event, can support modular and multi-stage composite decision-making, and effectively realizes product quality control.

Description

Technical Field

[0001] This disclosure relates to the field of semiconductor manufacturing technology, and more specifically, to a method and apparatus for controlling the production of memory modules. Background Technology

[0002] With the rapid development of big data, artificial intelligence, and high-performance computing, Dynamic Random Access Memory (DRAM) modules, as core storage components of electronic systems, are facing increasingly stringent industry requirements regarding capacity density, data bandwidth, operational stability, and manufacturing costs. DRAM production is a typical long-process precision manufacturing process, which can include multiple stages such as bare wafer preparation, front-end wafer fabrication, wafer probe testing, chip dicing and sorting, chip packaging, surface mount technology (SMT) assembly, and finished product performance testing.

[0003] Due to the precision and complexity of the memory module manufacturing process, an increasing number of intelligent manufacturing production control technologies have been introduced into it. The automated control of intelligent manufacturing processes refers to the use of automation technology, artificial intelligence, and other means to achieve intelligent, automated, and efficient production processes. For example, in the memory module manufacturing process, the Manufacturing Execution System (MES) can achieve automated control of the production process through a rule engine (Dispose Rule).

[0004] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] The purpose of this disclosure is to provide a production control method, a production control device, an electronic device, a computer-readable storage medium, and a computer program product for memory modules, thereby overcoming, to at least a certain extent, the problem that the related production control process adopts a sequential search mechanism that ends upon the first match. In the face of complex and ever-changing inventory control scenarios, it cannot support the parallel triggering of rules or the combined effect of multiple rules, which leads to business process interruption, control failure, or omission of key alarms, thereby causing product quality risks.

[0006] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0007] According to a first aspect of this disclosure, a method for controlling the production of a memory module is provided, comprising: responding to a production event triggering instruction for a memory module to be processed, determining a target production stage of the memory module to be processed; determining a target processing rule matching the target production stage, the target processing rule comprising a plurality of first-level rule groups, each first-level rule group corresponding to at least one second-level sub-rule, the rule group association relationship of the first-level rule groups comprising at least one of parallel execution relationship and sequential execution relationship; executing a rule group entry operation of the first-level rule groups based on the rule group association relationship, and obtaining a second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation; determining a matching result for each second-level sub-rule based on the production requirements of the target production stage; determining a rule matching result of the target processing rule based on the rule group association relationship and the matching result of the second-level sub-rule; and performing a production operation on the memory module to be processed based on the rule matching result to obtain a processed memory module.

[0008] In one exemplary embodiment of this disclosure, determining the target processing rule that matches the target production stage includes: starting a rule execution engine, the rule execution engine being used to invoke a pre-configured set of candidate processing rules; and determining the target processing rule from the set of candidate processing rules according to the target production stage.

[0009] In one exemplary embodiment of this disclosure, the candidate processing rule set is constructed through the following steps: obtaining production demand information of the memory module to be processed, the production demand information including at least one production stage; determining the production target corresponding to each production stage based on the production demand information; performing rule configuration operations on each production stage based on the production target to obtain candidate processing rules corresponding to each production stage, the candidate processing rules including multiple first-level candidate rule groups, the candidate rule group association relationship between the multiple first-level candidate rule groups, and second-level candidate sub-rules corresponding to the first-level candidate rule groups; and constructing the candidate processing rule set based on the multiple candidate processing rules.

[0010] In one exemplary embodiment of this disclosure, the step of configuring rules for each production stage based on the production target to obtain candidate processing rules corresponding to each production stage includes: determining the rule group priorities corresponding to multiple first-level candidate rule groups and the sub-rule priorities corresponding to multiple second-level candidate sub-rules according to the production target; sorting the multiple first-level candidate rule groups according to the rule group priorities to obtain sorted first-level candidate rule groups; sorting the multiple second-level candidate sub-rules according to the sub-rule priorities to obtain sorted second-level candidate sub-rules; and obtaining the candidate processing rule based on the sorted first-level candidate rule groups and the sorted second-level candidate sub-rules.

[0011] In one exemplary embodiment of this disclosure, the step of executing the rule group entry operation of the first-level rule group based on the rule group association relationship, and obtaining the second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation, includes: in response to the rule group association relationship being the parallel execution relationship, executing the rule group entry operation of the first-level rule group in parallel; and in the parallel execution of multiple rule group entry operations, obtaining the second-level sub-rule corresponding to each first-level rule group in parallel.

[0012] In one exemplary embodiment of this disclosure, the step of obtaining the second-level sub-rule corresponding to each first-level rule group in parallel during the parallel execution of multiple rule group entry operations includes: generating a corresponding first rule group entry event in response to the rule group entry operation of each first-level rule group; and obtaining the second-level sub-rule corresponding to each first-level rule group in parallel according to each first rule group entry event.

[0013] In one exemplary embodiment of this disclosure, the first-level rule group includes a preceding first-level rule group and a current first-level rule group. The step of executing a rule group entry operation of the first-level rule group based on the rule group association relationship, and obtaining a second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation, includes: in response to the rule group association relationship being the sequential execution relationship, obtaining a preceding second-level sub-rule corresponding to the preceding first-level rule group before executing the rule group entry operation of the current first-level rule group; and obtaining a current second-level sub-rule corresponding to the current first-level rule group based on the execution result of the preceding second-level sub-rule.

[0014] In one exemplary embodiment of this disclosure, obtaining the current second-level sub-rule corresponding to the current first-level rule group based on the execution result of the preceding second-level sub-rule includes: generating a second rule group entry event corresponding to the current first-level rule group based on the execution result of the preceding second-level sub-rule; triggering a rule execution operation of the current first-level rule group based on the second rule group entry event, and obtaining the current second-level sub-rule.

[0015] In one exemplary embodiment of this disclosure, determining the rule matching result of the target processing rule based on the rule group association relationship and the matching result of the second-level sub-rules includes: determining a second-level target sub-rule from the second-level sub-rules based on the production target of the target production stage; performing an action execution operation based on the second-level target sub-rules to obtain an action execution result; and generating the rule matching result based on the rule group association relationship and the action execution results of multiple second-level target sub-rules.

[0016] In one exemplary embodiment of this disclosure, the step of performing a production operation on the memory module to be processed based on the rule matching result to obtain a processed memory module includes: obtaining a plurality of second-level target sub-rules included in the rule matching result, determining the rule execution action corresponding to each second-level target sub-rule; pushing the plurality of rule execution actions to an action execution queue; and performing a memory module production operation according to the execution result of the action execution queue to obtain the processed memory module.

[0017] In one exemplary embodiment of this disclosure, the method further includes: generating a rule group entry event log corresponding to the rule group entry event of the first-level rule group according to the rule execution operation of the target processing rule; generating a rule hit event log corresponding to the sub-rule hit event according to the acquisition operation of the second-level target sub-rule; generating an action execution event log corresponding to the action execution event according to the rule execution result of the second-level target sub-rule; and generating a memory module production event log of the processed memory module according to the rule group entry event log, the rule hit event log, and the action execution event log.

[0018] According to a second aspect of this disclosure, a production control device for memory modules is provided, comprising: a production stage determination module, configured to determine a target production stage of the memory module to be processed in response to a production event triggering instruction; a target rule determination module, configured to determine a target processing rule matching the target production stage, the target processing rule including a plurality of first-level rule groups, each first-level rule group corresponding to at least one second-level sub-rule, the rule group association relationship of the first-level rule groups including at least one of parallel execution relationship and sequential execution relationship; a sub-rule acquisition module, configured to execute a rule group entry operation of the first-level rule group based on the rule group association relationship, and acquire a second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation; a sub-rule matching module, configured to determine a matching result for each second-level sub-rule based on the production requirements of the target production stage; a matching result determination module, configured to determine a rule matching result of the target processing rule based on the rule group association relationship and the matching result of the second-level sub-rule; and a production processing module, configured to perform a production operation on the memory module to be processed based on the rule matching result to obtain a processed memory module.

[0019] In one exemplary embodiment of this disclosure, the target rule determination module includes a target rule determination unit, configured to: start a rule execution engine, wherein the rule execution engine is configured to call a pre-configured set of candidate processing rules; and determine the target processing rule from the set of candidate processing rules according to the target production stage.

[0020] In one exemplary embodiment of this disclosure, the target rule determination module includes a candidate rule construction unit, configured to: obtain production demand information of the memory module to be processed, the production demand information including at least one production stage; determine the production target corresponding to each production stage based on the production demand information; perform rule configuration operations on each production stage based on the production target to obtain candidate processing rules corresponding to each production stage, the candidate processing rules including multiple first-level candidate rule groups, the candidate rule group association relationship between the multiple first-level candidate rule groups, and second-level candidate sub-rules corresponding to the first-level candidate rule groups; and construct the candidate processing rule set based on the multiple candidate processing rules.

[0021] In one exemplary embodiment of this disclosure, the candidate rule construction unit includes a candidate rule construction subunit, configured to: determine rule group priorities corresponding to multiple first-level candidate rule groups and sub-rule priorities corresponding to multiple second-level candidate sub-rules based on the production target; sort the multiple first-level candidate rule groups according to the rule group priorities to obtain sorted first-level candidate rule groups; sort the multiple second-level candidate sub-rules according to the sub-rule priorities to obtain sorted second-level candidate sub-rules; and obtain the candidate processing rule based on the sorted first-level candidate rule groups and the sorted second-level candidate sub-rules.

[0022] In one exemplary embodiment of this disclosure, the sub-rule acquisition module includes a first sub-rule acquisition unit, configured to: in response to the rule group association relationship being the parallel execution relationship, execute the rule group entry operation of the first-level rule group in parallel; and during the parallel execution of multiple rule group entry operations, acquire the second-level sub-rule corresponding to each first-level rule group in parallel.

[0023] In one exemplary embodiment of this disclosure, the first sub-rule acquisition unit includes a first sub-rule acquisition sub-unit, configured to: generate a corresponding first rule group entry event in response to the rule group entry operation of each first-level rule group; and acquire, in parallel, the second-level sub-rules corresponding to each first-level rule group based on each first rule group entry event.

[0024] In one exemplary embodiment of this disclosure, the first-level rule group includes a preceding first-level rule group and a current first-level rule group. The sub-rule acquisition module includes a second sub-rule acquisition unit, configured to: in response to the rule group association relationship being the sequential execution relationship, before executing the rule group entry operation of the current first-level rule group, acquire the preceding second-level sub-rule corresponding to the preceding first-level rule group; and acquire the current second-level sub-rule corresponding to the current first-level rule group based on the execution result of the preceding second-level sub-rule.

[0025] In one exemplary embodiment of this disclosure, the second sub-rule acquisition unit includes a second sub-rule acquisition sub-unit, configured to: generate a second rule group entry event corresponding to the current first-level rule group based on the execution result of the preceding second-level sub-rule; and trigger a rule execution operation of the current first-level rule group based on the second rule group entry event to acquire the current second-level sub-rule.

[0026] In one exemplary embodiment of this disclosure, the matching result determination module includes a matching result determination unit, configured to: determine a second-level target sub-rule from the second-level sub-rules based on the production target of the target production process; perform an action execution operation based on the second-level target sub-rule to obtain an action execution result; and generate the rule matching result according to the rule group association relationship and the action execution results of multiple second-level target sub-rules.

[0027] In one exemplary embodiment of this disclosure, the production processing module includes a production processing unit, configured to: obtain multiple second-level target sub-rules included in the rule matching result, determine the rule execution action corresponding to each second-level target sub-rule; push the multiple rule execution actions to the action execution queue; and perform memory module production operation according to the execution result of the action execution queue to obtain the processed memory module.

[0028] In one exemplary embodiment of this disclosure, the memory module production control device further includes a production log generation module, configured to: generate a rule group entry event log corresponding to the rule group entry event of the first-level rule group according to the rule execution operation of the target processing rule; generate a rule hit event log corresponding to the sub-rule hit event according to the acquisition operation of the second-level target sub-rule; generate an action execution event log corresponding to the action execution event according to the rule execution result of the second-level target sub-rule; and generate a memory module production event log for the processed memory module according to the rule group entry event log, the rule hit event log, and the action execution event log.

[0029] According to a third aspect of this disclosure, an electronic device is provided, comprising: a processor; and a memory storing computer-readable instructions, which, when executed by the processor, implement the production control method for a memory module according to any one of the preceding claims.

[0030] According to a fourth aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the production control method for a memory module according to any one of the preceding claims.

[0031] According to a fifth aspect of this disclosure, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the memory module production control method described in any one of the preceding claims.

[0032] The technical solution provided in this disclosure may include the following beneficial effects: The memory module production control method in the exemplary embodiments of this disclosure, on the one hand, triggers the matching and execution of multiple independent rule groups through memory module production events, which can support modular and multi-stage composite decision-making and avoid problems such as business process interruption, control failure, or omission of key alarms. On the other hand, through a hierarchical rule execution architecture, after matching multiple rule groups, production execution operations are performed based on the hit sub-rules of each rule group, which can adapt to complex business scenarios involving multiple parallel actions and effectively achieve product quality control.

[0033] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0034] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings: Figure 1 This diagram illustrates the execution flow chart corresponding to the production control mechanism in the relevant scheme that uses sequential search and ends upon the first match; Figure 2 A flowchart illustrating a production control method for a memory module according to an exemplary embodiment of the present disclosure is shown schematically. Figure 3 The diagram illustrates a production stage corresponding to a memory module manufacturing process according to an exemplary embodiment of the present disclosure. Figure 4 This illustration schematically shows a hierarchical rule architecture pattern design diagram adopted in an exemplary embodiment of the present disclosure; Figure 5 The illustration shows a schematic diagram of a production rule constructed based on a two-layer grouped rule architecture according to an exemplary embodiment of the present disclosure; Figure 6 This illustration schematically shows the execution flowchart corresponding to the production control mechanism employing a hierarchical rule architecture pattern in an exemplary embodiment of this disclosure; Figure 7 This illustration schematically shows the operation page effect corresponding to the production control mechanism using a hierarchical rule architecture pattern in an exemplary embodiment of this disclosure. Figure 1 ; Figure 8 This illustration schematically shows the operation page effect corresponding to the production control mechanism using a hierarchical rule architecture pattern in an exemplary embodiment of this disclosure. Figure 2 ; Figure 9A block diagram illustrating a production control apparatus for a memory module according to an exemplary embodiment of the present disclosure is shown schematically. Figure 10 A schematic diagram of a computer-readable storage medium according to an exemplary embodiment of the present disclosure is shown. Figure 11 A block diagram of an electronic device according to an exemplary embodiment of the present disclosure is shown schematically. Detailed Implementation

[0035] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0036] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced without one or more of the specific details described, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known structures, methods, apparatuses, implementations, materials, or operations are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0037] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, or in one or more software-hardened modules, or in different network and / or processor devices and / or microcontroller devices.

[0038] According to embodiments of this disclosure, a method for controlling the production of memory modules, a device for controlling the production of memory modules, a computer-readable storage medium, an electronic device, and a computer program product are proposed.

[0039] The principles and spirit of this disclosure will be explained in detail below with reference to several representative embodiments.

[0040] In related semiconductor manufacturing process automation control solutions, taking the memory module production process as an example, the execution engine can achieve special inventory control purposes by formulating rules, such as holding lots or changing the production steps of goods. However, the control process of the above-mentioned execution engine has the problem of rigid architecture, specifically its "sequential search, end when the first match" mechanism. When facing the high-frequency and ever-changing complex inventory control scenarios in the semiconductor back-end process, this mechanism cannot support the parallel triggering of rules or the combined effect of multiple rules, resulting in business process interruption, control failure or omission of key alarms, and thus causing product quality risks.

[0041] refer to Figure 1 , Figure 1 The diagram illustrates the execution flow chart corresponding to the production control mechanism in the relevant scheme that employs sequential search and ends upon the first match. Figure 1 As can be seen, for product batch Lot A, the receiving station has pre-configured multiple execution rules, including rule 1, rule 2, ..., rule N. However, using the aforementioned production control mechanism, the triggering rules are matched from top to bottom, and the product leaves the station when the first rule is matched. Figure 1 In the process, the first matching rule is rule 2. At this point, the current site's production process will be skipped. Even if there are subsequent rules that meet the matching conditions of Lot A, such as rule 3 and rule 4, these rules cannot be triggered and executed.

[0042] Taking the memory module manufacturing process as an example, the requirements for the production process of Dual-Inline-Memory-Modules (DIMMs) are as follows: the automated optical inspection station performs three automated special controls on product A simultaneously, including: 1) detaining the goods for Zhang San to handle; 2) changing the goods production step to the system speed detection step; 3) changing the product grade to Level 1. In actual business scenarios, the first three rules need to be triggered simultaneously to achieve the purpose of controlling the goods. However, the current execution architecture only supports triggering the first rule, which may lead to control failure and thus cause quality problems.

[0043] Based on this, in this example embodiment, a method for controlling the production of memory modules is first provided. The method for controlling the production of memory modules disclosed herein can be implemented using a server or using a terminal device. The terminal described in this disclosure may include mobile terminals such as mobile phones, tablets, laptops, handheld computers, and personal digital assistants (PDAs), as well as fixed terminals such as desktop computers. Figure 2 A schematic diagram illustrating a production control method flow for a memory module according to some embodiments of the present disclosure is provided. (Reference) Figure 2 The production control method for this memory module may include the following steps: Step S210: In response to the production event trigger instruction of the memory module to be processed, determine the target production stage of the memory module to be processed; Step S220: Determine the target processing rules that match the target production process. The target processing rules include multiple first-level rule groups. Each first-level rule group corresponds to at least one second-level sub-rule. The rule group association relationship of the first-level rule groups includes at least one of parallel execution relationship and sequential execution relationship. Step S230: Execute the rule group entry operation of the first-level rule group based on the rule group association relationship, and obtain the second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation; Step S240: Based on the production requirements of the target production process, determine the matching result of each second-level sub-rule; Step S250: Determine the rule matching result of the target processing rule based on the rule group association relationship and the matching result of the second-level sub-rules; Step S260: Based on the rule matching results, perform production operations on the memory module to be processed to obtain the processed memory module.

[0044] According to the memory module production control method in this example implementation, on the one hand, by triggering the matching and execution of multiple independent rule groups through memory module production events, modular and multi-stage composite decision-making can be supported, avoiding problems such as business process interruption, control failure, or omission of key alarms. On the other hand, through a hierarchical rule execution architecture, after matching multiple rule groups, production execution operations are performed based on the hit sub-rules of each rule group, which can adapt to complex business scenarios involving multiple parallel actions and effectively achieve product quality control.

[0045] The production control method for memory modules in this example embodiment will be further explained below.

[0046] For step S210, in response to the production event trigger instruction for the memory module to be processed, the target production stage of the memory module to be processed is determined. The memory module to be processed can be a memory module awaiting further processing during the chip manufacturing process. The production event trigger instruction can be a control instruction that triggers the execution of a certain production event. Taking the appearance inspection production stage of the memory module as an example, the corresponding production event trigger instruction can be generated based on the production step of performing appearance inspection on the memory module. The target production stage can be the production stage corresponding to the current processing flow of the memory module to be processed.

[0047] Upon receiving a production event trigger instruction for the memory module to be processed, the target production stage corresponding to the memory module is determined based on the instruction. There can be one or more target production stages. The processing rules corresponding to the target production stage are then obtained, and the memory module to be processed is subjected to processing operations.

[0048] In one exemplary embodiment of this disclosure, step S220, determining the target processing rule that matches the target production stage, includes: starting a rule execution engine, which is used to call a pre-configured set of candidate processing rules; and determining the target processing rule from the set of candidate processing rules according to the target production stage.

[0049] Upon receiving a production event trigger command, the rule execution engine is activated. The rule execution engine, or rule engine for short, is a component that allows for individual configuration of business decision logic. It automatically matches input content with predefined rules and executes corresponding actions, enabling configurable, hot-updating, and traceable decision-making for business rules. The rule execution engine can invoke a pre-configured set of candidate processing rules. This set can be a group of candidate processing rules defined and stored in advance through a configuration interface or configuration file. This set can contain multiple candidate processing rules, each corresponding to a different production stage or different production scenario. The specific content of the candidate processing rule set can be pre-set and updated by administrators according to actual production needs. Candidate processing rules can be configured and updated based on the business needs and production goals of the memory modules to be processed at different production stages, and are used to execute actual production processing operations.

[0050] The relevant information of the identified memory modules to be processed is used as input to the rule execution engine. This input may include, but is not limited to, basic information about the memory modules, production information (such as the target production stage), and the operation target indicated in the production event triggering instruction. The rule execution engine can obtain the identification information of the target production stage, which may be the name, number, or other information uniquely identifying the production stage. Using this identification information as the basis for querying, the rule execution engine performs a matching search within the candidate processing rule set. Each candidate processing rule in the set can be pre-configured with an associated production stage identifier. When the production stage identifier associated with a candidate processing rule matches the identifier of the target production stage, that processing rule is determined as the target processing rule.

[0051] The rule execution engine executes the production and processing operations on the memory modules to be processed by invoking the target processing rules that match the target production stage. The target processing rules can be the processing rules used to process the memory modules to be processed. This embodiment can automatically match and determine the target processing rule from a pre-configured set of candidate processing rules based on the target production stage, improving the automation level and processing efficiency of rule matching in the production process.

[0052] In one exemplary embodiment of this disclosure, the candidate processing rule set is constructed through the following steps: obtaining production demand information of the memory module to be processed, the production demand information including at least one production stage; determining the production target corresponding to each production stage based on the production demand information; performing rule configuration operations on each production stage based on the production target to obtain candidate processing rules corresponding to each production stage, the candidate processing rules including multiple first-level candidate rule groups, the candidate rule group association relationship between multiple first-level candidate rule groups, and second-level candidate sub-rules corresponding to the first-level candidate rule groups; and constructing a candidate processing rule set based on the multiple candidate processing rules.

[0053] This implementation provides a scheme for constructing a candidate processing rule set, obtaining production demand information for the memory modules to be processed. This production demand information can be information associated with the production task of the current batch or model of memory modules, and its specific content may include order information, product specification information, or production work orders, etc. The production demand information includes at least one production stage, as referenced... Figure 3 , Figure 3 The illustration shows a schematic diagram of the production stages corresponding to an exemplary embodiment of the memory module manufacturing process of this disclosure. For memory module production, the production stages may include, but are not limited to, surface mounting, cutting and labeling (such as label dispensing and placement, LDP), system level testing (SLT), station automated optical inspection (SAOI), outgoing quality control (OQC), and packaging and shipping. Furthermore, different memory module models or batches may correspond to different combinations of production stages.

[0054] Based on production demand information, the production objectives for each production stage are determined. Production objectives refer to specific business metrics or requirements that need to be achieved in that stage. For example, for the testing stage, the production objective might be to ensure that the appearance of the memory modules to be processed meets process standards, such as free of scratches, dirt, and oxidation on the connectors, which relates to conductivity and signal integrity, as well as component integrity. Additionally, the production objective for the testing stage might include acceptable downgrades, allowing a certain percentage of minor appearance defects that do not affect functionality and reliability; these products can be downgraded rather than scrapped. For the quality sampling inspection stage, the production objective might be to guarantee the quality level of the entire batch of products with statistical confidence levels, employing strict sampling standards, parameter settings, and precise testing indicators.

[0055] After determining the production objectives for each production stage, rule configuration operations are performed on each production stage based on these objectives. These rule configuration operations generate corresponding candidate processing rules for each production stage. The processing rule logic of this disclosure adopts a hierarchical organizational structure. For example, candidate processing rules may include multiple first-level candidate rule groups and second-level candidate sub-rules corresponding to each first-level candidate rule group.

[0056] The first-level candidate rule groups are used to manage different categories of processing logic within the target production stage. For example, candidate processing rules for a testing stage may include multiple first-level candidate rule groups such as quality judgment groups, exception handling groups, and data recording groups. Furthermore, since different production stages have different production goals, the rule group relationships between multiple first-level candidate rule groups may be parallel execution relationships, sequential execution relationships, or a combination of both. The rule group relationships can be set according to the production goals of different production stages, and the specific execution order between multiple first-level candidate rule groups will be determined based on the rule group relationships.

[0057] Each first-level candidate rule group contains at least one second-level candidate sub-rule. The second-level candidate sub-rule defines the specific triggering conditions and corresponding execution actions of the candidate rule. For example, a quality judgment group may contain second-level candidate sub-rules such as good product sub-rules and defective product sub-rules. Each second-level candidate sub-rule is configured with corresponding judgment conditions and processing actions. The specific triggering conditions and corresponding execution actions of the second-level candidate sub-rules can be determined according to the production objectives of different production stages, and this disclosure does not impose any special limitations on them.

[0058] refer to Figure 4 , Figure 4 The diagram illustrates a hierarchical rule architecture pattern design used in an exemplary embodiment of this disclosure. Figure 4 The diagram shows a rule architecture diagram of candidate processing rules, taking a two-layer hierarchical rule as an example. Figure 4 It includes first-level candidate rule groups, such as rule A, rule B, and rule C; and second-level sub-rules corresponding to each first-level candidate rule group, such as rule A may include rule A1, rule A2, and rule A3; rule B may include rule B1, rule B2, and rule B3; and rule C may include rule C1, rule C2, and rule C3.

[0059] It will be readily understood by those skilled in the art that the number of rule levels, the relationship between rule groups, and the number of sub-rules contained in each rule group can be configured according to the actual production needs of the memory modules. For example, the number of rule levels can be configured to three or four levels, and the number of sub-rules can be arbitrary; this disclosure does not impose any special limitations on this. Furthermore, during the production process of memory modules, if candidate processing rules are added or changed, these rules can be configured independently by relevant personnel, such as adding, deleting, or changing candidate processing rules, to adapt to changes in the production process.

[0060] After configuring rules for all production stages, the candidate processing rules for each stage are aggregated to form a candidate processing rule set. This set contains all processing rules related to the entire production process of the memory module to be processed. The candidate processing rule set can be stored in a rule configuration library or in memory for subsequent use by the rule execution engine. When an event is triggered in a production stage during actual production, the rule execution engine can match the target processing rule corresponding to the target production stage from this set and execute it. Through these steps, rules are configured for each production stage based on production demand information, and a candidate processing rule set is constructed. The hierarchical organizational structure of the candidate processing rules resolves issues such as single-layer rule logic conflicts and coverage blind spots, enabling multi-dimensional production control of the memory module and improving the decision-making dimensions and flexibility of the rule engine.

[0061] In one exemplary embodiment of this disclosure, rule configuration operations are performed on each production stage based on production goals to obtain candidate processing rules corresponding to each production stage. This includes: determining the priority of rule groups corresponding to multiple first-level candidate rule groups and the priority of sub-rules corresponding to multiple second-level candidate sub-rules based on production goals; sorting the multiple first-level candidate rule groups according to the rule group priorities to obtain sorted first-level candidate rule groups; sorting the multiple second-level candidate sub-rules according to the sub-rule priorities to obtain sorted second-level candidate sub-rules; and obtaining candidate processing rules based on the sorted first-level candidate rule groups and the sorted second-level candidate sub-rules.

[0062] When configuring rules for the production process based on production goals, it is necessary to determine the execution order of each rule group and sub-rules to ensure that the subsequent rule execution engine can match and execute rules according to reasonable priorities. For example, if there are interdependent inputs and outputs between rule groups, the priority of each of the multiple first-level candidate rule groups can be determined according to the production goals; in addition, the priority of each second-level candidate sub-rule within each first-level candidate rule group also needs to be determined.

[0063] Rule group priority is used to characterize the importance or execution order of different first-level candidate rule groups in the processing flow when there is a dependency between their inputs and outputs. Sub-rule priority is used to characterize the matching order of different second-level candidate sub-rules within the same rule group. The determination of rule group priority and sub-rule priority can be set according to the specific requirements of the memory module production goals. For example, if the production goals specify that the handling of certain abnormal situations should take precedence over regular judgments, the rule group priority of the abnormal handling group can be set higher than that of the quality judgment group. Similarly, within the same rule group, if the condition corresponding to a certain sub-rule is more critical or needs to be matched first, a higher sub-rule priority can be set for it.

[0064] After determining the priority of rule groups and sub-rules, the priority can be represented numerically, with smaller numbers indicating higher priority; it can also be represented by a level identifier; or the priorities of each rule group and sub-rule can be arranged in order of priority, and the corresponding rule group or sub-rule can be called according to the sorting order of the rules in the candidate processing rule set. Furthermore, the priority of rule groups corresponding to different first-level candidate rule groups can be the same as the priority of sub-rules corresponding to second-level candidate sub-rules.

[0065] For example, the first-level candidate rule groups are arranged in descending order of their rule group priority. The sorted first-level candidate rule groups form an ordered list, which defines the order in which the rule execution engine traverses each rule group when processing this production stage. Similarly, multiple second-level candidate sub-rules within each first-level candidate rule group can be sorted according to their sub-rule priorities, resulting in sorted second-level candidate sub-rules. For each first-level candidate rule group, its multiple second-level candidate sub-rules are arranged in descending order of their sub-rule priority. The sorted second-level candidate sub-rules form an ordered list, which defines the order in which the rule execution engine traverses each sub-rule after entering the rule group.

[0066] Furthermore, the first-level candidate rule groups and their corresponding multiple second-level candidate sub-rules can be stored using key-value pairs, association tables, or nested data structures. For example, a table mapping rule groups to sub-rules can be created, recording the identifier of each first-level candidate rule group and a list of identifiers for its corresponding second-level sub-rules.

[0067] refer to Figure 5 , Figure 5 The illustration shows a schematic diagram of a production rule constructed based on a two-layer grouped rule architecture according to an exemplary embodiment of the present disclosure. Figure 5 The production rules in the document refer to the simultaneous automated control processing of product A at the appearance inspection station. Figure 5 As can be seen, Rule A detains products, and its sub-rules define the detainee (Owner) according to product type. Sub-rule 1 of Rule A detains Product A for User 1; sub-rule 2 detains Product B for User 2; and sub-rule 3 detains Product C for User 3. Rule B controls changes to processing steps, and its sub-rules define different processing steps according to product type. Sub-rule 1 of Rule B changes the processing step for Product B to equipment appearance inspection; sub-rule 2 changes the processing step for Product A to system speed inspection; sub-rule 3 changes the processing step for Product C to the maintenance process; and sub-rule 4 changes the processing step for Product D to the reprogramming process. Rule C controls changes to product attributes, and its sub-rules change label parameters according to product type. Sub-rule 1 of Rule C changes the level of Product A to Level 1; sub-rule 2 changes the level of Product B to Level 2; sub-rule 3 changes the shipping label of Product C to Label 1; and sub-rule 4 changes the shipping label of Product D to Label 2.

[0068] Figure 5 The diagram illustrates a rule architecture where the first-level rule groups are executed in parallel. These first-level rule groups consist of rules A, B, and C. The second-level sub-rules include the sub-rules contained within each rule group. Through these steps, a two-layer ordered structure is constructed, ensuring that the rule execution engine can match and execute rules according to a preset priority order during subsequent calls. This avoids the problem of the first rule group being matched, preventing subsequent rules from being matched and executed when multiple rule groups exist.

[0069] It is readily understood by those skilled in the art that for multiple first-level rule groups that can be executed in parallel, there is no need to determine the priority of the first-level rule groups. During the rule matching process, the first-level rule groups can be executed in parallel, thereby improving the efficiency of rule operation.

[0070] In one exemplary embodiment of this disclosure, step S230 involves executing a rule group entry operation for a first-level rule group based on the rule group association relationship, and obtaining a second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation. This includes: in response to the rule group association relationship being a parallel execution relationship, executing the rule group entry operation for the first-level rule group in parallel; and obtaining the second-level sub-rule corresponding to each first-level rule group in parallel during the parallel execution of multiple rule group entry operations.

[0071] During rule matching, the rule group association relationship between multiple first-level rule groups can be determined first. This association relationship describes whether there is a dependency between the inputs and outputs of multiple first-level rule groups. The rule group association relationship can include at least one of parallel execution relationship and sequential execution relationship. The parallel execution relationship indicates that multiple first-level rule groups can be executed in parallel, and the rule matching results of different first-level rule groups do not have a dependency relationship.

[0072] Sequential execution relationships indicate that the rule matching operations of some first-level rule groups require the matching results of other first-level rule groups for determination; that is, there is a sequential order of execution among multiple first-level rule groups. When the rule group association relationship is sequential, the second-level sub-rule retrieval operation corresponding to the current first-level rule group is completed before the second-level sub-rule retrieval operation corresponding to the next first-level rule group is executed. Through these steps, the execution method of rule matching operations for multiple first-level rule groups can be determined based on the pre-defined rule group association relationship. This allows for multi-dimensional management of memory, improving rule matching efficiency and accuracy.

[0073] When the rule group relationship is a parallel execution relationship, it is assumed that multiple first-level rule groups matching the target production process can be executed in parallel. In this case, rule group entry operations for multiple first-level rule groups can be executed concurrently. For example, rule group entry operations can be executed by retrieving the rule group identifiers corresponding to each first-level rule group in the target processing rules. When multiple first-level rule group identifiers are obtained, a list of sub-rule identifiers for the corresponding second-level sub-rules can be queried based on each rule group identifier. The specific content of the corresponding second-level sub-rules, including the triggering conditions and associated actions of each sub-rule, can then be obtained from this list of sub-rule identifiers.

[0074] Continue to refer to Figure 4If the rule group associations between multiple first-level rule groups are parallel execution relationships, then the contents of three rule groups (rule A, rule B, and rule C) can be executed in parallel. When entering rule A, rule B, and rule C respectively, the corresponding sub-rules of the above three rule groups can be retrieved in parallel, thereby performing rule matching operations. The operation of retrieving second-level sub-rules based on the rule group identifier of the first-level rule group is executed in parallel, which can improve the execution efficiency of rule matching.

[0075] In one exemplary embodiment of this disclosure, the second-level sub-rules corresponding to each first-level rule group are obtained in parallel according to the rule group entry operation of the first-level rule group, including: generating a corresponding first rule group entry event in response to the rule group entry operation of each first-level rule group; and obtaining the second-level sub-rules corresponding to each first-level rule group in parallel according to the first rule group entry event.

[0076] During the operation of the rule execution engine, when a rule group entry operation is executed for a first-level rule group, the corresponding second-level sub-rules are retrieved based on the correspondence between first-level rule groups and second-level sub-rules. A rule group entry operation is triggered when the rule execution engine processes the current first-level rule group and begins evaluating the sub-rules within that group. In response to this entry operation, the engine searches for the second-level sub-rules associated with the current first-level rule group's identifier within the rule group association relationship, using that identifier as the query basis.

[0077] In response to rule group entry operations from multiple first-level rule groups, a corresponding first-level rule group entry event is generated. This first-level rule group entry event is an event message used to trigger the parallel acquisition of second-level sub-rules from multiple first-level rule groups. This event carries relevant information about the multiple first-level rule groups to be entered. For example, the first-level rule group entry event can carry information such as a list of rule group identifiers for each first-level rule group to clearly indicate all rule groups involved in this parallel entry operation.

[0078] In the processing flow of the rule execution engine, when the engine needs to enter multiple first-level rule groups with parallel execution relationships, it can generate a first rule group entry event corresponding to the rule group entry operation. Parallel execution means that there is no sequential dependency between multiple first-level rule groups; the rule execution engine can enter these rule groups simultaneously and retrieve their respective second-level sub-rules for subsequent processing. For example, when the rule groups are associated with a parallel execution relationship, upon detecting that the parallel entry condition is met, a first rule group entry event is created and distributed to the corresponding processing module or thread.

[0079] Then, based on the entry event of the first rule group, the second-level sub-rules corresponding to each first-level rule group are retrieved in parallel. For example, the information carried in the entry event of the first rule group is parsed to obtain the rule group identifiers of each first-level rule group that needs to be processed in parallel. For each rule group identifier, the corresponding retrieval task is started. The retrieval tasks are independent of each other and are executed in parallel. Each retrieval task is responsible for processing one first-level rule group. Its processing includes: querying the pre-determined rule group association relationship based on the rule group identifier, obtaining the list of second-level sub-rules corresponding to the rule group identifier, and obtaining the specific content of each second-level sub-rule in the list.

[0080] In the parallel acquisition method, there's no need to wait for the acquisition of sub-rules from one rule group to complete before starting the acquisition of the next rule group; instead, the acquisition of sub-rules from multiple rule groups is performed simultaneously. The acquisition of second-level sub-rules corresponding to each first-level rule group is independent and does not affect each other. After all acquisition tasks are completed, the second-level sub-rules corresponding to each first-level rule group will be obtained. Each rule group can then perform subsequent condition evaluations and action execution operations on its acquired second-level sub-rules.

[0081] The above steps enable the parallel acquisition of second-level sub-rules corresponding to each first-level rule group after the rule group enters the event, based on an event-driven mechanism. This provides support for the efficient operation of the rule execution engine in parallel scenarios with multiple rule groups. Furthermore, since multiple sub-rule acquisition tasks can be executed in parallel, the acquisition process of second-level sub-rules corresponding to each rule group can be completed synchronously, effectively shortening the overall acquisition time in scenarios with multiple rule groups.

[0082] In one exemplary embodiment of this disclosure, step S230, which involves executing a rule group entry operation for a first-level rule group based on the rule group association relationship, and obtaining a second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation, includes: in response to the rule group association relationship being a sequential execution relationship, obtaining a preceding second-level sub-rule corresponding to the preceding first-level rule group before executing the rule group entry operation for the current first-level rule group; and obtaining the current second-level sub-rule corresponding to the current first-level rule group based on the execution result of the preceding second-level sub-rule.

[0083] If the rule group association is a sequential execution relationship, then the execution of multiple first-level rule groups is considered to have a certain order. Sequential execution means that each first-level rule group is executed in a preset order, and the processing of subsequent rule groups depends on the execution results of preceding rule groups. In the rule execution engine, the rule group association between multiple first-level rule groups can be configured as a sequential execution relationship. For example, the output of first-level rule group 1 serves as one of the inputs to first-level rule group 2, affecting the matching and selection of second-level sub-rules in first-level rule group 2; furthermore, first-level rule group 2 must wait for first-level rule group 1 to complete execution before triggering rule matching.

[0084] In a sequential execution relationship, it's impossible to retrieve all second-level sub-rules corresponding to first-level rule groups in parallel. Instead, they must be processed group by group in sequence, and the retrieval of sub-rules for subsequent rule groups can be determined based on the execution results of preceding rule groups. For example, in the rule execution operation of a first-level rule group, the preceding second-level sub-rules corresponding to the preceding first-level rule group are retrieved first. The rule execution engine enters the preceding first-level rule group in the current execution order according to a preset order. In response to the entry operation of this rule group, based on the pre-determined rule group association relationship, the second-level sub-rules corresponding to the preceding first-level rule group, i.e., the preceding second-level sub-rules, are retrieved.

[0085] After obtaining the preceding second-level sub-rules, the rule execution engine evaluates the conditions of those sub-rules. If the conditions of a preceding second-level sub-rule are met, its associated action is executed, and the corresponding execution result is generated. The execution result of the preceding second-level sub-rules records the information generated during the processing of the rule group. The content of the execution result may include the identifier of the hit sub-rule, the status of the action execution, and the output data value.

[0086] After the preceding first-level rule group has been processed, the rule execution engine enters the current first-level rule group. Furthermore, based on the execution results of the preceding second-level sub-rules, the current second-level sub-rules corresponding to the current first-level rule group can be obtained. In one implementation, all second-level sub-rules corresponding to the current first-level rule group can be directly obtained as the current second-level sub-rules for subsequent sub-rule matching and action execution operations.

[0087] In another implementation, the acquisition of the current second-level sub-rule can be determined by combining the execution results of the previous second-level sub-rules. In this case, it is not simply based on the preset rule group association relationship to directly acquire all sub-rules, but can be dynamically determined based on the previous execution results. For example, based on the specific field values ​​in the execution results of the previous second-level sub-rules, the current second-level sub-rules that should be acquired by the current first-level rule group can be filtered or determined.

[0088] Continue to refer to Figure 4 If the rule group association relationship between the first-level rule groups is a sequential execution relationship, the execution flow is as follows: start with rule A for sequential matching. Within rule A, match sub-rules A1, A2, and A3 in sequence. After the first successful matching of a sub-rule, immediately jump to rule B. Repeat the sub-rule matching logic of rule B until all rule groups have been traversed.

[0089] For example, if the execution result of a preceding second-level sub-rule indicates that a specific type of exception has already been handled in the previous stage, the current first-level rule group can skip the sub-rules related to that exception and only acquire the remaining sub-rules as the current second-level sub-rules. Similarly, a parameter value from the preceding execution result can be used as the selection criterion for the current second-level sub-rule; in this case, the corresponding second-level sub-rule can be matched from the current first-level rule group based on that parameter value. After acquiring the current second-level sub-rule, the rule execution engine can continue to evaluate its conditions and execute its actions.

[0090] Through the above steps, it is possible to dynamically obtain the corresponding sub-rules based on the execution results of the preceding rule group under the sequential execution relationship, so that the processing logic between rule groups can be executed according to the actual execution situation, thereby enhancing the flexibility of rule execution.

[0091] In one exemplary embodiment of this disclosure, obtaining the current second-level sub-rule corresponding to the current first-level rule group based on the execution result of the preceding second-level sub-rule includes: generating a second rule group entry event corresponding to the current first-level rule group based on the execution result of the preceding second-level sub-rule; triggering the rule execution operation of the current first-level rule group based on the second rule group entry event, and obtaining the current second-level sub-rule.

[0092] After obtaining the execution result of the preceding second-level sub-rule, a second rule group entry event can be generated based on that result. The second rule group entry event can be an event message triggered by the rule execution engine when the rule group relationship is sequential, indicating that the first-level rule group has entered the rule group. Under sequential execution, after the preceding first-level rule group has been processed, a second rule group entry event corresponding to the current first-level rule group is generated based on the execution result of the preceding second-level sub-rules.

[0093] When a preceding second-level sub-rule within a preceding first-level rule group is hit and executed, a corresponding execution result is generated. This result includes information output during the processing of the preceding rule group, such as the identifier of the hit sub-rule, the action execution status, and the generated data values. The execution result of this preceding second-level sub-rule is retrieved, and a second rule group entry event is generated based on this result. The second rule group entry event may carry information related to the processing of the current first-level rule group, which can be determined based on the preceding execution result. For example, the second rule group entry event may include the identifier of the current first-level rule group, as well as context data or parameters extracted from the preceding execution result for use by the current rule group.

[0094] After a second rule group entry event is generated, the execution operation of the current first-level rule group is triggered based on this event to obtain the current second-level sub-rules. The second rule group entry event is dispatched to the module or thread in the rule execution engine responsible for handling the current first-level rule group. In response to the second rule group entry event, the rule execution engine executes the entry operation of the current first-level rule group.

[0095] During the entry process, the rule execution engine parses the information carried in the entry event of the second rule group to obtain the identifier of the current first-level rule group and related context data. Then, based on the identifier of the current first-level rule group, it searches for the corresponding second-level sub-rule in the pre-determined rule group relationships to obtain the specific content of the current second-level sub-rule. If the entry event of the second rule group carries data related to the results of previous executions, this data can be used as a reference when obtaining the current second-level sub-rule. For example, based on specific fields in the context data, the corresponding current second-level sub-rule can be filtered or matched in the rule group relationships.

[0096] After obtaining the current second-level sub-rule, the rule execution engine continues to evaluate the conditions and execute actions for that sub-rule. Through the above steps, an entry event can be generated based on the results of the preceding execution, triggering the entry of subsequent rule groups and the acquisition of sub-rules in an event-driven manner. This allows rule groups in a sequential execution relationship to be decoupled and orderly passed on through an event mechanism.

[0097] For step S240, based on the production requirements of the target production stage, the matching result of each second-level sub-rule is determined. After obtaining the second-level sub-rules, the rule execution engine performs condition evaluation and action execution on the current second-level sub-rule based on the production requirements of the target production stage, and determines the second-level target sub-rule that matches the production requirements of the target production stage, which is taken as the matching result of the second-level sub-rule.

[0098] In one exemplary embodiment of this disclosure, step S250, determining the rule matching result of the target processing rule based on the rule group association relationship and the matching result of the second-level sub-rules, includes: determining the second-level target sub-rules from the second-level sub-rules based on the production target of the target production process; performing action execution operations based on the second-level target sub-rules to obtain action execution results; and generating rule matching results based on the rule group association relationship and the action execution results of multiple second-level target sub-rules.

[0099] During the operation of the rule execution engine, based on the production target of the target production stage, second-level target sub-rules are determined from the second-level sub-rules. These second-level sub-rules are the sub-rules corresponding to the currently processed first-level rule group. Based on the production target and according to the preset sub-rule arrangement order, each second-level sub-rule is evaluated and matched sequentially.

[0100] The condition-based matching process may include: using relevant data from the production objectives of the target production stage as input parameters, and substituting them into the triggering conditions of the current second-level sub-rule for judgment. If the triggering conditions are not met, the next second-level sub-rule is evaluated. If the triggering conditions are met, the second-level sub-rule is identified as the second-level target sub-rule, and matching of the remaining second-level sub-rules within the current rule group is stopped.

[0101] After determining the second-level target sub-rule, actions will be executed based on it to obtain the results. For example, each second-level sub-rule is pre-configured with associated actions. When a second-level sub-rule is matched, the action definition associated with that rule is retrieved and the action is executed. The content of the action may include, but is not limited to, calling the equipment interface to adjust process parameters, sending a notification message to the terminal, triggering the start command of the next production stage, and recording production data.

[0102] After an action is completed, a corresponding action execution result is generated. The action execution result records relevant information about the action execution, such as whether the action was successful, the output data generated during execution, and the execution time. Since the target processing rules may include multiple first-level rule groups, each first-level rule group has corresponding second-level sub-rules. After all multiple first-level rule groups have been processed, each rule group may generate a corresponding second-level target sub-rule and its action execution result. Subsequently, based on the rule group association relationships and the action execution results of the aforementioned multiple second-level target sub-rules, a rule matching result is generated.

[0103] Taking a scenario where multiple first-level rule groups are executed in parallel as an example, the identifiers of the matched second-level target sub-rules in these groups, along with the execution results of each action, are aggregated and integrated to form a unified rule matching result. This result reflects the processing status of the entire rule execution engine after the production event is triggered, including which rule groups were matched, which sub-rules were matched, and the execution status of each action. The rule matching result can be used in subsequent processes, such as recording it in the production log for later traceability, or feeding it back to the upper-level production management system to display the current processing status.

[0104] refer to Figure 6 , Figure 6 The illustration schematically shows the execution flowchart corresponding to the production control mechanism employing a hierarchical rule architecture pattern in an exemplary embodiment of this disclosure. For Lot A product batch, the first-level rule group may include a production equipment efficiency rule group (Hold Rule For Production Equipment Efficiency, i.e., Hold Rule For PEE) and a planning and scheduling rule group (Hold Rule For Planning). When the production equipment efficiency rule group matches rule 2, the planning and scheduling rule group matches rule 3, and the actions corresponding to rules 2 and 3 have been completed, an outbound operation is performed on product Lot A.

[0105] Taking a first-level rule group as an example where multiple first-level rule groups are executed sequentially, since the execution of the current first-level rule group depends on the execution result of the preceding first-level rule group, the execution result of the last first-level rule group has already summarized the matching results of the second-level sub-rules located before this first-level rule group. Finally, the second-level sub-rules matched by the last first-level rule group can be used as the rule matching result.

[0106] Furthermore, the rule group relationships among multiple first-level rule groups can also be a combination of sequential and parallel execution relationships. In this case, the corresponding rule group entry operation can be performed based on the specific positions of the sequential and parallel execution relationships within the multiple first-level rule groups. After completing the above rule matching operation, the rule matching result is finally determined based on the second-level target sub-rules matched in each first-level rule group, combined with the rule group relationships. The above steps realize a complete processing flow from production event triggering to sub-rule matching, action execution, and result aggregation, providing closed-loop support for rule matching and execution in the production process.

[0107] In one exemplary embodiment of this disclosure, step S260, which involves performing a production operation on the memory module to be processed based on the rule matching result to obtain a processed memory module, includes: obtaining multiple second-level target sub-rules included in the rule matching result; determining the rule execution action corresponding to each second-level target sub-rule; pushing the multiple rule execution actions to the action execution queue; and performing a memory module production operation based on the execution result of the action execution queue to obtain a processed memory module.

[0108] After the rule execution engine completes processing of all first-level rule groups, it obtains the generated rule matching results, which include multiple second-level target sub-rules that were matched during this rule execution. The rule matching results are then parsed to extract the identification information of each second-level target sub-rule. For each second-level target sub-rule, its corresponding rule execution action is determined.

[0109] For the action execution process, each second-level target sub-rule has been associated with a corresponding action definition during the configuration phase. Based on the identifier of the second-level target sub-rule, the associated action configured for that sub-rule is obtained and identified as the rule execution action corresponding to that sub-rule. The specific content of the rule execution action may include, but is not limited to: adjusting the process parameters of the production equipment, triggering the start of the next production stage, sending status notifications to the production management system, recording quality inspection data, etc.

[0110] When the rule matching result contains multiple second-level target sub-rules, the rule execution action corresponding to each second-level target sub-rule will be determined one by one, resulting in multiple rule execution actions. These multiple rule execution actions will then be pushed to the action execution queue, which is an ordered queue structure used to manage actions to be executed. According to a predetermined order or priority, each rule execution action will be added to the action execution queue in sequence. Each action in the action execution queue awaits to be retrieved and executed by the component to be executed.

[0111] By pushing rule execution actions to the action execution queue, rule matching and action execution are decoupled. The rule execution engine focuses on rule matching, while the specific action execution is handled by the action execution queue and its corresponding execution components, making the processing flow clearer. As each rule execution action in the action execution queue is executed sequentially, and each action produces a corresponding execution result, memory module production is performed based on the execution result of the action execution queue to obtain the processed memory module.

[0112] The execution results of the action execution queue indicate the completion status of each rule's execution action. Based on these execution results, the corresponding production equipment is triggered or controlled to perform actual production processing operations on the memory modules. For example, based on the process parameter adjustment instructions in the execution results, the welding equipment is controlled to adjust the temperature settings; based on the release instructions in the execution results, the conveyor is controlled to send the memory modules to the next production stage; and based on the defective product marking instructions in the execution results, the sorting device is controlled to sort defective memory modules to designated areas.

[0113] Once all relevant production operations are completed, the current batch or the current memory module completes its production process, resulting in a processed memory module. This processed memory module can then proceed to subsequent production stages or be packaged as a finished product. This method achieves a complete closed loop from rule matching results to action queue push and then to actual production operations, effectively translating the rule engine's decision into the actual production processing of the memory module.

[0114] refer to Figure 7 , Figure 7 This illustration schematically shows the operation page effect corresponding to the production control mechanism using a hierarchical rule architecture pattern in an exemplary embodiment of this disclosure. Figure 1 When using the hierarchical rules of this disclosure in the production control process, the page navigation process and page content displayed during the production control operation of the memory module are shown through the operation interface. For example, on page 1, rule 710 (sub-rule 1) and rule 720 (sub-rule 2) are matched according to the target production stage of the memory module to be processed. Figure 7 The document shows the definition 730 of the product type in sub-rule 1, and the definition 740 of sub-rule 1 of withholding the product for a designated person. It includes attribute content and information related to special actions. The attribute content may include the action identifier, specific content, operation options, etc. for a certain action. The information related to special actions may include the business code, withholding code, or the holder of the product after withholding.

[0115] refer to Figure 8 , Figure 8 This illustration schematically shows the operation page effect corresponding to the production control mechanism using a hierarchical rule architecture pattern in an exemplary embodiment of this disclosure. Figure 2 .exist Figure 8 On page 2, when sub-rule 1 and sub-rule 2 are matched, the triggered node 1 can be a Repair-Sorting node, i.e., node 810, and the triggered node 2 can be a TackOut node, i.e., node 820. The corresponding main rule trigger list 830 (i.e., rule list) includes multiple sub-rules contained in each rule group, as well as related descriptions of the sub-rules. Page 3 contains the specific content 840 of sub-rule 1 and sub-rule 2.

[0116] In one exemplary embodiment of this disclosure, a rule group entry event log corresponding to the rule group entry event of the first-level rule group is generated according to the rule execution operation of the target processing rule; a rule hit event log corresponding to the sub-rule hit event is generated according to the acquisition operation of the second-level target sub-rule; an action execution event log corresponding to the action execution event is generated according to the rule execution result of the second-level target sub-rule; and a memory module production event log of the processed memory module is generated according to the rule group entry event log, the rule hit event log, and the action execution event log.

[0117] During rule matching and action execution, this embodiment records events at each stage of rule execution to form a complete production traceability log. For example, during the rule execution engine's processing, when a rule execution operation based on the target processing rule enters a first-level rule group, a rule group entry event log corresponding to the first-level rule group's rule group entry event is generated. A rule group entry event refers to an event triggered when the rule execution engine enters a first-level rule group according to a preset order or jump logic. In response to this event, information related to this entry operation is recorded, and a rule group entry event log is generated.

[0118] The content of the rule group entry event log may include, but is not limited to, the identifier of the first-level rule group entered, the entry timestamp, the preceding event or identifier of the preceding rule group that triggered the entry operation, and the identification information of the current production process. The rule group entry event log is used to record which rule groups the rule execution engine enters in sequence during execution, providing a basis for subsequent execution path tracing.

[0119] Upon entering the first-level rule group, the system retrieves the second-level target sub-rules that match the first-level rule group. Based on the production goals of the target production stage, it generates a rule hit event log corresponding to the sub-rule hit event. For example, when the rule execution engine evaluates the conditions of second-level sub-rules within the first-level rule group and determines that the conditions of a certain second-level sub-rule are met, thus identifying it as a target sub-rule, a sub-rule hit event is generated. In response to this event, information related to this hit operation is recorded, and a rule hit event log is generated.

[0120] The rule hit event log may include: the identifier of the hit second-level target sub-rule, the identifier of the first-level rule group to which the sub-rule belongs, the hit timestamp, and relevant information about the production event that triggered the hit. The rule hit event log is used to record which sub-rule was hit within each rule group, providing a basis for subsequent decision-making and traceability.

[0121] After determining the second-level target sub-rule, the action associated with that sub-rule is executed. Based on the execution result of the second-level target sub-rule, an action execution event log is generated corresponding to the action execution event. When the action associated with the second-level target sub-rule is executed and produces an execution result, an action execution event is generated. In response to this event, information related to the execution of that action is recorded, and an action execution event log is generated.

[0122] The action execution event log may include: the action identifier, the identifier of the corresponding second-level target sub-rule, the action execution start time, the action execution end time, the action execution status (success or failure), and the output data generated during the action execution. The action execution event log is used to record the specific actions triggered by each hit rule and their execution status, providing a basis for subsequent effect tracking.

[0123] After processing all first-level rule groups, a memory module production event log is generated based on the generated rule group entry event log, rule hit event log, and action execution event log. For example, these three types of event logs are integrated according to timestamp order or logical relationship to form a complete production event log for the currently processed memory module. This memory module production event log records the entire process from the start to the end of the rule execution engine, including which rule groups were entered sequentially, which sub-rules were hit within each rule group, what actions were performed by each hit sub-rule, and the specific execution results.

[0124] The memory module production event log is associated with the product identifier of the processed memory modules and stored in the production management system's database. This log can be used for backtracking audits of the production process, troubleshooting quality issues, and statistical analysis of production data. Through these steps, multi-dimensional event logging of the entire rule execution process can be achieved, providing complete traceability support for memory module production.

[0125] In summary, the memory module production control method disclosed herein, in response to a production event trigger instruction for a memory module to be processed, determines the target production stage of the memory module to be processed; determines the target processing rule matching the target production stage, the target processing rule including multiple first-level rule groups, each first-level rule group corresponding to at least one second-level sub-rule, the rule group association relationship of the first-level rule groups including at least one of parallel execution relationship and sequential execution relationship; executes the rule group entry operation of the first-level rule group based on the rule group association relationship, and obtains the second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation; determines the matching result of each second-level sub-rule based on the production requirements of the target production stage; determines the rule matching result of the target processing rule based on the rule group association relationship and the matching result of the second-level sub-rule; and performs production operation on the memory module to be processed based on the rule matching result to obtain the processed memory module. On the one hand, by triggering the matching and execution of multiple independent rule groups through the production event of the memory module, it can support modular and multi-stage composite decision-making, avoiding problems such as business process interruption, control failure, or omission of key alarms. On the other hand, through the hierarchical rule execution architecture, after matching multiple rule groups, production execution operations are performed based on the hit sub-rules of each rule group. This can adapt to complex business scenarios involving multiple parallel actions and effectively achieve product quality control.

[0126] It should be noted that although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.

[0127] Furthermore, in this example embodiment, a production control device for memory modules is also provided. (See reference) Figure 9 The production control device 900 for the memory module may include: a production process determination module 910, a target rule determination module 920, a sub-rule acquisition module 930, a sub-rule matching module 940, a matching result determination module 950, and a production processing module 960.

[0128] Specifically, the production stage determination module 910 is used to determine the target production stage of the memory module to be processed in response to the production event trigger instruction of the memory module to be processed; the target rule determination module 920 is used to determine the target processing rule that matches the target production stage. The target processing rule includes multiple first-level rule groups, each first-level rule group corresponds to at least one second-level sub-rule, and the rule group association relationship of the first-level rule groups includes at least one of parallel execution relationship and sequential execution relationship; the sub-rule acquisition module 930 is used to execute the rule group entry operation of the first-level rule group based on the rule group association relationship, and acquire the second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation; the sub-rule matching module 940 is used to determine the matching result of each second-level sub-rule based on the production requirements of the target production stage; the matching result determination module 950 is used to determine the rule matching result of the target processing rule according to the rule group association relationship and the matching result of the second-level sub-rule; and the production processing module 960 is used to perform production operation on the memory module to be processed based on the rule matching result to obtain the processed memory module.

[0129] In one exemplary embodiment of this disclosure, the target rule determination module 920 includes a target rule determination unit, configured to: start a rule execution engine, wherein the rule execution engine is used to call a pre-configured set of candidate processing rules; and determine a target processing rule from the set of candidate processing rules according to the target production stage.

[0130] In one exemplary embodiment of this disclosure, the target rule determination module 920 includes a candidate rule construction unit, configured to: obtain production demand information of the memory module to be processed, the production demand information including at least one production stage; determine the production target corresponding to each production stage based on the production demand information; perform rule configuration operations on each production stage based on the production target to obtain candidate processing rules corresponding to each production stage, the candidate processing rules including multiple first-level candidate rule groups, the candidate rule group association relationship between the multiple first-level candidate rule groups, and second-level candidate sub-rules corresponding to the first-level candidate rule groups; and construct a candidate processing rule set based on the multiple candidate processing rules.

[0131] In one exemplary embodiment of this disclosure, the candidate rule construction unit includes a candidate rule construction subunit, configured to: determine the rule group priorities corresponding to multiple first-level candidate rule groups and the sub-rule priorities corresponding to multiple second-level candidate sub-rules based on production targets; sort the multiple first-level candidate rule groups according to the rule group priorities to obtain sorted first-level candidate rule groups; sort the multiple second-level candidate sub-rules according to the sub-rule priorities to obtain sorted second-level candidate sub-rules; and obtain candidate processing rules based on the sorted first-level candidate rule groups and the sorted second-level candidate sub-rules.

[0132] In one exemplary embodiment of this disclosure, the sub-rule acquisition module 930 includes a first sub-rule acquisition unit, configured to: in response to the rule group association relationship being a parallel execution relationship, execute the rule group entry operation of the first-level rule group in parallel; and during the parallel execution of multiple rule group entry operations, acquire the second-level sub-rules corresponding to each first-level rule group in parallel.

[0133] In one exemplary embodiment of this disclosure, the first sub-rule acquisition unit includes a first sub-rule acquisition sub-unit, configured to: generate a corresponding first rule group entry event in response to the rule group entry operation of each first-level rule group; and acquire the second-level sub-rules corresponding to each first-level rule group in parallel according to each first rule group entry event.

[0134] In one exemplary embodiment of this disclosure, the first-level rule group includes a preceding first-level rule group and a current first-level rule group. The sub-rule acquisition module 930 includes a second sub-rule acquisition unit, configured to: in response to the rule group association relationship being a sequential execution relationship, acquire the preceding second-level sub-rule corresponding to the preceding first-level rule group before executing the rule group entry operation of the current first-level rule group; and acquire the current second-level sub-rule corresponding to the current first-level rule group based on the execution result of the preceding second-level sub-rule.

[0135] In one exemplary embodiment of this disclosure, the second sub-rule acquisition unit includes a second sub-rule acquisition sub-unit, configured to: generate a second rule group entry event corresponding to the current first-level rule group based on the execution result of the preceding second-level sub-rule; and trigger the rule execution operation of the current first-level rule group based on the second rule group entry event to acquire the current second-level sub-rule.

[0136] In one exemplary embodiment of this disclosure, the matching result determination module 950 includes a matching result determination unit, configured to: determine a second-level target sub-rule from the second-level sub-rules based on the production target of the target production process; perform an action execution operation based on the second-level target sub-rules to obtain an action execution result; and generate a rule matching result based on the rule group association relationship and the action execution results of multiple second-level target sub-rules.

[0137] In one exemplary embodiment of this disclosure, the production processing module 960 includes a production processing unit, configured to: obtain multiple second-level target sub-rules included in the rule matching result, determine the rule execution action corresponding to each second-level target sub-rule; push the multiple rule execution actions to the action execution queue; and perform memory module production operation according to the execution result of the action execution queue to obtain the processed memory module.

[0138] In one exemplary embodiment of this disclosure, the memory module production control device 900 further includes a production log generation module, configured to: generate a rule group entry event log corresponding to a rule group entry event of a first-level rule group based on the rule execution operation of the target processing rule; generate a rule hit event log corresponding to a sub-rule hit event based on the acquisition operation of the second-level target sub-rule; generate an action execution event log corresponding to an action execution event based on the rule execution result of the second-level target sub-rule; and generate a memory module production event log for the processed memory module based on the rule group entry event log, the rule hit event log, and the action execution event log.

[0139] The specific details of the virtual modules of the production control device for each of the above memory modules have been described in detail in the corresponding production control method for the memory modules. For any undisclosed details, please refer to the implementation method in the method section, and therefore will not be repeated here.

[0140] It should be noted that although several modules or units of the memory module production control device have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0141] An exemplary embodiment of this disclosure also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the aforementioned memory module production control method.

[0142] In one implementation, the computer program product may be a tangible product containing a computer program, such as a computer-readable storage medium storing the computer program. (See reference...) Figure 10 , Figure 10 The schematic diagram illustrates a computer-readable storage medium 1000 according to an exemplary embodiment of the present disclosure. The computer-readable storage medium 1000 can be a storage medium based on signals such as electrical, magnetic, optical, electromagnetic, or infrared radiation, including but not limited to: random access memory (RAM), read-only memory (ROM), magnetic tape, floppy disk, flash memory, hard disk drive (HDD), solid-state drive (SSD), etc. Exemplarily, a computer program product can be implemented as a non-volatile storage medium storing a computer program, such as read-only memory, NAND flash memory, etc.

[0143] In one implementation, the computer program product can be an intangible product containing a computer program. For example, the computer program product can be implemented as a virtual digital product, such as a digital file storing an executable file, installation package, or other digital file containing the computer program.

[0144] Computer program code can be written in one or more programming languages. Examples of programming languages ​​include C, Java, and C++. Program code can execute entirely on the user's computing device, partially on the user's computing device, or as a standalone software package. It can also execute partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, such as a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via an internet connection provided by a mobile network operator).

[0145] Computer programs can be carried or transmitted via signals such as electrical, magnetic, optical, electromagnetic, and infrared rays. Electronic devices can convert signals carrying computer programs into digital signals, thereby running the computer programs. When a computer program runs on an electronic device, its code is used to cause the electronic device to execute (more specifically, to execute by the processor of the electronic device) the method steps of various exemplary embodiments of this disclosure, such as the memory module production control method described above.

[0146] Exemplary embodiments of this disclosure also provide an electronic device, which may include a processor and a memory. The memory stores executable instructions of the processor, such as a computer program. The processor executes the executable instructions to perform the method steps of various exemplary embodiments of this disclosure. Furthermore, the electronic device may also include a display for displaying a graphical user interface.

[0147] The following is for reference. Figure 11 The electronic device is illustrated by way of a general-purpose computing device. It should be understood that... Figure 11 The electronic device 1100 shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0148] like Figure 11 As shown, the electronic device 1100 may include: a processor 1110, a memory 1120, a bus 1130, an I / O (input / output) interface 1140, a network adapter 1150, and a display 1160.

[0149] The memory 1120 may include volatile memory, such as RAM 1121 and cache unit 1122, and may also include non-volatile memory, such as ROM 1123. The memory 1120 may also include one or more program modules 1124, which include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. For example, program module 1124 may include the modules described in the above-described apparatus.

[0150] The processor 1110 may include one or more processing units, such as an AP (Application Processor), a modem processor, a GPU (Graphics Processing Unit), an ISP (Image Signal Processor), a controller, an encoder, a decoder, a DSP (Digital Signal Processor), a baseband processor, and / or an NPU (Neural-Network Processing Unit).

[0151] The processor 1110 can be used to execute executable instructions stored in the memory 1120, such as the production control method for the memory module described above.

[0152] Bus 1130 is used to connect different components of electronic device 1100 and may include a data bus, an address bus and a control bus.

[0153] Electronic device 1100 can communicate with one or more external devices 1200 (such as keyboard, mouse, external controller, etc.) through I / O interface 1140.

[0154] Electronic device 1100 can communicate with one or more networks via network adapter 1150. For example, network adapter 1150 can provide mobile communication solutions such as 3G / 4G / 5G, or wireless communication solutions such as wireless LAN, Bluetooth, and near-field communication. Network adapter 1150 can communicate with other modules of electronic device 1100 via bus 1130.

[0155] Electronic device 1100 can display a graphical user interface via display 1160, such as a visualization interface showing the production process of memory modules.

[0156] although Figure 11Other hardware and / or software modules, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, may also be configured in the electronic device 1100.

[0157] As can be seen from the above, the technical solutions disclosed herein can be implemented as methods, apparatus, systems, computer program products, storage media, electronic devices, etc. Those skilled in the art will understand that various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software aspects, which may be referred to as "circuit," "module," or "system," respectively.

[0158] It should be understood that this disclosure is not limited to the specific methods, steps, or structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. Those skilled in the art will readily conceive of other embodiments based on the specific implementations provided in this disclosure. Therefore, the specific implementations provided in this disclosure are merely exemplary, and the scope and spirit of this disclosure are indicated by the claims, and should cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary technical means in the art not disclosed in this disclosure.

Claims

1. A method for controlling the production of memory modules, characterized in that, include: In response to a production event trigger command for the memory module to be processed, the target production stage of the memory module to be processed is determined; Determine the target processing rules that match the target production process. The target processing rules include multiple first-level rule groups, each first-level rule group corresponds to at least one second-level sub-rule, and the rule group association relationship of the first-level rule groups includes at least one of parallel execution relationship and sequential execution relationship. Based on the rule group association relationship, the rule group entry operation of the first level rule group is executed, and the second level sub-rule corresponding to the first level rule group is obtained based on the rule group entry operation; Based on the production requirements of the target production stage, determine the matching result of each second-level sub-rule; Based on the matching results between the rule group association relationship and the second-level sub-rules, the rule matching result of the target processing rule is determined; Based on the rule matching results, the memory module to be processed is processed to obtain the processed memory module.

2. The method according to claim 1, characterized in that, The determination of the target processing rules that match the target production stage includes: Start the rule execution engine, which is used to invoke a pre-configured set of candidate processing rules; Based on the target production stage, the target processing rule is determined from the set of candidate processing rules.

3. The method according to claim 2, characterized in that, The candidate processing rule set is constructed through the following steps: Obtain the production demand information of the memory module to be processed, wherein the production demand information includes at least one production stage; Based on the production demand information, determine the production target corresponding to each of the production stages; Based on the production target, rule configuration operations are performed on each of the production stages to obtain candidate processing rules corresponding to each of the production stages. The candidate processing rules include multiple first-level candidate rule groups, the candidate rule group association relationship between the multiple first-level candidate rule groups, and second-level candidate sub-rules corresponding to the first-level candidate rule groups. The candidate processing rule set is constructed based on multiple candidate processing rules.

4. The method according to claim 3, characterized in that, The step of configuring rules for each production stage based on the production target to obtain candidate processing rules for each production stage includes: Based on the production target, determine the priority of the rule groups corresponding to the multiple first-level candidate rule groups, and the priority of the sub-rules corresponding to the multiple second-level candidate sub-rules; The first-level candidate rule groups are sorted according to the priority of the rule groups to obtain the sorted first-level candidate rule groups. The multiple second-level candidate sub-rules are sorted according to the sub-rule priority to obtain the sorted second-level candidate sub-rules; The candidate processing rules are obtained based on the sorted first-level candidate rule group and the sorted second-level candidate sub-rules.

5. The method according to claim 1, characterized in that, The step of executing the rule group entry operation of the first-level rule group based on the rule group association relationship, and obtaining the second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation, includes: In response to the rule group association relationship being the parallel execution relationship, the rule group entry operation of the first-level rule group is executed in parallel. During the parallel execution of multiple rule group entry operations, the second-level sub-rules corresponding to each first-level rule group are obtained in parallel.

6. The method according to claim 5, characterized in that, During the parallel execution of the entry operations of multiple rule groups, the parallel acquisition of the second-level sub-rules corresponding to each first-level rule group includes: In response to the rule group entry operation of each first-level rule group, a corresponding first rule group entry event is generated; Based on the entry events of each of the first rule groups, the second-level sub-rules corresponding to each of the first-level rule groups are obtained in parallel.

7. The method according to claim 1, characterized in that, The first-level rule group includes a preceding first-level rule group and a current first-level rule group. The step of executing a rule group entry operation based on the rule group association relationship, and obtaining a second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation, includes: In response to the rule group association relationship being the sequential execution relationship, before executing the rule group entry operation of the current first-level rule group, the preceding second-level sub-rule corresponding to the preceding first-level rule group is obtained; Based on the execution result of the preceding second-level sub-rule, obtain the current second-level sub-rule corresponding to the current first-level rule group.

8. The method according to claim 7, characterized in that, The step of obtaining the current second-level sub-rule corresponding to the current first-level rule group based on the execution result of the preceding second-level sub-rule includes: Based on the execution result of the preceding second-level sub-rule, a second rule group entry event corresponding to the current first-level rule group is generated; Based on the second rule group entry event, the rule execution operation of the current first-level rule group is triggered to obtain the current second-level sub-rule.

9. The method according to claim 1, characterized in that, The step of determining the rule matching result of the target processing rule based on the matching result of the rule group association relationship and the second-level sub-rules includes: Based on the production target of the target production stage, a second-level target sub-rule is determined from the second-level sub-rules; Based on the second-level target sub-rule, the action execution operation is performed to obtain the action execution result; The rule matching result is generated based on the association relationship of the rule group and the action execution results of multiple second-level target sub-rules.

10. The method according to claim 1, characterized in that, The step of performing a production operation on the memory module to be processed based on the rule matching result to obtain a processed memory module includes: Obtain multiple second-level target sub-rules included in the rule matching results, and determine the rule execution action corresponding to each second-level target sub-rule; Push multiple rule execution actions to the action execution queue; The memory module production operation is performed based on the execution result of the action execution queue to obtain the processed memory module.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: According to the rules of the target processing rules, the operation is executed, and the rule group corresponding to the first level rule group is entered into the event log. Based on the acquisition operation of the second-level target sub-rule, generate the rule hit event log corresponding to the sub-rule hit event; Based on the rule execution results of the second-level target sub-rules, generate action execution event logs corresponding to the action execution events; Based on the rule group entry event log, the rule hit event log, and the action execution event log, a memory module production event log for the processed memory module is generated.

12. A production control device for memory modules, characterized in that, include: The production process determination module is used to determine the target production process of the memory module to be processed in response to the production event triggering instruction of the memory module to be processed. The target rule determination module is used to determine the target processing rules that match the target production process. The target processing rules include multiple first-level rule groups, each first-level rule group corresponds to at least one second-level sub-rule, and the rule group association relationship of the first-level rule groups includes at least one of parallel execution relationship and sequential execution relationship. The sub-rule acquisition module is used to perform a rule group entry operation of the first-level rule group based on the rule group association relationship, and to acquire the second-level sub-rule corresponding to the first-level rule group based on the rule group entry operation; The sub-rule matching module is used to determine the matching result of each second-level sub-rule based on the production requirements of the target production process. The matching result determination module is used to determine the rule matching result of the target processing rule based on the matching result of the rule group association relationship and the second-level sub-rule; The production processing module is used to perform production operations on the memory module to be processed based on the rule matching results, so as to obtain the processed memory module.

Images