Data Unbinding Method, Device, User Terminal and Medium

Abstract

The present invention discloses a data unbinding method, apparatus, user terminal and medium. The method obtains a test process identifier and a module identifier corresponding to a target test module, and then based on the test process identifier and the module identifier, sends an unbinding request to a test database, so that the test database queries relevant test data corresponding to the test process identifier and the module identifier, and unbinds these relevant test data from the test process identifier and the module identifier.

Description

Technical Field

[0001] The present invention relates to the field of product testing technology, and in particular to a data unbinding method, device, user terminal and medium. Background Art

[0002] To ensure product quality during production, products will be tested at multiple test stations, i.e. test nodes. Generally speaking, during the product testing process, products that have been tested at the later stations cannot be taken back to the previous stations for retesting, i.e. product testing cannot be "reflowed". To ensure the effectiveness of this measure, the test software will first perform anti-jump station and anti-fool logic at each station during testing. The anti-jump station logic will confirm whether the test data of the subsequent stations exists and is valid. If so, the anti-jump station logic will feedback an exception and output a "product reflow" exception.

[0003] However, the above logic is fine when the product is produced normally, but there will be problems when it comes to returned products: the returned products will be re-flow tested after rework, but because the returned products may have been tested at multiple stations, there will be a "product reflux" anomaly when the flow test is re-performed, resulting in the inability to complete the test. Summary of the invention

[0004] The present invention provides a data unbinding method, device, user terminal and medium, which can realize the unbinding of product test data, and is conducive to realizing the testing of returned products on the basis of following the "product return" logic.

[0005] In a first aspect, an embodiment of the present specification provides a data unbinding method, the method comprising: obtaining a test process identifier and a module identifier corresponding to a target test module; based on the test process identifier and the module identifier, sending an unbinding request to a test database, so that the test database queries relevant test data corresponding to the test process identifier and the module identifier, and unbinds the relevant test data from the test process identifier and the module identifier.

[0006] Furthermore, the method further includes: receiving unbinding result information fed back by the test database, wherein the unbinding result information is used to indicate whether the unbinding is successful.

[0007] Furthermore, before sending the unbinding request to the test database, the method further includes: establishing a communication connection with the test database. After receiving the unbinding result information fed back by the test database, the method further includes: if the unbinding is determined to be successful based on the unbinding result information, releasing the communication connection with the test database.

[0008] Further, after receiving the unbinding result information fed back by the test database, it further includes: if it is determined that the unbinding fails based on the unbinding result information, resend the unbinding request to the test database.

[0009] Further, obtaining the module identifier of the target test module includes: starting the target test module, reading the module identifier of the target test module; and closing the target test module.

[0010] Further, obtaining the test process identifier corresponding to the target test module includes: presenting an identifier input window to the user; and obtaining the test process identifier input by the user in the identifier input window.

[0011] Further, the method further includes: in response to an unbinding instruction triggered by the user, triggering the execution of obtaining the test process identifier and the module identifier corresponding to the target test module; and based on the process identifier and the module identifier, sending an unbinding request to the test database.

[0012] In a second aspect, an embodiment of the present specification provides a data unbinding device, where the device includes: an obtaining module, configured to obtain the test process identifier and the module identifier corresponding to the target test module; and an unbinding module, configured to send an unbinding request to the test database based on the test process identifier and the module identifier, so that the test database queries the relevant test data corresponding to the test process identifier and the module identifier, and unbinds the relevant test data from the test process identifier and the module identifier.

[0013] In a third aspect, an embodiment of the present specification provides a user terminal, including: a processor, a memory, and a computer program stored on the memory, where when the processor executes the computer program, the steps of the data unbinding method provided in the first aspect are implemented.

[0014] In a fourth aspect, an embodiment of the present specification provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps of the data unbinding method provided in the first aspect are implemented.

