Data management method, system, device and medium for semiconductor manufacturing execution system

Abstract

The application discloses a data management method, system, device and medium of a semiconductor manufacturing execution system, and the method comprises the following steps: creating or obtaining unique identifiers of upper-layer components and lower-layer components in a connection component tree, each layer of components of the component tree is mapped to state data of different scopes to realize isolation of component states at a hierarchical boundary; confirming a mixing mode of context data between the upper-layer components and the lower-layer components; mixing the state data of the upper-layer components and the context data of the lower-layer components based on the mixing mode and the unique identifiers to form current scope data corresponding to the lower-layer components; and the lower-layer components obtain service data provided to the upper-layer components based on the unique identifiers in the current scope data through a scope component, so that the service data is used by the service. The application realizes a dynamic state isolation mechanism, a state management tool can well realize state isolation at a component level, extraction and reuse of complex services are realized, and data combination forms between components are more flexible.

Description

Technical Field

[0001] This invention relates to the field of real-time monitoring and management technology of production processes, and in particular to a data management method, system, device and medium for a semiconductor manufacturing execution system. Background Technology

[0002] Manufacturing Execution System (MES), as the core system connecting enterprise management and shop floor execution, plays a crucial role in the informatization process of modern manufacturing. This system not only processes production plans from the upper-level ERP system but also interfaces with the lower-level automated equipment to achieve real-time monitoring and management of the production process.

[0003] In the front-end development of MES systems, state management is an unavoidable technical challenge. This stems from several aspects: First, MES systems involve complex business processes, including production planning, work order management, quality control, and equipment maintenance, with intricate data interactions and state dependencies between these modules. Second, to improve development efficiency and code reusability, the system extensively uses reusable components, which may require maintaining independent states in different scenarios. Finally, the system needs to support scenarios with multiple pages coexisting, making the lifecycle management of each page's state a crucial issue.

[0004] Traditional global state management solutions fall short when handling such complex business scenarios. For example, when multiple pages reuse the same business component, sharing the same global state can easily lead to data contamination. Furthermore, as the business scales up, the global state tree becomes increasingly bloated, and the dependencies between states become more complex. This not only impacts system performance but also significantly increases the difficulty of code maintenance.

[0005] Against this backdrop, developing a state management solution tailored to the characteristics of MES systems is particularly necessary. This solution needs to maintain the advantages of existing state management tools while addressing various problems encountered in actual development, providing better technical support for the front-end development of MES systems. Summary of the Invention

[0006] To address the aforementioned technical problems, the present invention aims to provide a data management method based on a semiconductor manufacturing execution system that solves the problems of state isolation and sharing in the prior art.

[0007] The present invention discloses a data management method for a semiconductor manufacturing execution system, comprising: creating or obtaining unique identifiers for upper-level and lower-level components in a component tree, wherein each layer of the component tree achieves isolation of component states at hierarchical boundaries by mapping state data corresponding to different scopes; confirming the mixing method of context data between the upper-level and lower-level components; mixing the state data of the upper-level component and the context data of the lower-level component based on the mixing method and the unique identifier to form current scope data corresponding to the lower-level component; and the lower-level component obtaining business data provided to the upper-level component through the scope component based on the unique identifier in the current scope data for business use.

[0008] The component tree is a multi-level component tree.

[0009] The unique identifier is generated using the Symbol function in JavaScript.

[0010] The mixing method is a merge mixing, which takes the data of the parent context as the main data and merges the data of the current layer into the parent context, ensuring that key-value pairs not defined in the parent context take priority over the data of the current layer.

[0011] The mixing method is a supplementary mixing, where the data of the lower-level component is the primary data source, and the key-value pairs not defined by the lower-level component are supplemented only from the context of the parent upper-level component.

[0012] The mixing method is overlay mixing, where the data of the current layer overlays the data of the scope.

[0013] The scope component includes at least a context hook for accessing business data in the context, a context wrapper for inserting the business data in the context into the lower-level component, and a context accessor for extracting the business data in the context from the lower-level component.

[0014] The data management system for a semiconductor manufacturing execution system includes:

