Docking processing device, method and equipment of factory system and storage medium

Abstract

The invention provides a factory system docking processing device, method and equipment and a storage medium, the docking processing device comprising at least three layers of class structures including a basic abstraction class, a system abstraction class and a docking processing class is constructed, the basic abstraction class comprises common attributes and / or common methods used for docking various types of factory systems, and the system abstraction class comprises common attributes and / or common methods used for docking various types of factory systems. The system abstraction class further comprises system attributes and / or system methods used for being in butt joint with corresponding types of factory systems on the basis of inheriting the basic abstraction class, and the butt joint processing class further comprises specific attributes and / or specific methods used for being in butt joint with the corresponding factory systems on the basis of inheriting the system abstraction class. The device can be in butt joint with factory systems with various types and various business requirements, the software development and test efficiency is high, the cost is low, excessive branches and switches do not need to be arranged, and maintenance is easy.

Description

Technical Field

[0001] The present disclosure relates to chip testing technology, software development technology, and in particular to a docking processing device, method, equipment and storage medium for a factory system. Background Art

[0002] The factory system docking processing software is used to collect data from the docked factory system and provide the collected data to the external management software for data analysis to realize the information management of the factory. Since the factory system types of different customers may be different and the business needs are different. At present, for customers with little difference in functional requirements, the factory system of the customer is connected by switch control. When different switches are turned on, the software can meet the docking requirements of different types of factory systems. For example, the switches corresponding to each type of customer are set in the configuration file. When switch A is turned on, the software executes the docking program of customer A's factory system, and when switch B is turned on, the software executes the docking program of customer B's factory system. For customers with large differences in system types and business needs, it is usually necessary to release corresponding software packages for each type of customer to meet the feature function requirements of each type of customer. When the customer's needs change, iterative development and software updates are performed on the corresponding software version.

[0003] However, using switches to control factory system docking will result in too many code branches and poor maintainability; for the docking method of developing multiple versions of software, when the general functions of the software are updated, developers need to perform software maintenance and upgrades based on all versions and release corresponding patch packages for each version of the software. The methods of related technologies increase the workload from software development, software testing to software release and upgrade maintenance by multiples, the software development efficiency is low, and the resource requirements for development, testing, and management are large. Summary of the invention

[0004] The embodiments of the present disclosure provide a factory system docking processing device, method, equipment and storage medium, which can improve the development efficiency of factory system docking processing software and reduce development, testing and management costs.

[0005] In one aspect of an embodiment of the present disclosure, a docking processing device for a factory system is provided, the docking processing device comprising at least three layers of class structures, wherein the at least three layers of class structures include a basic abstract class, a system abstract class, and a docking processing class;

[0006] The basic abstract class includes common properties and / or common methods for connecting to various factory systems;

[0007] The system abstract class inherits the common properties and / or the common methods of the base abstract class, and the system abstract class also includes system properties and / or system methods for connecting to a corresponding type of factory system, and different system abstract classes correspond to different factory system types;

[0008] The docking processing class inherits the common properties and / or the common methods in the corresponding system abstract class, as well as the system properties and / or the system methods. The docking processing class also includes specific properties and / or specific methods for docking with the corresponding factory system. Different docking processing classes inherited from the same system abstract class are used to dock with factory systems of the same factory system type but with different business requirements.

[0009] Optionally, the docking processing device is used to register and create functional components based on the at least three-layer class structure, and the functional components are used to dock and process data with the factory system based on the calling instructions of the docking requester.

[0010] Optionally, the basic abstract class includes a component creation class and an abstract interface class;

[0011] The component creation class is used to create a functional component corresponding to the target factory system based on the factory system docking request of the docking requester, wherein the factory system docking request includes the factory system type of the target factory system, and different factory system types correspond to different functional components;

[0012] A component calling interface is defined in the abstract interface class, and the component calling interface is used to generate the calling instruction according to the call of the connection requester.

[0013] Optionally, the base abstract class supports extending a new system abstract class corresponding to a new factory system type, the new system abstract class inherits the common properties and / or the common methods in the base abstract class, and the new system abstract class also includes new system properties and / or new system methods corresponding to the new factory system type;

[0014] The system abstract class supports the expansion of a new docking processing class corresponding to a new factory system, and the new docking processing class inherits the common properties and / or the common methods in the new system abstract class, as well as the new system properties and / or the new system methods.

[0015] Optionally, the factory system includes a chip testing system, and the docking requester includes a chip testing device;

[0016] The docking processing device is used to receive the chip test instruction sent by the chip test system, and forward the chip test instruction to the chip test device;

[0017] The docking processing device is also used to receive the chip test instruction execution result called back by the chip testing device, and send the chip test instruction execution result to the chip testing system.

[0018] Another aspect of the present disclosure provides a docking processing method for a factory system, the method being applied to a docking processing device for the factory system, the method comprising:

[0019] receiving a factory system connection request sent by a connection requesting party, wherein the factory system connection request includes a factory system type of a target factory system;

[0020] The functional components corresponding to the target factory system are created by the docking processing device; wherein the docking processing device includes at least three layers of class structure, the at least three layers of class structure include a basic abstract class, a system abstract class and a docking processing class, the basic abstract class includes common attributes and / or common methods for docking various types of factory systems, the system abstract class inherits the common attributes and / or the common methods of the basic abstract class, the system abstract class also includes system attributes and system methods for docking corresponding types of factory systems, different system abstract classes correspond to different types of factory systems, the docking processing class inherits the common attributes and / or the common methods in the corresponding system abstract class, as well as the system attributes and / or the system methods, the docking processing class also includes specific attributes and / or specific methods for docking corresponding factory systems, and different docking processing classes inherited from the same system abstract class are used to dock factory systems with the same factory system type but different business requirements;

[0021] A component pointer of the functional component is sent to the docking requester, and the docking requester is used to call the functional component based on the component pointer to dock with the target factory system.

[0022] Optionally, before receiving the factory system docking request sent by the docking requester, the method further includes:

[0023] In response to the process start instruction, component initialization is performed, and functional components corresponding to the basic abstract class, the system abstract class, and the docking processing class are registered;

[0024] The step of creating the functional components corresponding to the target factory system by the docking processing device includes:

[0025] Determine a target system abstract class and a target docking processing class corresponding to the plant system type of the target plant system in the docking processing device;

[0026] Based on the registered functional components of the basic abstract class, the target system abstract class and the target docking processing class, the functional components corresponding to the target factory system are created.

[0027] Optionally, the sending the component pointer of the functional component to the connection requesting party includes:

[0028] generating a raw pointer of the functional component based on a storage address of the functional component;

[0029] The original pointer is encapsulated into a smart pointer, and the smart pointer is sent to the connection requesting party; the smart pointer is used to release the storage space corresponding to the functional component when the call of the functional component ends.

[0030] Another aspect of the present disclosure provides an electronic device, including:

[0031] Memory for storing computer programs;

[0032] The processor is used to execute the computer program stored in the memory, and when the computer program is executed, the method described in the above aspects is implemented.

[0033] Another aspect of the embodiments of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method described in the above aspects is implemented.

[0034] Another aspect of the embodiments of the present disclosure provides a computer program, including computer program instructions, which implement the methods described in the above aspects when executed by a processor.

[0035] Based on the embodiment of the present disclosure, by constructing a docking processing device including at least three layers of class structure including a basic abstract class, a system abstract class and a docking processing class, the basic abstract class includes common attributes and / or common methods for docking various types of factory systems, the system abstract class also includes system attributes and / or system methods for docking corresponding types of factory systems on the basis of inheriting the basic abstract class, and the docking processing class further includes specific attributes and / or specific methods for docking corresponding factory systems on the basis of inheriting the system abstract class, so that the device can be docked with factory systems of various types and various business needs, and only the basic abstract class needs to be updated once when the general docking function is updated. When the business needs of a certain type of factory system change, only the corresponding system abstract class needs to be updated. When the business needs of a specific factory system change, only the corresponding docking processing class needs to be updated. The software development and testing efficiency is high and the cost is low, and factory systems of different types and different business needs can be independently docked with each other without setting too many branches and switches, and easy maintenance.

[0036] The technical solution of the present disclosure is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings, which constitute a part of the specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0038] The present disclosure may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:

[0039] Figure 1 It is a structural block diagram of an embodiment of a docking processing device of a factory system disclosed in the present invention;

[0040] Figure 2 It is a structural block diagram of an embodiment of the docking processing functional component of the factory system disclosed in the present invention;

[0041] Figure 3 A flowchart of an embodiment of a docking processing method for a factory system disclosed in the present invention;

[0042] Figure 4 A flowchart of another embodiment of the docking processing method of the factory system disclosed in the present invention;

[0043] Figure 5 It is a structural block diagram of another embodiment of the docking processing device of the factory system disclosed in the present invention;

[0044] Figure 6 The figure is a schematic diagram of the structure of an application embodiment of the electronic device disclosed in the present invention. DETAILED DESCRIPTION

[0045] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that the relative arrangement of components and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure unless otherwise specifically stated.

[0046] Those skilled in the art can understand that the terms "first" and "second" in the embodiments of the present disclosure are only used to distinguish different steps, devices or modules, etc., and neither represent any specific technical meaning nor indicate the necessary logical order between them.

[0047] It should also be understood that in the embodiments of the present disclosure, “plurality” may refer to two or more than two, and “at least one” may refer to one, two, or more than two.

