CN113641963A - Electronic component testing system and deadline auditing method - Google Patents
Electronic component testing system and deadline auditing method Download PDFInfo
- Publication number
- CN113641963A CN113641963A CN202010390952.4A CN202010390952A CN113641963A CN 113641963 A CN113641963 A CN 113641963A CN 202010390952 A CN202010390952 A CN 202010390952A CN 113641963 A CN113641963 A CN 113641963A
- Authority
- CN
- China
- Prior art keywords
- deadline
- component
- time point
- authorization
- auditing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 133
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000013475 authorization Methods 0.000 claims abstract description 101
- 238000012550 audit Methods 0.000 claims description 37
- 238000010998 test method Methods 0.000 claims description 13
- 238000012956 testing procedure Methods 0.000 claims description 10
- 230000000977 initiatory effect Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 8
- 230000008901 benefit Effects 0.000 description 2
- 230000001186 cumulative effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/12—Protecting executable software
- G06F21/121—Restricting unauthorised execution of programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/51—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Multimedia (AREA)
- Technology Law (AREA)
- Quality & Reliability (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
The application provides an electronic component testing system and a deadline auditing method. The testing device comprises a backboard which is electrically connected with at least one testing single board and comprises a time limit auditing component, and the time limit auditing component stores an authorization starting time point and an authorization ending time point. The interface device is electrically connected with the testing device and used for providing a testing instruction. The test device starts a test program according to the test instruction, and after the test program is finished, the deadline auditing component updates the authorized starting time point to a first stopping time point when the test program is finished.
Description
Technical Field
The present invention relates to an electronic device testing system and a deadline auditing method, and more particularly, to an electronic device testing system and a deadline auditing method capable of checking and updating an authorized period.
Background
Generally, a dealer opens a machine to be sold to a customer for trial use, and defines an authorized period for trial use as a sale policy of the machine. The method has the advantages that the customer can install the machine on the production line firstly, so that the trial time is more abundant, and the function and the working benefit of the machine can be evaluated on site. However, there is a risk to the business, for example, if the customer subsequently does not purchase the machine or approve the machine, in which case the business may not be able to retrieve the machine successfully. In addition, since the machines are still in the customer's place, the customer may go on to use the free machines for overdue against the contractual spirit. Therefore, the client can not only cause loss to the business but also give the client a malicious opportunity to take a skimming.
In order to solve the problem that the client uses the machine after term, part of operators add the authority to the operation program of the machine so as to prevent the client from continuing to use the machine under the condition of no authority. However, in practice, the authority of the locking operation program is easily cracked or bypassed, for example, the internal time of the system may be modified to avoid the check during the authorization period, so that the purpose of stopping the machine from being used for a long time is not easily achieved. Accordingly, there is a need for a new system and method for checking authorization periods to ensure that customers cannot use machines outside of the authorization period, thereby reducing operator losses.
Disclosure of Invention
In view of the above, the present disclosure provides an electronic device testing system, in which a deadline checking component is designed on a machine, and before starting, the deadline checking component determines a checking authorization period, because hardware is used to avoid the checking from being bypassed. In addition, the deadline audit component automatically updates the authorization period to prevent the client from modifying the internal time of the system to avoid checking the authorization period.
The application provides an electronic component testing system, which comprises a testing device and an interface device, wherein the testing device comprises a back plate, the back plate is used for being electrically connected with at least one testing single plate, the back plate comprises a time limit auditing component, and the time limit auditing component stores an authorization starting time point and an authorization ending time point. The interface device is electrically connected with the testing device and used for providing a testing instruction. The test device starts a test program according to the test instruction, and after the test program is finished, the deadline auditing component updates the authorized starting time point to a first stopping time point when the test program is finished.
In some embodiments, when the testing device receives the testing instruction, the deadline auditing component may check whether the first execution time in the testing instruction is later than the authorized start time, and the testing device may determine whether to start the testing procedure. When the first execution time point is later than the authorization start time point, the deadline auditing component can generate an auditing passing signal, and the testing device starts a testing program according to the auditing passing signal. When the first execution time point is not later than the authorization start time point, the deadline auditing component does not generate an auditing passing signal.
In some embodiments, when the testing device receives the testing command, the deadline checking component may further check whether the first execution time is earlier than the authorized termination time, and the testing device may determine whether to initiate the testing procedure. When the first execution time point is earlier than the authorization termination time point, the deadline auditing component can generate an auditing passing signal, and the testing device starts a testing program according to the auditing passing signal. When the first execution time point is not earlier than the authorization termination time point, the deadline auditing component does not generate an auditing passing signal.
In some embodiments, the deadline auditing component may check whether the first execution time is earlier than the first stop time before the deadline auditing component updates the authorized start time to the first stop time. When the deadline checking component checks that the first execution time point is not earlier than the first stop time point, the deadline checking component may accumulate the internal timing value of the first execution time point to obtain a real stop time point, and the deadline checking component may update the authorized start time point to the real stop time point.
The application provides a deadline auditing method, which can judge the checking authorization period by a deadline auditing component and automatically update the authorization period by the deadline auditing component, and can prevent a client from modifying the internal time of a system to avoid the checking of the authorization period.
The application provides a deadline auditing method, which comprises the following steps. First, a time limit auditing component is provided, and the time limit auditing component stores an authorization starting time point and an authorization ending time point. Then, the test program is started according to the test instruction. When the test program is finished, the authorization starting time point is updated to the first stopping time point when the test program is finished by the limit auditing component.
In some embodiments, the step of starting the test program according to the test instruction further includes the following steps. First, the limit audit component checks whether the first execution time point in the test instruction is later than the authorization start time point. When the first execution time point is later than the authorization start time point, the time limit auditing component generates an auditing passing signal. And then, starting a test program according to the audit passing signal. In addition, the deadline audit component does not generate an audit pass signal when the first execution time is not later than the authorization start time.
In some embodiments, the step of starting the test program according to the test instruction further includes the following steps. First, the deadline checking component checks whether the first execution time point is earlier than an authorized termination time point. When the first execution time point is earlier than the authorization termination time point, the time limit auditing component generates an auditing passing signal. And then, starting a test program according to the audit passing signal. In addition, the deadline auditing component does not generate an audit pass signal when the first execution time point is not earlier than the authorization termination time point.
In some embodiments, before the step of updating the authorized start time to the first stop time when the testing process is ended by the deadline auditing component, the following steps are further included. First, the deadline checking component checks whether the first execution time point is earlier than a first stop time point. When the deadline checking component checks that the first execution time point is not earlier than the first stop time point, the deadline checking component accumulates the internal timing value of the first execution time point to obtain a real stop time point. Then, the authorization start time is updated to the real stop time by the limit auditing component.
In summary, the electronic component testing system and the deadline auditing method provided by the application avoid the customer from modifying the internal time of the system to avoid the check during the authorization period by arranging the deadline auditing component which cannot be bypassed on the machine and utilizing the deadline auditing component to judge the check authorization period. In addition, in the electronic device testing system and the deadline auditing method provided by the application, the deadline auditing component can automatically update the authorization period and check whether the system time is modified again before the system time is updated, and if the deadline auditing component judges that the system time is incorrect, the internal timing value is changed to update the authorization period.
Further details regarding other functions and embodiments of the present application are described below with reference to the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a functional block diagram of an electronic device testing system according to an embodiment of the present application;
FIG. 2 is a timing diagram illustrating the operation of an electronic device testing system according to an embodiment of the present application;
FIG. 3 is a timing diagram illustrating the operation of an electronic device testing system according to another embodiment of the present application;
FIG. 4 is a timing diagram illustrating the operation of an electronic device testing system according to yet another embodiment of the present application;
FIG. 5 is a flowchart illustrating steps of a deadline auditing method according to an embodiment of the present application.
Description of the symbols
1 electronic component test system
10 testing device 100 backboard 102 testing single board
104 deadline auditing component 12 interface device T0 authorization start time
T1 authorizes the termination time T2 the first execution time T3 the first stop time
The procedure of the steps S20-S24 at the first stop time RT4 of T4
Detailed Description
In order to specifically describe the embodiments and achieve the effects of the present application, an embodiment is provided and described below with reference to the drawings.
Referring to fig. 1, fig. 1 is a functional block diagram of an electronic device testing system according to an embodiment of the present application. As shown in fig. 1, the electronic device testing system 1 of the present embodiment includes a testing device 10 and an interface device 12, wherein the testing device 10 is electrically connected to the interface device 12. In practice, the test apparatus 10 may be an automatic test equipment (automatic test equipment), and the interface apparatus 12 may be a computer for operating the automatic test equipment. In one example, the interface device 12 may be loaded with an operation program of the testing device 10, and a user may issue a testing instruction to the testing device 10 from the operation program of the interface device 12, where the testing instruction may cause the testing device 10 to execute a corresponding testing program. Of course, the present embodiment does not limit what kind of test the testing device 10 or the testing program is used for, and those skilled in the art can apply to different target machines with different test items. In addition, the present embodiment also does not limit the testing device 10 to be connected to the interface device 12 by wire or wirelessly, and it is within the scope of the present embodiment as long as the interface device 12 can be used to provide the testing instructions to the testing device 10. Each component of the electronic component test system 1 will be described below.
The testing apparatus 10 includes a back plate 100, wherein the back plate 100 is electrically connected to at least one testing board 102. Here, the test board 102 may be a function card that is pluggable into a corresponding slot of the backplane 100 and may be used to execute a test program. In addition, the backplane 100 further comprises a deadline auditing component 104, wherein the deadline auditing component 104 can be disposed on the backplane 100, and the deadline auditing component 104 can store an authorization start time and an authorization end time. In practice, the deadline auditing component 104 may be an electronic component with computing and storing functions, and the embodiment herein does not particularly limit the kind of the deadline auditing component 104. In one example, the authorization start time point and the authorization end time point represent time intervals during which the test apparatus 10 is legally authorized to be used, that is, the test apparatus 10 can be normally used at any time between the authorization start time point and the authorization end time point. In practice, when the manufacturer provides or installs the electronic device testing system 1, the time point of the authorization start and the time point of the authorization end can be written in the deadline auditing component 104 in advance. That is, since the authorization start time and the authorization end time are written by the vendor, it is naturally ensured that the authorization start time and the authorization end time are correct. In an example, the authorization start time point and the authorization end time point do not necessarily refer to a specific time point of a certain date, but may also be a cumulative number of hours, for example, a trial number of hours may be given, and the embodiment is not limited. In addition, as can be seen from the above description, the authorization start time and the authorization end time are recorded in hardware (e.g., the deadline auditing component 104) and not in software (e.g., an operating program), and the embodiment does not limit how the authorization start time and the authorization end time are written into the deadline auditing component 104.
In practical terms, when the interface device 12 transmits a test command, the deadline auditing component 104 first checks the information in the test command to determine whether to initiate the test procedure. In practice, the test instructions may include system time information of the interface device 12 in addition to instructions for controlling the test device 10 to execute the test program, and the deadline auditing component 104 is used to check the system time information. In one example, the test instruction may include a first execution time point when the test program starts to be executed, or a first stop time point when the test program ends. For convenience of explaining how the deadline audit element 104 checks the system time information in the test command, please refer to fig. 1 and fig. 2 together, and fig. 2 is a timing diagram illustrating the operation of the electronic device testing system according to an embodiment of the present application. As shown, the authorization start time and the authorization end time of the pre-write deadline auditing component 104 are respectively denoted by T0 and T1, and it can be seen that the authorization start time T0 should be earlier than the authorization end time T1.
When the user operates the interface device 12 to issue a test command requesting to start executing the test program, the deadline auditing component 104 checks the system time information included in the test command. Assuming that the system time information (i.e., the first execution time) of the test command requesting the test procedure is T2, the deadline auditing component 104 checks whether the first execution time T2 is later than the authorized start time T0. In the example of fig. 2, the first execution time T2 is indeed later than the authorization start time T0. In one example, the deadline audit component 104 can generate an audit pass signal based thereon, upon which the testing device 10 receives and initiates the testing process. Of course, the deadline auditing component 104 may also generate the audit pass signal based on other determination conditions, for example, the deadline auditing component 104 checks the precedence relationship between the first execution time point T2 and the authorization expiration time point T1 in addition to checking the precedence relationship between the first execution time point T2 and the authorization start time point T0. For example, the deadline audit component 104 checks whether the first execution time T2 is earlier than the authorized expiration time T1. In practice, when the first execution time T2 is later than the authorization start time T0 and the first execution time T2 is earlier than the authorization end time T1, which means that the interface device 12 issues the test command to request the start of the currently legal authorization period of the test procedure (the first execution time T2 is between the authorization start time T0 and the authorization end time T1), the deadline auditing component 104 may generate the audit pass signal to enable the test device 10 to start the test procedure.
Conversely, it should be understood by those skilled in the art that if the deadline audit component 104 checks that the first execution time is earlier than the authorization start time T0, it means that the authorization period has not been reached or the customer use operation has not been opened. At this time, the deadline audit component 104 will not generate an audit pass signal to prevent the customer from prematurely starting using the testing device 10. In addition, if the deadline auditing component 104 checks that the first execution time is later than the authorization expiration time T1, meaning that the authorization period has passed, the deadline auditing component 104 will not generate an audit pass signal to prevent the customer from overdue use of the testing device 10. In other words, the deadline auditing component 104 may determine whether the testing device 10 is currently in the authorized period by checking the first execution time T2, the authorization start time T0 and the authorization end time T1, and determine whether to enable the testing device 10 to start the testing procedure.
On the other hand, when the user operates the interface device 12 to issue the test command to request the test procedure to be ended, the deadline auditing component 104 will also check the system time information included in the test command. Assuming that the system time information (i.e., the first stop time) of the test command requesting the test procedure to be ended is T3, the deadline auditing component 104 detects that the test procedure is ended and updates the authorized start time T0 to the time of the first stop time T3. That is, the first stop time T3 is not recorded, but the first stop time T3 of the previous testing procedure is used as the new authorized start time T0 after the previous testing procedure is finished. Thus, when the next time the interface device 12 issues a test command to start the test procedure, the authorized start time T0 checked by the deadline auditing component 104 is the previous first stop time T3. In a white word, the new authorization initiation point T0 is shifted backwards and closer to the authorization termination point T1, so that modifying the strategy of the authorization initiation point T0 allows the authorization period to be shortened after each use.
Of course, in practice, there may be a case where the user attempts to provide the deadline auditing component 104 with an erroneous first stop time T3, for example, by intentionally modifying the system time information of the interface device 12, so that the interface device 12 includes the erroneous system time information when issuing the test command to end the test procedure. For convenience of description, referring to fig. 1 and fig. 3 together, fig. 3 is a timing diagram illustrating an operation of an electronic device testing system according to another embodiment of the present application. For the example of FIG. 3, since the first execution time T2 is between the authorization start time T0 and the authorization end time T1, the deadline auditing component 104 determines that the current time is within the legal authorization period, so that the deadline auditing component 104 can enable the testing device 10 to initiate the testing procedure. However, it is assumed that the user intentionally modifies the system time information of the interface apparatus 12, so that the system time information including the error, i.e. the error first stop time T4, is included when the interface apparatus 12 issues the test command to request the test program to be ended. At this time, the erroneous first stop time T4 may be modified earlier than the first execution time T2 as shown in fig. 3, and it appears that the test program is stopped before being started, which obviously has a logical problem.
To deal with such issues of intentionally modifying the system time information, the deadline auditing component 104 of the present embodiment may perform one more layer of check before updating the authorization start time T0. For example, the deadline audit component 104 may first check whether the first execution time T2 is earlier than the first stop time T4, and normally the first execution time T2 should be earlier than the first stop time T4. In the example of fig. 3, the first stop time T4 is earlier than the first execution time T2 because the user maliciously modifies the system time information of the interface apparatus 12. In one example, the testing device 10 may automatically issue an alert notification to alert the manufacturer when the deadline checker 104 checks that the first stop time T4 is earlier than the first execution time T2. In addition, it is further important that the deadline audit component 104 correctly updates the authorization start time T0. In practice, the deadline auditing component 104 of this embodiment may also calculate the time itself, so that the deadline auditing component 104 may be considered to have an internal timing value.
Referring to fig. 1 and 4 together, fig. 4 is a timing diagram illustrating an operation of an electronic device testing system according to still another embodiment of the present application. As shown, when the deadline checking component 104 checks that the first stop time T4 is earlier than the first execution time T2, the deadline checking component 104 abandons the updating of the authorized start time T0 with the wrong first stop time T4, but accumulates the internal timer value of the first execution time T2 to obtain the real stop time of the test procedure. Here, assuming that the internal timing value of the deadline auditing component 104 is Δ T, the deadline auditing component 104 may obtain the real stop time RT4 after accumulating the internal timing value Δ T from the first execution time T2. The deadline audit component 104 then updates the authorized start time T0 with the real stop time RT 4. That is, the deadline audit component 104 of the present embodiment may automatically correct the incorrect system time information, and the new authorization start time is calculated from the RT4 when the testing device 10 performs the next testing.
In summary, the deadline checking component 104 of the embodiment still has an opportunity to check the behavior of modifying the system time information, assuming that the user does not modify the system time information seriously, for example, the first stop time T4 is not earlier than the first execution time T2, but only slightly earlier than the first stop time T4 or locks the first stop time T4 to a specific time. For example, the deadline audit component 104 can periodically or randomly check the system time information to check whether the user has modified the system time information in a spot check. In the example of fig. 2, the recorded first execution time T2 and the first stop time T3 are used to calculate the usage time of the test program, and the usage time of the test program is compared with the internal timer value, if there is a difference or difference to a certain extent, the testing apparatus 10 may also automatically issue a warning notification to remind the manufacturer, and update the authorization start time at the next time with the real stop time. Of course, if the deadline audit component 104 ever checks that the system time information is incorrect, the deadline audit component 104 may also automatically increase the frequency of checking the system time information to suppress such behavior and to ensure the interests of the dealer.
For explaining the deadline auditing method of the present application, please refer to fig. 1 and fig. 5 together, and fig. 5 is a flowchart illustrating steps of the deadline auditing method according to an embodiment of the present application. As shown in step S20, a deadline auditing component 104 is provided within the electronic device testing system 1, and the deadline auditing component 104 may store an authorization start time and an authorization end time. In step S22, the testing device 10 in the electronic device testing system 1 may start the testing procedure according to the testing command, which may be from the interface device 12, for example. In step S24, after the testing process of the testing device 10 is completed, the deadline auditing component 104 may update the authorized start time to a first stop time when the testing process is completed. The flow of steps of the deadline auditing method of the present embodiment is fully described in the embodiment of the electronic device testing system 1, and the detailed description of the present embodiment is omitted here.
In summary, the electronic component testing system and the deadline auditing method provided by the application avoid the customer from modifying the internal time of the system to avoid the check during the authorization period by arranging the deadline auditing component which cannot be bypassed on the machine and utilizing the deadline auditing component to judge the check authorization period. In addition, in the electronic device testing system and the deadline auditing method provided by the application, the deadline auditing component can automatically update the authorization period and check whether the system time is modified again before the system time is updated, and if the deadline auditing component judges that the system time is incorrect, the internal timing value is changed to update the authorization period.
The above-described embodiments and/or implementations are only illustrative of the preferred embodiments and/or implementations for implementing the technology of the present application, and are not intended to limit the implementations of the technology of the present application in any way, and those skilled in the art can make many changes or modifications to the equivalent embodiments without departing from the scope of the technology disclosed in the present application, but should still be considered as the technology or implementations substantially the same as the present application.
Claims (15)
1. An electronic component testing system, comprising:
the testing device comprises a backboard, wherein the backboard is used for being electrically connected with at least one testing single board and comprises a deadline auditing component, and the deadline auditing component stores an authorization starting time point and an authorization ending time point;
an interface device electrically connected to the test device for providing a test instruction; and
the test device starts a test program according to the test instruction, and when the test program is finished, the deadline auditing component updates the authorization starting time point to a first stop time point when the test program is finished.
2. The system as claimed in claim 1, wherein the deadline checking component checks whether a first execution time of the test instructions is later than the authorized start time when the test apparatus receives the test instructions, the test apparatus accordingly determining whether to start the test procedure.
3. The system as claimed in claim 2, wherein the deadline auditing component generates an audit pass signal when the first execution time is later than the authorization start time, the testing device initiates the testing procedure according to the audit pass signal.
4. The electronic device testing system of claim 3, wherein the deadline audit component does not generate the audit pass signal when the first execution time is not later than the authorization start time.
5. The system as claimed in claim 2, wherein the deadline checking component further checks whether the first execution time is earlier than the authorized termination time when the testing device receives the testing command, and the testing device determines whether to start the testing procedure accordingly.
6. The system as claimed in claim 5, wherein the deadline auditing component generates an audit pass signal when the first execution time is earlier than the authorization expiration time, the testing device initiates the testing procedure according to the audit pass signal.
7. The electronic device testing system of claim 6, wherein the deadline audit component does not generate the audit pass signal when the first execution time point is not earlier than the authorization expiration time point.
8. The system of claim 1, wherein the deadline checking component checks whether the first execution time is earlier than the first stop time before the deadline checking component updates the authorized start time to the first stop time.
9. The system of claim 8 wherein the deadline checking component increments the first execution time by an internal timer value to obtain a real stop time when the deadline checking component checks that the first execution time is not earlier than the first stop time, the deadline checking component updates the authorized start time to the real stop time.
10. A deadline auditing method, comprising:
providing a deadline auditing component, wherein the deadline auditing component stores an authorization starting time point and an authorization ending time point;
starting a test program according to a test instruction; and
when the test program is finished, the time limit auditing component updates the authorization starting time point to a first stop time point when the test program is finished.
11. The deadline auditing method of claim 10, wherein the step of initiating the test procedure according to the test instruction further comprises:
checking whether a first execution time point in the test instruction is later than the authorization starting time point by the time limit auditing component;
when the first execution time point is later than the authorization start time point, the deadline auditing component generates an auditing passing signal; and
and starting the test program according to the audit passing signal.
12. The method of claim 11, wherein the deadline audit component does not generate the audit pass signal when the first execution time is not later than the authorization start time.
13. The deadline auditing method of claim 11, wherein the step of initiating the test procedure according to the test instruction further comprises:
checking whether the first execution time point is earlier than the authorization termination time point by the deadline checking component;
when the first execution time point is earlier than the authorization termination time point, generating an auditing passing signal by the deadline auditing component; and
and starting the test program according to the audit passing signal.
14. The method of claim 13, wherein the deadline auditing component does not generate the audit pass signal when the first execution time point is not earlier than the authorization expiration time point.
15. The method of claim 10, wherein before the step of updating the authorized start time to the first stop time at the end of the testing process, the deadline auditing component further comprises:
checking whether the first execution time point is earlier than the first stop time point by the deadline checking component;
when the deadline checking component checks that the first execution time point is not earlier than the first stop time point, the deadline checking component accumulates the first execution time point by an internal timing value to obtain a real stop time point; and
the time limit auditing component updates the authorization starting time point to the real stopping time point.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010390952.4A CN113641963A (en) | 2020-05-11 | 2020-05-11 | Electronic component testing system and deadline auditing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010390952.4A CN113641963A (en) | 2020-05-11 | 2020-05-11 | Electronic component testing system and deadline auditing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113641963A true CN113641963A (en) | 2021-11-12 |
Family
ID=78415259
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010390952.4A Pending CN113641963A (en) | 2020-05-11 | 2020-05-11 | Electronic component testing system and deadline auditing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113641963A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1535405A (en) * | 2001-02-27 | 2004-10-06 | �Ҵ���˾ | Controlling access to electronically stored and protected data contents |
| CN101571830A (en) * | 2009-06-19 | 2009-11-04 | 北京航空航天大学 | Automatic closed loop test system of real-time embedded software |
| CN204719150U (en) * | 2014-11-17 | 2015-10-21 | 致茂电子(苏州)有限公司 | Testing device with plug-in power supply |
-
2020
- 2020-05-11 CN CN202010390952.4A patent/CN113641963A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1535405A (en) * | 2001-02-27 | 2004-10-06 | �Ҵ���˾ | Controlling access to electronically stored and protected data contents |
| CN101571830A (en) * | 2009-06-19 | 2009-11-04 | 北京航空航天大学 | Automatic closed loop test system of real-time embedded software |
| CN204719150U (en) * | 2014-11-17 | 2015-10-21 | 致茂电子(苏州)有限公司 | Testing device with plug-in power supply |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9940225B2 (en) | Automated error checking system for a software application and method therefor | |
| US7555749B2 (en) | Software updating system and method | |
| CA2283947C (en) | Program management method and apparatus for gaming device components | |
| CN109189451A (en) | A kind of firmware upgrade method and device | |
| US8095987B2 (en) | Software anti-piracy protection | |
| CN108845812A (en) | Update of plug-in method, apparatus, computer equipment and storage medium | |
| CN109726099A (en) | A kind of application gray scale dissemination method, device and equipment | |
| WO2011075139A1 (en) | Methods and devices for updating firmware of a component using a firmware update application | |
| CN110795128B (en) | Program bug repairing method and device, storage medium and server | |
| CN109992515B (en) | Test method and device and electronic equipment | |
| CN111258850B (en) | Method and device for updating software information based on Linux system | |
| CN104850427B (en) | A kind of code upgrade method and device | |
| CN109445937A (en) | A kind of modularization programming and seamless execution method | |
| US6968998B2 (en) | System and method for ensuring payment for sold or leased equipment | |
| CN113641963A (en) | Electronic component testing system and deadline auditing method | |
| US8079026B2 (en) | Job definition verification system, and method and program thereof | |
| US20230315620A1 (en) | System and Method for Diagnosing a Computing Device in Safe Mode | |
| TWI790440B (en) | Electronic component testing system and time certification method | |
| US20090158269A1 (en) | Software configuration based on entitlement records | |
| CN106845164B (en) | Network-based software authorization method | |
| CN111324537A (en) | Test script-based test method and device and computer equipment | |
| CN113806720A (en) | Software authentication method, system and storage medium supporting offline scene | |
| KR20150070175A (en) | Application modes determined from previous and current states of a license | |
| CN117201072B (en) | User password acquisition method, device, equipment and storage medium | |
| CN113377409B (en) | Method, equipment and storage medium for stabilizing BIOS updating |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |