Management method and apparatus, and ate test system
By introducing a session management module into a multi-module communication system, the problems of complexity and low efficiency of multi-module communication in the prior art are solved, and efficient information sharing and module collaboration are realized.
Patent Information
- Application Number
- PCT/CN2024/089277
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-12-18
- Filing Date
- 2024-04-23
- Publication Date
- 2025-06-26
AI Technical Summary
When managing multiple test modules and listening modules, existing communication methods cannot reduce communication complexity and improve module operation efficiency, especially when the number of modules exceeds three.
By introducing a session management module, the communication between the test module and the listening module is managed. The session management module receives update instructions, querys session tables, sends demand instructions, and forwards and obtains instructions and shared information to realize information sharing and collaboration between multiple modules.
It effectively reduces the complexity of multi-module communication, improves the module operation efficiency, and realizes efficient collaborative work between multi-test modules and multi-monitor modules.
Smart Images

Figure CN2024089277_26062025_PF_FP_ABST
Abstract
Description
Management method, device and ATE test system
[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 18, 2023, with application number 202311734692.8, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The embodiments of the present application relate to the field of communication technology, for example, to a management method, device and ATE test system. Background Art
[0003] Communication between test modules and monitoring modules is the foundation for multi-module collaboration, such as in Automatic Test Equipment (ATE) testing. Traditional communication methods for multi-module collaboration include pipes, message queues, shared memory, remote procedure calls, and sockets.
[0004] However, most of the above methods are only applicable to communication between a single test module and a single monitoring module. When the total number of test modules and monitoring modules exceeds three, the communication complexity and module operation efficiency will be greatly affected.
[0005] Summary of the Invention
[0006] The embodiments of the present application provide a management method, device and ATE test system, which solve the problem that the existing communication method cannot reduce the communication complexity and improve the module operation efficiency when managing a total of more than three test modules and monitoring modules, such as multiple test modules and multiple monitoring modules.
[0007] According to one aspect of the present application, a management method is provided, which is executed by a session management module, the session management module being connected to at least one test module and at least one listening module, the method comprising: receiving an update instruction sent by a target test module, wherein the update instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module, and the target test module is a test module whose shared information is updated; querying a session table based on the identification information corresponding to the target test module to obtain a set of listening module identifiers corresponding to the target test module, wherein the session table is stored in the session management module; sending a request instruction to a listening module corresponding to each listening module identifier in the set of listening module identifiers, wherein the request instruction carries the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module; receiving a get instruction sent by a listening module, and sending the get instruction to the target test module, so that the target test module sends shared information corresponding to the shared information identifier to the session management module, wherein the get instruction carries the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module; receiving shared information corresponding to the shared information identifier sent by the target test module, and sending the shared information corresponding to the shared information identifier to the listening module.
[0008] According to one aspect of the present application, a management method is provided, which is executed by a monitoring module, and the method includes: receiving a demand instruction sent by a session management module, wherein the demand instruction carries identification information corresponding to a target test module and a shared information identifier corresponding to the target test module; in response to a business operation rule satisfying a first condition, generating an acquisition instruction according to the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module; sending the acquisition instruction to the session management module, so that the session management module sends the acquisition instruction to the target test module after receiving the acquisition instruction; and receiving shared information corresponding to the shared information identifier sent by the target test module through the session management module.
[0009] According to another aspect of the present application, a management device is provided, comprising: an update instruction receiving module, configured to receive an update instruction sent by a target test module, wherein the update instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module, and the target test module is a test module for shared information update; a monitoring module obtaining module, configured to query a session table according to the identification information corresponding to the target test module to obtain a monitoring module identifier set corresponding to the target test module, wherein the session table is stored in a session management module; a demand instruction sending module, configured to send a demand instruction to the monitoring module corresponding to each monitoring module identifier in the monitoring module identifier set. Command, wherein the demand instruction carries the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module; an acquisition instruction receiving module is configured to receive the acquisition instruction sent by the monitoring module, and send the acquisition instruction to the target test module, so that the target test module sends the shared information corresponding to the shared information identifier to the session management module, wherein the acquisition instruction carries the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module; a shared information receiving module is configured to receive the shared information corresponding to the shared information identifier sent by the target test module, and send the shared information corresponding to the shared information identifier to the monitoring module.
[0010] According to another aspect of the present application, a management device is provided, including: a demand instruction receiving module, configured to receive a demand instruction sent by a session management module, wherein the demand instruction carries identification information corresponding to a target test module and a shared information identifier corresponding to the target test module; an acquisition instruction generating module, configured to generate an acquisition instruction according to the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module in response to a business operation rule satisfying a first condition; an acquisition instruction sending module, configured to send the acquisition instruction to the session management module, so that the session management module sends the acquisition instruction to the target test module after receiving the acquisition instruction; and a shared information sending module, configured to receive shared information corresponding to the shared information identifier sent by the target test module through the session management module.
[0011] According to another aspect of the present application, an ATE test system is provided, which includes at least one of the following: an ATE test machine and a test machine auxiliary device, at least one of the test machine and the test machine auxiliary device runs at least one executed computer program to implement the management method described in any embodiment of the present application.
[0012] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the management method described in any embodiment of the present application when executed. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] FIG1 is a flow chart of a management method in Example 1 of the present application;
[0014] FIG2 is a schematic diagram of another management method in Example 1 of the present application;
[0015] FIG3 is a flow chart of a management method in Example 2 of the present application;
[0016] FIG4 is a schematic diagram of a multi-program operation in Example 2 of the present application;
[0017] FIG5 is a schematic diagram of the structure of a management device in Example 3 of the present application;
[0018] FIG6 is a schematic diagram of the structure of a management device in Example 4 of the present application;
[0019] FIG. 7 is a schematic diagram of the structure of an ATE test system in Example 5 of the present application. DETAILED DESCRIPTION
[0020] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.
[0021] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0022] It is understandable that before using the technical solutions disclosed in multiple embodiments of this disclosure, the type, scope of use, usage scenarios, etc. of personal information involved in this disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.
[0023] Example 1
[0024] Figure 1 is a flow chart of a management method in Example 1 of the present application. This embodiment is applicable to multi-module communication management, such as information sharing, process collaboration, etc. in the process of multi-module communication. The method can be executed by the management device in Example 3 of the present application, and the device can be implemented in software and / or hardware. As shown in Figure 1, the method is executed by a session management module, and the session management module is respectively connected to at least one test module and at least one monitoring module. It should be noted that the test module and the monitoring module can run in the same device or in different devices respectively. The session management module can run in the same device with any module or run alone in an independent device. The management method includes the following steps.
[0025] S110 , receiving an update instruction sent by a target test module, wherein the update instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module, and the target test module is a test module for which shared information is updated.
[0026] The target test module is the test module whose shared information is updated. The test module can be a test program, including but not limited to at least one of: an ATE tester test program, a test item, a robot control program, a production monitoring program, a third-party data analysis program, an equipment maintenance self-test program, a yield analysis program, and a fault detection program. The update instruction is used to notify the session management module of changes to the shared information in the target test module.
[0027] When the shared information of the target test module is updated, the session management module receives an update instruction sent by the target test module, wherein the update instruction carries the identification information of the target test module and the shared information identification corresponding to the target test module, so that the session management module can quickly determine the target test module and the shared information of the target test module that has changed.
[0028] Optionally, before receiving the update instruction sent by the target test module, it also includes: obtaining a session table, wherein the session table includes: identification information corresponding to at least one test module, status information corresponding to at least one test module, attribute information corresponding to each test module identifier, and a public function corresponding to each shared information, wherein the attribute information includes: at least one listening module identifier and at least one shared information identifier corresponding to the test module identifier.
[0029] The session table can be stored in the session management module. The attribute information corresponding to each test module identifier includes: at least one monitoring module identifier and at least one shared information identifier corresponding to the test module identifier. The attribute information can also include whether monitoring is allowed. It should be noted that the monitoring module can monitor all shared information in the test module, or it can monitor only any shared information of the test module. The session table can also include: status information of at least one test module, where the status information can include: registration or deregistration status. It should be noted that the monitoring module and the test module can both be programs. When the program is used for testing, it is a test module, and when the program is used to monitor other programs, it is a monitoring module. That is, the test module and the monitoring module are relative. A program can be both a test module and a monitoring module that monitors other programs. Multiple programs can achieve mutual collaboration by calling the public function corresponding to each shared information in the session table.
[0030] Optionally, obtaining the session table includes: receiving a registration instruction sent by at least one test module or a listening module, and registering in the session table with registration information corresponding to the test module or the listening module according to the registration instruction, and updating the session table, wherein the registration instruction carries registration information, the registration information of the test module includes identification information, status information, attribute information and a common function corresponding to each shared information, wherein the attribute information of the test module includes at least one shared information identifier corresponding to the test module; the registration information of the listening module includes identification information, status information and attribute information, wherein the attribute information of the listening module includes at least one shared information identifier of the test module to be monitored by the listening module.
[0031] When at least one test module or listening module is started, it sends a registration instruction to the session management module. The session management module registers the registration information (unique identifier ID) corresponding to the test module or the listening module in the session table. During registration, the session table is updated with the registration information. It should be noted that the public function corresponding to each shared information may not exist in the listening module's registration information, that is, the public function corresponding to each shared information may be empty. The listening module can selectively monitor the shared information in the test module or monitor all shared information in the test module.
[0032] By receiving a registration instruction sent by at least one test module or a monitoring module, registering the test module or the monitoring module in a session table according to the registration instruction, and updating the session table, a more convenient access mechanism can be provided for the newly added test module or the monitoring module. At the same time, shared information can be set according to the registration information corresponding to the test module, and at least one shared information of the test module that the monitoring module wants to monitor can be set according to the registration information corresponding to the monitoring module. In this way, if the shared information that the monitoring module wants to monitor is updated during the subsequent monitoring process, the function of updating the session table in blocks can be realized.
[0033] Optionally, obtaining the session table includes: receiving an information modification instruction sent by at least one test module or a monitoring module, and modifying the session table with modification information corresponding to the test module or the monitoring module according to the information modification instruction, and updating the session table, wherein the information modification instruction carries modification information, and the modification information includes at least one of status information, attribute information, and public functions.
[0034] If at least one test module or listener module needs to change its registration information during operation, such as when a new test module or listener module is registered in the session table, the module sends a modification instruction to the session management module. The modification instruction carries modification information, including at least one of state information, attribute information, and public functions. After receiving the modification instruction, the session management module updates the session table based on the modification information carried in the modification instruction. For example, as shown in Table 1, Table 1 shows the updated session table after the session management module receives the modification instruction for Program A. As can be seen from Table 1, Program A is both a test module and a listener module, Program B is a listener module, and Program C is a test module. Since Program C is not registered in the original session table, Program A cannot listen to Program C. After Program C connects to the session management module, the session table is updated based on Program C's registration information. Since Program A needs to listen to Share 3 and Share 4 in Program C after Program C registers, the module sends a modification instruction to the session management module. Based on the modification instruction, the module updates the attribute information of Program A in the session table and adds Share 3 and Share 4, which monitor Program C. Through the above optional embodiment, the monitoring module or the testing module can actively modify the registration information in the session table.
[0035] Table 1
[0036] S120 , querying a session table according to identification information corresponding to the target test module to obtain a set of monitoring module identifications corresponding to the target test module, wherein the session table is stored in a session management module.
[0037] The session table is stored in the session management module, and the monitoring module identifier set includes at least one monitoring module identifier.
[0038] The session management module queries the session table based on the identification information corresponding to the target test module in the update instruction to obtain a set of monitoring module identifications for the monitoring target test module. Alternatively, the session management module queries the session table based on the identification information and shared information identification corresponding to the target test module in the update instruction to obtain a set of monitoring module identifications for the shared information corresponding to the shared information identification of the monitoring target test module. In this case, the monitoring module corresponding to each monitoring module identification in the monitoring module identification set monitors the updated shared information in the target test module. It should be noted that the status information of the monitoring module corresponding to each monitoring module identification in the monitoring module identification set in the session table should be a registered status.
[0039] S130 : Send a demand instruction to the monitoring module corresponding to each monitoring module identifier in the monitoring module identifier set, wherein the demand instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module.
[0040] The session management module calls the public function corresponding to the shared information to send a demand instruction to the monitoring module corresponding to each monitoring module identifier in the monitoring module identifier set. The demand instruction is used to notify the monitoring module that the shared information of the target test module it monitors has changed.
[0041] S140, receiving the acquisition instruction sent by the monitoring module, and sending the acquisition instruction to the target test module, so that the target test module sends the shared information corresponding to the shared information identifier to the session management module, wherein the acquisition instruction carries the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module.
[0042] The session management module receives an acquisition instruction sent by the monitoring module, wherein the acquisition instruction is used to inform the session management module that it needs to obtain the updated shared information in the target test module. The session management module sends the acquisition instruction to the target test module. After receiving the acquisition instruction, the target test module calls the public function corresponding to the shared information and returns the updated shared information corresponding to the shared information identifier to the session management module. It should be noted that the monitoring module that sends the acquisition instruction to the session management module may be multiple monitoring modules. When sending the acquisition instruction, the acquisition instruction may also carry the identification information of the monitoring module, so that the session management module can send the updated shared information corresponding to the shared information identifier of the target test module to the corresponding monitoring module.
[0043] S150: Receive shared information corresponding to the shared information identifier sent by the target test module, and send the shared information corresponding to the shared information identifier to the monitoring module.
[0044] After receiving the updated shared information corresponding to the shared information identifier sent by the target test module, the session management module calls the public function corresponding to the shared information to send the updated shared information corresponding to the shared information identifier to the monitoring module.
[0045] The acquisition instruction is forwarded through the session management module, and the updated shared information is forwarded to the monitoring module. The session management module does not store the updated shared information, which can better achieve lightweightness.
[0046] In one example, FIG2 is a schematic diagram of another management method in the first embodiment of the present application. As shown in FIG2, if the test module is program A, and the monitoring modules are program B and program C, when program A, program B, and program C are started, they all need to create a new session and register with corresponding identification information in the session table of the session management module, update and maintain the session table, and the session table includes attribute information and status information of all programs. When a new session is created, the status information of program A, program B, and program C is the registered status; program B and program C both monitor program A, and when the shared information of program A changes, program A sends an update instruction to the session management module to notify the session management module that the shared information has changed. The session management module receives the update instruction. After the instruction, the listening module of the listening program A is queried in the session table, and the listening module of the listening program A is notified, that is, the session management module calls the public function corresponding to the shared information to send a demand instruction to program B and program C, notifying program B and program C that the shared information of the monitored program A has changed. After receiving the demand instruction, program B and program C determine whether they need to obtain the updated shared information of program A. If they need to obtain the updated shared information of program A, they call the public function corresponding to the shared information to send an acquisition instruction to the session management module. The session management module obtains the updated shared information from program A through the acquisition instruction. If the call is successful, the session management module obtains the updated shared information and sends the updated shared information to the listening module.
[0047] It should be noted that if both program B and program C need to update shared information, they both need to call the public function corresponding to the shared information, that is, call the public function corresponding to the shared information twice through the session management module. The session management module actually acts as a proxy, and actually calls the public function interface. The updated shared information will be sent to the session management module twice, but the session management module does not retain the cached updated shared information. All shared information only needs to be maintained within the test module.
[0048] Optionally, it also includes: if the acquisition instruction sent by the listening module is not received, then updating the status information corresponding to the listening module in the session table according to the identification information corresponding to the listening module, and / or, if the call success information of the listening module is not received within the preset time, wherein the call success information indicates that the listening module successfully establishes a connection with the corresponding target test module by calling the public function through the session management module, then updating the status information corresponding to the target test module in the session table, the shared information identifier corresponding to the public function in the attribute information, and at least one of the public functions according to the public function corresponding to the target test module, and / or, if the shared information corresponding to the shared information identifier sent by the target test module is not received within the preset time, then updating the status information corresponding to the target test module in the session table according to the identification information corresponding to the target test module.
[0049] The preset time can be set according to actual needs.
[0050] In the first case, if the session management module does not receive the acquisition instruction sent by the listening module after sending the demand instruction to the listening module, it is determined that an error has occurred in the listening module (abnormal exit), and the session management module cannot connect to the listening module. Then, the status information corresponding to the listening module in the session table is updated according to the identification information corresponding to the listening module, and the registration status is updated to the deregistration status.
[0051] In the second case, if the session management module receives the acquisition instruction from the listening module and sends the acquisition instruction to the target test module, that is, the listening module calls the public function corresponding to the shared information identifier through the session management module to establish a connection with the target test module, if the session management module does not receive the call success information feedback from the listening module within the preset time, then the session management module updates the status information corresponding to the target test module according to the public function corresponding to the target test module, such as updating the status information from the registered status to the unregistered status, or updating the shared information identifier in the attribute information of the target test module, this shared information identifier corresponds to the above-mentioned public function that failed to call, such as deleting the shared information identifier, or updating the above-mentioned public function, such as deleting or correcting the corresponding public function. As shown in Table 1, if program B, which serves as a monitoring module, wants to monitor the shared information 2 of program A, which can serve as a test module, then program B will call the public function getInfo2 corresponding to the shared information 2 through the session management module to establish a connection with program A. If the session management module does not receive the call success information fed back by program B within the preset time, then program A has not established a connection with program B through the session management module. In this case, the session management module will update the public function getInfo2 corresponding to program A in the session table and delete it; or delete the shared information 2 in the attribute information, or modify the status information of program A to be deregistered, or perform the above update operations at the same time.
[0052] In the third case, if the session management module does not receive the updated shared information corresponding to the shared information identifier sent by the target test module within a preset time after sending a retrieval instruction to the target test module, it is determined that an error has occurred in the target test module (abnormal exit). The target test module's corresponding status information in the session table is then updated based on the identifier information corresponding to the target test module, changing the registered status to the deregistered status. This updates the session table and simultaneously notifies the monitoring module that the target test module has been deregistered. As shown in Figure 2, if the session management module does not obtain updated shared information for Program A within the preset time, indicating a communication failure, the session management module deregisters Program A from the session table, i.e., changes Program A's status information to the deregistered status.
[0053] By updating the status information corresponding to the listening module in the session table according to the identification information corresponding to the listening module if the acquisition instruction sent by the listening module is not received, and / or, if the call success information of the listening module is not received within the preset time, updating the status information corresponding to the target test module in the session table, the shared information identifier corresponding to the public function in the attribute information, and at least one of the public functions according to the public function corresponding to the target test module if the acquisition instruction sent by the listening module is not received within the preset time, and / or, if the shared information corresponding to the shared information identifier sent by the target test module is not received within the preset time, updating the status information corresponding to the target test module in the session table according to the identification information corresponding to the target test module, the session table in the session management module can be quickly updated according to the status of multiple modules, redundant sessions can be discovered and processed in time, and other modules can be ensured not to be affected.
[0054] The technical solution of this embodiment is to receive an update instruction sent by a target test module, wherein the update instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module, and the target test module is a test module for shared information update; query the session table according to the identification information corresponding to the target test module to obtain a listening module identification set corresponding to the target test module; send a demand instruction to the listening module corresponding to each listening module identification in the listening module identification set, wherein the demand instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module; receive an acquisition instruction sent by the listening module, and send the acquisition instruction to the target test module, so that the target test module sends the shared information corresponding to the shared information identifier to the session management module, wherein the acquisition instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module; receive the target test module The shared information identifier sent corresponds to the shared information, and the shared information corresponding to the shared information identifier is sent to the listening module. When the shared information of the test module changes, the session management module can be notified, and the session management module then notifies the listening module that listens to the test module. Then the listening module can obtain the updated shared information of the test module through the session management module, which solves the problem that when managing a total of more than three test modules and listening modules, such as multiple test modules and multiple listening modules, the existing communication method cannot reduce the communication complexity and cannot improve the module operation efficiency, and realizes effective management of multiple modules and synchronous monitoring updates. Compared with traditional communication methods, the complexity is lower; at the same time, since the session management module is only responsible for forwarding the shared information updated by the test module, it does not have a data storage function and is a distributed storage mode, which can realize the rapid forwarding of shared information, improve the module operation efficiency, and thereby improve the work coordination between multiple test modules and multiple listening modules.
[0055] Example 2
[0056] Figure 3 is a flow chart of a management method in Example 2 of the present application. This embodiment is applicable to multi-module communication management, such as information sharing and process collaboration during multi-module communication. This method can be executed by the management device in Example 4 of the present application, which can be implemented in software and / or hardware. As shown in Figure 3, the method is executed by the monitoring module and includes the following steps.
[0057] S210: Receive a requirement instruction sent by the session management module, wherein the requirement instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module.
[0058] The monitoring module receives the demand instruction sent by the session management module and clearly monitors the changes in the shared information in the target test module.
[0059] S220: If the business operation rule satisfies the first condition, an acquisition instruction is generated according to the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module.
[0060] The first condition can be set based on the monitoring module's own business operation rules (business logic). The business operation rules are the business logic included in the test sequences within a preset range (pre- and post-preset ranges) of the current test sequence of the current monitoring module. For example, the first condition can be a feedback flag included in the test sequence within the preset range of the current test sequence of the monitoring module, and the waiting result corresponding to the feedback flag is generated by the test sequence of the target test module.
[0061] After receiving the demand instruction, each monitoring module determines whether its own business operation rules meet the first condition. If the first condition is met, it means that the current monitoring module needs the updated shared information of the target test module. The acquisition instruction is generated according to the identification information corresponding to the target test module and the shared information identification corresponding to the target test module. It should be noted that the acquisition instruction can carry the identification information of the current monitoring module.
[0062] S230: Send the acquisition instruction to the session management module, so that the session management module sends the acquisition instruction to the target test module after receiving the acquisition instruction.
[0063] The monitoring module that needs updated shared information of the target test module calls the public function corresponding to the shared information and sends an acquisition instruction to the session management module. After receiving the acquisition instruction, the session management module forwards the acquisition instruction to the target test module.
[0064] S240: Receive shared information corresponding to the shared information identifier sent by the target test module through the session management module.
[0065] After the target test module receives the acquisition instruction, the updated shared information corresponding to the shared information identifier is sent to the session management module. After receiving the updated shared information, the session management module calls the public function corresponding to the shared information to send the updated shared information to the listening module that needs the updated shared information of the target test module. The listening module that needs the updated shared information of the target test module receives the updated shared information corresponding to the shared information identifier.
[0066] Optionally, if the business operation rules meet the first condition, an acquisition instruction is generated based on the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module, including: if the test timing within the preset range of the current test timing corresponding to the monitoring module contains a feedback flag, then the first target test timing corresponding to the target waiting result corresponding to the feedback flag is acquired; if the first target test timing is the test timing of the target test module, it is determined that the business operation rules of the monitoring module meet the first condition; and an acquisition instruction is generated based on the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module.
[0067] The preset range can be the front and back preset range corresponding to the current test timing, and the preset range can be set according to actual needs. The feedback flag is used to indicate the test data or test results updated by the test timing in the test module waiting for monitoring. The target waiting result is the waiting test data or test result corresponding to the feedback flag. The first target test timing is the test timing that generates the waiting test data or test result.
[0068] If the test timing within the preset range of the current test timing corresponding to the monitoring module contains a feedback flag, and the target test timing corresponding to the target waiting result corresponding to the feedback flag is the test timing of the target test module, then it is determined that the business operation rules of the monitoring module meet the first condition, and the monitoring module needs to obtain the updated shared information of the target test module. The monitoring module generates an acquisition instruction based on the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module.
[0069] In one example, FIG4 is a schematic diagram of a multi-program operation in Example 2 of the present application. As shown in FIG4 , when an ATE automated tester tests multiple devices under test, multiple programs need to cooperate across programs due to the relevance of their services. If the target test module is Program A, Program A is associated with Program B. Program B pre-registers a listener for Program A in the session table in the session management module. Program B is a listener module, and when the shared information of Program A changes, Program B needs to be notified. Program A and Program B include test sequences at multiple times, such as N and N+1. When Program B is running N+1 test sequences, a feedback flag R: N+1 is included in the preset range, indicating that Program B needs to wait for the test results generated by Program A's N+1 test sequence. Therefore, it indicates that Program B needs updated shared information from Program A. In Figure 4, when program A runs to the N+1th test sequence, the N+1th test sequence includes feedback identification information RRR. After a period of time, the test result of the N+1th test sequence appears in the response of the device under test (DUT), that is, R:N+1. Program A must first send R:N+1 to the session management module. The session management module is equivalent to an agent and feeds back R:N+1 to program B. After monitoring the feedback of R:N+1, program B stops waiting and continues to run the test sequence at time N+2.
[0070] Optionally, if the business operation rules meet the first condition, an acquisition instruction is generated based on the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module, including: if the test timing within the preset range of the current test timing corresponding to the monitoring module contains a comparison flag, then a second target test timing corresponding to at least one comparison information corresponding to the comparison flag is obtained; if the second target test timing is the test timing of the target test module, it is determined that the business operation rules of the monitoring module meet the first condition; an acquisition instruction is generated based on the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module.
[0071] The comparison flag is used to instruct to compare the test result of the current test sequence with the comparison information of the target test sequence, where the comparison information is the test data or test result of the target test sequence. The second target test sequence is the test sequence that generates the comparison information.
[0072] If the test timing within the preset range of the current test timing corresponding to the monitoring module contains a comparison flag, and at least one comparison information corresponding to the comparison flag is generated by the second target test timing in the target test module, then it is determined that the business operation rules of the monitoring module meet the first condition, and the monitoring module needs the shared information updated by the target test module. The monitoring module generates an acquisition instruction based on the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module.
[0073] In one example, as shown in FIG4 , when the target test module is program B and the monitoring module is program C, the preset range of the test sequence N+6 in program C includes a comparison flag CR: N+2, and the corresponding at least one comparison information is the test result of the test sequence N+2 of program B, indicating that program C needs updated shared information of program B. In FIG4 , when program B runs to the N+2 test sequence, the test sequence includes the comparison flag information CR and No-Go N+3, then program B waits for the DUT to respond with the test result. When the test result is "Update No-Go, Fail Bin", that is, the comparison information is "Update No-Go, Fail Bin", program B first sends the comparison information to the session management module, which forwards it to program C. After obtaining the comparison information, program C waits for a period of time and then stops running.
[0074] Optionally, the shared information identifier includes: an identifier of the end of a shared test, an identifier of shared test resource occupancy information, an identifier of shared manipulator control information, an identifier of shared test result data information, an identifier of shared test exception information, an identifier of shared test status, an identifier of shared test time, an identifier of shared device temperature information, an identifier of shared device environment information, and at least one of an identifier of shared fault detection result information.
[0075] In some examples, the technical solution of this embodiment is applicable to automated mass production testing in an ATE test machine, where multiple test modules and multiple monitoring modules need to jointly operate the test process and perform data communication.
[0076] In one example, the test program needs to test each device under test and record the results in the session table. If test program A needs to test device under test 1, device under test 2, and device under test 3 at the same time, when test program A is started, a new session is created and registered with corresponding identification information in the session table of the session management module. At the same time, test item A1 for device under test 1, test item A2 for device under test 2, and test item A3 for device under test 3 are all registered with corresponding identification information in the session table of the session management module. Test program A monitors test item A1, test item A2, and test item A3. If the identifier of the monitored shared information is the identifier of the end of the shared test, then when test item A1 completes the test of device under test 1, that is, when the shared information corresponding to test item A1 changes, test item A1 Notify the session management module, and the session management module broadcasts information to all programs that monitor test item A1. In this example, test program A is notified. If the business operation rules of test program A determine that it is necessary to call the public function of shared information in the session management module to obtain updated shared information, then test program A is the monitoring module, test item A1 is the testing module, and test program A obtains the updated shared information of test item A1. Similarly, test program A can obtain the updated shared information of test item A2 and test item A3. It should be noted that the multiple test items of test program A can also monitor each other. For example, when test item A1 monitors test item A2 and test item A3, the identifier of the shared information can be the identifier of the shared test resource occupancy information, thereby realizing parallel testing of multiple test items, that is, testing multiple devices under test at the same time, improving the utilization rate of test resources, and saving testing costs.
[0077] In one example, the manipulator (Handler) control program can replace the device under test in a timely manner according to the test results of the test program. If the program for testing the device under test is test program A, and the manipulator control program is program B, programs A and B are registered in the session table in the session management module, and program B listens to program A. When the identifier of program A's shared information is the identifier of shared test result data information, when program A's test result data information is tested, program A's shared information changes, and program A notifies the session management module. The session management module broadcasts information to all programs that listen to program A, that is, notifies the manipulator control program B. If program B determines that it needs to call the public function of the shared information in the session management module to obtain the updated shared information based on its own business operation rules, then test program A is the test module and program B is the listening module. Program B needs to obtain the updated shared information of test program A, thereby generating a replacement instruction based on the updated shared information to replace the device under test in a timely manner.
[0078] In one example, when a production monitoring program monitors the entire test process, it can detect anomalies and promptly intervene. When the program testing the device under test is test program A and the production monitoring program is program C, program C registers in the session table of the session management module and monitors test program A. Test program A's shared information identifier can be a shared test exception information identifier, which can be understood as exception information indicating that test program A's test result is a fail. When test program A's test result is test exception information, the shared information changes. Test program A notifies the session management module, which broadcasts the information to all programs registered to monitor program A, notifying production monitoring program C. If production monitoring program C determines, based on its own business operation rules, that it needs to call a public function for shared information in the session management module to obtain updated shared information, then test program A becomes the testing module and program C becomes the monitoring module. Program C needs to obtain the updated shared information of test program A and promptly take corresponding intervention measures based on the test exception information of test program A, such as issuing an alarm or stopping the execution of test program A to facilitate needle clearing.
[0079] In one example, a third-party data analysis program analyzes the test results of a test program, optimizes the test plan, and achieves adaptive testing. When the third-party data analysis program is program D, and the program that tests the device under test is test program A, program D registers in the session table of the session management module and monitors test program A. Test program A's shared information identifier can be an identifier for shared test result data or an identifier for the quantity of shared test result data. When the quantity of program A's test result data exceeds a preset threshold, i.e., when program A's shared information changes, program A notifies the session management module. The session management module broadcasts the information to all programs registered to monitor program A, notifying third-party data analysis program D. If third-party data analysis program D determines, based on its own business operation rules, that it needs to call a public function for shared information in the session management module to obtain updated shared information, then test program A becomes the testing module and program D becomes the monitoring module. Program D needs to obtain the updated shared information of test program A, thereby intervening in the test process and promptly analyzing the test results based on the quantity of program A's test result data to optimize and adjust the current test plan, achieving adaptive testing.
[0080] In one example, when the device maintenance self-test program is Program E and the program for testing the device under test is Test Program A, Program E is registered in the session table of the session management module and monitors Test Program A. The shared information identifier of Test Program A can be at least one of a shared test exception information identifier, a shared test time identifier, or a shared test status identifier. When Test Program A's test is abnormal, or the test time reaches a preset time threshold, or the test status is idle, the shared information changes, and Program A notifies the session management module. The session management module broadcasts information to all programs registered to monitor Program A, namely, notifying Device Maintenance Self-Test Program E. Device Maintenance Self-Test Program E can implement the device maintenance self-test program using the same principle as described above to ensure that the accuracy of the test results meets the preset threshold. Similarly, in another example, Yield Analysis Program F is registered in the session table of the session management module and monitors Test Program A. The shared information identifier of Test Program A can be an identifier for shared test result data information, so that Yield Analysis Program F can perform yield analysis and classify the test results into valid and invalid results. The monitoring process will not be further described. In another example, the fault detection program F is registered in the session table in the session management module and monitors the test program A. The shared information identifier of the test program A may be at least one of the identifier of the shared device temperature information, the identifier of the shared device environment information, and the identifier of the shared fault detection result information. If the device temperature of the test program A is abnormal, the device environment information is abnormal, or the fault detection result information is abnormal, that is, when the shared information of the program A changes, the fault detection program F determines according to its own business operation rules that it needs to call the public function of the shared information in the session management module to obtain the updated shared information. The fault detection program F then obtains the updated shared information of the test program A to perform fault detection. The process is no longer repeated.
[0081] The above programs all require data communication and cross-operation with each other to varying degrees. The session management module of this application can better complete collaborative work and achieve information sharing between multiple programs.
[0082] The technical solution of this embodiment is to receive a demand instruction sent by a session management module, wherein the demand instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module; if the business operation rule meets the first condition, generate an acquisition instruction according to the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module; send the acquisition instruction to the session management module, so that the session management module sends the acquisition instruction to the target test module after receiving the acquisition instruction; receive the shared information corresponding to the shared information identifier sent by the target test module through the session management module, thereby solving the problem that multiple modules cannot complete work efficiently due to the need to frequently obtain shared information of other modules when running, and the problem of low data transmission efficiency, and can improve the efficiency of operation of multiple modules and ensure efficient collaborative work of multiple modules.
[0083] Example 3
[0084] FIG5 is a schematic diagram of the structure of a management device in Example 3 of the present application. This embodiment is applicable to multi-module communication management, such as information sharing during communication and collaboration of multiple test processes. The device can be implemented in software and / or hardware and can be integrated into any device that provides management functions. As shown in FIG5, the management device includes: an update instruction receiving module 310, a monitoring module obtaining module 320, a demand instruction sending module 330, an acquisition instruction receiving module 340, and a shared information receiving module 350.
[0085] The update instruction receiving module 310 is configured to receive an update instruction sent by a target test module, wherein the update instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module, and the target test module is a test module for shared information update.
[0086] The monitoring module obtaining module 320 is configured to query a session table according to the identification information corresponding to the target test module to obtain a monitoring module identification set corresponding to the target test module, wherein the session table is stored in the session management module.
[0087] The demand instruction sending module 330 is configured to send a demand instruction to the monitoring module corresponding to each monitoring module identifier in the monitoring module identifier set, wherein the demand instruction carries the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module.
[0088] The acquisition instruction receiving module 340 is configured to receive the acquisition instruction sent by the monitoring module and send the acquisition instruction to the target test module so that the target test module sends the shared information corresponding to the shared information identifier to the session management module, wherein the acquisition instruction carries the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module.
[0089] The shared information receiving module 350 is configured to receive the shared information corresponding to the shared information identifier sent by the target test module, and send the shared information corresponding to the shared information identifier to the monitoring module.
[0090] Optionally, it further includes: a session table acquisition module, configured to obtain a session table, wherein the session table includes: identification information corresponding to at least one test module, status information corresponding to at least one test module, attribute information corresponding to each test module identifier, and a public function corresponding to each shared information, wherein the attribute information includes: at least one listening module identifier corresponding to the test module identifier and at least one shared information identifier.
[0091] Optionally, the session table acquisition module is configured to: receive a registration instruction sent by at least one test module or a listening module, and register in the session table with registration information corresponding to the test module or the listening module according to the registration instruction, and update the session table, wherein the registration instruction carries registration information, the registration information of the test module includes identification information, status information, attribute information and a common function corresponding to each shared information, wherein the attribute information of the test module includes at least one shared information identifier corresponding to the test module; the registration information of the listening module includes identification information, status information and attribute information, wherein the attribute information of the listening module includes at least one shared information identifier of the test module to be monitored by the listening module.
[0092] Optionally, the session table acquisition module is configured to: receive an information modification instruction sent by at least one test module or a monitoring module, and modify the session table with modification information corresponding to the test module or the monitoring module according to the information modification instruction, and update the session table, wherein the information modification instruction carries modification information, and the modification information includes at least one of status information, attribute information, and public functions.
[0093] Optionally, it also includes: a status information update module, which is configured to update the status information corresponding to the listening module in the session table according to the identification information corresponding to the listening module if the acquisition instruction sent by the listening module is not received, and / or, if the call success information of the listening module is not received within a preset time, wherein the call success information indicates that the listening module successfully establishes a connection with the corresponding target test module by calling the public function through the session management module, then update the status information corresponding to the target test module in the session table, the shared information identifier corresponding to the public function in the attribute information, and at least one of the public functions according to the public function corresponding to the target test module, and / or, if the shared information corresponding to the shared information identifier sent by the target test module is not received within the preset time, then update the status information corresponding to the target test module in the session table according to the identification information corresponding to the target test module.
[0094] The above-mentioned product can execute the method provided in any embodiment of the present application and has the corresponding functional modules for executing the method.
[0095] Example 4
[0096] FIG6 is a schematic diagram of the structure of a management device in Example 4 of the present application. This embodiment is applicable to multi-module communication management, such as information sharing and process collaboration during multi-module communication. The device can be implemented in software and / or hardware and can be integrated into any device that provides management functions. As shown in FIG6, the management device includes: a demand instruction receiving module 410, an acquisition instruction generating module 420, an acquisition instruction sending module 430, and a shared information sending module 440.
[0097] The demand instruction receiving module 410 is configured to receive a demand instruction sent by the session management module, wherein the demand instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module.
[0098] The acquisition instruction generation module 420 is configured to generate an acquisition instruction according to the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module if the business operation rule meets the first condition.
[0099] The acquisition instruction sending module 430 is configured to send the acquisition instruction to the session management module, so that the session management module sends the acquisition instruction to the target test module after receiving the acquisition instruction.
[0100] The shared information sending module 440 is configured to receive shared information corresponding to the shared information identifier sent by the target test module through the session management module.
[0101] Optionally, the acquisition instruction generation module is configured to: if the test timing within a preset range of the current test timing corresponding to the monitoring module contains a feedback flag, then obtain the first target test timing corresponding to the target waiting result corresponding to the feedback flag; if the first target test timing is the test timing of the target test module, then determine that the business operation rules of the monitoring module meet the first condition; and generate an acquisition instruction based on the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module.
[0102] Optionally, the acquisition instruction generation module is configured to: if the test timing within a preset range of the current test timing corresponding to the monitoring module contains a comparison flag, then obtain a second target test timing corresponding to at least one comparison information corresponding to the comparison flag; if the second target test timing is the test timing of the target test module, then determine that the business operation rules of the monitoring module meet the first condition; and generate an acquisition instruction based on the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module.
[0103] Optionally, the shared information identifier includes: an identifier of the end of a shared test, an identifier of shared test resource occupancy information, an identifier of shared manipulator control information, an identifier of shared test result data information, an identifier of shared test exception information, an identifier of shared test status, an identifier of shared test time, an identifier of shared device temperature information, an identifier of shared device environment information, and at least one of an identifier of shared fault detection result information.
[0104] The above-mentioned product can execute the method provided in any embodiment of the present application and has the corresponding functional modules for executing the method.
[0105] Example 5
[0106] Figure 7 is a schematic diagram of the structure of an ATE test system in Example 5 of the present application. The ATE test system includes an ATE tester and / or tester auxiliary equipment. The tester includes a test head and an industrial computer. The tester auxiliary equipment may be a manipulator or third-party data analysis instrument. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or claimed herein.
[0107] As shown in FIG7 , an ATE test system 10 includes a main control module 11 in at least one ATE tester and / or tester auxiliary device, and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the main control module 11 in the at least one ATE tester and / or tester auxiliary device. The memory stores computer programs executable by at least one processor. The main control module 11 in the ATE tester and / or tester auxiliary device can perform various appropriate actions and processes based on the computer programs stored in ROM 12 or loaded from storage unit 18 into RAM 13. RAM 13 can also store various programs and data required for the operation of the ATE test system 10. The main control module 11, ROM 12, and RAM 13 in the ATE tester and / or tester auxiliary device are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to bus 14.
[0108] Multiple components in the ATE test system 10 are connected to the I / O interface 15, including an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the ATE test system 10 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.
[0109] The main control module 11 in the ATE tester and / or the tester auxiliary equipment can be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the main control module 11 in the ATE tester and / or the tester auxiliary equipment include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), a variety of dedicated artificial intelligence (AI) computing chips, a variety of processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The main control module 11 in the ATE tester and / or the tester auxiliary equipment performs the multiple methods and processes described above, such as the management method.
[0110] In some embodiments, the management method can be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on ATE test system 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by main control module 11 in the ATE tester and / or tester auxiliary device, one or more steps of the management method described above can be performed. Alternatively, in other embodiments, main control module 11 in the ATE tester and / or tester auxiliary device can be configured to perform the management method in any other suitable manner (e.g., via firmware).
[0111] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard parts (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0112] Computer programs for implementing the methods of the present application may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the computer program is executed by the processor, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The computer program may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.
[0113] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. A computer-readable storage medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a RAM, a ROM, an erasable programmable read-only memory (EPROM) or a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0114] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a cathode ray tube (CRT) or a liquid crystal display (LCD) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).
[0115] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.
[0116] A computing system may include a client and a server. The client and server are generally remote from each other and typically interact via a communication network. The client-server relationship arises through computer programs running on the respective computers and establishing a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, a host product within a cloud computing service ecosystem that addresses the management difficulties and limited scalability of traditional physical hosts and virtual private server (VPS) services.
[0117] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the multiple steps described in this application can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of this application can be achieved. This is not limited herein.
Claims
1. A management method, executed by a session management module, wherein the session management module is respectively connected to at least one test module and at least one monitoring module, the method comprising: Receive an update instruction sent by a target test module, wherein the update instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module, and the target test module is a test module for which shared information is updated; querying a session table according to the identification information corresponding to the target test module to obtain a set of monitoring module identifications corresponding to the target test module, wherein the session table is stored in the session management module; Sending a demand instruction to a monitoring module corresponding to each monitoring module identifier in the monitoring module identifier set, wherein the demand instruction carries the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module; Receive an acquisition instruction sent by the monitoring module, and send the acquisition instruction to the target test module, so that the target test module sends the shared information corresponding to the shared information identifier to the session management module, wherein the acquisition instruction carries the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module; The shared information corresponding to the shared information identifier sent by the target test module is received, and the shared information corresponding to the shared information identifier is sent to the monitoring module.
2. The method according to claim 1, before receiving the update instruction sent by the target test module, further comprising: Obtain a session table, wherein the session table includes: identification information corresponding to at least one test module, status information corresponding to at least one test module, attribute information corresponding to each test module identifier in the identification information corresponding to at least one test module, and a common function corresponding to each shared information, wherein the attribute information includes: at least one listening module identifier and at least one shared information identifier corresponding to the test module identifier.
3. The method according to claim 2, wherein: The obtaining of the session table includes: Receive a registration instruction sent by at least one of the test modules or the listening module, and register in the session table with registration information corresponding to at least one of the test modules or the listening module according to the registration instruction, and update the session table, wherein the registration instruction carries the registration information, the registration information of the test module includes identification information, state information, attribute information and a common function corresponding to each shared information, wherein the attribute information of the test module includes at least one shared information identifier corresponding to the test module; the registration information of the listening module includes identification information, state information and attribute information, wherein the attribute information of the listening module includes at least one shared information identifier of the test module to be listened to by the listening module.
4. The method according to claim 3, wherein: The obtaining of the session table includes: Receive an information modification instruction sent by at least one of the test modules or the listening modules, and modify the session table with modification information corresponding to at least one of the test modules or the listening modules according to the information modification instruction, and update the session table, wherein the information modification instruction carries the modification information, and the modification information includes at least one of state information, attribute information, and public functions.
5. The method according to claim 2, further comprising at least one of the following: In response to not receiving the acquisition instruction sent by the monitoring module, updating the state information corresponding to the monitoring module in the session table according to the identification information corresponding to the monitoring module; In response to not receiving the successful call information of the monitoring module within the preset time, wherein: The call success information indicates that the monitoring module successfully establishes a connection with the corresponding target test module by calling the public function through the session management module, and updates the state information corresponding to the target test module in the session table, the shared information identifier corresponding to the public function in the attribute information, and at least one of the public functions according to the public function corresponding to the target test module; In response to not receiving the shared information corresponding to the shared information identifier sent by the target test module within a preset time, updating the state information corresponding to the target test module in the session table according to the identifier information corresponding to the target test module.
6. A management method, executed by a monitoring module, comprising: Receive a demand instruction sent by a session management module, wherein the demand instruction carries identification information corresponding to a target test module and a shared information identifier corresponding to the target test module; In response to the business operation rule satisfying the first condition, generating an acquisition instruction according to the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module; Sending the acquisition instruction to the session management module, so that the session management module sends the acquisition instruction to the target test module after receiving the acquisition instruction; Receive the shared information corresponding to the shared information identifier sent by the target test module through the session management module.
7. The method according to claim 6, wherein: In response to the business operation rule satisfying the first condition, generating an acquisition instruction according to the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module includes: In response to a test timing within a preset range of the current test timing corresponding to the monitoring module including a feedback flag, obtaining a first target test timing corresponding to a target waiting result corresponding to the feedback flag; In response to the first target test sequence being the test sequence of the target test module, determining that the service operation rule of the monitoring module satisfies the first condition; An acquisition instruction is generated according to the identification information corresponding to the target test module and the shared information identification corresponding to the target test module.
8. The method according to claim 6, wherein: In response to the business operation rule satisfying the first condition, generating an acquisition instruction according to the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module includes: In response to a test timing within a preset range of the current test timing corresponding to the monitoring module including a comparison mark, obtaining a second target test timing corresponding to at least one comparison information corresponding to the comparison mark; In response to the second target test sequence being the test sequence of the target test module, determining that the service operation rule of the monitoring module satisfies the first condition; An acquisition instruction is generated according to the identification information corresponding to the target test module and the shared information identification corresponding to the target test module.
9. The method according to claim 6, wherein: The shared information identifier includes: an identifier of the end of a shared test, an identifier of shared test resource occupancy information, an identifier of shared manipulator control information, an identifier of shared test result data information, an identifier of shared test exception information, an identifier of a shared test status, an identifier of a shared test time, an identifier of shared device temperature information, an identifier of shared device environment information, and at least one of an identifier of shared fault detection result information.
10. A management device, comprising: An update instruction receiving module, configured to receive an update instruction sent by a target test module, wherein the update instruction carries identification information corresponding to the target test module and a shared information identifier corresponding to the target test module, and the target test module is a test module for shared information update; A monitoring module obtaining module is configured to query a session table according to the identification information corresponding to the target test module to obtain a monitoring module identification set corresponding to the target test module, wherein the session table is stored in the session management module; A demand instruction sending module is configured to send a demand instruction to a listening module corresponding to each listening module identifier in the listening module identifier set, wherein the demand instruction carries the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module; An acquisition instruction receiving module, configured to receive an acquisition instruction sent by the monitoring module, and send the acquisition instruction to the target test module, so that the target test module sends the shared information corresponding to the shared information identifier to the session management module, wherein the acquisition instruction carries the identification information corresponding to the target test module and the shared information identifier corresponding to the target test module; A shared information receiving module is configured to receive a shared information identification pair sent by the target test module. The corresponding shared information is received, and the shared information corresponding to the shared information identifier is sent to the monitoring module.
11. An automatic test equipment ATE test system, comprising at least one of the following: ATE tester and tester auxiliary equipment, at least one of the ATE tester and the tester auxiliary equipment runs at least one executed computer program to implement the management method described in any one of claims 1-5 or the management method described in any one of claims 6-9.
Citation Information
Patent Citations
Management method and device and ATE test system
CN117424843A
Software testing method and software testing system based on distributed testing node cluster
CN110297766A
Equipment testing method and device, server and readable storage medium
CN111782547A
Information processing method, device, equipment and system
CN112749023A
Processing method and device of test equipment, electronic equipment and storage medium
CN114647544A