[0048] It should also be understood that any component, data or structure mentioned in the embodiments of the present disclosure can generally be understood as one or more, unless explicitly limited or otherwise indicated in the context.

[0049] In addition, the term "and / or" in the present disclosure is only a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in the present disclosure generally indicates that the associated objects before and after are in an "or" relationship.

[0050] It should also be understood that the description of the various embodiments in the present disclosure focuses on the differences between the various embodiments, and the same or similar aspects thereof can be referenced to each other, and for the sake of brevity, they will not be described one by one.

[0051] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0052] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present disclosure, its application, or uses.

[0053] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered as part of the specification.

[0054] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0055] Please refer to Figure 1 , which shows a structural block diagram of a docking processing device for a factory system provided by an exemplary embodiment of the present disclosure. The docking processing device includes at least three layers of class structures, wherein at least three layers of class structures include a basic abstract class 101, a system abstract class 102 and a docking processing class 103.

[0056] The basic abstract class 101 includes common attributes and / or common methods for docking various types of factory systems. Among them, the method is the behavior of the class, which is mainly used to express the operations that the object can perform, and the various functions of the object can be realized through the method; the attribute is the state of the class, which is mainly used to store the relevant data of the object to describe the characteristics of the object. For example, the attributes may include the data type of the factory system, the data generation time, the value of the test data, etc. In the software development process, the common attributes of various types of factory systems and / or the common methods used in docking processing are abstracted and defined as the common attributes and / or common methods in the basic abstract class.

[0057] The system abstract class 102 inherits the common properties and / or common methods of the base abstract class 101. The system abstract class 102 also includes system properties and / or system methods for connecting to the corresponding type of factory system. Different system abstract classes 102 correspond to different types of factory systems. Inheritance refers to the ability of a subclass to inherit properties and methods from a parent class. Through inheritance, a subclass can directly access non-private properties and methods in the parent class. In the disclosed embodiment, a corresponding system abstract class 102 can be designed for each type of factory system based on the factory system connection requirements. Figure 1As shown, a plurality of system abstract classes 102 are provided in the device, including system abstract class a, system abstract class b, system abstract class c and other system abstract classes, and the system abstract classes 102 all inherit the basic abstract class 101. Different system abstract classes 102 correspond to different factory system types, for example, system abstract class a includes system properties and / or system methods for interfacing with the Manufacturing Execution System (MES), system abstract class b includes system properties and / or system methods for interfacing with the Equipment Automation Programming (EAP) system, and system abstract class c includes system properties and / or system methods for interfacing with the Semiconductor Equipment Communication Standard (SECS) system.

[0058] The docking processing class 103 inherits the common properties and / or common methods in the corresponding system abstract class 102, as well as the system properties and / or system methods. The docking processing class 103 also includes specific properties and / or specific methods for docking with the corresponding factory system. Different docking processing classes 103 inherited from the same system abstract class 102 are used to dock with factory systems of the same factory system type but with different business requirements. The docking processing class 103 inherits the corresponding system abstract class 102, that is, it inherits the common properties and / or common methods inherited by the system abstract class 102 from the base abstract class 101, as well as the system properties and / or system methods of the system abstract class 102 itself. Figure 1 As shown, a docking processing class 103 inherits a system abstract class 102, and a system abstract class 102 supports one or more docking processing classes 103 inheritance. For example, docking processing class aa is used to dock the MES system of customer A, docking processing class ab is used to dock the MES system of customer B, docking processing class ba is used to dock the EAP system of customer A, docking processing class ca is used to dock the SECS system of customer A, and docking processing class cb is used to dock the SECS system of customer B. Optionally, for two factory systems with the same system type and the same business requirements, the factory system docking can be achieved through the same docking processing class 103. For example, if the business requirements of the MES system of customer A and the MES system of customer C are the same, both can be docked through the docking processing class aa.

[0059] Optionally, the docking processing device provided in the embodiment of the present disclosure may be applied to docking processing software, applets, web pages, and other applications of the factory system. The embodiment of the present disclosure does not limit the implementation form of the docking processing device.

[0060] Based on the embodiment of the present disclosure, by constructing a docking processing device including at least three layers of class structures including a basic abstract class, a system abstract class and a docking processing class, the basic abstract class includes common attributes and / or common methods for docking various types of factory systems, the system abstract class also includes system attributes and / or system methods for docking corresponding types of factory systems on the basis of inheriting the basic abstract class, and the docking processing class further includes specific attributes and / or specific methods for docking corresponding factory systems on the basis of inheriting the system abstract class, so that the device can dock factory systems of various types and various business needs; when the general docking function is updated, only the basic abstract class needs to be updated once, and when the basic abstract class is updated, the system abstract classes corresponding to all factory system types are synchronously updated; when there is a change in business requirements for a certain type of factory system, only the corresponding system abstract class needs to be updated, and when there is a change in business requirements for a specific factory system, only the corresponding docking processing class needs to be updated, the software development and testing efficiency is high and the cost is low, and factory systems of different types and different business requirements can be independently docked with each other, without setting too many branches and switches, and the code is highly readable and easy to maintain.