[0015] The data unbinding method provided by an embodiment of this specification obtains the test process identifier and module identifier corresponding to the target test module, and based on the test process identifier and module identifier, sends an unbinding request to the test database, so that the test database queries the relevant test data corresponding to the test process identifier and module identifier, and unbinds these relevant test data from the test process identifier and module identifier. In this way, the unbinding of the target test module from the relevant product test data can be achieved online. After unbinding, when performing streamline testing on the target test module again, the anti-skip station logic will not be violated, ensuring that on the basis of following the "product return" logic, the re-streamline testing of the target test module can be realized. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] By reading the following detailed description of the preferred embodiments, various other advantages and benefits will become clear to those of ordinary skill in the art. The drawings are only for the purpose of illustrating the preferred embodiments and are not considered to be a limitation of this specification. Moreover, throughout the drawings, the same reference numerals are used to represent the same components. In the drawings:

[0017] Figure 1 is a flowchart of a data unbinding method provided in the first aspect of the embodiments of this specification;

[0018] Figure 2 is an exemplary communication link diagram provided in the embodiments of this specification;

[0019] Figure 3 is a block diagram of a data unbinding device provided in the second aspect of the embodiments of this specification;

[0020] Figure 4 is a schematic structural diagram of a user terminal provided in the third aspect of the embodiments of this specification. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0021] In order to better understand the technical solutions provided by the embodiments of this specification, the technical solutions of the embodiments of this specification will be described in detail below through the drawings and specific embodiments. It should be understood that the specific features in the embodiments of this specification and the embodiments are detailed descriptions of the technical solutions of the embodiments of this specification, rather than limitations on the technical solutions of this specification. Without conflict, the technical features in the embodiments of this specification and the embodiments can be combined with each other.

[0022] In the first aspect, an embodiment of the present invention provides a data unbinding method, which is applied to a user terminal. As Figure 1 shown, the method may include the following steps S101 to step S102.

[0023] Step S101, obtain the test process identifier and module identifier corresponding to the target test module.

[0024] In this embodiment, the target test module is the module that needs to enter the streamline test again. For example, it can be a repaired module. It can be understood that the module can be a camera module, an LED module, or other product modules that need to be tested by the streamline test, which is specifically determined according to the actual application scenario.

[0025] The test process identifier is the unique identifier of the streamline test process corresponding to the target test module, and the module identifier is the unique identifier of the target test module.

[0026] It can be understood that when the product provider stores the streamline test data of the test module, in order to associate the product project information and the workstations, that is, the test node information included in the streamline test process, the test process identifier can be set as the intermediate medium information. Before the product test, the test process identifier is created first, and the associated workstation process information is established to form a binding relationship.

[0027] The test process identifier can be created according to the needs of the actual application scenario. For example, the test process identifier can be the process card number. As shown in Table 1, the process card number corresponding to a certain product is "YF-202300001", and the workstation process information associated with this process card number includes: Station T01, Station T02, Station T03, Station T04, Station T05, and Station T06. That is to say, the streamline test of this product needs to go through the tests of these six test stations in sequence. During the test process, the execution logic of each test station passed through includes: anti-skip station logic, test item logic, and test item data upload logic, and the test item logic of each test station is determined according to the actual application scenario.

[0028] Table 1

[0029] YF-202300001 T01 T02 T03 T04 T05 T06

[0030] After the test item logic of each test station is completed, the test item data will be uploaded to the test database, and in the test database, the corresponding records include the process card number, module identifier, station, test data, and valid bit corresponding to the current station, as shown in Table 2. Among them, the valid bit is used to indicate whether the test data of the current station is in a valid state. For example, when the valid bit is "1", it means that the test data of the current station is in a valid state, and when the valid bit is "0", it means that the test data of the current station is in an invalid state.

[0031] Table 2

[0032] Process Card Number Module Identification Station Data1 Data2 Data3 Data4 Data5 Valid Bit YF-202300001 523036391200001BOE T02 1 2 3 4 5 1

[0033] After that, the current test database already has test data of module "523036391200001BOE" at station T02, and the valid bit of the test data at station T02 is 1, which is a valid state. If the current module is taken back to station T01 for testing, the anti-station jump logic will return a "product reflux" exception.