[0015] Create a module to create or obtain unique identifiers for upper-level and lower-level components in the component tree. The components at each level of the component tree are isolated at the hierarchical boundaries by mapping state data corresponding to different scopes.

[0016] The confirmation module confirms the mixing method of context data between the upper-layer component and the lower-layer component;

[0017] The mixing module mixes the state data of the upper-layer component and the context data of the lower-layer component based on the mixing method and the unique identifier to form the current scope data corresponding to the lower-layer component.

[0018] The acquisition module allows the lower-level component to obtain business data provided to the upper-level component based on a unique identifier in the current scope data, through the scope component, for business use.

[0019] A data management device for a semiconductor manufacturing execution system includes: a memory storing a data management method program for the semiconductor manufacturing execution system and a processor for running the data management method program for the semiconductor manufacturing execution system, wherein the data management method program for the semiconductor manufacturing execution system is configured to implement the steps of the data management method for the semiconductor manufacturing execution system.

[0020] A computer-readable storage medium storing a data management method program for a semiconductor manufacturing execution system, the data management method program for the semiconductor manufacturing execution system being executed by a processor to implement the steps of the data management method of the semiconductor manufacturing execution system.

[0021] This invention merges contextual data using different merging methods and uses the merged data as a basis for further downward propagation, ensuring that each component only needs to focus on the dependent data of its current level, thus avoiding a bloated state tree. It also ensures data independence for components in different scenarios, provides a top-down state sharing mechanism, flexibly supports the independence, sharing, and composition of scopes between parent and child components, effectively manages the lifecycle of states, and provides a clear state dependency management mechanism to solve problems such as complex cross-module dependency management, thus supporting rapid iterative development of the system. Attached Figure Description

[0022] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings.

[0023] Figure 1 For existing technology flowcharts;

[0024] Figure 2 This is a general flowchart of the data management method of the semiconductor manufacturing execution system according to an embodiment of the present invention;

[0025] Figure 3 This is a flowchart illustrating the data sharing and isolation process in an embodiment of the present invention.

[0026] Figure 4 This is a diagram showing specific page elements in an embodiment of the present invention;

[0027] Figure 5 This is the parent scope diagram of an embodiment of the present invention;

[0028] Figure 6 This is a data management device for a semiconductor manufacturing execution system according to an embodiment of the present invention;

[0029] Figure 7 A computer device for data management of a semiconductor manufacturing execution system according to an embodiment of the present invention. Detailed Implementation

[0030] The data management method of the semiconductor manufacturing execution system of the present invention will be further described in detail below with reference to the accompanying drawings. In the following detailed description, only certain exemplary embodiments of the invention are described by way of illustration. It will be readily apparent to those skilled in the art that various modifications can be made to the described embodiments without departing from the spirit and scope of the invention. Therefore, the drawings and description are illustrative in nature and not intended to limit the scope of the claims.

[0031] Provide: In the Vue 3 framework, provide is a cross-level dependency injection mechanism that allows a parent or root component to directly provide shared data or functional methods to child components at any level in its descendant component tree through a declarative interface. This mechanism is implemented through the provide() function, supports static or dynamic data binding, and has reactive characteristics by default.

[0032] Inject (data injection): Inject is a dependency receiving mechanism used in conjunction with provide, allowing child components to declare and obtain data or methods provided by ancestor components through the inject() function.

[0033] Symbol: A new primitive data type introduced in ECMAScript 6 (ES6) for creating unique and immutable data types.

[0034] mixBy: Used to determine which merge strategy to choose.

[0035] Pinia: An application state management tool officially provided by Vue3, suitable for managing the global state of an application.

[0036] defineStore: A function in Pinia used to create context state management.

[0037] Identifier: A unique key that marks the context state.

[0038] getContextKey: A method to retrieve the unique key for the context state.

[0039] useContext: Retrieves data passed from the parent component using the specified key.

[0040] ContextProvider: Defines an accessible context state object using developer-provided context state and merging strategies, used to share data across the component tree.

[0041] withContext: An advanced usage based on ContextProvider, with the same function as ContextProvider.