[0061] In a possible implementation, the docking processing device in the above embodiment can be used to register and create a functional component based on at least three layers of class structure, and the functional component is used to dock and process data with the factory system based on the call instruction of the docking requester. When the docking requester requests the docking processing device to access a new factory system, the docking processing device determines the corresponding system abstract class and docking processing class based on the system type and business requirements of the system to be connected, and creates the functional component corresponding to the system to be connected based on the basic abstract class, the corresponding system abstract class and the docking processing class. When the user needs to use the docking processing device to obtain data from the factory system or issue a control instruction to the factory system, the client (docking requester) performs relevant operations to send a call instruction to the docking processing device, and the call instruction indicates the target functional component to be called and the target business requirement. The docking processing device calls the target functional component based on the call instruction of the docking requester to dock and communicate with the corresponding factory system, completes the target business requirement and feeds back the execution result to the docking requester.

[0062] Specifically, the basic abstract class may include but is not limited to a component creation class and an abstract interface class.

[0063] The component creation class is used to create the functional components corresponding to the target factory system based on the factory system connection request of the connection requester. The factory system connection request includes the factory system type of the target factory system. Different factory system types correspond to different functional components.

[0064] The abstract interface class defines a component calling interface, which is used to generate a calling instruction according to the call of the docking requester.

[0065] That is, the component creation class is used to create the functional components corresponding to the target factory system when the target factory system is first connected, and the abstract interface class is used to implement the call to the functional components during the subsequent connection process between the connection requester and the target factory system to execute the corresponding connection processing business.

[0066] Indicative, Figure 2 The structural block diagram of a functional component is shown. Among them, IObjectUnknown is a component creation class, which is used to create a functional component corresponding to the target factory system based on the factory system docking request of the docking requester; IFactory is based on an abstract interface class, and a component calling interface is defined in IFactory; CEAPFactory, CMESFactory, and CDebugFactory are functional components corresponding to each factory system, which are respectively used to dock and process data with the corresponding factory system; CGeneralMoudle is a public functional component, which encapsulates the common functions of various factory system functional components. Encapsulating the common functions separately in this component can save memory and computing resources to a certain extent. Using public functional components to execute the common functions of docking various factory systems realizes code reuse, simplifies the process of public code upgrade and maintenance, reduces repeated development work, and can improve program development efficiency and program stability.

[0067] In a possible implementation, the base abstract class of the docking processing device can support the expansion of a new system abstract class corresponding to a new factory system type, the new system abstract class inherits the common properties and / or common methods in the base abstract class, and the new system abstract class also includes new system properties and / or new system methods corresponding to the new factory system type. The system abstract class supports the expansion of a new docking processing class corresponding to a new factory system, the new docking processing class inherits the common properties and / or common methods in the new system abstract class, and adds new system properties and / or new system methods.

[0068] When a user has a new requirement and needs to connect with a new type of factory system, a new system abstract class corresponding to the new factory system type and a new connection processing class that inherits the new system abstract class can be added to the connection processing device to expand the connection processing device. Alternatively, when a user needs to connect with a certain type of factory system, and the connection business requirements of the factory system are different from those of other factory systems of the same type, the new connection processing class of the new factory system can be directly added to the connection processing device.

[0069] The docking processing device of the disclosed embodiment supports horizontal expansion of system abstract classes and docking processing classes without modifying other parts of the device, making the device more stable and not involving the development and update of multiple versions of software, thereby improving the update and iteration efficiency of the product.

[0070] In a possible application scenario, the factory system in the above embodiment may include a chip testing system, and the docking requester includes a chip testing device.

[0071] In a possible implementation, the docking processing device is specifically used to receive the chip test instruction sent by the chip test system, and forward the chip test instruction to the chip test device. In addition, the docking processing device can also be selectively used to receive the chip test instruction execution result called back by the chip test device, and send the chip test instruction execution result to the chip test system.

[0072] In the chip testing scenario, the chip testing device usually cannot be directly connected to the chip testing factory system, and needs to be connected to various chip testing systems and forward chip testing instructions through a docking processing device. Optionally, the chip testing device and the docking processing device can be integrated into the chip testing software.

[0073] Based on the factory system docking processing device provided by the above-mentioned public embodiment, the decoupling of different factory system docking programs is achieved, and the functional components of each factory system are independent of each other and do not affect each other, thereby improving the stability of the docking processing device; through layered design, one device is connected to multiple types of factory systems, and there is no need to synchronously update multiple versions of software when developing new functions and fixing problems, which reduces function modification and testing work, can greatly shorten the project development cycle, improve R&D efficiency and save costs; and the docking processing device supports horizontal expansion. When there is a new type of factory system, it only needs to add a new system abstract class and docking processing class on the basis of the docking processing device and create corresponding functional components to complete the docking, thereby improving the compatibility of the docking processing device.