[0034] Therefore, before taking the current module back to the T01 station for testing, it is necessary to first execute the data unbinding method provided by this application to unbind the binding relationship of the current module test data in the test database, for example, by setting the valid bit of the relevant test data of the current module to 0, the existing test data of the current module is invalidated. In this way, when the current module is re-streamlined, when searching for valid data of the following stations (i.e., stations T02 to T06) in the test database, no data will be found, and there will be no "product reflux" anomaly.

[0035] Specifically, as an implementation method, in the above step S101, the process of obtaining the module identification of the target test module may include: starting the target test module, reading the module identification of the target test module; and then closing the target test module. It can be understood that the module identification is stored in the target test module, and when the target test module is in a working state, the module identification stored therein can be read by connecting to the target test module. In addition, the present application does not limit the execution order of the step of closing the target test module after completing the module identification reading. For example, it can be executed after reading the module identification of the target test module, or it can be executed after the unbinding is successful.

[0036] As an implementation method, the process of obtaining the test flow identifier corresponding to the target test module may include: displaying an identifier input window to the user; obtaining the test flow identifier input by the user in the identifier input window. Of course, in other implementation methods, the identifier input window can be used not only to input the test flow identifier, but also to input the module identifier.

[0037] As another implementation, a graphic code such as a barcode or a QR code carrying a test process identifier and / or a module identifier may be pre-pasted or sprayed on the test module, and the test process identifier and / or module identifier corresponding to the target test module may be obtained by scanning the graphic code.

[0038] Step S102: Based on the test flow identifier and the module identifier, an unbinding request is sent to the test database, so that the test database queries the relevant test data corresponding to the test flow identifier and the module identifier, and unbinds the relevant test data from the test flow identifier and the module identifier.

[0039] For example, the test database can be the MES (Manufacturing Execution System) database corresponding to the product provider, and the relevant test data is the MES data corresponding to the target test module. The MES system is a production information management system for the workshop execution layer of a manufacturing enterprise. Of course, the test database can also be a separate database used to store product test data.

[0040] Among them, the unbinding request includes the test process identifier and module identifier of the target test module. After the test database receives the unbinding request, it parses the test process identifier and module identifier of the target test module from the unbinding request, and then searches for the corresponding relevant test data through the test process identifier and module identifier, that is, searches for all valid test data corresponding to the test process identifier and module identifier in the test database, and updates the status of these valid test data found to an invalid state, so as to realize the unbinding between the relevant test data and the test process identifier and module identifier, that is, unbinding the test data bound to the target test module in the test database. In this way, the target test module can be streamlined again. During the retesting process, when the anti-jump station logic is executed, the valid test data of the subsequent stations will not be queried in the test database, and the "product reflux" exception will not be output, so as to ensure the smooth completion of the retesting process.

[0041] For example, in the examples shown in Tables 1 and 2 above, for the target test module with the test process identifier "YF-202300001" and the module identifier "523036391200001BOE", if the test database already has test item data for the module at stations T01 to T06, and all valid bits are "1", when it is necessary to re-perform streamline testing of stations T01 to T06 on the module, it is necessary to update the valid bits of the test item data for the module at stations T01 to T06 in the test database to "0".

[0042] Alternatively, in addition to the above-mentioned method of setting and updating the valid bit of data, the unbinding of the relevant test data of the target test module can also be achieved through other implementation methods. For example, a valid binding relationship table and an invalid binding relationship table can be set up in the test database respectively, and the target test module and the relevant test data are removed from the valid binding relationship table and transferred to the invalid binding relationship table to achieve the unbinding of the relevant test data of the target test module. Accordingly, when the streamline test process is performed on the target test module, the valid binding relationship table is queried to see whether the relevant test data exists. If not, the "product reflux" exception will not be output, and after completing the test items of the current station, the test item data of the current station is stored in the valid binding relationship table accordingly.

[0043] Further, in order to determine the unbinding result in a timely manner, after sending an unbinding request to the test database, the data unbinding method provided by this application further includes: receiving the unbinding result information fed back by the test database, where the unbinding result information is used to represent whether the unbinding is successful. That is to say, after the test database responds to the unbinding request, whether the unbinding is successful or failed, it will feed back the unbinding result information to the user terminal to timely inform the user of the unbinding result, facilitating the user to perform subsequent tests on the target test module.