[0042] Existing solution: The official Vue 3 recommendation for Pinia uses a global state container approach, defining the store through the `defineStore` function and storing it as a singleton within the application. This approach causes all components to share the same state when accessing the same store, which can easily lead to state pollution issues in complex business scenarios.

[0043] In complex scenarios of enterprise applications, components often need to aggregate state data from multiple dispersed business domains. Traditional solutions struggle to handle this cross-domain data effectively. The approach provided by this invention can effectively reduce the complexity of data flow management and improve code maintainability and business decoupling.

[0044] In complex business scenarios, front-end applications function like massive, precisely operating machines, with interwoven functional modules and intricate business logic. For front-end development teams, efficiently building maintainable and easily extensible systems, and component extraction and reuse, become core methods to improve development efficiency and reduce maintenance costs. However, in actual development, Pinia (a mainstream state management library) has revealed many limitations.

[0045] Insufficient isolation in data sharing, such as Figure 1 When page 1 and page 2 share component A, the state data of storeA that this component depends on will face the risk of isolation. Pinia acts as a global state management library, and the Store it creates adopts the singleton pattern by default. This will lead to the risk of cross-component pollution. The root cause is that Pinia lacks a component-level Store isolation mechanism.

[0046] This invention provides a data management method for a semiconductor manufacturing execution system. It achieves multi-level transparent access through a hierarchical injection strategy and an intelligent merging strategy, and realizes dynamic context state isolation and sharing through a scope component. This primarily solves the state isolation and sharing problems in existing technologies. The key to this invention's technical solution lies in:

[0047] 1) State isolation mechanism: It uses JavaScript's Symbol feature to create a unique context identifier. Internally, it maintains the state space of different scopes through a map to achieve logical boundary isolation of component states and prevent cross-component state pollution. This solves the problem of state sharing and scope pollution that occurred when Pinia was used as a state management tool in previous projects.

[0048] 2) Intelligent state sharing strategy: Based on Vue 3's provide mechanism, state is provided and obtained through `inject(contextKey)`. It creatively offers three hybrid modes: self, parent, and isolated. These three modes are controlled by the `mixby` parameter when using `ContextProvider` to provide context, and can be set to `self`, `parent`, or not passed. The `self` mode is suitable for scenarios where component self-definition needs to be maintained while selectively inheriting from the parent context. This mode prioritizes the current component's configuration over the parent, inheriting only undefined properties from the parent. The `parent` mode is suitable for scenarios where the parent context needs to override the component's default settings. It prioritizes the parent configuration over the current component, allowing upper-level components to control and unify the behavior of lower-level components. The default (no passing) mode is suitable for scenarios where complete isolation between the component and the parent context is required. In this mode, the component runs completely independently, unaffected by the parent configuration, maintaining maximum encapsulation and determinism. The specific value to choose depends on different business scenarios. Lower-level components use the scoped data provided by the upper-level component through `inject`.

[0049] 3) A two-way mapping state management mechanism is used to accurately pass through the state through the getContext and withContext functions, and to obtain data for business use through the useContext function.

[0050] Developing under this model can effectively solve the problem of insufficient isolation in data sharing when using Pinia as a state management library, such as... Figure 3 As shown.

[0051] like Figures 1-5 As shown below, the page layout includes a left selection area and a right display area, which are managed through three main modules: parentContext, leftContext, and rightContext.

[0052] Parent scope

[0053] This function is responsible for storing global permission information. It includes methods for querying data in the left-hand selection area and storing the query results. It also includes methods for querying data in the right-hand display area and storing the query results. It provides permission verification and data access control to ensure the security and compliance of user operations.

[0054] Left selection area

[0055] Includes selection boxes and a search button, allowing users to filter and display relevant data based on search criteria. The selection boxes have independent interaction logic, but this logic depends on permission information in the parentContext. When a user selects an item in the left selection area, it triggers a query for detailed information in the right display area.

[0056] Right side display area