[0074] based on Figure 1 The docking processing device shown in the figure, the embodiment of the present disclosure also provides a docking processing method for a factory system. Please refer to Figure 3 , which shows a flow chart of a docking processing method for a factory system provided by an exemplary embodiment of the present disclosure. The docking processing device applied to the factory system, the method comprises the following steps:

[0075] Step 301: receiving a factory system connection request sent by a connection requesting party, wherein the factory system connection request includes a factory system type of a target factory system.

[0076] When a user needs to use a docking processing device to dock and process a new factory system, the user can perform relevant operations through the client (docking requester) to send a factory system docking request to the docking processing device. The factory system docking request includes the factory system type of the target factory system and may also include specific business requirements and other information so that the docking processing device can create corresponding functional components.

[0077] Step 302: Create functional components corresponding to the target factory system through the docking processing device.

[0078] Among them, the docking processing device includes at least three layers of class structure, which include basic abstract classes, system abstract classes and docking processing classes. The basic abstract classes include common attributes and / or common methods for docking various types of factory systems. The system abstract classes inherit the common attributes and / or common methods of the basic abstract classes. The system abstract classes also include system attributes and system methods for docking corresponding types of factory systems. Different system abstract classes correspond to different types of factory systems. The docking processing classes inherit the common attributes and / or common methods in the corresponding system abstract classes, as well as system attributes and / or system methods. The docking processing classes also include specific attributes and / or specific methods for docking corresponding factory systems. Different docking processing classes inherited from the same system abstract class are used to dock factory systems with the same factory system type but different business requirements.

[0079] In one possible implementation, the docking processing device is used to register and create a functional component based on the above-mentioned at least three-layer class structure after receiving a factory system docking request from the docking requester. The functional component is used to dock and process data with the factory system based on subsequent calling instructions from the docking requester.

[0080] The specific implementation of the docking processing device can refer to the above embodiment, and the embodiment of the present disclosure will not be repeated here.

[0081] Step 303: Send a component pointer of the functional component to the docking requester, and the docking requester is used to call the functional component based on the component pointer to dock with the target factory system.

[0082] The component pointer is used to indicate the storage address of the functional component. After creating the functional component corresponding to the target factory system, the docking processing device sends the component pointer of the functional component to the docking requester, so that the docking requester can subsequently call the functional component through the component pointer to perform docking and business processing with the target factory system.

[0083] Based on the embodiment of the present disclosure, a docking processing device including at least three layers of class structures, namely, a basic abstract class, a system abstract class and a docking processing class, is constructed. The basic abstract class includes common properties and / or common methods for docking various types of factory systems. The system abstract class also includes system properties and / or system methods for docking corresponding types of factory systems on the basis of inheriting the basic abstract class. The docking processing class further includes specific properties and / or specific methods for docking corresponding factory systems on the basis of inheriting the system abstract class. This allows the device to dock various types of factory systems with various business needs. When the general docking function is updated, only the basic abstract class needs to be updated once. When the business needs of a certain type of factory system change, only the basic abstract class needs to be updated once. A new corresponding system abstract class is created. When the business requirements of a specific factory system change, only the corresponding docking processing class needs to be updated. Software development and testing are efficient and low-cost. Factory systems of different types and with different business requirements can be independently docked with each other without the need to set up too many branches and switches, which is easy to maintain. The docking requester does not need to be aware of the specific creation process of the functional components, and can create or modify the corresponding functional components based on the actual needs of the docking requester. There is no need to make special processing of all functional components based on different business requirements, which realizes the decoupling of functional components of different factory systems. The modification of the functional components docked with a factory system will not affect the functional components docked with other factory systems, thereby enhancing the stability of the system.

[0084] In a possible implementation manner, before the above step 301, the method provided by the embodiment of the present disclosure further includes the following steps:

[0085] In response to the process start instruction, the components are initialized and the functional components corresponding to the basic abstract class, the system abstract class and the docking processing class are registered.

[0086] When the main process of the docking processing device is started, the component initialization is first performed to register the functional components corresponding to the basic abstract class, the system abstract class and the docking processing class. Optionally, the component initialization process includes static initialization and dynamic initialization, wherein static initialization is used to register the functional components required for the operation of the docking processing device, and dynamic initialization can dynamically select the required functional components for registration according to the software configuration, and the functional components that are not needed can be not initialized.

[0087] The above step 302 may include the following steps:

[0088] Step 302a: determine the target system abstract class and the target docking processing class corresponding to the plant system type of the target plant system in the docking processing device.