[0044] It can be understood that in order to realize data transmission between the user terminal and the test database, a communication connection needs to be established between the user terminal 100 and the database server 200 configured with the test database, as Figure 2 shown. In an optional implementation manner, in order to reduce resource occupation of the test database, a communication connection with the test database can be established before sending an unbinding request to the test database. After receiving the unbinding result information fed back by the test database, if it is determined that the unbinding is successful based on the unbinding result information, the communication connection with the test database is released.

[0045] In addition, due to network disconnection or other reasons, the test database may have a situation where the unbinding fails, or it may not be able to respond to the unbinding request, resulting in the user terminal not receiving the unbinding result information after exceeding the waiting time. Whether the unbinding result information is not received after exceeding the waiting time or the unbinding result information indicates that the unbinding fails, it is determined that the unbinding result is failed. In this application, if it is determined that the unbinding fails based on the unbinding result information, an unbinding request can be resent to the test database until the unbinding is successful.

[0046] In an optional implementation manner, the unbinding method provided by this application can be initiated by the user performing a preset trigger operation to issue an unbinding instruction, and the user terminal responds to the unbinding instruction triggered by the user and triggers the execution of the above steps S101 to step S102. Specifically, there can be multiple ways for the user to trigger the unbinding instruction. For example, the unbinding instruction can be triggered by clicking an unbinding button set in advance, or alternatively, the unbinding instruction can be triggered by inputting a corresponding password through an input device such as a keyboard or a touch screen, which is not limited here.

[0047] For example, in an application scenario, a test software is installed on the user terminal for performing streamline tests on the module. The data unbinding method provided by this application can be applied to the test software as a function of the test software for unbinding the test data corresponding to the target test module in the test database. When in use, the user can open the test software on the user terminal and connect to the target test module, and then just press the "0" key to trigger the execution of the data unbinding method provided by this application to realize "one-key" unbinding of the test data of the target test module.

[0048] Furthermore, in the specific software implementation process, in order to decouple and improve efficiency, all database operations can be implemented by using stored procedures. A stored procedure is a set of SQL statements for completing specific functions such as the unbinding function. It is stored in the database and is permanently valid after being compiled once. Users execute it by specifying the name of the stored procedure and providing parameters (if the stored procedure has parameters). A stored procedure is an important object in the database. In the case of extremely large amounts of data, using stored procedures can achieve a multiple-fold improvement in efficiency.

[0049] In an alternative embodiment, the test software installed in the user terminal can be connected to the test database through ADO (ActiveX Data Object) technology. After connecting to the test database, the test process identifier, module identifier, etc. can be passed as parameters to the stored procedure pre-set in the test database, and the stored procedure can be executed to achieve the unbinding operation of the test data. Moreover, in order to further decouple the software modules, operations such as database connection, parameter passing, stored procedure execution, and connection release can be encapsulated as classes in advance, and the test software accesses them through class objects.

[0050] In summary, the data unbinding method provided by this application can effectively unbind the test data in the test database, ensuring that on the basis of following the "product return" logic, the re-streamline test of the target test module is achieved. Moreover, compared with the method of manually recording the test process identifier and module identifier and sending them offline to the back-end professionals in the form of a table, and then the back-end professionals operate the test database to unbind the corresponding test data, it greatly reduces the operation complexity, improves the data unbinding efficiency, reduces the occupation of human resources, and at the same time avoids the error risk caused by manual recording and operation, which is beneficial to ensuring the accuracy of the unbinding operation.

[0051] In a second aspect, based on the same inventive concept as the data unbinding method provided in the foregoing first aspect embodiments, the embodiments of the present invention also provide a data unbinding device, as Figure 3 shown. The data unbinding device 30 includes:

[0052] An obtaining module 301, configured to obtain a test process identifier and a module identifier corresponding to a target test module;

[0053] An unbinding module 303, configured to send an unbinding request to the test database based on the test process identifier and the module identifier, so that the test database queries relevant test data corresponding to the test process identifier and the module identifier, and unbinds the relevant test data from the test process identifier and the module identifier.