[0057] The content displayed dynamically depends on the element selected in the left-hand selection area. This includes detailed information about the selected element, executable operations, and specific business logic. The displayed content is related to the current state of the selected element in the left-hand selection area. When an element is selected, the business logic display area on the right is updated. When the user performs certain operations (such as deployment or deletion) in the right-hand display area, the state of the selected element on the left is updated to reflect the latest business logic and data changes.

[0058] The specific implementation steps are as follows:

[0059] Step S1: Identify as Symbol

[0060] To ensure the uniqueness and isolation of contexts, each context scope is identified by a Symbol.

[0061] 1) Parent Context:

[0062] In the parent component, a parentContext is defined, which contains common data for the left and right regions, such as storing global permission information, methods for querying data in the left region, storing the result set retrieved from the left region, methods for querying data in the right region, storing the result set retrieved from the right region, and using Symbol to identify the parent scope.

[0063] 2) Sub-scopes of the left and right regions

[0064] The left selection area (leftContext) and the right display area (rightContext) each have their own scope, identified by a Symbol. These Symbols are dynamically generated using get methods to ensure that each scope has a unique identifier and avoid context data conflicts.

[0065] Step S2: Components at any level are implemented with hierarchical injection through the inject method.

[0066] The parent component uses provide to provide its attributes and methods to the child components. The left selection area and the right display area obtain the context provided by the parent component through inject.

[0067] Step S3: Multiple context data are merged by specifying the merge method through the mixBy parameter

[0068] When merging context data in the left selection area, the merge method mixBy = "self" is used. This ensures that the component can display the query conditions defined by itself first, while inheriting the attributes and methods provided by the parent scope, enabling the left selection area to access and use the permission-related data in the parent scope. Since the selection conditions and their linkage logic in the left selection area are independent and do not depend on the parent scope, an isolation mode can be used in the independent component to define its own context.

[0069] The right display area is used to dynamically display the detailed information and operation options related to the elements selected in the left selection area. To ensure that the selected state data in the parentContext has the highest priority, mixBy = "parent" is used. This allows for priority display based on the data in the parent scope and dynamic adjustment according to the data of the elements selected in the left selection area to display additional relevant information.

[0070] Step S4: The merged context data is used as the data of the current layer's scope and provided to downstream components through provide

[0071] In the left selection area, the merged leftContext is provided to the child components through the provide method. The filter box in the left selection area will be联动 updated according to the relevant attributes of the leftContext. Clicking the query button will trigger the query method provided by the parentContext to update the elements on the left. When an element on the left is selected, the query method provided by the parent component will be called to update the data in the right business content display area. This mechanism ensures the clarity and consistency of data flow and state management between components, enabling the left selection area to effectively respond to user interactions.

[0072] The right-hand business content display area retrieves the right-side query result set stored in the parentContext via `inject` to display detailed information. This ensures that the right-hand display area can dynamically display detailed information and operation options related to the selected element in the left-hand selection area, while maintaining decoupling between components. Furthermore, a layer of form validation logic exists within the right-hand display area, which depends on the data details there. Therefore, the right-hand display area also uses `provide` to provide its properties and methods to downstream components. This allows downstream components to access and use these properties and methods to ensure the correctness and consistency of the form validation logic.

[0073] In one embodiment, such as Figure 2 As shown, a data management method for a semiconductor manufacturing execution system is provided, including the following steps:

[0074] Create or retrieve unique identifiers for upper-level and lower-level components in the component tree. Each layer of the component tree maps state data corresponding to different scopes to achieve isolation of component states at hierarchical boundaries.

[0075] Confirm how context data is mixed between upper-level and lower-level components;

[0076] The state data of the upper-level component and the context data of the lower-level component are mixed based on the mixing method and the unique identifier to form the current scope data corresponding to the lower-level component;

[0077] Lower-level components obtain business data provided to upper-level components through the scope components based on the unique identifier in the current scope data, for business use.

[0078] In the data management method of the aforementioned semiconductor manufacturing execution system, context data is merged through different merging methods, and the merged data is used as the basis for further downward transmission. This ensures that each component only needs to focus on the dependent data of the current level, thereby avoiding the bloat of the state tree and ensuring the data independence of components in different scenarios. At the same time, it can also provide a top-down state sharing mechanism, which can flexibly support the independence, sharing, and composition of scopes between parent and child components.