[0089] Step 302b, based on the registered functional components of the basic abstract class, the target system abstract class and the target docking processing class, create the functional components corresponding to the target factory system.

[0090] After receiving the factory system docking request sent by the docking requester, based on the factory system type indicated by the factory system docking request and the specific business requirements, the corresponding target system abstract class and target docking processing class are determined, and the functional components corresponding to the target factory system are created.

[0091] In a possible implementation, the docking processing device may send a smart pointer corresponding to the functional component to the docking requester to call the functional component. Specifically, the above step 303 may include the following steps:

[0092] Step 303a: Generate an original pointer of the functional component based on the storage address of the functional component.

[0093] Step 303b, encapsulate the original pointer into a smart pointer, and send the smart pointer to the connection requesting party; the smart pointer is used to release the storage space corresponding to the functional component when the call of the functional component ends.

[0094] A raw pointer is a pointer that directly operates on a memory address, and indirectly accesses a functional component by storing the address of the functional component. A smart pointer is a class used to manage dynamically allocated memory, and can automatically release the memory resources it points to. A smart pointer is an encapsulation of a raw pointer, and compared to a raw pointer, it can automatically allocate memory and prevent memory leaks.

[0095] Indicative, Figure 4The present invention shows a flowchart of the interaction between a docking processing device and a docking requester during the initialization, creation and calling of a functional component. The docking processing device includes a main thread, a component manager and a component provider, and the component user is the docking requester. The interaction process includes: 1. The main thread triggers the component provider to perform static initialization of the component, and the static initialization is used to register the functional components required for the operation of the docking processing device; 2. The component provider registers the functional component from the component manager, and the component manager registers the functional component statically initialized in step 1; 3. The main thread triggers the component manager to load the component dynamic link library; 4. The component manager triggers the component provider to perform dynamic initialization of the component, and the dynamic initialization can dynamically select the required functional components for registration according to the software configuration, and the functional components that are not needed can be not initialized; 5. The component provider registers the functional component from the component manager, and the component manager registers the functional component dynamically initialized in step 4; 6. The component user requests the component manager to obtain the component, and the component user determines the target factory system that needs to be docked based on the user's docking processing operation, and sends a work request to the component manager. The factory system docking request is used to request to obtain the corresponding functional component. The specific docking request sending process can refer to the above step 301, which is not repeated in the embodiment of the present disclosure; 7. The component manager creates the functional component through the component provider. The component provider creates the functional component based on the above docking processing device and generates the original pointer of the functional component. The specific functional component creation process can refer to the above step 302, which is not repeated in the embodiment of the present disclosure; 8. The component provider sends the original pointer to the component manager; 9. The component manager sends the smart pointer to the component user. The component manager encapsulates the original pointer into a smart pointer and feeds it back to the component user. The specific pointer generation and sending process can refer to the above step 303, which is not repeated in the embodiment of the present disclosure; 10. The component user calls the functional component from the component provider. The component user uses the smart pointer to call the corresponding functional component when performing the docking processing business.

[0096] Please refer to Figure 5 , which shows a structural block diagram of a docking processing device for a factory system provided by an exemplary embodiment of the present disclosure. The device includes:

[0097] The receiving module 501 is used to receive a factory system connection request sent by a connection requesting party, wherein the factory system connection request includes a factory system type of a target factory system;

[0098] A creation module 502 is used to create a functional component corresponding to the target factory system determined by the receiving module 501 through a docking processing device; wherein the docking processing device includes at least three layers of class structure, the at least three layers of class structure include a basic abstract class, a system abstract class and a docking processing class, the basic abstract class includes common attributes and / or common methods for docking various types of factory systems, the system abstract class inherits the common attributes and / or common methods of the basic abstract class, the system abstract class also includes system attributes and system methods for docking corresponding types of factory systems, different system abstract classes correspond to different types of factory systems, the docking processing class inherits the common attributes and / or common methods in the corresponding system abstract class, as well as the system attributes and / or system methods, the docking processing class also includes specific attributes and / or specific methods for docking the corresponding factory system, and different docking processing classes inherited from the same system abstract class are used to dock factory systems with the same factory system type but different business requirements;

[0099] The sending module 503 is used to send the component pointer of the functional component created by the creating module 502 to the docking requester, and the docking requester is used to call the functional component based on the component pointer to dock with the target factory system.

[0100] Optionally, in a possible implementation, the device may further include a registration module, which is used to respond to the process start instruction, initialize the components, and register the functional components corresponding to the basic abstract class, the system abstract class, and the docking processing class;

[0101] The creation module 502 may also be used to:

[0102] Determine a target system abstract class and a target docking processing class corresponding to a plant system type of a target plant system in a docking processing device;

[0103] Based on the registered functional components of the base abstract class, the target system abstract class and the target docking processing class, the functional components corresponding to the target factory system are created.