[0054] In an alternative embodiment, the above data unbinding device 30 further includes: a result receiving module 304, configured to receive the unbinding result information fed back by the test database, where the unbinding result information is used to indicate whether the unbinding is successful.

[0055] In an alternative embodiment, the above data unbinding device 30 further includes: a connection module 302, configured to establish a communication connection with the test database; a connection release module 305, configured to release the communication connection with the test database if it is determined that the unbinding is successful based on the unbinding result information.

[0056] In an alternative embodiment, the above result receiving module 304 is further configured to: if it is determined that the unbinding fails based on the unbinding result information, resend an unbinding request to the test database.

[0057] In an alternative embodiment, the above obtaining module 301 is configured to: start the target test module, read the module identifier of the target test module; and close the target test module.

[0058] In an alternative embodiment, the above obtaining module 301 is configured to: display an identifier input window to the user; and obtain the test process identifier input by the user in the identifier input window.

[0059] In an alternative embodiment, the above data unbinding device 30 further includes: a response module, configured to, in response to an unbinding instruction triggered by the user, trigger and execute the steps of obtaining the test process identifier and the module identifier corresponding to the target test module; and sending an unbinding request to the test database based on the process identifier and the module identifier.

[0060] It should be noted that the above modules may be implemented by software code or by hardware such as integrated circuit chips.

[0061] It should also be noted that for the specific processes of the above modules to implement their respective functions, please refer to the specific content described in the above method embodiments, and details are not described herein again.

[0062] In a third aspect, based on the same inventive concept as the data unbinding method provided in the foregoing embodiments, an embodiment of the present specification further provides a user terminal. As Figure 4 shown, the user terminal includes a memory 404, one or more processors 402, and a computer program stored on the memory 404 and executable on the processor 402. When the processor 402 executes the program, it implements the steps of any one of the embodiments of the data unbinding method provided in the first aspect above.

[0063] Among them, in Figure 4Among them, there is a bus architecture (represented by bus 400). Bus 400 may include any number of interconnected buses and bridges. Bus 400 links together various circuits of one or more processors represented by processor 402 and a memory represented by memory 404. Bus 400 may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and thus will not be further described herein. Bus interface 405 provides an interface between bus 400 and receiver 401 and transmitter 403. Receiver 401 and transmitter 403 may be the same element, i.e., a transceiver, providing a unit for communicating with various other devices over a transmission medium. Processor 402 is responsible for managing bus 400 and general processing, while memory 404 may be used to store data used by processor 402 when performing operations.

[0064] It can be understood that Figure 4 The structure shown is only schematic. The user terminal provided by the embodiments of the present invention may also include more or fewer components than those shown Figure 4 in, or have a configuration different from that shown Figure 4 in. Figure 4 Each component shown in can be implemented by hardware, software, or a combination thereof.

[0065] In a fourth aspect, based on the same inventive concept as the data unbinding method provided in the foregoing embodiments, an embodiment of this specification also provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the steps of any one of the data unbinding methods provided in the first aspect above.

[0066] This specification is described with reference to the flowcharts and / or block diagrams of methods, devices, and computer program products according to the embodiments of this specification. It should be understood that each flow and / or block in the flowchart and / or block diagram, and the combination of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0067] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device that implements the functions in the flow Figure 1one or more processes and / or blocks Figure 1 the functions specified in one or more blocks.

[0068] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus, so that a series of operational steps are performed on the computer or other programmable apparatus to produce a computer-implemented process, and thus the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions specified in one Figure 1 one or more processes and / or blocks Figure 1 or more processes and / or the functions specified in one or more blocks.

[0069] In this specification, relational terms such as "first" and "second" are used solely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual such relationship or order between these entities or operations. Also, the terms "comprises", "comprising", or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that comprises the element. The term "plural" means two or more, including two or greater than two.

[0070] Although the preferred embodiments of the present specification have been described, additional changes and modifications can be made by those skilled in the art once they learn of the basic creative concept. Therefore, the appended claims are intended to be construed to include the preferred embodiments as well as all changes and modifications that fall within the scope of this specification.

[0071] Obviously, those skilled in the art can make various changes and modifications to this specification without departing from the spirit and scope of this specification. Thus, if these modifications and variations of this specification fall within the scope of the claims of this specification and their equivalent technologies, this specification is also intended to include these modifications and variations.

Claims

1. A data unbinding method, characterized in that, The method includes: Before the target test module enters the streamline test process again, obtain the test process identifier and module identifier corresponding to the target test module. The test process identifier is the unique identifier of the streamline test process corresponding to the target test module, and the test process identifier is associated with the workstation process information of the streamline test. The workstation process information includes the test stations passed through by the streamline test in sequence. The execution logic of each test station includes anti-skip station logic, test item logic, and test item data upload logic; Based on the test process identifier and module identifier, send an unbinding request to the test database, so that the test database queries the relevant test data corresponding to the test process identifier and module identifier, and unbinds the relevant test data from the test process identifier and the module identifier. Among them, the test database stores the test item data uploaded after each test station completes the test item logic, as well as the test process identifier, module identifier, station identifier, and valid bit corresponding to the test item data. Unbinding the relevant test data from the test process identifier and the module identifier includes: setting the valid bit of the relevant test data to an invalid state to invalidate the existing test data of the target test module in the streamline test; Among them, obtaining the test process identifier and module identifier corresponding to the target test module includes: displaying an identifier input window to the user, and obtaining the test process identifier input by the user in the identifier input window; starting the target test module, reading the module identifier of the target test module, and closing the target test module; The method further includes: receiving the unbinding result information feedback by the test database, where the unbinding result information is used to indicate whether the unbinding is successful; establishing a communication connection with the test database before sending the unbinding request to the test database; and after receiving the unbinding result information feedback by the test database, if it is determined that the unbinding is successful based on the unbinding result information, releasing the communication connection with the test database.

2. The method according to claim 1, wherein After receiving the unbinding result information feedback by the test database, it further includes: If it is determined that the unbinding fails based on the unbinding result information, resend the unbinding request to the test database.

3. The method according to claim 1, characterized in that The method further includes: In response to the unbinding instruction triggered by the user, triggering the execution of the steps of obtaining the test process identifier and module identifier corresponding to the target test module; and sending an unbinding request to the test database based on the process identifier and module identifier.

4. A data unbinding device, characterized in that, The device includes: An acquisition module, configured to acquire a test process identifier and a module identifier corresponding to a target test module before the target test module enters the streamline test process again. The test process identifier is the unique identifier of the streamline test process corresponding to the target test module, and the test process identifier is associated with the station process information of the streamline test. The station process information includes the test stations passed by the streamline test in sequence, and the execution logic of each test station includes an anti-skip station logic, a test item logic, and a test item data upload logic. An unbinding module, configured to send an unbinding request to a test database based on the test process identifier and the module identifier, so that the test database queries relevant test data corresponding to the test process identifier and the module identifier, and unbinds the relevant test data from the test process identifier and the module identifier. Among them, the test database stores the test item data uploaded after each test station completes the test item logic, as well as the test process identifier, module identifier, station identifier, and valid bit corresponding to the test item data. Unbinding the relevant test data from the test process identifier and the module identifier includes: setting the valid bit of the relevant test data to an invalid state to invalidate the existing test data of the target test module in the streamline test. Among them, acquiring the test process identifier and the module identifier corresponding to the target test module includes: displaying an identifier input window to the user, and acquiring the test process identifier input by the user in the identifier input window; starting the target test module, reading the module identifier of the target test module, and closing the target test module. The data unbinding device further includes: a result receiving module, configured to receive the unbinding result information fed back by the test database, and the unbinding result information is used to indicate whether the unbinding is successful; a connection module, configured to establish a communication connection with the test database before sending the unbinding request to the test database; and a connection release module, configured to release the communication connection with the test database if it is determined that the unbinding is successful based on the unbinding result information.

5. A user terminal, characterized in that, Including: A processor, a memory, and a computer program stored on the memory. When the processor executes the computer program, the steps of the method according to any one of claims 1-3 are implemented.

6. A computer-readable storage medium, characterized in that, A computer program is stored thereon, and when the program is executed by a processor, the steps of the method according to any one of claims 1-3 are implemented.

Images