WO2022247422A1 - 资源队列管理接口的验证方法、电子设备、存储介质 - Google Patents
资源队列管理接口的验证方法、电子设备、存储介质 Download PDFInfo
- Publication number
- WO2022247422A1 WO2022247422A1 PCT/CN2022/082550 CN2022082550W WO2022247422A1 WO 2022247422 A1 WO2022247422 A1 WO 2022247422A1 CN 2022082550 W CN2022082550 W CN 2022082550W WO 2022247422 A1 WO2022247422 A1 WO 2022247422A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- resource
- management interface
- queue management
- request
- resource queue
- Prior art date
Links
- 238000012795 verification Methods 0.000 title claims abstract description 343
- 238000000034 method Methods 0.000 title claims abstract description 115
- 230000008569 process Effects 0.000 claims abstract description 53
- 230000003993 interaction Effects 0.000 claims abstract description 30
- 238000007726 management method Methods 0.000 claims description 752
- 230000004044 response Effects 0.000 claims description 582
- 230000002159 abnormal effect Effects 0.000 claims description 72
- 238000013500 data storage Methods 0.000 claims description 18
- 238000013480 data collection Methods 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 6
- 230000008859 change Effects 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 15
- 238000012545 processing Methods 0.000 description 6
- 238000004364 calculation method Methods 0.000 description 5
- 230000005856 abnormality Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000012856 packing Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
- G06F11/221—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested to test buses, lines or interfaces, e.g. stuck-at or open line faults
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2247—Verification or detection of system hardware configuration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/76—Adapting program code to run in a different environment; Porting
Definitions
- Embodiments of the present disclosure relate to the field of chip technology.
- the resource queue management interface refers to the interface between the master module and the slave module in the chip for transmitting resource queue management signals and resource queue management data.
- the current resource queue management interface verification method mainly uses the resource queue management interface proxy module corresponding to the master module to verify the master module, and uses the resource queue management interface proxy module corresponding to the slave module to verify the slave module.
- Embodiments of the present application provide a method for verifying a resource queue management interface, an electronic device, and a storage medium.
- the present disclosure provides a method for verifying a resource queue management interface, the method comprising: generating a verification instance; connecting the first resource queue management interface of the verification instance with the second resource queue management interface of the main module to be verified In the case of connection, realize the verification of the second resource queue management interface of the main module to be verified by the verification instance; the first resource queue management interface of the verification instance and the third slave module to be verified In the case that the resource queue management interface is connected, the verification of the third resource queue management interface of the slave module to be verified is realized by the verification instance; the first resource queue management interface of the verification instance and the second In the case that both the resource queue management interface and the third resource queue management interface are connected, the verification of the interaction process between the second resource queue management interface and the third resource queue management interface is implemented through the verification instance .
- the present disclosure provides an electronic device, which includes: at least one processor; and a memory, on which at least one program is stored, and when the at least one program is executed by the at least one processor, the An authentication method for any one of the above resource queue management interfaces.
- the present disclosure provides a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, any method for verifying the above-mentioned resource queue management interface is implemented.
- FIG. 1 is a schematic diagram of interaction between a master module and a slave module in the related art
- Fig. 2 is a schematic diagram of verifying the main module by using the resource queue management interface agent module corresponding to the main module in the related art
- Fig. 3 is a schematic diagram of verifying the slave module by using the resource queue management interface proxy module corresponding to the slave module in the related art
- FIG. 4 is a flowchart of a method for verifying a resource queue management interface according to an embodiment of the present disclosure
- FIG. 5 is a schematic diagram of status changes of resources in a resource pool in a scenario where the second resource queue management interface corresponding to the main module to be verified is verified according to an embodiment of the present disclosure
- FIG. 6 is a schematic diagram of state changes of resources in the resource pool in a scenario where the third resource queue management interface corresponding to the slave module to be verified is verified according to an embodiment of the present disclosure
- FIG. 7 is a schematic diagram of a packaged data structure according to an embodiment of the present disclosure.
- FIG. 8 is a block diagram of a device for verifying a resource queue management interface according to an embodiment of the present disclosure
- FIG. 9 is a compositional block diagram of a verification example according to an embodiment of the present disclosure.
- FIG. 1 is a schematic diagram of interaction between a master module and a slave module in the related art.
- the master module includes an interface 1
- the slave module includes an interface 2
- the master module and the slave module transmit resource queue management signals and resource queue management data through the interface 1 and the interface 2 .
- the master module is a resource queue management module
- the slave module is a processing module for requesting resources and receiving queue tasks.
- the interface 1 and the interface 2 as the resource queue management interface can be specifically implemented by using a corresponding number of pins.
- Resource queue management specifically includes four types of operations: resource application, resource release, resource enqueue, and resource dequeue.
- the current resource queue management interface verification method mainly uses the resource queue management interface proxy module corresponding to the master module to verify the master module, and uses the resource queue management interface proxy module corresponding to the slave module to verify the slave module.
- part of the implementation codes of the resource queue management interface proxy module corresponding to the main module and the resource queue management interface proxy module corresponding to the slave module are repeated, and the code maintenance efficiency is low, and it is impossible to implement the master module and slave module.
- the interaction process between the resource queue management interface is verified.
- FIG. 2 is a schematic diagram of verifying the main module by using the resource queue management interface proxy module corresponding to the main module in the related art.
- the resource queue management interface agent module corresponding to the main module transmits resource queue management signals and resource queue management data through interface 3 and interface 1 of the main module.
- the verification process of the main module by the agent module of the resource queue management interface corresponding to the main module may include: sending a valid request signal to the interface 1 of the main module to be verified through the interface 3, the request type used to represent the resource application, and the resources to be applied for type, the number of resources to be applied for; receive the valid response signal and response data sent by the main module to be verified through interface 1 through interface 3; collect the valid request signal sent by interface 3, the request type used to represent the resource application, and the required application
- the type of resources to be applied for, the number of resources to be applied for, and the effective response signal and response data received by the collection interface 3, and the main module to be verified is verified according to the collected data; the request is sent to the interface 1 of the main module to be verified through the interface 3
- FIG. 3 is a schematic diagram of verifying a slave module by using a resource queue management interface agent module corresponding to the slave module in the related art.
- the resource queue management interface proxy module corresponding to the slave module transmits resource queue management signals and resource queue management data with interface 2 of the slave module through interface 4 .
- the process of verifying the slave module by the agent module of the resource queue management interface corresponding to the slave module generally includes: detecting the request valid signal and request type information sent by the slave module to be verified through interface 2 through interface 4; parsing the request type information; if the request The type information indicates that the request type is resource application and resource dequeue, and sends a valid response signal, response data and resource ID to the interface 2 of the slave module to be verified through the interface 4; collects the valid request signal received by the interface 4, the request type information, and Collect the effective response signal, response data and resource ID sent by interface 4, and verify the slave module to be verified according to the collected data; if the request type information indicates that the request type is resource release and resource enqueue, send the slave module to be verified Interface 2 of the module sends a valid response signal; collects the valid request signal and request type information received by interface 4, and collects the valid response signal sent by interface 4; sends the collected data of the four operations to other verification modules for other verification.
- the resource queue management interface proxy module corresponding to the master module needs to collect the data sent and received by interface 3
- the resource queue management interface proxy module corresponding to the slave module needs to collect the data sent and received by interface 4
- the resource queue management interface proxy module corresponding to the master module and the resource queue management interface proxy module corresponding to the slave module are two independent modules, and interface 3 and interface 4 are also different interfaces. Therefore, corresponding codes are required to collect interfaces
- the data sent and received by interface 3 and interface 4 that is to say, the implementation code for collecting the data sent and received by interface 3 and the implementation code for collecting the data sent and received by interface 4 are actually the same, that is, repeated.
- the main module to be verified contains multiple sets of interfaces 1, it is necessary to write corresponding codes for each set of interfaces 1 to realize the verification of the set of interfaces 1, and the codes of different sockets 1 are maintained separately.
- the slave module to be verified contains multiple sets of interfaces 2, it is necessary to write corresponding codes for each set of interfaces 2 to realize the verification of the socket 2, and the codes of different sockets 2 are maintained separately. In this case, it is impossible to share improvements to the code during the verification process, and the pitfalls are often repeated, which reduces the efficiency of code maintenance.
- the resource queue management interface proxy module corresponding to the above-mentioned master module can only verify the resource queue management interface of the master module to be verified, and the resource queue management interface proxy module corresponding to the slave module can only verify the resource queue management interface of the slave module to be verified Verification is performed, but the interaction process of the resource queue management interface between the master module and the slave module cannot be verified.
- the verification of the resource queue management interface refers to the verification of the resource queue management signal and resource queue management data transmitted by the resource queue management interface, as well as the verification of the timing of the transmitted data, so as to ensure the transmission of the resource queue management interface.
- the correctness of resource queue management signals and resource queue management data, and the correctness of the timing of data transmission are the correctness of the resource queue management signals and resource queue management data, and the correctness of the timing of data transmission.
- the master module is responsible for resource queue management, and the slave module is responsible for requesting resources and processing queue tasks.
- resources are the data storage space used by the master module and the slave module in the process of business processing.
- Resources are divided into multiple types and multiple quantities. Different types of resources are distinguished by parameters, such as certain types of resources Have the same base address, and each resource is offset by a fixed amount, but they are all within the maximum offset range.
- the resource ID is the first address of the resource, which is the first address of a series of regular, non-overlapping and non-interfering address sequences.
- Fig. 4 is a flowchart of a verification method of a resource queue management interface according to an embodiment of the present disclosure.
- the method for verifying a resource queue management interface includes steps 400 to 403 .
- a verification instance is generated.
- a verification instance can realize the verification of a set of resource queue management interfaces.
- a verification instance can realize the verification of a set of resource queue management interfaces of the main module to be verified, and can also realize the verification of a set of resource queue management interfaces of the slave module to be verified, and can also realize the verification of a set of resource queue management interfaces of the main module to be verified. Verification of the interaction process between the set of resource queue management interfaces and the set of resource queue management interfaces of the slave modules to be verified.
- two or more verification instances can be generated to realize two or more sets of resource queue management interfaces of the main module to be verified Verification without rewriting the code, which improves the efficiency of code usage.
- two or more verification instances can be generated to realize two or more resource queue management interfaces of the slave module to be verified Verification without rewriting the code, which improves the efficiency of code usage.
- the generation and management process of resources in the resource pool is extracted from the main module, and the generation and management process of resources is set as a global shared process, and the resources in the resource pool are naturally also globally shared resources , for use by verification instances. Different verification instances share the same resource generation and management process, so that resource coverage can be improved during resource generation and management processes, and resource conflicts can be reduced.
- step 401 when the first resource queue management interface of the verification instance is connected to the second resource queue management interface of the main module to be verified, the verification of the second resource queue management interface of the main module to be verified is implemented through the verification instance .
- the resource queue management interface includes four operations: resource application, resource release, resource enqueue and resource dequeue.
- resource application resource application
- resource release resource release
- resource enqueue resource dequeue
- the following methods can be used to generate resources in the resource pool and give the management authority of the resources in the resource pool to the main module to be verified: generate a resource ID sequence corresponding to each resource type according to configuration parameters; The parameters are configured in the main module to be verified; the data storage space address parameter of the resource ID sequence is configured in the main module to be verified; the resource ID sequence is written into the data storage space address corresponding to the data storage space address parameter; After the main module to be verified reads the resource ID sequence from the address of the data storage space, it clears the resource ID sequence.
- the configuration parameters include: resource base address, resource quantity, resource maximum offset range parameter, and resource minimum offset address.
- the resource ID sequence in the resource pool in an initial state, that is, before verification, the resource ID sequence in the resource pool is empty. That is to say, after the management authority of the resources in the resource pool is handed over to the main module to be verified, there is no available resource ID in the resource pool. After the verification is completed, the resource ID sequence in the resource pool should also be empty, so as to ensure that there is no available resource ID in the resource pool, and all resources in the resource pool are returned to the main module to be verified for management.
- Fig. 5 is a schematic diagram of status changes of resources in a resource pool in a scenario where a second resource queue management interface corresponding to a main module to be verified is verified according to an embodiment of the present disclosure.
- the resource ID sequence is generated, the state of all resource IDs in the generated resource ID sequence is idle, after the resource management authority is handed over to the main module to be verified, that is, before verification , the resource ID in the resource pool is empty.
- the status of some resource IDs is changed to occupied state.
- the resource ID in the resource pool is empty.
- the resource application includes two cases of resource application success and resource application failure, and the verification process for these two cases will be described respectively below.
- the verification of the second resource queue management interface of the main module to be verified through the verification instance includes: sending a request valid signal to the second resource queue management interface through the first resource queue management interface, the first request type information and first request data, wherein the first request type information indicates that the request type is resource application, and the first request data includes the type of resource to be applied for and the quantity of resources to be applied for; upon receiving the second request through the first resource queue management interface When the response valid signal and the first response data sent by the resource queue management interface are sent, and the first response data indicates that the resource application is successful, the second response data sent by the second resource queue management interface is continuously received through the first resource queue management interface, Until receiving an invalid response signal sent by the second resource queue management interface, wherein the second response data includes the applied resource ID; adding the applied resource ID to the resource corresponding to the resource type corresponding to the applied resource ID In the ID sequence, the state of the resource ID applied for is set to an idle state; in the case of collecting a valid request signal, the first request type information
- the request valid signal, the first request type information and the first request data are sent in parallel, the response valid signal and the first response data are also received in parallel, and the process of receiving the second response data is also simultaneously
- the response valid signal is received, that is to say, the response valid signal and the second response data are also received in parallel.
- the first response data and the second response data can only be obtained when the response valid signal is received; and the first response data and the second response data cannot be obtained when the response invalid signal is received.
- determining whether the timing of the second resource queue management interface is normal according to the collected second response data quantity and the resource quantity to be applied for includes: When the number of resources is the same, determine that the timing of the second resource queue management interface is normal; when the number of collected second response data is different from the number of resources to be applied for, determine that the timing of the second resource queue management interface is abnormal , and output first alarm information, where the first alarm information is used to indicate that the timing of the second resource queue management interface is abnormal.
- the verification of the second resource queue management interface of the main module to be verified through the verification instance includes: sending a request valid signal to the second resource queue management interface through the first resource queue management interface, the first request type information and first request data, wherein the first request type information indicates that the request type is resource application, and the first request data includes the type of resource to be applied for and the quantity of resources to be applied for; when the second resource is received through the first resource queue management interface When the response valid signal and the first response data sent by the queue management interface, and the first response data indicates that the resource application fails, it is determined that the resource application operation is completed; when the request valid signal is collected, the first request type information and First request data; when the first request type information indicates that the request type is resource application, and the valid response signal and the first response data are collected, and the first response data indicates that the resource application fails, it is determined that the collection of resource application data is completed.
- the method further includes: verifying each resource ID in the applied resource IDs to obtain a first verification result; when the first verification result indicates When each resource ID in the applied resource ID is normal, continue to execute the step of adding the applied resource ID to the resource ID sequence corresponding to the resource type corresponding to the applied resource ID;
- the test result indicates that at least one of the resource IDs applied for is abnormal
- output second warning information the second warning information is used to indicate that at least one of the applied resource IDs is abnormal
- the second warning information may include instructions for indicating Information about abnormal resource IDs and the abnormal resource IDs.
- verifying each resource ID in the applied for resource ID includes: verifying the resource minimum offset address of the applied for resource ID, and the verification result is verification success , and the resource type of the applied resource ID is successfully calculated, and the applied resource ID does not exist in the resource ID sequence corresponding to the corresponding resource type, it is determined that the applied resource ID is normal;
- the verification result of the minimum resource offset address of the applied resource ID is verification failure, or the resource type calculation of the applied resource ID fails, or there is a corresponding resource type for the applied resource ID If the corresponding resource ID is in the sequence, it is determined that the requested resource ID is abnormal.
- the applied resource ID is the resource ID in the resource pool, and different verification instances share the same resource pool.
- implementing the verification of the second resource queue management interface of the main module to be verified through the verification instance includes: reading at least one resource ID in an idle state, and converting the read resource ID from the corresponding resource ID to The resource ID sequence corresponding to the resource type is deleted, which means that these resource IDs have been released and can no longer be used as incentives; the request valid signal is sent to the second resource queue management interface through the first resource queue management interface, and the second request type Information and second request data, wherein the second request type information indicates that the request type is resource release, and the second request data includes the number of resources that need to be released, that is, the number of resource IDs read; the read resource IDs are included in the Among the three request data, the third request data is sent to the second resource queue management interface through the first resource queue management interface; after sending all the resource IDs read by sending the third request data, the request valid signal is converted into Request an invalid signal and send the request invalid signal to the second resource queue management interface through the first resource queue management interface; in the case of receiving
- the request valid signal, the second request type information, and the second request data are sent in parallel, and the request valid signal is also sent while the third request data is sent, that is, the request valid signal and The third request data is also sent in parallel.
- the sending of the second request type information, the second request data, and the third request data can be accepted by the receiving end. get.
- the determining whether the timing of the second resource queue management interface is normal according to the collected quantity of the third request data and the quantity of resources to be released includes: in the collected When the quantity of the third request data is the same as the quantity of resources to be released, it is determined that the timing of the second resource queue management interface is normal; If the resource quantities are not the same, determine that the timing of the second resource queue management interface is abnormal, and output third alarm information, where the third alarm information is used to indicate that the timing of the second resource queue management interface is abnormal.
- implementing the verification of the second resource queue management interface of the main module to be verified through the verification instance includes: reading a resource ID in an idle state, and modifying the state of the read resource ID to an occupied state; Send a request valid signal, third request type information, and fourth request data to the second resource queue management interface through the first resource queue management interface, wherein the third request type information indicates that the request type is resource enqueue, and the fourth request data includes The read resource ID; the enqueue feature parameter corresponding to the read resource ID is included in the fifth request data and the fifth request data is sent to the second resource queue management interface through the first resource queue management interface; After sending the fifth request data and sending all the characteristic parameters of the enqueue, convert the request valid signal into a request invalid signal and send the request invalid signal to the second resource queue management interface through the first resource queue management interface; When the queue management interface receives a valid response signal sent by the second resource queue management interface, it determines that the resource enqueue operation is completed; when the queue management interface receives a valid
- the request valid signal, the third request type information, and the fourth request data are sent in parallel, and while the fifth request data is sent, the request valid signal is also sent, that is, the fifth request data and request valid signals are also sent in parallel.
- the third request type information, fourth request data, and fifth request data can only be sent by the receiving end. get.
- determining whether the timing of the second resource queue management interface is normal according to the collected fifth request data quantity and the read quantity of enqueue characteristic parameters corresponding to the resource ID includes: When the quantity of requested data is the same as the quantity of enqueue characteristic parameters corresponding to the read resource ID, it is determined that the timing of the second resource queue management interface is normal; the collected fifth request data quantity and the read resource ID If the numbers of corresponding enqueue feature parameters are different, determine that the timing of the second resource queue management interface is abnormal, and output fourth alarm information, where the fourth alarm information is used to indicate that the timing of the second resource queue management interface is abnormal.
- implementing the verification of the second resource queue management interface of the main module to be verified through the verification instance includes: receiving a queue information sent by the second resource queue management interface through the first resource queue management interface The queue task indicates a valid signal or the queue task indicates an invalid signal; the request valid signal, the fourth request type information and the sixth request data are sent to the second resource queue management interface through the first resource queue management interface, wherein the fourth request type information indicates The request type is resource dequeue, and the sixth request data includes the dequeue queue number; after receiving the response valid signal sent by the second resource queue management interface through the first resource queue management interface, the third response data, and the third response data indicating If the dequeue is successful, and the queue task indication signal corresponding to the dequeue queue number is an invalid queue task indication signal, the fifth alarm information is output, and the fifth alarm information is used to indicate the timing of the second resource queue management interface Abnormal; collect the queue task indication valid signal of the queue or the queue task indication invalid signal; in the case of collecting a valid
- the request valid signal, the fourth request type information and the sixth request data are sent in parallel, and the response valid signal and the third response data are also sent in parallel.
- implementing the verification of the second resource queue management interface of the main module to be verified through the verification instance further includes: receiving a valid response signal sent by the second resource queue management interface through the first resource queue management interface, The third response data, when the third response data indicates that dequeue failure, and the queue task indication signal corresponding to the dequeue queue number is a queue task indication valid signal, receive the second resource through the first resource queue management interface The fourth response data sent by the queue management interface; in the case that the fourth response data includes an error code that the queue is empty, the sixth alarm information is output, and the sixth alarm information is used to indicate that the timing of the second resource queue management interface is abnormal; When the valid response signal and the third response data are received, and the third response data indicates that dequeuing fails, the fourth response data is collected.
- the response valid signal and the third response data are sent in parallel.
- implementing the verification of the second resource queue management interface of the main module to be verified through the verification instance further includes: receiving a valid response signal sent by the second resource queue management interface through the first resource queue management interface, The third response data, when the third response data indicates that the dequeue is successful, and the queue task indication signal corresponding to the dequeue queue number is a queue task indication valid signal, receive the second resource queue through the first resource queue management interface
- the fifth response data sent by the management interface wherein the fifth response data includes: the first resource ID in the resource ID sequence corresponding to the dequeue queue number; modify the state of the first resource ID to an idle state; If the valid response signal and the third response data are collected, and the third response data indicates that the dequeue is successful, the fifth response data is collected.
- implementing the verification of the second resource queue management interface of the main module to be verified through the verification instance further includes: verifying the first resource ID to obtain the second verification result; In the case of indicating that the first resource ID is normal, continue to execute the step of modifying the state of the first resource ID to an idle state; when the second verification result indicates that the first resource ID is abnormal, output the seventh warning message , the seventh alarm information is used to indicate that the first resource ID is abnormal.
- verifying the first resource ID includes: the verification result obtained after verifying the resource minimum offset address of the first resource ID is that the verification is successful, and verifying the first resource ID If the resource type of ID is successfully calculated, and the first resource ID does not exist in the resource ID sequence corresponding to the corresponding resource type, and the state of the first resource ID is idle, it is determined that the first resource ID is normal;
- the verification result of verifying the resource minimum offset address of the first resource ID is a verification failure, or the calculation of the resource type of the first resource ID fails, or there is a corresponding resource type corresponding to the first resource ID In the sequence of resource IDs, and the state of the first resource ID is occupied, it is determined that the first resource ID is abnormal.
- implementing the verification of the second resource queue management interface of the main module to be verified through the verification instance further includes: receiving a valid response signal sent by the second resource queue management interface through the first resource queue management interface, The third response data, when the third response data indicates that dequeue failure, and the queue task indication signal corresponding to the dequeue queue number is a queue task indication invalid signal, receive the sixth resource queue management interface sent by the second resource Response data, wherein the sixth response data includes an error code; when the response valid signal, the third response data, and the queue task indication invalid signal are collected, and the third response data indicates failure to dequeue, the sixth response data is collected.
- the verification method of the resource queue management interface further includes: packing the data collected during the verification process of the above four operations and sending them to other verification modules for other verification, the packaged data structure As shown in Figure 7.
- step 402 when the first resource queue management interface of the verification instance is connected to the third resource queue management interface of the slave module to be verified, the verification of the third resource queue management interface of the slave module to be verified is realized through the verification instance .
- the resource queue management interface includes four operations: resource application, resource release, resource enqueue and resource dequeue.
- resource application resource application
- resource release resource release
- resource enqueue resource dequeue
- the resources in the resource pool need to be generated, and the configuration parameters of the generated resources in the resource pool are sent to the slave module to be verified , so that the slave module to be verified can work normally.
- the resources in the resource pool may be generated in the following manner: generating a resource ID sequence corresponding to each resource type according to configuration parameters.
- the configuration parameters include: resource base address, resource quantity, resource maximum offset range parameter, and resource minimum offset address.
- the resource ID sequence in the resource pool in the initial state, that is, before verification, is not empty, that is, there are available resources in the resource pool, and the state of the resources in the resource pool must be idle.
- the resource ID sequence in the resource pool should also be non-empty, ensuring that the number of resource ID sequences in the resource pool is the same as the number of resource ID sequences in the resource pool in the initial state, and the resources in the resource pool
- the state of the ID must also be in an idle state to ensure that there are no abnormal resources in the slave module to be verified, and no resource tasks remain inside the slave module to be verified.
- FIG. 6 is a schematic diagram of state changes of resources in the resource pool in a scenario where the third resource queue management interface corresponding to the slave module to be verified is verified according to the embodiment of the present application.
- the resource ID sequence in the resource pool is not empty, the number of resource ID sequences is the same, and the state of resource ID is also idle.
- some resources The status of the ID is changed to Occupied.
- the resource application includes two cases of resource application success and resource application failure, and the verification processes of the two cases are described below respectively.
- implementing the verification of the third resource queue management interface of the slave module to be verified through the verification instance includes:
- the first request type information and the first request data sent by the third resource queue management interface through the first resource queue management interface indicates that the request type is a resource application
- the first request data includes In the case of the resource type that needs to be applied for and the number of resources that need to be applied for, search for the resource ID in the idle state in the resource ID sequence corresponding to the resource type that needs to be applied for; if the number of resource IDs that are found in the idle state is greater than or equal to When the number of resources needs to be applied for, select N resource IDs from the found resource IDs in the idle state, change the status of the selected N resource IDs to the occupied state, and the selected N resource IDs can no longer be used as Encourage use, where N is the number of resources that need to be applied for; send a valid response signal and first response data to the third resource queue management interface through the first resource queue management interface, wherein the first response data indicates that the resource application is successful; will select The N resource IDs of the resource are included in the second
- the request valid signal, the first request type information, and the first request data are received in parallel, the response valid signal and the first response data are sent in parallel, and while the second response data is sent, the In addition to the valid response signal, that is to say, the second response data and the valid response signal are also sent in parallel.
- determining whether the timing of the third resource queue management interface is normal according to the collected second response data quantity and the resource quantity to be applied for includes: When the number of resources is the same, determine that the timing of the third resource queue management interface is normal; when the number of collected second response data is different from the number of resources to be applied for, determine that the timing of the third resource queue management interface is abnormal , outputting eighth alarm information, where the eighth alarm information is used to indicate that the timing of the third resource queue management interface is abnormal.
- implementing the verification of the third resource queue management interface of the slave module to be verified through the verification instance includes: after receiving the request valid signal sent by the third resource queue management interface through the first resource queue management interface, the second A request type information and first request data, where the first request type information indicates that the request type is resource application, and when the first request data includes the type of resource to be applied for and the quantity of resources to be applied for, in the case of the type of resource to be applied for Searching for resource IDs in the idle state in the resource ID sequence; when the number of found resource IDs in the idle state is less than the number of resources to be applied for, send a response to the third resource queue management interface through the first resource queue management interface A valid signal and first response data, wherein the first response data indicates that the resource application has failed; if the request valid signal is collected, the first request type information and the first request data are collected; the first request type information indicates the request type For resource application, the valid response signal and the first response data are collected, and if the first response data indicates that the
- implementing the verification of the third resource queue management interface of the slave module to be verified through the verification instance includes: after receiving the request valid signal sent by the third resource queue management interface through the first resource queue management interface, the second 2. Request type information and second request data.
- the second request type information indicates that the request type is resource release. If the second request data includes the number of resources to be released, the third resource queue management interface is continuously received through the first resource queue management interface.
- the management interface sends a response valid signal; the state of the resource ID to be released is changed to an idle state; when the request valid signal is collected, the second request type information and the second request data are collected; the second request type information indicates the request
- the type is resource release, continue to collect the third request data until an invalid request signal is received; in the case of collecting a valid response signal, determine the third request data according to the amount of the collected third request data and the amount of resources that need to be released. Whether the timing of the three-resource queue management interface is normal.
- the request valid signal, the second request type information, and the second request data are sent in parallel, and the request valid signal is also sent while the third request data is sent, that is, the request valid signal and The third request data is also sent in parallel.
- the second request type information, second request data, and third request data can only be obtained by the receiving end when the request valid signal is sent in parallel with the second request type information, second request data, and third request data.
- implementing the verification of the third resource queue management interface of the slave module to be verified through the verification instance further includes: verifying each of the resource IDs that need to be released to obtain the third verification result; When the third check result indicates that each of the resource IDs that need to be released is normal, continue to perform the step of modifying the state of the resource ID that needs to be released to an idle state; in the third check result that indicates that the resource ID that needs to be released In the case of at least one abnormality, the ninth warning information is output.
- the ninth warning information is used to indicate that at least one resource ID that needs to be released is abnormal.
- the ninth warning information may include information indicating that the resource ID is abnormal, and the abnormal resource ID .
- verifying each of the resource IDs that need to be released includes: after verifying the resource minimum offset address of the resource ID that needs to be released, the verification result is that the verification is successful; If the resource type of the resource ID that needs to be released is successfully calculated, and the resource ID that needs to be released does not exist in the resource ID sequence corresponding to the resource type, it is determined that the resource ID that needs to be released is normal; The verification result of the resource minimum offset address of the resource ID is verification failure, or the calculation of the resource type of the resource ID to be released fails, or the resource ID to be released has a resource corresponding to the resource type In the case of the ID sequence, it is determined that the ID of the resource that needs to be released is abnormal.
- determining whether the timing of the third resource queue management interface is normal according to the collected quantity of the third request data and the quantity of resources to be released includes: When the number of resources is the same, determine that the timing of the third resource queue management interface is normal; when the amount of collected third request data is not the same as the number of resources to be released, determine that the timing of the third resource queue management interface is abnormal , outputting tenth alarm information, where the tenth alarm information is used to indicate that the timing of the third resource queue interface is abnormal.
- implementing the verification of the third resource queue management interface of the slave module to be verified through the verification instance includes:
- the third request type information and the fourth request data sent by the third resource queue management interface through the first resource queue management interface the third request type information indicates that the request type is resource enqueue
- the fourth request data In the case of including the resource ID of enqueue, continue to receive the fifth request data sent by the third resource queue management interface through the first resource queue management interface until the request invalid signal is received, wherein the fifth request data includes: enqueue The queue-entry feature parameter corresponding to the resource ID of the resource ID; send a valid response signal to the third resource queue management interface through the first resource queue management interface; modify the state of the resource ID that has entered the queue to an idle state; when the valid request signal is collected Next, collect the third request type information and the fourth request data; in the case where the third request type information indicates that the request type is resource enqueue, continue to collect the fifth request data until the request invalid signal is received; when the response is collected In the case of a valid signal, it is determined whether the timing of the third resource queue management interface
- the request valid signal, the third request type information, and the fourth request data are received in parallel, and while receiving the fifth request data, the request valid signal is also received, that is, the fifth request data and request valid signals are also received in parallel.
- the third request type information, the fourth request data and the fifth request data will be obtained only when the request valid signal is received.
- implementing the verification of the third resource queue management interface of the slave module to be verified through the verification instance further includes: verifying the resource IDs enqueued to obtain the fourth verification result; In the case of indicating that the resource ID entering the queue is normal, continue to execute the step of modifying the status of the resource ID entering the queue to an idle state; in the case of an abnormal resource ID entering the queue, output the eleventh alarm information, and the eleventh alarm The information is used to indicate that the enqueued resource ID is abnormal.
- verifying the resource ID entering the queue includes: after verifying the resource minimum offset address of the resource ID entering the queue, the verification result is that the verification is successful; If the calculation of the resource type is successful, the resource ID that enters the queue does not exist in the resource ID sequence corresponding to the resource type, and the status of the resource ID that enters the queue is occupied, it is determined that the resource ID that enters the queue is normal;
- the verification result of checking the resource minimum offset address of the resource ID of the team is a verification failure, or the calculation of the resource type of the resource ID entering the queue fails, or there is a resource corresponding to the resource type corresponding to the resource ID entering the queue In the ID sequence, or when the state of the resource ID entering the queue is idle, it is determined that the resource ID entering the queue is abnormal.
- determining whether the sequence of the third resource queue management interface is normal according to the collected quantity of fifth request data and the quantity of enqueue characteristic parameters includes: When the number of characteristic parameters is the same, determine that the timing of the third resource queue management interface is normal; when the number of collected fifth request data is not the same as the number of enqueue characteristic parameters, determine that the third resource queue management interface The timing of the third resource queue management interface is abnormal, and the twelfth alarm information is output, and the twelfth alarm information is used to indicate the timing abnormality of the third resource queue management interface.
- implementing the verification of the third resource queue management interface of the slave module to be verified through the verification instance includes: when the resource ID sequence corresponding to the queue number of a queue is not empty, through the first resource The queue management interface sends the queue task indication valid signal of the one queue to the third resource queue management interface; when the resource ID sequence corresponding to the queue number of a queue is empty, through the first resource queue management interface Sending the queue task indication invalid signal of the one queue to the third resource queue management interface; receiving the request valid signal sent by the third resource queue management interface, the fourth request type information and the first resource queue management interface through the first resource queue management interface Sixth request data, the fourth request type information indicates that the request type is resource dequeue, and when the sixth request data includes the dequeue queue number, it is judged whether the resource ID sequence corresponding to the dequeue queue number is empty; When the resource ID sequence corresponding to the queue number is not empty, send a valid response signal and third response data to the third resource queue management interface through the first resource queue management
- the request valid signal, the fourth request type information and the sixth request data are received in parallel, the response valid signal and the third response data are sent in parallel, and the fifth response data and the response valid signal are also sent in parallel of.
- implementing the verification of the third resource queue management interface of the slave module to be verified through the verification instance further includes: when the resource ID sequence corresponding to the dequeued queue number is empty, through the first resource queue
- the management interface sends a valid response signal and third response data to the third resource queue management interface, wherein the third response data indicates failure to dequeue; includes a random error code in the sixth response data, and passes the first resource queue management
- the interface sends the sixth response data to the third resource queue management interface; when the response valid signal, the third response valid signal and the queue task indication invalid signal are collected, and the third response valid signal indicates that dequeuing fails, collect the sixth response data 6.
- Response data when the resource ID sequence corresponding to the dequeued queue number is empty, through the first resource queue
- the management interface sends a valid response signal and third response data to the third resource queue management interface, wherein the third response data indicates failure to dequeue; includes a random error code in the sixth response data, and passes the first resource queue management
- the interface
- the response valid signal and the third response data are sent in parallel.
- the method further includes: packing the data collected in the verification process of the above four operations and sending them to other verification modules for other verification.
- the data structure of the packing is shown in FIG. 7 .
- step 403 when the first resource queue management interface of the verification instance is connected to the second resource queue management interface and the third resource queue management interface at the same time, the second resource queue management interface and the third resource queue are realized through the verification instance Validation of the interaction process between management interfaces.
- the resource queue management interface includes four operations: resource application, resource release, resource enqueue, and resource dequeue.
- resource application resource application
- resource release resource release
- resource enqueue resource dequeue
- the following describes the operation of the second resource queue management interface and the third resource queue respectively for these four operations.
- the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through the verification instance includes: collecting the request valid signal sent by the third resource queue management interface, the first Request type information and first request data, wherein the first request type information indicates that the request type is a resource application, and the first request data includes the type of resource to be applied for and the quantity of resources to be applied for; collect the response sent by the second resource queue management interface Valid signal and first response data; if the first response data indicates that the resource application is successful, continuously collect the second response data sent by the second resource queue management interface until the invalid response signal sent by the second resource queue management interface is collected So far, wherein, the second response data includes: the applied resource ID; according to the quantity of the collected second response data and the quantity of resources to be applied for, it is determined whether the timing of the second resource queue management interface is normal.
- determining whether the timing of the second resource queue management interface is normal according to the collected second response data quantity and the resource quantity to be applied for includes: When the number of resources is the same, determine that the timing of the second resource queue management interface is normal; when the number of collected second response data is different from the number of resources to be applied for, determine that the timing of the second resource queue management interface is abnormal , outputting first alarm information, where the first alarm information is used to indicate that the timing of the second resource queue management interface is abnormal.
- a pre-generated virtual resource ID may be used instead.
- the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through the verification example includes: collecting the request valid signal sent by the third resource queue management interface, the second request Type information and second request data; wherein, the second request type information indicates that the request type is resource release, and the second request data includes the number of resources to be released; continue to collect the third request data sent by the third resource queue management interface until the collection Until the request invalid signal sent by the third resource queue management interface, wherein the third request data includes: the ID of the resource to be released; collecting the response valid signal sent by the second resource queue management interface; according to the collected third request The amount of data and the amount of resources to be released determine whether the timing of the second resource queue management interface is normal.
- a pre-generated virtual resource ID may be used instead.
- determining whether the timing of the second resource queue management interface is normal according to the collected quantity of the third request data and the quantity of resources to be released includes: When the amount of requested data is the same as the amount of resources that need to be released, it is determined that the timing of the second resource queue management interface is normal; when the amount of the collected third request data is equal to the amount of resources that need to be released If not, determine that the timing of the second resource queue management interface is abnormal, and output third alarm information.
- the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through the verification example includes: collecting the request valid signal sent by the third resource queue management interface, the third request Type information and the fourth request data, wherein, the third request type information indicates that the request type is resource enqueue, and the fourth request data includes enqueue resource ID; continue to collect the fifth request data sent by the third resource queue management interface until Until the request invalid signal is collected, the fifth request data includes: the enqueue characteristic parameter corresponding to the resource ID of the enqueue; collect the response valid signal sent by the second resource queue management interface; according to the collected fifth request data quantity
- the number of enqueue characteristic parameters corresponding to enqueue resource IDs determines whether the timing of the third resource queue management interface is normal.
- pre-generated virtual resource IDs may be used instead.
- determining whether the sequence of the third resource queue management interface is normal according to the collected quantity of fifth request data and the quantity of enqueue characteristic parameters includes: When the number of characteristic parameters is the same, determine that the timing of the third resource queue management interface is normal; when the number of collected fifth request data is the same as the number of enqueue characteristic parameters, determine that the timing of the third resource queue management interface The timing is abnormal, and the eleventh alarm information is output, and the eleventh alarm information is used to indicate that the timing of the third resource queue management interface is abnormal.
- the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through the verification instance includes: collecting the queue task indication of a certain queue sent by the second resource queue management interface A valid signal or an invalid signal indicating a queue task; collect a valid request signal sent by the third resource queue management interface, the fourth request type information and the sixth request data, wherein the fourth request type information indicates that the request type is resource dequeue, and the sixth
- the request data includes the queue number of the dequeue; when the valid response signal sent by the second resource queue management interface and the third response data are collected, and the third response data indicates that the dequeue is successful, it is determined that the collection of the resource dequeue data is completed.
- implementing the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through the verification instance further includes: after collecting a valid response signal sent by the second resource queue management interface, The third response data, and in the case that the third response data indicates that dequeuing fails, the fourth response data is collected.
- implementing the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through the verification instance further includes: after collecting a valid response signal sent by the second resource queue management interface, The third response data, and if the third response data indicates that the dequeue is successful, the fifth response data is collected.
- implementing the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through the verification instance further includes: after collecting a valid response signal sent by the second resource queue management interface, The third response data, and if the third response data indicates that dequeuing fails, the sixth response data is collected.
- the method further includes:
- the data collected during the verification process of the above four operations are packaged and sent to other verification modules for other verification.
- the packaged data structure is shown in Figure 7.
- the verification method of the resource queue management interface realizes the verification method of the resource queue management interface by generating a verification instance, because the same verification instance can be used for the second resource queue management interface of the main module to be verified, the The interaction process between the third resource queue management interface, the second resource queue management interface and the third resource queue management interface of the slave module is verified, so that there will be no repeated parts in the code, and only one set of code needs to be maintained.
- the code maintenance efficiency is improved, and the interaction process of the resource queue management interface between the master module and the slave module is realized to be verified.
- the present disclosure also relates to an electronic device, the electronic device includes: at least one processor; a memory, at least one program is stored in the memory, and when the at least one program is executed by at least one processor, any resource queue management interface described above is implemented verification method.
- Processor is a device with data processing capability, which includes but not limited to central processing unit (CPU), etc.; memory is a device with data storage capability, which includes but not limited to random access memory (RAM, more specifically SDRAM, DDR etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH).
- RAM random access memory
- ROM read-only memory
- EEPROM electrically erasable programmable read-only memory
- FLASH flash memory
- the processor and the memory are connected to each other through a bus, and further connected to other components of the computing device.
- the present disclosure also relates to a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, any method for verifying the above-mentioned resource queue management interface is implemented.
- Fig. 8 is a block diagram of an apparatus for verifying a resource queue management interface according to an embodiment of the present disclosure.
- the device for verifying a resource queue management interface includes a generation module 801 and a verification module 802 .
- the generation module 801 is used to generate verification examples.
- the verification module 802 is configured to: when the first resource queue management interface of the verification instance is connected to the second resource queue management interface of the main module to be verified, implement the second resource queue management interface of the main module to be verified through the verification instance Verification; In the case that the first resource queue management interface of the verification instance is connected with the third resource queue management interface of the slave module to be verified, the verification of the third resource queue management interface of the slave module to be verified is realized by the verification instance; In the case that the first resource queue management interface of the verification instance is connected to both the second resource queue management interface and the third resource queue management interface, the verification instance realizes the connection between the second resource queue management interface and the third resource queue management interface Verification of the interaction process between them.
- the verification module 802 is configured to implement the verification of the second resource queue management interface of the main module to be verified through the verification instance in the following manner: send a message to the second resource queue management interface through the first resource queue management interface Request a valid signal, first request type information, and first request data, wherein the first request type information indicates that the request type is a resource application, and the first request data includes the type of resource to be applied for and the number of resources to be applied for;
- the resource queue management interface receives the valid response signal and the first response data sent by the second resource queue management interface, and the first response data indicates that the resource application is successful, it continues to receive the second resource queue management interface through the first resource queue management interface.
- the verification module 802 is further configured to: receive the valid response signal and the first response data sent by the second resource queue management interface through the first resource queue management interface, and the first response data indicates that the resource application fails In this case, it is determined that the resource application operation is completed; when the first request type information indicates that the request type is a resource application, the response valid signal and the first response data are collected, and the first response data indicates that the resource application fails, the resource application data is determined Collection complete.
- the verification module 802 uses the following method to determine whether the timing of the second resource queue management interface is normal according to the quantity of the collected second response data and the quantity of resources to be applied for: in the collected second response data When the number of resources and the number of resources to be applied are the same, determine that the timing of the queue management interface of the second resource is normal; The timing of the queue management interface is abnormal, and the first alarm information is output.
- the verification module 802 is also used to: verify each resource ID in all applied resource IDs to obtain the first verification result; If each resource ID is normal, continue to execute the step of adding the applied resource ID to the resource ID sequence corresponding to the resource type corresponding to the applied resource ID; when the first verification result indicates the applied resource ID When at least one of the resource IDs is abnormal, the second warning information is output.
- the applied resource ID is the resource ID in the resource pool, and different verification instances share the same resource pool.
- the verification module 802 is also used to: generate a resource ID sequence corresponding to each resource type according to the configuration parameters; configure the configuration parameters into the main module to be verified; set the data storage space address of the resource ID sequence The parameters are configured in the main module to be verified; the resource ID sequence is written into the data storage space address corresponding to the data storage space address parameter; after the main module to be verified reads the resource ID sequence from the data storage space address, the resource The ID sequence is cleared.
- the verification module 802 is configured to implement the verification of the second resource queue management interface of the main module to be verified through the verification instance in the following manner: read at least one resource ID that is in an idle state, and read the The resource ID is deleted from the resource ID sequence corresponding to the corresponding resource type; the request valid signal, the second request type information and the second request data are sent to the second resource queue management interface through the first resource queue management interface, wherein the second request The type information indicates that the request type is resource release, and the second request data includes the number of resources to be released, that is, the number of resource IDs read; the read resource IDs are included in the third request data and passed through the first resource queue management interface Send the third request data to the second resource queue management interface; after sending all the resource IDs read by sending the third request data, convert the request valid signal into a request invalid signal and pass the first resource queue management interface The invalid request signal is sent to the second resource queue management interface; in the case of receiving the valid response signal sent by the second resource queue management interface through the first resource
- the verification module 802 is configured to determine whether the timing of the second resource queue management interface is normal according to the collected quantity of the third request data and the quantity of resources to be released: When the quantity of the collected third request data is the same as the quantity of resources to be released, it is determined that the timing of the second resource queue management interface is normal; when the quantity of the collected third request data and If the quantities of resources to be released are different, it is determined that the timing of the second resource queue management interface is abnormal, and outputting third alarm information.
- the verification module 802 is used to realize the verification of the second resource queue management interface of the main module to be verified through the verification instance in the following manner: read a resource ID in an idle state, and read the resource ID The state of the ID is changed to an occupied state; the request valid signal, the third request type information and the fourth request data are sent to the second resource queue management interface through the first resource queue management interface, wherein the third request type information indicates that the request type is resource Enqueue, the fourth request data includes the read resource ID; include the enqueue feature parameter corresponding to the read resource ID in the fifth request data, and send the fifth request data to the first resource queue management interface through the first resource queue management interface 2.
- Resource queue management interface After sending all the characteristic parameters of the queue by sending the fifth request data, convert the request valid signal into a request invalid signal and send the request invalid signal to the second resource queue through the first resource queue management interface Management interface; in the case of receiving a valid response signal sent by the second resource queue management interface through the first resource queue management interface, determine that the resource enqueue operation is completed; in the case of collecting a valid request signal, collect the third request type information and the fourth request data; in the case where the third request type information indicates that the request type is resource enqueuing, continue to collect the fifth request data until an invalid request signal is collected; when a valid response signal is collected, according to The collected quantity of the fifth request data and the read quantity of the enqueue characteristic parameters corresponding to the resource ID determine whether the timing of the second resource queue management interface is normal.
- the verification module 802 is configured to determine whether the timing of the second resource queue management interface is determined according to the number of collected fifth request data and the number of enqueue characteristic parameters corresponding to the read resource ID in the following manner: Normal: When the number of collected fifth request data is the same as the number of enqueue characteristic parameters corresponding to the read resource ID, it is determined that the timing of the second resource queue management interface is normal; the collected fifth request data In the case that the quantity and the quantity of the enqueue characteristic parameters corresponding to the read resource ID are not the same, it is determined that the timing of the second resource queue management interface is abnormal, and the fourth alarm information is output.
- the verification module 802 is configured to realize the verification of the second resource queue management interface of the main module to be verified through the verification instance in the following manner: receiving the second resource through the first resource queue management interface The queue task indication valid signal or the queue task indication invalid signal of a queue sent by the queue management interface; the request valid signal, the fourth request type information and the sixth request data are sent to the second resource queue management interface through the first resource queue management interface, Among them, the fourth request type information indicates that the request type is resource dequeue, and the sixth request data includes the queue number of dequeue; when the response valid signal, the third response data, and the third response data are received through the first resource queue management interface Indicate that the dequeue is successful, and when the queue task indication signal corresponding to the dequeue queue number is an invalid queue task indication signal, output the fifth alarm information; collect the queue task indication valid signal or queue task indication of the one queue Invalid signal; when a valid request signal is collected, the fourth request type information and sixth request data are collected; when a valid request signal is collected; when
- the verification module 802 is further configured to: receive a valid response signal and third response data through the first resource queue management interface, and the third response data indicates that dequeuing fails, and the dequeuing queue
- the queue task indication signal corresponding to the queue number is a valid queue task indication signal
- the fourth response data is received through the first resource queue management interface; when the fourth response data includes an error code indicating that the queue is empty, the sixth alarm information is output ; Collecting the fourth response data when the valid response signal and the third response data are collected, and the third response data indicates that dequeuing fails.
- the verification module 802 is further configured to: receive a valid response signal and third response data through the first resource queue management interface, and the third response data indicates that the dequeue is successful, and the dequeue queue
- the fifth response data is received through the first resource queue management interface, wherein the fifth response data includes: The first resource ID; changing the state of the first resource ID to an idle state; collecting fifth response data when a valid response signal and third response data are collected, and the third response data indicates that the dequeue is successful.
- the verification module 802 is further configured to: verify the first resource ID to obtain a second verification result; if the second verification result indicates that the first resource ID is normal, continue to execute the A step of changing the state of the first resource ID to an idle state; when the second verification result indicates that the first resource ID is abnormal, outputting seventh warning information.
- the verification module 802 is further configured to: receive a valid response signal and third response data through the first resource queue management interface, and the third response data indicates that dequeuing fails, and the dequeuing queue
- the sixth response data is received, wherein the sixth response data includes: a random error code; when the valid response signal and the third response data are collected, and the sixth response data In the case where the third response data indicates that dequeuing fails, the sixth response data is collected.
- the verification module 802 is configured to implement the verification of the third resource queue management interface of the slave module to be verified through the verification instance in the following manner: after receiving the third resource queue management interface through the first resource queue management interface The request valid signal sent by the interface, the first request type information, and the first request data, where the first request type information indicates that the request type is resource application, and the first request data includes the type of resource to be applied for and the number of resources to be applied for, Search for idle resource IDs in the resource ID sequence corresponding to the resource type that needs to be applied for; when the number of found idle resource IDs is greater than or equal to the number of resources that need to be applied for, start from the found idle resource IDs Select N resource IDs from the resource IDs of the state, and modify the states of the selected N resource IDs to the occupied state, where N is the number of resources to be applied for; send it to the third resource queue management interface through the first resource queue management interface Responding to a valid signal and first response data, wherein the first response data indicates that
- the verification module 802 is further configured to: when the number of found resource IDs in the idle state is less than the number of resources to be applied for, report to the third resource queue management interface through the first resource queue management interface Sending a valid response signal and first response data, wherein the first response data indicates resource application failure; the first request type information indicates that the request type is resource application, and the valid response signal and first response data are collected, and the first response data In the case of indicating resource application failure, it is determined that resource application data collection is completed.
- the verification module 802 is configured to determine whether the sequence of the third resource queue management interface is normal according to the quantity of the collected second response data and the quantity of resources to be applied for in the following manner: When the amount of response data is the same as the number of resources to be applied for, determine that the timing of the third resource queue management interface is normal; The timing of the management interface of the three resource queues is abnormal, and the eighth alarm information is output.
- the verification module 802 is configured to implement the verification of the third resource queue management interface of the slave module to be verified through the verification instance in the following manner: after receiving the third resource queue management interface through the first resource queue management interface The request valid signal sent by the interface, the second request type information, and the second request data.
- the second request type information indicates that the request type is resource release.
- the first resource queue management continues to receive the third request data sent by the third resource queue management interface until it receives an invalid request signal sent by the third resource queue management interface, wherein the third request data includes: the ID of the resource to be released;
- the queue management interface sends a valid response signal to the third resource queue management interface; the state of the resource ID that needs to be released is modified to an idle state; when the valid request signal is collected, the second request type information and the second request data are collected; In the case where the second request type information indicates that the request type is resource release, continue to collect the third request data until an invalid request signal is received; in the case of collecting a valid response signal, according to the amount of the collected third request data and the quantity of resources to be released determine whether the timing of the third resource queue management interface is normal.
- the verification module 802 is further configured to: verify each of the resource IDs that need to be released to obtain a third verification result; the third verification result indicates that each of the resource IDs that need to be released If all are normal, continue to execute the step of modifying the state of the resource ID to be released to an idle state; when the third verification result indicates that at least one of the resource IDs to be released is abnormal, output a ninth warning message.
- the verification module 802 is configured to determine whether the timing of the third resource queue management interface is normal according to the collected third request data quantity and the resource quantity to be released in the following manner: When the amount of requested data is the same as the amount of resources to be released, determine that the timing of the third resource queue management interface is normal; The timing of the three-resource queue management interface is abnormal, and the tenth alarm information is output.
- the verification module 802 is configured to implement the verification of the third resource queue management interface of the slave module to be verified through the verification instance in the following manner: after receiving the third resource queue management interface through the first resource queue management interface The request valid signal sent by the interface, the third request type information and the fourth request data, the third request type information indicates that the request type is resource enqueue, and the fourth request data includes the resource ID enqueued, through the first resource queue
- the management interface continues to receive the fifth request data sent by the third resource queue management interface until the request invalid signal is received, wherein the fifth request data includes: the enqueue characteristic parameter corresponding to the enqueue resource ID;
- the management interface sends a valid response signal to the third resource queue management interface; the state of the resource ID that enters the team is modified to an idle state; when the valid signal of the request is collected, the third request type information and the fourth request data are collected;
- the third request type information indicates that the request type is resource enqueue
- the verification module 802 is further configured to: verify the resource IDs entering the queue to obtain a fourth verification result; if the fourth verification result indicates that the resource IDs entering the queue are normal, continue to execute the A step of modifying the state of the resource ID entering the queue to an idle state; when the resource ID entering the queue is abnormal, output an eleventh alarm message.
- the verification module 802 is configured to determine whether the sequence of the third resource queue management interface is normal according to the collected quantity of the fifth request data and the quantity of enqueue characteristic parameters: 5. When the number of requested data is the same as the number of enqueued characteristic parameters, it is determined that the timing of the third resource queue management interface is normal; in the case that the collected fifth request data is not the same as the number of enqueued characteristic parameters , determining that the timing of the third resource queue management interface is abnormal, and outputting twelfth alarm information.
- the verification module 802 is used to realize the verification of the third resource queue management interface of the slave module to be verified through the verification instance in the following manner: when the resource ID sequence corresponding to the queue number of a queue is not empty Next, send the queue task indication valid signal of the one queue to the third resource queue management interface through the first resource queue management interface; when the resource ID sequence corresponding to the queue number of a queue is empty, through The first resource queue management interface sends the queue task indication invalid signal of the one queue to the third resource queue management interface; after receiving the request valid signal sent by the third resource queue management interface through the first resource queue management interface , the fourth request type information and the sixth request data, the fourth request type information indicates that the request type is resource dequeue, and if the sixth request data includes the dequeue queue number, determine the resource ID sequence corresponding to the dequeue queue number Whether it is empty; in the case that the resource ID sequence corresponding to the dequeue queue number is not empty, send a valid response signal and third response data to
- the verification module 802 is further configured to: send a valid response signal to the third resource queue management interface through the first resource queue management interface when the resource ID sequence corresponding to the dequeue queue number is empty, The third response data, wherein, the third response data indicates failure to dequeue; the random error code is included in the sixth response data, and the sixth response data is sent to the third resource queue management interface through the first resource queue management interface ; Collect the sixth response data when the response valid signal and the third response valid signal are collected, and the third response valid signal indicates that dequeuing fails.
- the verification module 802 is configured to realize the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through the verification instance in the following manner: collect the information sent by the third resource queue management interface The request valid signal, the first request type information and the first request data, wherein the first request type information indicates that the request type is a resource application, and the first request data includes the type of resource to be applied for and the quantity of resources to be applied for; the collection of the second The response valid signal and the first response data sent by the resource queue management interface; if the first response data indicates that the resource application is successful, continue to collect the second response data sent by the second resource queue management interface until the second resource queue is collected Until the response invalid signal sent by the management interface, wherein the second response data includes: the applied resource ID; determine whether the timing of the second resource queue management interface is normal according to the quantity of the collected second response data and the quantity of resources to be applied for .
- the verification module 802 is configured to realize the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through a verification instance in the following manner: collect the third resource queue management interface A valid request signal, second request type information, and second request data sent by the interface, wherein the second request type information indicates that the request type is resource release, and the second request data includes the number of resources that need to be released; The third request data sent by the third resource queue management interface is collected until the request invalid signal sent by the third resource queue management interface is collected, wherein the third request data includes: the resource ID to be released; A valid response signal sent by the resource queue management interface; determine whether the timing of the second resource queue management interface is normal according to the collected quantity of the third request data and the quantity of resources to be released.
- the verification module 802 is configured to realize the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through the verification instance in the following manner: collect the information sent by the third resource queue management interface The request valid signal, the third request type information and the fourth request data, wherein, the third request type information indicates that the request type is resource enqueue, and the fourth request data includes enqueue resource ID; continuously collect the third resource queue management interface The fifth request data is sent until an invalid request signal is collected, wherein the fifth request data includes: the enqueue characteristic parameter corresponding to the resource ID of the enqueue; collect the response valid signal sent by the second resource queue management interface; according to the collected Whether the sequence of the third resource queue management interface is normal is determined by the quantity of the received fifth request data and the quantity of enqueue characteristic parameters corresponding to the enqueue resource ID.
- the verification module 802 is configured to realize the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through the verification instance in the following manner: collect the information sent by the second resource queue management interface The queue task indication valid signal or the queue task indication invalid signal of a certain queue; collect the request valid signal sent by the third resource queue management interface, the fourth request type information and the sixth request data, wherein the fourth request The type information indicates that the request type is resource dequeue, and the sixth request data includes the queue number of dequeue; the response valid signal and the third response data sent by the second resource queue management interface are collected, and the third response data indicates If the queue is successful, it is determined that the data collection of resource dequeue is completed.
- the specific implementation process of the verification device of the resource queue management interface according to the embodiment of the present disclosure is the same as the specific realization process of the verification method of the resource queue management interface according to the embodiment of the present disclosure, and will not be repeated here.
- FIG. 9 is a compositional block diagram of a verification example according to an embodiment of the present disclosure.
- each verification instance is implemented through a resource pool unit, a main drive unit, an acquisition unit, a slave drive unit, and an interface unit.
- Different verification instances share the same resource pool unit, and the main drive unit and acquisition unit of different verification instances , slave drive unit and interface unit are all different.
- the interface unit includes a first resource queue management interface.
- the resource pool unit is used to: generate a resource ID sequence corresponding to each resource type according to the configuration parameters; configure the configuration parameters into the main module to be verified; configure the data storage space address parameter of the resource ID sequence to In the main module to be verified; write the resource ID sequence into the data storage space address corresponding to the data storage space address parameter; after the main module to be verified reads the resource ID sequence from the data storage space address, clear the resource ID sequence .
- the main drive unit is used to: send a valid request signal, first request type information and first request data to the interface unit, wherein the first request type information indicates that the request type is resource application, and the first request data includes the resource type and The number of resources that need to be applied for; when receiving the effective response signal and the first response data sent by the interface unit, and the first response data indicates that the resource application is successful, continue to receive the second response data sent by the interface unit until the interface unit receives until an invalid response signal is sent, wherein the second response data includes the requested resource ID.
- the interface unit is used to: send the request valid signal, the first request type information and the first request data to the second resource queue management interface through the first resource queue management interface, and send the request valid signal, the first request type information and the first request data to the second resource queue management interface Send to the main drive unit; when receiving the valid response signal and the first response data sent by the second resource queue management interface through the first resource queue management interface, and the first response data indicates that the resource application is successful, through the first resource queue
- the management interface continues to receive the second response data sent by the second resource queue management interface until the response invalid signal sent by the second resource queue management interface is received; the response valid signal, the first response data, and the second response data are sent to the master Drive unit.
- the resource pool unit is configured to: add the applied resource ID to the resource ID sequence corresponding to the resource type corresponding to the applied resource ID, and mark the state of the applied resource ID as an idle state.
- the collection unit is used to: collect the first request type information and the first request data when the request valid signal is collected; collect the response valid signal and the first response data when the first request type information indicates that the request type is resource application , and the first response data indicates that the resource application is successful, continue to collect the second response data until an invalid response signal is collected; determine the second resource queue according to the number of collected second response data and the number of resources to be applied Whether the timing of the management interface is normal.
- the resource pool unit is further configured to: verify each of the applied resource IDs to obtain a first verification result; the first verification result indicates that each of the applied resource IDs If all are normal, continue to execute the step of adding the applied resource ID to the resource ID sequence corresponding to the resource type corresponding to the applied resource ID; when the first verification result indicates that at least one of the applied resource IDs is abnormal In the case of , send the second warning information to the main drive unit.
- the main drive unit is also used to: output second warning information, the second warning information is used to indicate at least one abnormality in the applied resource ID, and the second warning information may include information indicating that the resource ID is abnormal, and the abnormal resource ID ID.
- the main drive unit is used to: send a valid request signal, first request type information and first request data to the interface unit, wherein the first request type information indicates that the request type is resource application, and the first request data includes the resource type and The number of resources that need to be applied for; when the valid response signal and the first response data sent by the interface unit are received, and the first response data indicates that the resource application fails, it is determined that the resource application operation is completed.
- the interface unit is used to: send the request valid signal, the first request type information and the first request data to the second resource queue management interface through the first resource queue management interface, and send the request valid signal, the first request type information and the first request data to the second resource queue management interface Send to the main drive unit; when receiving the valid response signal and the first response data sent by the second resource queue management interface through the first resource queue management interface, and the first response data indicates that the resource application fails, determine that the resource application operation is completed ; Send the valid response signal and the first response data to the main drive unit.
- the collection unit is used to: collect the first request type information and the first request data when the request valid signal is collected; the first request type information indicates that the request type is a resource application, and the response valid signal and the first response are collected data, and if the first response data indicates that the resource application fails, it is determined that the collection of resource application data is completed.
- the main drive unit is used to: read at least one resource ID in an idle state; send a request valid signal, second request type information and second request data to the interface unit, wherein the second request type information indicates that the request type is resource release,
- the second request data includes the resource quantity that needs to be released, that is, the quantity of resource IDs read; the resource ID read is included in the third request data, and the third request data is sent to the interface unit; by sending the third request data After the request data has sent all the read resource IDs, convert the request valid signal into a request invalid signal, and send the request invalid signal to the interface unit; in the case of receiving the response valid signal sent by the interface unit, determine the resource release The operation is complete.
- the resource pool unit is used to: delete the read resource ID from the resource ID sequence corresponding to the corresponding resource type, indicating that these resource IDs have been released and can no longer be used as incentives.
- the interface unit is used to: send the request valid signal, the second request type information and the second request data to the second resource queue management interface through the first resource queue management interface; include the read resource ID in the third request data through the second resource queue management interface; A resource queue management interface sequentially sends to the second resource queue management interface; after all the resource IDs read are transmitted, the request valid signal is converted into a request invalid signal and sent to the second resource queue management interface through the first resource queue management interface ; When the response valid signal sent by the second resource queue management interface is received through the first resource queue management interface, it is determined that the resource release operation is completed.
- the collection unit is used to: collect the second request type information and the second request data when the valid request signal is collected; continue to collect the third request data when the second request type information indicates that the request type is resource release, Until an invalid request signal is collected; in the case of a valid response signal collected, determine whether the timing of the second resource queue management interface is based on the collected third request data quantity and the resource quantity to be released normal.
- the main drive unit is used to: read a resource ID in an idle state, notify the resource pool unit to modify the state of the read resource ID to an occupied state; send a request valid signal, third request type information and a fourth request to the interface unit Data; wherein, the third request type information indicates that the request type is resource enqueue, and the fourth request data includes the read resource ID; the enqueue characteristic parameter corresponding to the read resource ID is included in the fifth request data, and The fifth request data is sent to the interface unit; after sending the fifth request data to send all the characteristic parameters of the queue, the request valid signal is converted into a request invalid signal, and the request invalid signal is sent to the interface unit; In the case of the response valid signal sent by the unit, it is determined that the resource enqueue operation is completed.
- the interface unit is used to: send the request valid signal, the third request type information and the fourth request data to the second resource queue management interface through the first resource queue management interface; include the enqueue feature parameter corresponding to the read resource ID in the Among the five request data, the fifth request data is sent to the second resource queue management interface through the first resource queue management interface; after sending the fifth request data to send all the characteristic parameters of the enqueue, the request valid signal is converted into Request an invalid signal, and send the request invalid signal to the second resource queue management interface through the first resource queue management interface; in the case of receiving a valid response signal sent by the second resource queue management interface through the first resource queue management interface, Send a response valid signal to the main drive unit.
- the resource pool unit is used to: modify the state of the read resource ID to an occupied state.
- the collection unit is used to: collect the third request type information and the fourth request data when the valid request signal is collected; continue to collect the fifth request data when the third request type information indicates that the request type is resource enqueue , until an invalid request signal is collected; in the case of a valid response signal collected, determine the second resource queue management interface according to the number of collected fifth request data and the number of enqueue characteristic parameters corresponding to the read resource ID timing is normal.
- the main drive unit is configured to: receive a queue task indication valid signal or a queue task indication invalid signal sent by the interface unit; send a request valid signal, the fourth request type information and the sixth request to the interface unit Data, wherein the fourth request type information indicates that the request type is resource dequeue, and the sixth request data includes the queue number of dequeue; after receiving the response valid signal sent by the interface unit, the third response data, and the third response data indicates When the dequeue is successful, and the queue task indication signal corresponding to the dequeue queue number is an invalid queue task indication signal, the fourth alarm information is output, and the fourth alarm information is used to indicate that the timing of the second resource queue management interface is abnormal .
- the interface unit is configured to: receive a queue task indication valid signal or a queue task indication invalid signal of a queue sent by the second resource queue management interface through the first resource queue management interface;
- the resource queue management interface sends the request valid signal, the fourth request type information and the sixth request data; receives the response valid signal and the third response data through the first resource queue management interface, and sends the response valid signal and the third response data to the main drive unit Data and queue tasks indicate an invalid signal.
- the acquisition unit is used to: collect the queue task indication valid signal or the queue task indication invalid signal of the queue; in the case of collecting the valid request signal, collect the fourth request type information and the sixth request data; when the collected response is valid signal, the third response data, and if the third response data indicates that the dequeue is successful, it is determined that the resource dequeue data collection is completed.
- the interface unit is further configured to: when a valid response signal and third response data are received through the first resource queue management interface, and the third response data indicates that dequeuing fails, through the first resource queue
- the management interface receives the fourth response data; sends a valid response signal and the third response data to the main drive module, and sends the fourth response data to the main drive unit.
- the main drive unit is also used for: after receiving the effective response signal and the third response data sent by the interface unit, and the third response data indicates that the dequeue failed, and the queue task indication signal corresponding to the dequeue queue number is a queue task In the case of indicating a valid signal, the fourth response data sent by the interface unit is received; when the fourth response data includes an error code that the queue is empty, the fifth alarm information is output, and the fifth alarm information is used to indicate the second resource queue management The timing of the interface is abnormal.
- the collection unit is further configured to: collect fourth response data when the effective response signal and the third response data are collected, and the third response data indicates that dequeuing fails.
- the interface unit is further configured to: pass the first resource queue to The management interface receives the fifth response data; wherein, the fifth response data includes: the first resource ID in the resource ID sequence corresponding to the queue number out of the queue; sends a valid response signal and the third response data to the main drive unit; The drive unit sends fifth response data.
- the main drive unit is also used for: after receiving the effective response signal and the third response data sent by the interface unit, and the third response data indicates that the dequeue is successful, and the queue task indication signal corresponding to the dequeue queue number is a queue task In the case of indicating a valid signal, the fifth response data sent by the interface unit is received.
- the resource pool unit is also used to: modify the state of the first resource ID to an idle state.
- the collection unit is further configured to: collect fifth response data when the effective response signal and the third response data are collected, and the third response data indicates that the dequeue is successful.
- the interface unit is further configured to: receive the sixth response data after receiving the valid response signal and the third response data through the first resource queue management interface, and the third response data indicates that dequeuing fails, wherein,
- the sixth response data includes: a random error code; sending a valid response signal, the third response data and an invalid queue task indication signal to the main drive unit; sending the sixth response data to the main drive unit.
- the main drive unit is also used for: after receiving the effective response signal and the third response data sent by the interface unit, the third response data indicates that the dequeue failed, and the queue task indication signal corresponding to the dequeue queue number is a queue task indication
- the sixth response data sent by the interface unit is received in the case of an invalid signal.
- the collection unit is also used to: collect the sixth response data when the effective response signal and the third response data are collected, and the third response data indicates that dequeuing fails.
- the interface unit is configured to: receive the request valid signal sent by the third resource queue management interface, the first request type information and the first request data through the first resource queue management interface, wherein the first request type information indicates that the request type is a resource application , the first request data includes the type of resources to be applied for and the quantity of resources to be applied for; and the request valid signal, the first request type information and the first request data are sent to the slave drive unit.
- the slave drive unit is used to: in the case of receiving the valid request signal sent by the interface unit, the first request type information and the first request data, search for the resource ID in the idle state in the resource ID sequence corresponding to the resource type that needs to be applied for ; When the number of found resource IDs in the idle state is greater than or equal to the number of resources to be applied for, select N resource IDs from the found resource IDs in the idle state.
- the resource pool unit is used to: modify the state of the selected N resource IDs to the occupied state, and the selected N resource IDs can no longer be used as incentives, where N is the number of resources to be applied for.
- the slave drive unit is also used to: send a valid response signal and first response data to the interface unit, wherein the first response data indicates that the resource application is successful; the selected N resource IDs are included in the second response data, and the second The response data is sent to the interface unit; after all the selected N resource IDs are sent by sending the second response data, the response valid signal is converted into a response invalid signal, and the response invalid signal is sent to the interface unit.
- the interface unit is also used to: send a valid response signal and the first response data to the third resource queue management interface through the first resource queue management interface; include the selected N resource IDs in the second response data, and pass the first resource queue
- the management interface sends the second response data to the third resource queue management interface; after sending all the selected N resource IDs by sending the second response data, convert the response valid signal into a response invalid signal, and pass the first resource ID
- the queue management interface sends the corresponding invalidation signal to the third resource queue management interface.
- the collection unit is used to: collect the first request type information and the first request data when the request valid signal is collected; collect the response valid signal and the first response data when the first request type information indicates that the request type is resource application , and the first response data indicates that the resource application is successful, continue to collect the second response data until an invalid response signal is collected; determine the third resource queue according to the quantity of the collected second response data and the quantity of resources to be applied Whether the timing of the management interface is normal.
- the interface unit is configured to: receive the request valid signal sent by the third resource queue management interface, the first request type information and the first request data through the first resource queue management interface, wherein the first request type information indicates that the request type is a resource application , the first request data includes the type of resources to be applied for and the quantity of resources to be applied for; and the request valid signal, the first request type information and the first request data are sent to the slave drive unit.
- the slave drive unit is used to: in the case of receiving the valid request signal sent by the interface unit, the first request type information and the first request data, search for the resource ID in the idle state in the resource ID sequence corresponding to the resource type that needs to be applied for ; When the number of resource IDs found in the idle state is less than the number of resources that need to be applied for, send a valid response signal and first response data to the interface unit, wherein the first response data indicates resource application failure.
- the interface unit is further configured to: send the response valid signal and the first response data to the third resource queue management interface through the first resource queue management interface.
- the collection unit is used to: collect the first request type information and the first request data when the request valid signal is collected; collect the response valid signal and the first response data when the first request type information indicates that the request type is resource application , and if the first response data indicates that the resource application fails, it is determined that the collection of resource application data is completed.
- the slave drive unit is used to: receive the request valid signal sent by the interface unit, the second request type information and the second request data, the second request type information indicates that the request type is resource release, and the second request data includes the amount of resources to be released
- the third request data sent by the interface unit is continuously received until the request invalid signal sent by the interface unit is received, wherein the third request data includes: the resource ID to be released; and a valid response signal is sent to the interface unit.
- the interface unit is configured to: when the request valid signal, the second request type information and the second request data sent by the third resource queue management interface are received through the first resource queue management interface, continue to receive the second resource queue management interface through the first resource queue management interface.
- the drive unit sends the third request data; sends a valid response signal to the third resource queue management interface through the first resource queue management interface.
- the resource pool unit is used to: modify the state of the resource ID to be released to an idle state.
- the collection unit is used to: collect the second request type information and the second request data when the valid request signal is collected; continue to collect the third request data when the second request type information indicates that the request type is resource release, Until the request invalid signal is received; when the response valid signal is collected, determine whether the timing of the third resource queue management interface is normal according to the quantity of the collected third request data and the quantity of resources to be released.
- the resource pool unit is further used to: check the resource IDs that need to be released to obtain a third check result; when the third check result indicates that all resource IDs that need to be released are normal, continue to execute A step of changing the state of the resource ID to be released to an idle state; when the third verification result indicates that at least one resource ID to be released is abnormal, sending eighth warning information to the slave drive unit.
- the slave drive unit is further configured to: output eighth alarm information, the eighth alarm information is used to indicate that at least one resource ID that needs to be released is abnormal, and the eighth alarm information may include information indicating that the resource ID is abnormal and the abnormal resource ID.
- the interface unit is used to: receive the request valid signal sent by the third resource queue management interface, the third request type information and the fourth request data through the first resource queue management interface, and the third request type information indicates that the request type is resource enqueue , when the fourth request data includes the resource ID of the enqueue, continue to receive the fifth request data sent by the third resource queue management interface through the first resource queue management interface until a request invalid signal is received, wherein the fifth request
- the data includes: the enqueue feature parameter corresponding to the resource ID of the enqueue; send the request valid signal, the third request type information and the fourth request data to the slave drive unit; continuously send the fifth request data to the slave drive unit; pass the first resource The queue management interface sends a response valid signal to the third resource queue management interface.
- the slave drive unit is used to: continuously receive the fifth request sent by the third resource queue management interface through the first resource queue management interface, when receiving the request valid signal, the third request type information and the fourth request data sent by the interface unit. Request data until a request invalid signal is received; send a response valid signal to the interface unit.
- the resource pool unit is used for: modifying the state of the resource IDs enqueued into the idle state.
- the collection unit is used to: collect the third request type information and the fourth request data when the valid request signal is collected; continue to collect the fifth request data when the third request type information indicates that the request type is resource enqueue , until an invalid request signal is received; when a valid response signal is collected, determine whether the timing of the third resource queue management interface is normal according to the collected fifth request data quantity and the quantity of enqueue characteristic parameters.
- the resource pool unit is further configured to: check the resource IDs entering the queue to obtain a fourth verification result; if the fourth verification result is that the resource IDs entering the queue are normal, continue to execute the A step of modifying the state of the resource ID that has entered the queue to an idle state; when the resource ID that has entered the queue is abnormal, sending tenth alarm information to the slave drive unit.
- the slave drive unit is further configured to: output tenth alarm information, where the tenth alarm information is used to indicate that the ID of the resource enqueued is abnormal.
- the interface unit is configured to: send a queue task indication valid signal of a queue to the third resource queue management interface through the first resource queue management interface;
- the interface sends the queue task indication invalid signal of the one queue;
- the request valid signal, the fourth request type information and the sixth request data sent by the third resource queue management interface are received through the first resource queue management interface, wherein the fourth request The type information indicates that the request type is resource dequeue, and the sixth request data includes the dequeue queue number;
- the request valid signal, the fourth request type information and the sixth request data are sent to the slave drive unit;
- the three-resource queue management interface sends a valid response signal and the third response data, wherein the third response data indicates that the dequeue is successful; the first resource ID in the resource ID sequence corresponding to the dequeue queue number is included in the fifth response data , and send the fifth response data to the third resource queue management interface through the first resource queue management interface.
- the slave drive unit is used for: when the resource ID sequence corresponding to the queue number of a queue is not empty, send the queue task indication valid signal of the queue to the interface unit; the resource ID sequence corresponding to the queue number of a queue is When it is empty, send the queue task indication invalid signal of the one queue to the interface unit; in the case of receiving the request valid signal, the fourth request type information and the sixth request data sent by the interface unit, judge the queue that has been dequeued Whether the resource ID sequence corresponding to the queue number is empty; in the case that the resource ID sequence corresponding to the queue number out of the queue is not empty, send a valid response signal and the third response data to the interface unit; the resource ID corresponding to the queue number out of the queue The first resource ID in the sequence is included in the fifth response data sent to the interface unit.
- the collection module is used to: collect the queue task indication valid signal or the queue task indication invalid signal of the one queue; in the case that the request valid signal is collected, collect the fourth request type information and the sixth request data; Collecting the fifth response data when the response valid signal and the third response valid signal are collected, and the third response valid signal indicates that the dequeue is successful.
- the slave drive unit is further configured to: when the resource ID sequence corresponding to the dequeue queue number is empty, send a response valid signal and a third response data to the interface unit, wherein the third response data Indicate dequeue failure; include a random error code in the sixth response data, and send the sixth response data to the interface unit.
- the interface unit is also used to: send a valid response signal and the third response data to the third resource queue management interface through the first resource queue management interface; include a random error code in the sixth response data, and The interface sends the sixth response data to the third resource queue management interface.
- the collection unit is further configured to: collect sixth response data when the response valid signal and the third response valid signal are collected, and the third response valid signal indicates that dequeuing fails.
- the collection unit is used to: collect the valid request signal sent by the third resource queue management interface, the first request type information and the first request data, wherein the first request type information indicates that the request type is a resource application, and the first request data includes the required application resource type and the number of resources to be applied for; collect the valid response signal and the first response data sent by the second resource queue management interface; if the first response data indicates that the resource application is successful, continue to collect the information sent by the second resource queue management interface The second response data until the response invalid signal sent by the second resource queue management interface is collected, wherein the second response data includes: the resource ID applied for; The resource quantity determines whether the timing of the second resource queue management interface is normal.
- the collection unit is used to: collect the valid request signal sent by the third resource queue management interface, the second request type information and the second request data, wherein the second request type information indicates that the request type is resource release, and the second request data includes The number of resources; continue to collect the third request data sent by the third resource queue management interface until the request invalid signal sent by the third resource queue management interface is collected, wherein the third request data includes: the resource ID that needs to be released; collect A valid response signal sent by the second resource queue management interface; determine whether the timing of the second resource queue management interface is normal according to the collected quantity of the third request data and the quantity of resources to be released.
- the collection unit is used to: collect the valid request signal sent by the third resource queue management interface, the third request type information and the fourth request data, wherein the third request type information indicates that the request type is resource enqueue, and the fourth request data includes enqueue The resource ID of the team; continue to collect the fifth request data sent by the third resource queue management interface until the request invalid signal is collected, wherein the fifth request data includes: the entry feature parameter corresponding to the resource ID of the queue; collect the fifth request data 2.
- a valid response signal sent by the resource queue management interface determine whether the timing of the third resource queue management interface is normal according to the quantity of collected fifth request data and the quantity of enqueue characteristic parameters corresponding to the enqueue resource ID.
- the collection unit is used to: collect a queue task indication valid signal or a queue task indication invalid signal sent by the second resource queue management interface; collect the request valid signal, the fourth request type information and the sixth request type information sent by the third resource queue management interface.
- Request data wherein the fourth request type information indicates that the request type is resource dequeue, and the sixth request data includes the queue number of dequeue; after collecting the valid response signal and the third response data sent by the second resource queue management interface, and When the third response data indicates that the dequeue is successful, it is determined that the resource dequeue data collection is completed.
- implementing the verification of the interaction process between the second resource queue management interface and the third resource queue management interface through the verification instance further includes: after collecting a valid response signal sent by the second resource queue management interface, The third response data, and in the case that the third response data indicates that dequeuing fails, the fourth response data is collected.
- the collection unit is further configured to: collect the fifth response when the valid response signal and the third response data sent by the second resource queue management interface are collected, and the third response data indicates that the dequeue is successful data.
- the collection unit is further configured to: collect a sixth response when the valid response signal and the third response data sent by the second resource queue management interface are collected, and the third response data indicates that dequeuing fails data.
- the collection unit is further configured to: count the times of resource application, resource release, resource enqueue, and resource dequeue.
- the interface unit is also used for: performing assertion and coverage statistics.
- the functional modules/units in the system, and the device can be implemented as software, firmware, hardware, and an appropriate combination thereof.
- the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical components. Components cooperate to execute.
- Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit .
- Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
- computer storage media includes both volatile and nonvolatile media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. permanent, removable and non-removable media.
- Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage, or may be used Any other medium that stores desired information and can be accessed by a computer.
- communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Debugging And Monitoring (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (33)
- 一种资源队列管理接口的验证方法,包括:生成验证实例;在所述验证实例的第一资源队列管理接口与待验证的主模块的第二资源队列管理接口连接的情况下,通过所述验证实例实现对所述待验证的主模块的第二资源队列管理接口的验证;在所述验证实例的第一资源队列管理接口与待验证的从模块的第三资源队列管理接口连接的情况下,通过所述验证实例实现对所述待验证的从模块的第三资源队列管理接口的验证;在所述验证实例的第一资源队列管理接口与所述第二资源队列管理接口和所述第三资源队列管理接口均连接的情况下,通过所述验证实例实现对所述第二资源队列管理接口和所述第三资源队列管理接口之间的交互过程的验证。
- 根据权利要求1所述的资源队列管理接口的验证方法,其中,所述通过所述验证实例实现对所述待验证的主模块的第二资源队列管理接口的验证包括:通过所述第一资源队列管理接口向所述第二资源队列管理接口发送请求有效信号、第一请求类型信息和第一请求数据,其中,所述第一请求类型信息指示请求类型为资源申请,所述第一请求数据包括需要申请的资源类型和需要申请的资源数量;在通过所述第一资源队列管理接口接收到所述第二资源队列管理接口发送的响应有效信号和第一响应数据,且所述第一响应数据指示资源申请成功的情况下,通过所述第一资源队列管理接口持续接收所述第二资源队列管理接口发送的第二响应数据,直到接收到所述第二资源队列管理接口发送的响应无效信号为止,其中,所述第二响应数据包括申请到的资源标识(ID);将所述申请到的资源ID加入与对应于所述申请到的资源ID的资源类型对应的资源ID序列中,将所述申请到的资源ID的状态设置 为空闲状态;在采集到所述请求有效信号的情况下,采集所述第一请求类型信息和所述第一请求数据;在所述第一请求类型信息指示所述请求类型为资源申请,采集到所述响应有效信号和所述第一响应数据,且所述第一响应数据指示资源申请成功的情况下,持续采集所述第二响应数据,直到采集到所述响应无效信号为止;根据采集到的所述第二响应数据的数量和所述需要申请的资源数量确定所述第二资源队列管理接口的时序是否正常。
- 根据权利要求2所述的资源队列管理接口的验证方法,所述通过所述验证实例实现对所述待验证的主模块的第二资源队列管理接口的验证还包括:在通过第一资源队列管理接口接收到所述第二资源队列管理接口发送的所述响应有效信号和所述第一响应数据,且所述第一响应数据指示资源申请失败的情况下,确定资源申请操作完成;在所述第一请求类型信息指示所述请求类型为资源申请,采集到所述响应有效信号和所述第一响应数据,且所述第一响应数据指示资源申请失败的情况下,确定资源申请数据采集完成。
- 根据权利要求2所述的资源队列管理接口的验证方法,其中,所述根据采集到的所述第二响应数据的数量和所述需要申请的资源数量确定所述第二资源队列管理接口的时序是否正常包括:在采集到的所述第二响应数据的数量和所述需要申请的资源数量相同的情况下,确定所述第二资源队列管理接口的时序正常;在采集到的所述第二响应数据的数量和所述需要申请的资源数量不相同的情况下,确定所述第二资源队列管理接口的时序异常,并输出用于指示所述第二资源队列管理接口的时序异常的第一告警信息。
- 根据权利要求2所述的资源队列管理接口的验证方法,在所述确定资源申请操作完成后,还包括:对所述申请到的资源ID中的每一个资源ID进行校验,以得到第一校验结果;在所述第一校验结果指示所述申请到的资源ID中的每一个资源ID均正常的情况下,继续执行所述将所述申请到的资源ID加入与对应于所述申请到的资源ID的资源类型对应的资源ID序列中的步骤;在所述第一校验结果指示所述申请到的资源ID中的至少一个资源ID异常的情况下,输出用于指示所述至少一个资源ID异常的第二告警信息。
- 根据权利要求2所述的资源队列管理接口的验证方法,其中,所述申请到的资源ID为资源池中的资源ID,不同的验证实例共享同一个资源池。
- 根据权利要求2-6任意一项所述的资源队列管理接口的验证方法,在所述通过所述第一资源队列管理接口向所述第二资源队列管理接口发送请求有效信号、第一请求类型信息和第一请求数据的步骤之前,所述通过所述验证实例实现对所述待验证的主模块的第二资源队列管理接口的验证还包括:根据配置参数生成与每一种资源类型对应的资源ID序列;将所述配置参数配置到所述待验证的主模块中;将所述资源ID序列的数据存储空间地址参数配置到所述待验证的主模块中;将所述资源ID序列写入与所述数据存储空间地址参数对应的数据存储空间地址中;在所述待验证的主模块从所述数据存储空间地址中读取所述资源ID序列后,将所述资源ID序列清空。
- 根据权利要求1所述的资源队列管理接口的验证方法,其中, 所述通过所述验证实例实现对所述待验证的主模块的第二资源队列管理接口的验证包括:读取至少一个处于空闲状态的资源ID,将读取的资源ID从与对应于所述资源ID的资源类型对应的资源ID序列中删除;通过所述第一资源队列管理接口向所述第二资源队列管理接口发送请求有效信号、第二请求类型信息和第二请求数据,其中,所述第二请求类型信息指示请求类型为资源释放,所述第二请求数据包括需要释放的资源数量,所述需要释放的资源数量为所述读取的资源ID的数量;将所述读取的资源ID包含在第三请求数据中,并通过所述第一资源队列管理接口将所述第三请求数据发送给所述第二资源队列管理接口;在通过发送所述第三请求数据将所述读取的资源ID全部发送完成后,将所述请求有效信号转换为请求无效信号,并通过所述第一资源队列管理接口将所述请求无效信号发送给所述第二资源队列管理接口;在通过所述第一资源队列管理接口接收到所述第二资源队列管理接口发送的响应有效信号的情况下,确定资源释放操作完成;在采集到所述请求有效信号的情况下,采集所述第二请求类型信息和所述第二请求数据;在所述第二请求类型信息指示所述请求类型为资源释放的情况下,持续采集所述第三请求数据,直到采集到所述请求无效信号为止;在采集到所述响应有效信号的情况下,根据采集到的所述第三请求数据的数量和所述需要释放的资源数量确定所述第二资源队列管理接口的时序是否正常。
- 根据权利要求8所述的资源队列管理接口的验证方法,其中,所述根据采集到的所述第三请求数据的数量和所述需要释放的资源数量确定所述第二资源队列管理接口的时序是否正常包括:在采集到的所述第三请求数据的数量和所述需要释放的资源数 量相同的情况下,确定所述第二资源队列管理接口的时序正常;在采集到的所述第三请求数据的数量和所述需要释放的资源数量不相同的情况下,确定所述第二资源队列管理接口的时序异常,输出用于指示所述第二资源队列管理接口的时序异常的第三告警信息。
- 根据权利要求1所述的资源队列管理接口的验证方法,其中,所述通过所述验证实例实现对所述待验证的主模块的第二资源队列管理接口的验证包括:读取一个处于空闲状态的资源ID,将读取的资源ID的状态修改为占用状态;通过所述第一资源队列管理接口向所述第二资源队列管理接口发送请求有效信号、第三请求类型信息和第四请求数据,其中,所述第三请求类型信息指示请求类型为资源入队,所述第四请求数据包括所述读取的资源ID;将与所述读取的资源ID对应的入队特征参数包含在第五请求数据中,并通过所述第一资源队列管理接口将所述第五请求数据发送给所述第二资源队列管理接口;在通过发送所述第五请求数据将所述入队特征参数全部发送完成后,将所述请求有效信号转换为请求无效信号,并通过所述第一资源队列管理接口将所述请求无效信号发送给所述第二资源队列管理接口;在通过所述第一资源队列管理接口接收到所述第二资源队列管理接口发送的响应有效信号的情况下,确定资源入队操作完成;在采集到所述请求有效信号的情况下,采集所述第三请求类型信息和所述第四请求数据;在所述第三请求类型信息指示所述请求类型资源入队的情况下,持续采集所述第五请求数据,直到采集到请求无效信号为止;在采集到所述响应有效信号的情况下,根据采集到的所述第五请求数据的数量和与所述读取的资源ID对应的入队特征参数的数量确定所述第二资源队列管理接口的时序是否正常。
- 根据权利要求10所述的资源队列管理接口的验证方法,其中,所述根据采集到的所述第五请求数据的数量和所述读取的资源ID对应的入队特征参数的数量确定所述第二资源队列管理接口的时序是否正常包括:在采集到的所述第五请求数据的数量和所述读取的资源ID对应的入队特征参数的数量相同的情况下,确定所述第二资源队列管理接口的时序正常;在采集到的所述第五请求数据的数量和所述读取的资源ID对应的入队特征参数的数量不相同的情况下,确定所述第二资源队列管理接口的时序异常,输出用于指示所述第二资源队列管理接口的时序异常的第四告警信息。
- 根据权利要求1所述的资源队列管理接口的验证方法,其中,所述通过所述验证实例实现对所述待验证的主模块的第二资源队列管理接口的验证包括:通过所述第一资源队列管理接口接收所述第二资源队列管理接口发送的一个队列的队列任务指示有效信号或队列任务指示无效信号;通过所述第一资源队列管理接口向所述第二资源队列管理接口发送请求有效信号、第四请求类型信息和第六请求数据,其中,所述第四请求类型信息指示请求类型为资源出队,所述第六请求数据包括出队的队列号;在通过所述第一资源队列管理接口接收到所述第二资源队列管理接口发送的响应有效信号、第三响应数据,所述第三响应数据指示出队成功,且与所述出队的队列号对应的队列任务指示信号为队列任务指示无效信号的情况下,输出用于指示所述第二资源队列管理接口的时序异常的第五告警信息;采集所述一个队列的队列任务指示有效信号或队列任务指示无效信号;在采集到所述请求有效信号的情况下,采集所述第四请求类型信息和所述第六请求数据;在采集到所述响应有效信号、所述第三响应数据,且所述第三响应数据指示出队成功的情况下,确定资源出队数据采集完成。
- 根据权利要求12所述的资源队列管理接口的验证方法,所述通过所述验证实例实现对所述待验证的主模块的第二资源队列管理接口的验证还包括:在通过所述第一资源队列管理接口接收到所述第二资源队列管理接口发送的所述响应有效信号、所述第三响应数据,所述第三响应数据指示出队失败,且与所述出队的队列号对应的队列任务指示信号为队列任务指示有效信号的情况下,通过所述第一资源队列管理接口接收所述第二资源队列管理接口发送的第四响应数据;在所述第四响应数据包括队列空的错误码的情况下,输出用于指示所述第二资源队列管理接口的时序异常的第六告警信息;在采集到所述响应有效信号、所述第三响应数据,且所述第三响应数据指示出队失败的情况下,采集所述第四响应数据。
- 根据权利要求12所述的资源队列管理接口的验证方法,其中,所述通过所述验证实例实现对所述待验证的主模块的第二资源队列管理接口的验证还包括:在通过所述第一资源队列管理接口接收到所述第二资源队列管理接口发送的所述响应有效信号、所述第三响应数据,所述第三响应数据指示出队成功,且所述出队的队列号对应的队列任务指示信号为队列任务指示有效信号的情况下,通过所述第一资源队列管理接口接收所述第二资源队列管理接口发送的第五响应数据,其中,所述第五响应数据包括:与所述出队的队列号对应的资源ID序列中的第一个资源ID;将所述第一个资源ID的状态修改为空闲状态;在采集到所述响应有效信号、所述第三响应数据,且所述第三 响应数据指示出队成功的情况下,采集所述第五响应数据。
- 根据权利要求14所述的资源队列管理接口的验证方法,所述通过所述验证实例实现对所述待验证的主模块的第二资源队列管理接口的验证还包括:对所述第一个资源ID进行校验得到第二校验结果;在所述第二校验结果指示所述第一个资源ID正常的情况下,继续执行所述将所述第一个资源ID的状态修改为空闲状态的步骤;在所述第二校验结果指示所述第一个资源ID异常的情况下,输出用于指示所述第一个资源ID异常的第七告警信息。
- 根据权利要求12所述的资源队列管理接口的验证方法,所述通过所述验证实例实现对所述待验证的主模块的第二资源队列管理接口的验证还包括:在通过所述第一资源队列管理接口接收到所述第二资源队列管理接口发送的所述响应有效信号、所述第三响应数据,所述第三响应数据指示出队失败,且与所述出队的队列号对应的队列任务指示信号为队列任务指示无效信号的情况下,接收所述第二资源队列管理接口发送的第六响应数据,其中,所述第六响应数据包括错误码;在采集到所述响应有效信号、所述第三响应数据,且所述第三响应数据指示出队失败的情况下,采集所述第六响应数据。
- 根据权利要求1所述的资源队列管理接口的验证方法,其中,所述通过所述验证实例实现对所述待验证的从模块的第三资源队列管理接口的验证包括:在通过所述第一资源队列管理接口接收到所述第三资源队列管理接口发送的请求有效信号、第一请求类型信息和第一请求数据,所述第一请求类型信息指示请求类型为资源申请,所述第一请求数据包括需要申请的资源类型和需要申请的资源数量的情况下,在与所述需要申请的资源类型对应的资源ID序列中查找处于空闲状态的资源ID;在查找到的处于空闲状态的资源ID的数量大于或等于所述需要申请的资源数量的情况下,从所述查找到的处于空闲状态的资源ID中选择N个资源ID,将选择的N个资源ID的状态修改为占用状态,其中,N为所述需要申请的资源数量;通过所述第一资源队列管理接口向所述第三资源队列管理接口发送响应有效信号和第一响应数据,其中,所述第一响应数据指示资源申请成功;将所述选择的N个资源ID包含在第二响应数据中,并通过所述第一资源队列管理接口将所述第二响应数据发送给所述第三资源队列管理接口;在通过发送所述第二响应数据将所述选择的N个资源ID全部发送完成后,将所述响应有效信号转换为响应无效信号,并通过所述第一资源队列管理接口将所述响应无效信号发送给所述第三资源队列管理接口;在采集到所述请求有效信号的情况下,采集所述第一请求类型信息和所述第一请求数据;在所述第一请求类型信息指示所述请求类型为资源申请,采集到所述响应有效信号和所述第一响应数据,且所述第一响应数据指示资源申请成功的情况下,持续采集所述第二响应数据,直到采集到所述响应无效信号为止;根据采集到的所述第二响应数据的数量和所述需要申请的资源数量确定所述第三资源队列管理接口的时序是否正常。
- 根据权利要求17所述的资源队列管理接口的验证方法,所述通过所述验证实例实现对所述待验证的从模块的第三资源队列管理接口的验证还包括:在所述查找到的处于空闲状态的资源ID的数量小于所述需要申请的资源数量的情况下,通过所述第一资源队列管理接口向所述第三资源队列管理接口发送所述响应有效信号和所述第一响应数据,其中,所述第一响应数据指示资源申请失败;在所述第一请求类型信息指示请求类型为资源申请,采集到所述响应有效信号和所述第一响应数据,且所述第一响应数据指示资源申请失败的情况下,确定资源申请数据采集完成。
- 根据权利要求17所述的资源队列管理接口的验证方法,其中,所述根据采集到的所述第二响应数据的数量和所述需要申请的资源数量确定所述第三资源队列管理接口的时序是否正常包括:在采集到的所述第二响应数据的数量和所述需要申请的资源数量相同的情况下,确定所述第三资源队列管理接口的时序正常;在采集到的所述第二响应数据的数量和所述需要申请的资源数量不相同的情况下,确定所述第三资源队列管理接口的时序异常,输出用于指示所述第三资源队列管理接口的时序异常的第八告警信息。
- 根据权利要求1所述的资源队列管理接口的验证方法,其中,所述通过所述验证实例实现对所述待验证的从模块的第三资源队列管理接口的验证包括:在通过所述第一资源队列管理接口接收到所述第三资源队列管理接口发送的请求有效信号、第二请求类型信息和第二请求数据,所述第二请求类型信息指示请求类型资源释放,所述第二请求数据包括需要释放的资源数量的情况下,通过所述第一资源队列管理接口持续接收所述第三资源队列管理接口发送的第三请求数据,直到接收到所述第三资源队列管理接口发送的请求无效信号为止,其中,所述第三请求数据包括需要释放的资源ID;通过所述第一资源队列管理接口向所述第三资源队列管理接口发送响应有效信号;将所述需要释放的资源ID的状态修改为空闲状态;在采集到所述请求有效信号的情况下,采集所述第二请求类型信息和所述第二请求数据;在所述第二请求类型信息指示所述请求类型为资源释放的情况下,持续采集所述第三请求数据,直到接收到所述请求无效信号为止;在采集到所述响应有效信号的情况下,根据采集到的所述第三请求数据的数量和所述需要释放的资源数量确定所述第三资源队列管理接口的时序是否正常。
- 根据权利要求20所述的资源队列管理接口的验证方法,所述通过所述验证实例实现对所述待验证的从模块的第三资源队列管理接口的验证还包括:对所述需要释放的资源ID中的每一个进行校验,得到第三校验结果;在所述第三校验结果指示所述需要释放的资源ID中的每一个均正常的情况下,继续执行所述将所述需要释放的资源ID的状态修改为空闲状态的步骤;在所述第三校验结果指示所述需要释放的资源ID中的至少一个异常的情况下,输出用于指示所述至少一个需要释放的资源ID异常和指示异常的资源ID的第九告警信息。
- 根据权利要求20所述的资源队列管理接口的验证方法,其中,所述根据采集到的所述第三请求数据的数量和所述需要释放的资源数量确定所述第三资源队列管理接口的时序是否正常包括:在采集到的所述第三请求数据的数量和所述需要释放的资源数量相同的情况下,确定所述第三资源队列管理接口的时序正常;在采集到的所述第三请求数据的数量和所述需要释放的资源数量不相同的情况下,确定所述第三资源队列管理接口的时序异常,输出用于指示所述第三资源队列管理接口的时序异常的第十告警信息。
- 根据权利要求1所述的资源队列管理接口的验证方法,其中,所述通过所述验证实例实现对所述待验证的从模块的第三资源队列管理接口的验证包括:在通过所述第一资源队列管理接口接收到所述第三资源队列管理接口发送的请求有效信号、第三请求类型信息和第四请求数据,所 述第三请求类型信息指示请求类型为资源入队,所述第四请求数据包括入队的资源ID的情况下,通过所述第一资源队列管理接口持续接收所述第三资源队列管理接口发送的第五请求数据,直到接收到请求无效信号为止,其中,所述第五请求数据包括与所述入队的资源ID对应的入队特征参数;通过所述第一资源队列管理接口向所述第三资源队列管理接口发送响应有效信号;将所述入队的资源ID的状态修改为空闲状态;在采集到所述请求有效信号的情况下,采集所述第三请求类型信息和所述第四请求数据;在所述第三请求类型信息指示所述请求类型为资源入队的情况下,持续采集所述第五请求数据,直到接收到请求无效信号为止,在采集到所述响应有效信号的情况下,根据采集到的所述第五请求数据的数量和所述入队特征参数的数量确定所述第三资源队列管理接口的时序是否正常。
- 根据权利要求23所述的资源队列管理接口的验证方法,所述通过所述验证实例实现对所述待验证的从模块的第三资源队列管理接口的验证还包括:对所述入队的资源ID进行校验得到第四校验结果;在所述第四校验结果指示所述入队的资源ID正常的情况下,继续执行所述将所述入队的资源ID的状态修改为空闲状态的步骤;在所述入队的资源ID异常的情况下,输出用于指示所述入队的资源ID异常的第十一告警信息。
- 根据权利要求23所述的资源队列管理接口的验证方法,其中,所述根据采集到的所述第五请求数据的数量和所述入队特征参数的数量确定所述第三资源队列管理接口的时序是否正常包括:在采集到的所述第五请求数据的数量和所述入队特征参数的数量相同的情况下,确定所述第三资源队列管理接口的时序正常;在采集到的所述第五请求数据的数量和所述入队特征参数的数量不相同的情况下,确定所述第三资源队列管理接口的时序异常,输出用于指示所述第三资源队列管理接口的时序异常的第十二告警信息。
- 根据权利要求1所述的资源队列管理接口的验证方法,其中,所述通过所述验证实例实现对所述待验证的从模块的第三资源队列管理接口的验证包括:在与一个队列的队列号对应的资源ID序列非空的情况下,通过所述第一资源队列管理接口向所述第三资源队列管理接口发送所述一个队列的队列任务指示有效信号;在与所述一个队列的队列号对应的资源ID序列为空的情况下,通过所述第一资源队列管理接口向所述第三资源队列管理接口发送所述一个队列的队列任务指示无效信号;在通过所述第一资源队列管理接口接收到所述第三资源队列管理接口发送的请求有效信号、第四请求类型信息和第六请求数据,所述第四请求类型信息指示请求类型为资源出队,所述第六请求数据包括出队的队列号的情况下,判断与所述出队的队列号对应的资源ID序列是否为空;在与所述出队的队列号对应的资源ID序列非空的情况下,通过所述第一资源队列管理接口向所述第三资源队列管理接口发送响应有效信号、第三响应数据,其中,所述第三响应数据指示出队成功;将与所述出队的队列号对应的资源ID序列中的第一个资源ID包含在第五响应数据中,并通过所述第一资源队列管理接口将所述第五响应数据发送给所述第三资源队列管理接口;采集所述一个队列的所述队列任务指示有效信号或所述队列任务指示无效信号;在采集到所述请求有效信号的情况下,采集所述第四请求类型信息和所述第六请求数据;在采集到所述响应有效信号、所述第三响应有效信号和所述队 列任务指示有效信号,且所述第三响应有效信号指示出队成功的情况下,采集所述第五响应数据。
- 根据权利要求26所述的资源队列管理接口的验证方法,所述通过所述验证实例实现对所述待验证的从模块的第三资源队列管理接口的验证还包括:在与所述出队的队列号对应的资源ID序列为空的情况下,通过所述第一资源队列管理接口向所述第三资源队列管理接口发送响应有效信号、第三响应数据,其中,所述第三响应数据指示出队失败;将随机的错误码包含在第六响应数据中,并通过所述第一资源队列管理接口将所述第六响应数据发送给所述第三资源队列管理接口;在采集到所述响应有效信号、所述第三响应有效信号和所述队列任务指示无效信号,且所述第三响应有效信号指示出队失败的情况下,采集所述第六响应数据。
- 根据权利要求1所述的资源队列管理接口的验证方法,其中,所述通过所述验证实例实现对所述第二资源队列管理接口和所述第三资源队列管理接口之间的交互过程的验证包括:采集所述第三资源队列管理接口发送的请求有效信号、第一请求类型信息和第一请求数据,其中,所述第一请求类型信息指示请求类型为资源申请,所述第一请求数据包括需要申请的资源类型和需要申请的资源数量;采集所述第二资源队列管理接口发送的响应有效信号和第一响应数据;在所述第一响应数据指示资源申请成功的情况下,持续采集所述第二资源队列管理接口发送的第二响应数据,直到采集到所述第二资源队列管理接口发送的响应无效信号为止,其中,所述第二响应数据包括申请到的资源ID;根据采集到的所述第二响应数据的数量和所述需要申请的资源 数量确定所述第二资源队列管理接口的时序是否正常。
- 根据权利要求1所述的资源队列管理接口的验证方法,其中,所述通过所述验证实例实现对所述第二资源队列管理接口和所述第三资源队列管理接口之间的交互过程的验证包括:采集所述第三资源队列管理接口发送的请求有效信号、第二请求类型信息和第二请求数据,其中,所述第二请求类型信息指示请求类型资源释放,所述第二请求数据包括需要释放的资源数量;持续采集所述第三资源队列管理接口发送的第三请求数据,直到采集到第三资源队列管理接口发送的请求无效信号为止,其中,所述第三请求数据包括需要释放的资源ID;采集所述第二资源队列管理接口发送的响应有效信号;根据采集到的所述第三请求数据的数量和所述需要释放的资源数量确定所述第二资源队列管理接口的时序是否正常。
- 根据权利要求1所述的资源队列管理接口的验证方法,其中,所述通过所述验证实例实现对所述第二资源队列管理接口和所述第三资源队列管理接口之间的交互过程的验证包括:采集所述第三资源队列管理接口发送的请求有效信号、第三请求类型信息和第四请求数据,其中,所述第三请求类型信息指示请求类型为资源入队,所述第四请求数据包括入队的资源ID;持续采集所述第三资源队列管理接口发送的第五请求数据,直到采集到请求无效信号为止,其中,所述第五请求数据包括与所述入队的资源ID对应的入队特征参数;采集所述第二资源队列管理接口发送的响应有效信号;根据采集到的所述第五请求数据的数量和与所述入队的资源ID对应的入队特征参数的数量确定所述第三资源队列管理接口的时序是否正常。
- 根据权利要求1所述的资源队列管理接口的验证方法,其 中,所述通过所述验证实例实现对所述第二资源队列管理接口和所述第三资源队列管理接口之间的交互过程的验证包括:采集所述第二资源队列管理接口发送的一个队列的队列任务指示有效信号或队列任务指示无效信号;采集所述第三资源队列管理接口发送的请求有效信号、第四请求类型信息和第六请求数据,其中,所述第四请求类型信息指示请求类型为资源出队,所述第六请求数据包括出队的队列号;在采集到所述第二资源队列管理接口发送的响应有效信号、第三响应数据,且第三响应数据指示出队成功的情况下,确定资源出队数据采集完成。
- 一种电子设备,包括:至少一个处理器;存储器,所述存储器上存储有至少一个程序,当所述至少一个程序被所述至少一个处理器执行时,实现根据权利要求1-31任意一项所述的资源队列管理接口的验证方法。
- 一种存储介质,所述存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现根据权利要求1-31任意一项所述的资源队列管理接口的验证方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2023572965A JP2024519554A (ja) | 2021-05-27 | 2022-03-23 | リソースキュー管理インターフェースの検証方法、電子機器、記憶媒体 |
EP22810156.4A EP4350508A1 (en) | 2021-05-27 | 2022-03-23 | Resource queue management interface verification method, electronic device, and storage medium |
KR1020237040859A KR20230170978A (ko) | 2021-05-27 | 2022-03-23 | 리소스 큐 관리 인터페이스의 검증 방법, 전자 장치 및 저장 매체 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110588355.7 | 2021-05-27 | ||
CN202110588355.7A CN115408057A (zh) | 2021-05-27 | 2021-05-27 | 资源队列管理接口的验证方法、电子设备、存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022247422A1 true WO2022247422A1 (zh) | 2022-12-01 |
Family
ID=84156050
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/082550 WO2022247422A1 (zh) | 2021-05-27 | 2022-03-23 | 资源队列管理接口的验证方法、电子设备、存储介质 |
Country Status (5)
Country | Link |
---|---|
EP (1) | EP4350508A1 (zh) |
JP (1) | JP2024519554A (zh) |
KR (1) | KR20230170978A (zh) |
CN (1) | CN115408057A (zh) |
WO (1) | WO2022247422A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104407279A (zh) * | 2014-10-28 | 2015-03-11 | 深圳市芯海科技有限公司 | 一种用于自动测试芯片mdio总线协议的码型数据、装置及测试方法 |
CN109255001A (zh) * | 2018-08-31 | 2019-01-22 | 阿里巴巴集团控股有限公司 | 接口实例库的维护方法及装置、电子设备 |
US10628407B1 (en) * | 2017-02-27 | 2020-04-21 | Amazon Technologies, Inc. | Efficient multithreaded data structure processing |
CN112286746A (zh) * | 2020-10-31 | 2021-01-29 | 拓维电子科技(上海)有限公司 | 针对axi从设备接口的通用验证平台及方法 |
-
2021
- 2021-05-27 CN CN202110588355.7A patent/CN115408057A/zh active Pending
-
2022
- 2022-03-23 EP EP22810156.4A patent/EP4350508A1/en active Pending
- 2022-03-23 WO PCT/CN2022/082550 patent/WO2022247422A1/zh active Application Filing
- 2022-03-23 JP JP2023572965A patent/JP2024519554A/ja active Pending
- 2022-03-23 KR KR1020237040859A patent/KR20230170978A/ko unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104407279A (zh) * | 2014-10-28 | 2015-03-11 | 深圳市芯海科技有限公司 | 一种用于自动测试芯片mdio总线协议的码型数据、装置及测试方法 |
US10628407B1 (en) * | 2017-02-27 | 2020-04-21 | Amazon Technologies, Inc. | Efficient multithreaded data structure processing |
CN109255001A (zh) * | 2018-08-31 | 2019-01-22 | 阿里巴巴集团控股有限公司 | 接口实例库的维护方法及装置、电子设备 |
CN112286746A (zh) * | 2020-10-31 | 2021-01-29 | 拓维电子科技(上海)有限公司 | 针对axi从设备接口的通用验证平台及方法 |
Also Published As
Publication number | Publication date |
---|---|
JP2024519554A (ja) | 2024-05-16 |
CN115408057A (zh) | 2022-11-29 |
KR20230170978A (ko) | 2023-12-19 |
EP4350508A1 (en) | 2024-04-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5719930B2 (ja) | システムテスト装置 | |
CN109871225B (zh) | 电子控制单元ecu升级方法及ecu | |
US20170048008A1 (en) | Method and apparatus for verification of network service in network function virtualization environment | |
CN101123485B (zh) | iSCSI报文处理方法和装置、错误恢复方法和装置 | |
CN111858413B (zh) | Pcie交换芯片端口的数据调度方法及装置 | |
CN109597653A (zh) | Bios与bmc命令交互的方法、bios及bmc | |
CN110209529A (zh) | 射频参数的保护方法及电子设备 | |
CN101800672B (zh) | 设备检测方法和设备 | |
WO2022247422A1 (zh) | 资源队列管理接口的验证方法、电子设备、存储介质 | |
US9646252B2 (en) | Template clauses based SAT techniques | |
US8433952B2 (en) | Memory access control device, memory access control method and memory access control program | |
KR20170117326A (ko) | 랜덤 액세스 메모리를 포함하는 하나 이상의 처리 유닛을 위한 직접 메모리 액세스 제어 장치 | |
CN113852610B (zh) | 报文处理方法、装置、计算机设备和存储介质 | |
CN114327981A (zh) | 一种功能安全机制的安全校验***、方法及装置 | |
CN109669829A (zh) | 一种基于bmc的诊断调试方法、装置及服务器 | |
CN111930582A (zh) | ***管理总线检测平台、处理器及***管理总线检测方法 | |
CN112737872B (zh) | 一种arinc664p7端***跨网测试***和方法 | |
US20110314183A1 (en) | System and method for managing dataflow in a temporary memory | |
TWI757606B (zh) | 伺服器裝置及其基板管理控制器與可程式邏輯單元之間的通訊協定方法 | |
CN117076182B (zh) | 一种错误上报方法、片上***、计算机设备及存储介质 | |
CN117608618B (zh) | 服务器固件升级方法及装置、存储介质和电子设备 | |
CN110879747B (zh) | 资源管理方法及装置 | |
CN115827081A (zh) | 数据操作方法、装置、服务器以及存储介质 | |
CN112346922A (zh) | 服务器装置及其通讯协议方法 | |
CN116302008A (zh) | 一种固件更新方法、装置、电子设备及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22810156 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023572965 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18564069 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 20237040859 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020237040859 Country of ref document: KR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022810156 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2022810156 Country of ref document: EP Effective date: 20240102 |