[0104] Optionally, in a possible implementation manner, the sending module 503 may also be used to:

[0105] Generate an original pointer of the functional component based on the storage address of the functional component created by the creation module 502;

[0106] The original pointer is encapsulated as a smart pointer, and the smart pointer is sent to the docking requester; the smart pointer is used to release the storage space corresponding to the functional component when the call of the functional component ends.

[0107] Each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The parts of the same, similar or corresponding contents between the various embodiments can be referred to each other. Since the system, method, device, and equipment embodiments basically correspond to each other, the relevant parts can be referred to the description of the corresponding parts. The systems, methods, devices, and equipment of the embodiments of the present disclosure also correspond to each other in terms of specific implementation and beneficial technical effects. The relevant contents can be referred to each other and will not be repeated.

[0108] In addition, an embodiment of the present disclosure further provides an electronic device, including:

[0109] Memory for storing computer programs;

[0110] The processor is used to execute the computer program stored in the memory, and when the computer program is executed, the docking processing method of the factory system described in any of the above embodiments of the present disclosure is implemented.

[0111] Figure 6 This is a schematic diagram of the structure of an application embodiment of the electronic device disclosed in the present invention. Figure 6 The electronic device according to the embodiment of the present disclosure is described. The electronic device may be any one or both of the first device and the second device, or a stand-alone device independent of them, and the stand-alone device may communicate with the first device and the second device to receive the collected input signals from them.

[0112] like Figure 6 As shown, the electronic device includes one or more processors and memory.

[0113] The processor may be a central processing unit (CPU) or other forms of processing units having data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device to perform desired functions.

[0114] The memory may include one or more computer program products, and the computer program product may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, a random access memory (RAM) and / or a cache memory (cache), etc. The non-volatile memory may include, for example, a read-only memory (ROM), a hard disk, a flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor may execute the program instructions to implement the docking processing method of the factory system of each embodiment of the present disclosure described above and / or other desired functions.

[0115] In one example, the electronic device may further include: an input device and an output device, and these components are interconnected via a bus system and / or other forms of connection mechanisms (not shown).

[0116] In addition, the input device may also include, for example, a keyboard, a mouse, and the like.

[0117] The output device can output various information to the outside, including the determined distance information, direction information, etc. The output device can include, for example, a display, a speaker, a printer, a communication network and a remote output device connected thereto, and the like.

[0118] Of course, to simplify, Figure 6 Only some of the components related to the present disclosure in the electronic device are shown, and components such as a bus, an input / output interface, etc. are omitted. In addition, according to specific application situations, the electronic device may further include any other appropriate components.

[0119] In addition to the above-mentioned methods and devices, an embodiment of the present disclosure may also be a computer program product, which includes computer program instructions, which, when executed by a processor, enable the processor to execute the steps in the docking processing method of the factory system according to various embodiments of the present disclosure described in the above part of this specification.

[0120] The computer program product may be written in any combination of one or more programming languages ​​to write program code for performing the operations of the disclosed embodiments, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0121] In addition, an embodiment of the present disclosure may also be a computer-readable storage medium on which computer program instructions are stored. When the computer program instructions are executed by a processor, the processor executes the steps of the docking processing method of the factory system according to various embodiments of the present disclosure described in the above part of this specification.

[0122] The computer readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0123] A person of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk, etc., various media that can store program codes.

[0124] The basic principles of the present disclosure are described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, effects, etc. mentioned in the present disclosure are only examples and not limitations, and it cannot be considered that these advantages, strengths, effects, etc. are required by each embodiment of the present disclosure. In addition, the specific details disclosed above are only for the purpose of illustration and ease of understanding, and are not limitations. The above details do not limit the present disclosure to the necessity of adopting the above specific details to be implemented.

[0125] Each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the system embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0126] The block diagrams of the devices, apparatuses, equipment, and systems involved in this disclosure are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagrams. As will be appreciated by those skilled in the art, these devices, apparatuses, equipment, and systems can be connected, arranged, and configured in any manner. Words such as "including," "comprising," "having," and the like are open words, referring to "including but not limited to," and can be used interchangeably therewith. The words "or" and "and" used herein refer to the words "and / or," and can be used interchangeably therewith, unless the context clearly indicates otherwise. The word "such as" used herein refers to the phrase "such as but not limited to," and can be used interchangeably therewith.

[0127] The method and apparatus of the present disclosure may be implemented in many ways. For example, the method and apparatus of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above order of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above, unless otherwise specifically stated. In addition, in some embodiments, the present disclosure may also be implemented as a program recorded in a recording medium, which includes machine-readable instructions for implementing the method according to the present disclosure. Therefore, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0128] It should also be noted that in the apparatus, device and method of the present disclosure, each component or each step can be decomposed and / or recombined. Such decomposition and / or recombination should be regarded as equivalent solutions of the present disclosure.