[0079] The component tree is a multi-level component tree. At any level in the component tree, a component can obtain context data provided by the parent component through `inject(contextKey)`. This mechanism allows data to be passed between component levels while maintaining isolation.

[0080] The unique identifier is generated using the Symbol function in JavaScript. Leveraging the properties of Symbols, each context corresponds to a unique contextKey. This is used as an internal data source storage marker to ensure data independence for the component across different scenarios.

[0081] The blending modes are: Merge Blend, which prioritizes data from the parent context and merges data from the current layer into the parent context, ensuring that key-value pairs not defined in the parent context are preferentially used from the current layer's data; Supplement Blend, which prioritizes data from the lower-level component and supplements undefined key-value pairs from the parent component's context; and Override Blend, which overrides data from the scope with data from the current layer. These three unique blending strategies allow for more flexible data combination between components.

[0082] A scoped component must contain at least a context hook for accessing business data in the context, a context wrapper for inserting business data into lower-level components, and a context accessor for retrieving business data from lower-level components. It provides a top-down state sharing mechanism, flexibly supporting the independence, sharing, and composition of scopes between parent and child components.

[0083] It should be understood that, although Figure 2-5 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 2-5 At least some of the steps in the process may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

[0084] In one embodiment, such as Figure 6 As shown, a data management device for a semiconductor manufacturing execution system is provided, comprising: a creation module, a confirmation module, a mixing module, and an acquisition module, wherein:

[0085] Create modules to create or obtain unique identifiers for upper-level and lower-level components in the component tree. Each layer of the component tree achieves isolation of component states at hierarchical boundaries by mapping state data corresponding to different scopes.

[0086] The confirmation module confirms how context data is mixed between upper-level and lower-level components;

[0087] The hybrid module mixes the state data of the upper-level component and the context data of the lower-level component based on the hybridization method and a unique identifier to form the current scope data corresponding to the lower-level component.

[0088] The acquisition module allows lower-level components to obtain business data provided to upper-level components based on a unique identifier in the current scope data, for business use.

[0089] The merge module prioritizes data from the parent context, merging data from the current layer into the parent context, ensuring that key-value pairs not defined in the parent context are preferentially adopted from the current layer's data.

[0090] The supplementary hybrid module prioritizes data from the lower-level components, supplementing only the key-value pairs not defined in the lower-level components from the context of the parent components.

[0091] Override the blending module, overwriting the scope's data with the data from the current layer.

[0092] Specific limitations regarding the data management device of a semiconductor manufacturing execution system can be found in the limitations on the data management method of the semiconductor manufacturing execution system described above, and will not be repeated here. Each module in the aforementioned data management device of the semiconductor manufacturing execution system can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0093] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 7 As shown, the computer device includes a processor, memory, network interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements a data management method for a semiconductor manufacturing execution system. The display screen can be a liquid crystal display (LCD) or an electronic ink display. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0094] Those skilled in the art will understand that Figure 7The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0095] In one embodiment, a computer device is provided, including a memory and a processor, the memory storing a computer program, the processor executing the computer program to perform the following steps:

[0096] Create or retrieve unique identifiers for upper-level and lower-level components in the component tree. Each layer of the component tree maps state data corresponding to different scopes to achieve isolation of component states at hierarchical boundaries.

[0097] Confirm how context data is mixed between upper-level and lower-level components;

[0098] The state data of the upper-level component and the context data of the lower-level component are mixed based on the mixing method and the unique identifier to form the current scope data corresponding to the lower-level component;

[0099] Lower-level components obtain business data provided to upper-level components through the scope components based on the unique identifier in the current scope data, for business use.

[0100] In one embodiment, the component tree is implemented when the processor executes a computer program; it is a multi-level component tree.

[0101] In one embodiment, the unique identifier is generated using the Symbol function in JavaScript, which is implemented when the processor executes a computer program.