[0129] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the aspects shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

[0130] The above description has been given for the purpose of illustration and description. In addition, this description is not intended to limit the embodiments of the present disclosure to the forms disclosed herein. Although multiple example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims

1. A docking processing device for a factory system, characterized in that: The docking processing device comprises at least three layers of class structure, wherein the at least three layers of class structure comprise a basic abstract class, a system abstract class and a docking processing class; The basic abstract class includes common properties and / or common methods for connecting to various factory systems; The system abstract class inherits the common properties and / or the common methods of the base abstract class, and the system abstract class also includes system properties and / or system methods for connecting to a corresponding type of factory system, and different system abstract classes correspond to different factory system types; The docking processing class inherits the common properties and / or the common methods in the corresponding system abstract class, as well as the system properties and / or the system methods. The docking processing class also includes specific properties and / or specific methods for docking with the corresponding factory system. Different docking processing classes inherited from the same system abstract class are used to dock with factory systems of the same factory system type but with different business requirements.

2. The docking processing device according to claim 1, characterized in that: The docking processing device is used to register and create functional components based on the at least three-layer class structure, and the functional components are used to dock and process data with the factory system based on the calling instructions of the docking requester.

3. The docking processing device according to claim 2, characterized in that: The basic abstract class includes a component creation class and an abstract interface class; The component creation class is used to create a functional component corresponding to the target factory system based on the factory system docking request of the docking requester, wherein the factory system docking request includes the factory system type of the target factory system, and different factory system types correspond to different functional components; A component calling interface is defined in the abstract interface class, and the component calling interface is used to generate the calling instruction according to the call of the connection requester.

4. The docking processing device according to any one of claims 1 to 3, characterized in that: The base abstract class supports the expansion of a new system abstract class corresponding to a new factory system type, the new system abstract class inherits the common properties and / or the common methods in the base abstract class, and the new system abstract class also includes new system properties and / or new system methods corresponding to the new factory system type; The system abstract class supports the expansion of a new docking processing class corresponding to a new factory system, and the new docking processing class inherits the common properties and / or the common methods in the new system abstract class, as well as the new system properties and / or the new system methods.

5. The docking processing device according to any one of claims 1 to 3, characterized in that: The factory system includes a chip testing system, and the docking requester includes a chip testing device; The docking processing device is used to receive the chip test instruction sent by the chip test system and forward the chip test instruction to the chip test device; The docking processing device is also used to receive the chip test instruction execution result called back by the chip testing device, and send the chip test instruction execution result to the chip testing system.

6. A method for docking a factory system, characterized in that: The method is applied to a docking processing device of a factory system, and the method comprises: receiving a factory system connection request sent by a connection requesting party, wherein the factory system connection request includes a factory system type of a target factory system; The functional components corresponding to the target factory system are created by the docking processing device; wherein the docking processing device includes at least three layers of class structure, the at least three layers of class structure include a basic abstract class, a system abstract class and a docking processing class, the basic abstract class includes common attributes and / or common methods for docking various types of factory systems, the system abstract class inherits the common attributes and / or the common methods of the basic abstract class, the system abstract class also includes system attributes and system methods for docking corresponding types of factory systems, different system abstract classes correspond to different types of factory systems, the docking processing class inherits the common attributes and / or the common methods in the corresponding system abstract class, as well as the system attributes and / or the system methods, the docking processing class also includes specific attributes and / or specific methods for docking corresponding factory systems, and different docking processing classes inherited from the same system abstract class are used to dock factory systems with the same factory system type but different business requirements; A component pointer of the functional component is sent to the docking requester, and the docking requester is used to call the functional component based on the component pointer to dock with the target factory system.

7. The method according to claim 6, characterized in that Before receiving the factory system connection request sent by the connection requesting party, the method further includes: In response to the process start instruction, component initialization is performed, and functional components corresponding to the basic abstract class, the system abstract class, and the docking processing class are registered; The step of creating the functional components corresponding to the target factory system by the docking processing device includes: Determine a target system abstract class and a target docking processing class corresponding to the plant system type of the target plant system in the docking processing device; Based on the registered functional components of the basic abstract class, the target system abstract class and the target docking processing class, the functional components corresponding to the target factory system are created.

8. The method according to claim 6, characterized in that The sending the component pointer of the functional component to the connection requesting party includes: generating a raw pointer of the functional component based on a storage address of the functional component; The original pointer is encapsulated into a smart pointer, and the smart pointer is sent to the connection requesting party; the smart pointer is used to release the storage space corresponding to the functional component when the call of the functional component ends.

9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to execute a computer program stored in the memory, and when the computer program is executed, implement the method described in any one of claims 6 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method described in any one of claims 6 to 8 is implemented.

Images