[0102] In one embodiment, the processor executes a computer program and implements a merging method, prioritizing the data of the parent context and merging the data of the current layer into the parent context, ensuring that key-value pairs not defined in the parent context are preferentially adopted from the data of the current layer.

[0103] In one embodiment, implemented when the processor executes a computer program, the blending method is supplementary blending, where the data of the lower-level component is primary, and key-value pairs not defined by the lower-level component are supplemented only from the context of the parent upper-level component.

[0104] In one embodiment, the mixing method is overlay mixing, implemented when the processor executes a computer program, where the data of the current layer overlays the data of the scope.

[0105] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0106] In one embodiment, the component tree is implemented when the computer program is executed by a processor and is a multi-level component tree.

[0107] In one embodiment, the unique identifier implemented when the computer program is executed by the processor is a unique identifier generated using the Symbol function in JavaScript.

[0108] In one embodiment, the mixing method is implemented when the computer program is executed by the processor. The mixing method is a merge mixing, which takes the data of the parent context as the main data and merges the data of the current layer into the parent context, ensuring that key-value pairs not defined in the parent context take priority over the data of the current layer.

[0109] In one embodiment, the mixing method is implemented when the computer program is executed by the processor. It is a supplementary mixing method, where the data of the lower-level component is primary, and the data is supplemented only from the context of the parent upper-level component for key-value pairs that are not defined in the lower-level component.

[0110] In one embodiment, the mixing method is overlay mixing, implemented when the computer program is executed by the processor, where the data of the current layer overlays the data of the scope.

[0111] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0112] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0113] The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to the embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention, and these equivalent modifications or substitutions are all included within the scope of this application.

Claims

1. A data management method of a semiconductor manufacturing execution system, characterized by, The method comprises the following steps: creating or obtaining unique identifiers of an upper component and a lower component in a component tree, each layer of components in the component tree mapping state data corresponding to different scopes to achieve isolation of component state at the hierarchical boundary; confirming a mixing mode of context data between the upper component and the lower component; mixing state data of the upper component and context data of the lower component based on the mixing mode and the unique identifiers to form current scope data corresponding to the lower component; the lower component obtaining service data provided to the upper component based on the unique identifier in the current scope data through a scope component for business use; the component tree is a multi-layer component tree; the unique identifier is a unique identifier generated by a Symbol function in JavaScript; the mixing mode is a merge mixing, the data of the current layer is merged into the parent context, and the key-value pairs not defined in the parent context are ensured to use the data of the current layer; the mixing mode is a supplement mixing, the data of the lower component is given priority, and only the key-value pairs not defined in the lower component are supplemented from the context of the upper component of the parent; the mixing mode is an overlay mixing, the data of the current layer is used to cover the data of the scope; the scope component at least includes a context hook for accessing the context data, a context wrapper for inserting the context data into the context of the lower component, and a context accessor for extracting the context data from the lower component.

2. A data management system of a semiconductor manufacturing execution system including the data management method of the semiconductor manufacturing execution system according to claim 1, characterized by The method comprises the following steps: a creating module for creating or obtaining unique identifiers of an upper component and a lower component in a component tree, each layer of components in the component tree mapping state data corresponding to different scopes to achieve isolation of component state at the hierarchical boundary; a confirming module for confirming a mixing mode of context data between the upper component and the lower component; a mixing module for mixing state data of the upper component and context data of the lower component based on the mixing mode and the unique identifiers to form current scope data corresponding to the lower component; an obtaining module for the lower component to obtain service data provided to the upper component based on the unique identifier in the current scope data through a scope component for business use.

3. A data management apparatus of a semiconductor manufacturing execution system, characterized by comprising: The memory stores a semiconductor manufacturing execution system data management method program, and the processor is configured to execute the semiconductor manufacturing execution system data management method program to implement the steps of the semiconductor manufacturing execution system data management method. A semiconductor manufacturing execution system data management method program is stored on a computer readable storage medium, and the semiconductor manufacturing execution system data management method program is executed by a processor to implement the steps of the semiconductor manufacturing execution system data management method.

4. A computer readable storage medium, characterized in that, ​

Images