Intelligent test task right confirmation method and device oriented to test resource lineage

Abstract

The invention provides an intelligent test task right confirmation method and device oriented to a test resource provenance. The method comprises the following steps: constructing a decentralized and distributed resource provenance data platform; when the client node sends an operation request, the main node starts verification of the lineage relationship of the test resources stored in each backup node, the backup node with the abnormal lineage relationship of the stored test resources is used as an abnormal node, the correct lineage relationship of the test resources is determined through an error correction algorithm, and the verification of the lineage relationship of the test resources is completed. The content stored in the abnormal node is corrected according to the provenance relationship of the correct test resources, so that synchronization of the provenance relationship of the test resources stored in each backup node is realized; and determining the affiliation of each test resource based on the lineage relationship of the test resources in the backup node and the developer information of each test resource. According to the method, a distributed resource lineage data platform is established, and an effective basis is provided for affiliation right confirmation of test resources.

Description

Technical Field

[0001] The present invention relates to the technical field of data management, and in particular to an intelligent test task right confirmation method and device oriented to test resource lineage. Background Art

[0002] Military joint tests refer to simulation tests used in the military field, in which objects from different regions, types, and units are jointly conducted. They are characterized by complex sources of test objects and a large number of units participating in the tests.

[0003] In military joint tests, test resources refer to the equipment involved in the test and its proxy forwarding programs, simulation programs, and emulation programs. Resource service software is usually used to proxy and host test resources and provide services for accessing the test system. In order to improve the efficiency of test deployment, there will be frequent use of existing resources to develop new resources. At the same time, existing resources will continue to iterate as the test deployment proceeds to meet new needs. This makes the lineage of test resources complex, the ownership of test resources difficult to confirm, the rights of test resource creators cannot be effectively maintained, and the responsibility for maintaining test resources is difficult to implement.

[0004] The current method for confirming the ownership of experimental resources basically adopts the method of centralized resource platform, such as Figure 1 As shown, by establishing a resource service platform, the resources created and uploaded by different users are recorded and registered. When branching existing resources, you need to apply on the platform first, and then conduct secondary development after approval. When the ownership needs to be confirmed, the creator and modifier information of the resource is obtained from the resource library.

[0005] The advantages of this technology are low query and record process overhead, simple management platform structure, and easy deployment and maintenance. The disadvantages of this technology are that due to the lack of tracking records of the resource life cycle, the correctness of resource ownership depends on the joint maintenance of the uploader, making it difficult to prevent malicious behavior and lacking fault tolerance. At the same time, due to the use of a centralized storage method, the disaster tolerance of the entire system is weak.

[0006] During the development and deployment phase of test resources for joint military experiments, it is common to use existing resource services for secondary development. At the same time, joint military experiments cover a large geographical span, and the distribution of resource ownership is relatively dispersed, so the centralized platform structure cannot adapt to the actual situation. Summary of the invention

[0007] In order to solve the above technical problems, the present invention proposes an intelligent test task rights confirmation method and device for test resource lineage, which is used to solve the technical problem that the existing test resource ownership confirmation method cannot be applied to joint test environments with high update frequency and dispersed test resources.

[0008] The present invention proposes an intelligent test task right confirmation method oriented to the test resource lineage, the method comprising:

[0009] Step S1: construct a decentralized, distributed resource lineage data platform, which is used to store interfaces provided after the test resources are encapsulated, lineage relationships of the test resources, and operation records of the test resources. The test resources are generated by the test tasks, including the equipment participating in the test and its proxy forwarding program, simulation program, and simulation program; the resource lineage data platform includes multiple distributed server nodes, and one of the distributed server nodes is selected as the main node; among the other distributed server nodes, some nodes are used as client nodes for human-computer interaction, and the remaining nodes are used as backup nodes responsible for storing the lineage relationships of the test resources, wherein each backup node stores the complete lineage relationships of all test resources;

[0010] Step S2: Listen to the input of the client node. When the client node sends an operation request, the master node starts to check the lineage relationship of the test resources stored in each backup node, and regards the backup node with abnormal lineage relationship of the stored test resources as an abnormal node. The correct lineage relationship of the test resources is determined by the error correction algorithm, and the content stored in the abnormal node is corrected according to the correct lineage relationship of the test resources, so as to achieve synchronization of the lineage relationship of the test resources stored in each backup node.

[0011] Step S3: Determine the ownership of each test resource based on the lineage relationship of the test resources in the backup node and the developer information of each test resource.

[0012] Preferably, the step S2 comprises:

[0013] Step S21: The master node monitors that the client node sends an operation request to the master node<REQUEST,o,t,c> σc; where REQUEST is the instruction word, o is the operation content, t is the time when the operation request is issued, c is the client node information that issues the operation request, and σc is the identity verification information of the client that issues the operation request;

[0014] Step S22: The master node receives the operation request and then sends a pre-preparation message to each backup node.<PRE-PREPARE,v,n,d> ,m>; where PRE-PREPARE is the instruction word, m is the message in the operation request, d is the summary of the message of the operation request, v is the view number corresponding to the operation request, and n is the number of the operation request;

[0015] Step S23: The backup node receives the pre-prepare message and sends a prepare message to the other backup nodes.<PREPARE,v,n,d1,i> , and simultaneously receive preparation messages from the remaining backup nodes, wherein d1 is a summary of the lineage relationship of the test resources stored in the backup node that sends the preparation message and is identified by the backup node that sends the preparation message; compare whether the summary contents of the lineage relationship of the same test resource of the backup node that receives the preparation message and each backup node that sends the preparation message are the same; if they are the same, the corresponding backup node that sends the preparation message is used as a backup node that has passed the inspection, and the backup node that receives the preparation message writes the preparation message from the backup node that has passed the inspection into the message log; if they are not the same, the corresponding backup node that sends the preparation message is used as a backup node that has failed the inspection;

[0016] For any backup node, when it is verified as a verified backup node by more than or equal to 2f+1 other backup nodes, the backup node is regarded as a normal node; otherwise, the backup node is regarded as an abnormal node, where N>3f+1, N is the total number of distributed service nodes, and f is a parameter;

[0017] Step S24: Summarize all abnormal nodes, and modify the content stored in the abnormal nodes according to the lineage relationship of the test resources in the normal nodes;

[0018] Step S25: The master node confirms that all abnormal nodes have been corrected, and after that stage, sends the processing results to the client node.

[0019] Preferably, the selection formula of the master node is:

[0020] p=v mod|R|

[0021] Where v is the view number; R is the total number of distributed server nodes. When the master node fails or is overthrown, the view change is initiated, the view number is assigned the value of the original view number plus 1, and then the master node is selected according to the selection formula, and the tasks that have not been processed by the previous master node are inherited.

[0022] Preferably, the lineage relationship of the test resources includes an iterative relationship, an inheritance relationship, and a derivative relationship.

[0023] Preferably, the test resources are stored on several distributed service nodes, each test resource is encapsulated and provides an interface, the interface is stored in the distributed service node that stores the test resources corresponding to the interface, and when the test resources are secondary developed, the test resources are called according to the interface and the lineage information of the test resources is updated; the lineage information of the test resources is encapsulated on the backup node.

[0024] The present invention provides an intelligent test task right confirmation device oriented to the test resource lineage, the device comprising:

[0025] Initialization module: configured to build a decentralized, distributed resource lineage data platform, the resource lineage data platform is used to store the interface provided after the test resource is encapsulated, the lineage relationship of the test resource and the operation record of the test resource, the test resource is generated by the test task, including the equipment participating in the test and its proxy forwarding program, simulation program, and simulation program; the resource lineage data platform includes multiple distributed server nodes, and one of the distributed server nodes is selected as the main node; among the other distributed server nodes, some nodes are used as client nodes for human-computer interaction, and the remaining nodes are used as backup nodes responsible for storing the lineage relationship of the test resources, wherein each backup node stores the complete lineage relationship of all test resources;

[0026] Synchronization module: configured to monitor the input of the client node. When the client node sends an operation request, the master node starts to check the lineage relationship of the test resources stored in each backup node, and regards the backup node with abnormal lineage relationship of the stored test resources as an abnormal node. The correct lineage relationship of the test resources is determined by the error correction algorithm, and the content stored in the abnormal node is corrected according to the correct lineage relationship of the test resources, so as to realize the synchronization of the lineage relationship of the test resources stored in each backup node.

[0027] The ownership determination module is configured to determine the ownership of each test resource based on the lineage relationship of the test resources in the backup node and the developer information of each test resource.

[0028] The present invention provides an electronic device, comprising:

[0029] at least one processor; and

[0030] a memory communicatively connected to the at least one processor; wherein,

[0031] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method described above.

[0032] The present invention provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable the computer to execute the method as described above.

[0033] The present invention analyzes the lineage relationship of experimental resources, establishes a decentralized and distributed resource lineage data platform, records the entire life cycle of experimental resources, and provides an effective basis for confirming the ownership and confirmation of experimental resources. The resources in the joint experiment are recorded throughout their life cycle, and real-time synchronization is performed when resources are created, updated, inherited, and destroyed, providing resource traceability when confirming the ownership of experimental resources.

[0034] It should be understood that the contents described in the summary of the invention are not intended to limit the key or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, among which:

[0036] Figure 1 A schematic diagram of a method for determining ownership of experimental resources in the prior art;

[0037] Figure 2 A flow chart of the intelligent test task right confirmation method for test resource lineage proposed by the present invention;

[0038] Figure 3 It is a functional composition diagram of the intelligent test task ownership confirmation method oriented to the test resource lineage of the present invention;

[0039] Figure 4 It is a schematic diagram of the distributed node fault-tolerant algorithm flow of the present invention;

[0040] Figure 5 It is a schematic diagram of the asymmetric encryption algorithm flow of the present invention;

[0041] Figure 6 It is a schematic diagram of a flow chart of a specific embodiment of the present invention;

[0042] Figure 7 This is a schematic diagram of the structure of the intelligent test task rights confirmation device for test resource lineage proposed by the present invention. DETAILED DESCRIPTION

[0043] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0044] Figure 2 FIG. 1 is a schematic diagram of an intelligent test task right confirmation method for test resource lineage. It should be understood that in other embodiments, the order of some steps can be interchanged according to actual needs, or some steps can be omitted or deleted. Figure 2 As shown, the method includes:

[0045] Step S1: construct a decentralized, distributed resource lineage data platform, which is used to store interfaces provided after the test resources are encapsulated, lineage relationships of the test resources, and operation records of the test resources. The test resources are generated by the test tasks, including the equipment participating in the test and its proxy forwarding program, simulation program, and simulation program; the resource lineage data platform includes multiple distributed server nodes, and one of the distributed server nodes is selected as the main node; among the other distributed server nodes, some nodes are used as client nodes for human-computer interaction, and the remaining nodes are used as backup nodes responsible for storing the lineage relationships of the test resources, wherein each backup node stores the complete lineage relationships of all test resources;

[0046] Step S2: Listen to the input of the client node. When the client node sends an operation request, the master node starts to check the lineage relationship of the test resources stored in each backup node, and regards the backup node with abnormal lineage relationship of the stored test resources as an abnormal node. The correct lineage relationship of the test resources is determined by the error correction algorithm, and the content stored in the abnormal node is corrected according to the correct lineage relationship of the test resources, so as to achieve synchronization of the lineage relationship of the test resources stored in each backup node.

[0047] Step S3: Determine the ownership of each test resource based on the lineage relationship of the test resources in the backup node and the developer information of each test resource.

[0048] Since military joint experiments are conducted over large geographical areas and the experimental execution units are relatively dispersed, it is difficult to establish a centralized platform in a fixed location and managed by a single organization. This invention proposes a distributed resource lineage storage solution, which divides resource lineage information into multiple copies and stores them on multiple anonymous distributed nodes to improve the fairness and disaster tolerance of ownership confirmation.

[0049] Furthermore, the lineage relationship of the test resources includes iterative relationship, inheritance relationship, and derivative relationship. Iterative relationship refers to the relationship between different updated versions of the same test resource; inheritance relationship refers to the relationship between a new test resource obtained after modification based on an existing test resource and the original test resource. The new test resource has a brand new name, code and version number, and can be regarded as a development branch of the original test resource. Modification refers to the secondary development of existing content based on the existing test resource to generate a new test resource; derivative relationship refers to the relationship between a new test resource derived from a plurality of existing test resources after combination and / or splicing and / or fusion and the original test resource from which the new test resource is derived.

[0050] In other words, resource lineage refers to the iteration, inheritance, and derivation relationship of experimental resources. Iteration relationship refers to the update of different versions of the same experimental resource, and there is a strict order relationship between resources that meet the iteration relationship. Inheritance relationship refers to the relationship between a new resource obtained after modification based on an existing resource and the original resource. The new resource has a brand new name, code and version number, and can be regarded as a development branch of the original resource. Derivation relationship refers to the new resource derived from the combination, splicing and fusion of multiple existing resources. Compared with the inheritance relationship with a single source, the lineage of the derivative relationship is more complex and the difficulty of confirming the ownership is greater. The storage content of the resource lineage includes different versions of the same resource, the change of the same version in the experimental use status, the development branch derived from different resources, etc., and records and tracks the entire life cycle of the experimental resources. When the experimental resource is created, it will be registered in the resource lineage, record its creator, and record its operator information every time the information is changed thereafter. In the resource lineage, whenever the same resource is iteratively updated, the version number will be assigned in sequence, and the operator of each update will be recorded. At the same time, the resource content of the historical version will also be uploaded and saved. Use one or more existing resources to derive and develop new resource branches. The lineage relationship of the original resources will be inherited to the new resources. On this basis, the developer's information will be recorded to confirm ownership and trace responsibility.

[0051] In the present invention, after the lineage information of the experimental resource changes, all nodes update the local lineage database. In order to ensure the correctness of the lineage information, the distributed network will synchronize the lineage information every once in a while, find out the abnormal nodes by comparing the data of all nodes, and repair the lineage information stored in them.

[0052] The step S2 comprises:

[0053] Step S21: The master node monitors that the client node sends an operation request to the master node<REQUEST,o,t,c> σc; where REQUEST is the instruction word, o is the operation content, t is the time when the operation request is issued, c is the client node information that issues the operation request, and σc is the identity verification information of the client that issues the operation request;

[0054] Step S22: The master node receives the operation request and then sends a pre-preparation message to each backup node.<PRE-PREPARE,v,n,d> ,m>; where PRE-PREPARE is the instruction word, m is the message in the operation request, d is the summary of the message of the operation request, v is the view number corresponding to the operation request, and n is the number of the operation request;

[0055] Step S23: The backup node receives the pre-prepare message and sends a prepare message to the other backup nodes.<PREPARE,v,n,d1,i> , and simultaneously receive preparation messages from the remaining backup nodes, wherein d1 is a summary of the lineage relationship of the test resources stored in the backup node that sends the preparation message and is identified by the backup node that sends the preparation message; compare whether the summary contents of the lineage relationship of the same test resource of the backup node that receives the preparation message and each backup node that sends the preparation message are the same; if they are the same, the corresponding backup node that sends the preparation message is used as a backup node that has passed the inspection, and the backup node that receives the preparation message writes the preparation message from the backup node that has passed the inspection into the message log; if they are not the same, the corresponding backup node that sends the preparation message is used as a backup node that has failed the inspection;

[0056] For any backup node, when it is verified as a verified backup node by more than or equal to 2f+1 other backup nodes, the backup node is regarded as a normal node; otherwise, the backup node is regarded as an abnormal node, where N>3f+1, N is the total number of distributed service nodes, and f is a parameter;

[0057] Step S24: Summarize all abnormal nodes, and modify the content stored in the abnormal nodes according to the lineage relationship of the test resources in the normal nodes;

[0058] Step S25: The master node confirms that all abnormal nodes have been corrected, and after that stage, sends the processing results to the client node.

[0059] Furthermore, the selection formula of the master node is:

[0060] p=v mod|R|

[0061] Where v is the view number; R is the total number of distributed server nodes. When the master node fails or is overthrown, the view change is initiated, the view number is assigned the value of the original view number plus 1, and then the master node is selected according to the selection formula, and the tasks that have not been processed by the previous master node are inherited.

[0062] When the lineage information of the experimental resource changes, all nodes update the local lineage database. In order to ensure the correctness of the lineage information, the distributed network will synchronize the lineage information every once in a while, compare the data of all nodes, find out the abnormal nodes, and repair their stored lineage information.

[0063] The specific algorithm for data synchronization between nodes is the Practical Byzantine Fault Tolerance (PBFT) algorithm. This algorithm allows no more than one-third of the network nodes to report errors, that is, it satisfies the formula:

[0064] N>3f+1

[0065] Where N represents the total number of nodes, and f represents the number of faulty nodes. This algorithm aims to solve the problem of how to ensure the consistency and correctness of the final decision when there are malicious nodes in the entire network. The PBFT algorithm divides nodes into three categories: client, master node, and backup node.

[0066] 1) Client: The requester, the request is<REQUEST,o,t,c> σc, where t represents the timestamp of the current time, o represents the operation to be performed, and c represents the client node that sends the request;

[0067] 2) Master node: mainly accepts and sorts client requests and broadcasts information to backup nodes;

[0068] 3) Backup node: mainly receives node information and performs verification. After the verification is successful, the corresponding operation is completed and the result is transmitted to the client. The result is<REPLY,v,t,c,i,r> σi, where v is the current view number view, t is the timestamp of the client's relaxation request, c is the client, i is the number of the node processing the request id_node, and r is the result response obtained after executing the requested operation o.

[0069] The set of all nodes is represented by the capital letter R. Each replica in the geometry can be represented by an integer from 0 to (R-1). The ideal number of nodes in the set is:

[0070] |R|=3f+1

[0071] Where f is the number of error nodes.

[0072] The selection formula of the master node is:

[0073] p=v mod|R|

[0074] Where v is the view number. When the master node fails or is overthrown, the view change is initiated and a new node is selected using this formula.

[0075] In the specific implementation, the PBFT algorithm divides the process into five stages: request stage, pre-preparation stage, preparation stage, submission stage, and reply stage. The pre-preparation stage, preparation stage, and submission stage are three key stages. The pre-preparation and preparation stages ensure that the order of request sending in the same view is correct; the preparation and submission stages ensure that the confirmation requests between different views are in order.

[0076] The step S3: determining the ownership of each test resource based on the lineage relationship of the test resources in the backup node and the developer information of each test resource, includes:

[0077] For experimental resources without forward lineage relationships, the ownership rights belong to the creator of the experimental resources; for experimental resources with iterative relationships, the ownership rights belong to the creator of the experimental resources; for experimental resources that constitute inheritance relationships, the ownership rights of the experimental resources belong to the creators of all inherited experimental resources; for experimental resources that constitute derivative relationships, the ownership rights of the experimental resources belong to all users who use the experimental resources derivatively and the creator of the experimental resources.

[0078] In the present invention, in terms of security, malicious modification of lineage data is prevented by the scale of node numbers, a dynamic node model is adopted, active nodes are replaced regularly, and node ownership information is strictly protected during use.

[0079] The resource ownership confirmation method oriented to resource lineage builds lineage relationships for the unified description and definition model of experimental resources, resource digital construction, resource verification, and update and iteration processes, providing support for the relationship combing, tracking and evidence storage of the entire process of experimental resource generation and resource governance. Figure 3 As shown, the technical solution proposed by the present invention mainly includes two modules: distributed lineage storage and resource service encryption.

[0080] In terms of resource service encryption, in order to prevent the experimental resources from being redeveloped without being recorded in the lineage management system, the present invention proposes a method for encrypting resource services.

[0081] The test resources are stored on several distributed service nodes. Each test resource is encapsulated and provides an interface. The interface is stored in the distributed service node that stores the test resources corresponding to the interface. When the test resources are secondary developed, the test resources are called according to the interface and the lineage information of the test resources is updated; the lineage information of the test resources is encapsulated on the backup node.

[0082] In the present invention, the experimental resources are packaged after being digitized and stored in the form of resource service programs, avoiding the plain text storage of resource data through packaging. When the resources are secondary developed, they can only be called based on the interface of the packaged program without destroying the original structure of the resource service, or the original data of the experimental resources can be privately provided by the owner of the ownership of the resource and the modifying party after negotiation. The resource lineage management system will not store the data of the resource itself, but only provide packaged experimental resource services.

[0083] After the resources are packaged, in order to provide a technical basis for ownership confirmation, the experimental resource lineage management platform will package the resource lineage information in the program as a basis for ownership confirmation.

[0084] When the lineage relationship of the experimental resource is embedded in the resource and transmitted between distributed servers, an encryption algorithm is used to avoid plain text transmission. In the technical solution proposed by the present invention, an asymmetric encryption technology is used to process the lineage information. In this algorithm, the encryption and decryption keys are unrelated and there is no need to share the keys in advance. Although the efficiency is not good, the security is high and it is suitable for the actual application scenario of resource ownership confirmation.

[0085] The distributed resource lineage data platform holds a set of public keys, and each experimental resource has a unique private key. The distributed resource lineage data platform uses the public key for encryption and decryption, and the platform users use the private key. The advantage of this method is that even if a user accidentally leaks the private key, the security of other users in the platform can be guaranteed. In addition, the public key and private key are dynamically updated, generated by a set of randomly generated initialization parameters, and dynamically replaced regularly.

[0086] When the experimental resource lineage information is updated, the identity of the operator is verified by digital signature technology. The digital signature consists of two parts, namely the hash value of the resource lineage content and the private key of the resource owner. The system will use a commonly agreed hash value calculation method based on the content of the resource lineage to calculate the content summary of the lineage information. The hash value calculation process is irreversible, and it is impossible to reverse the original text from the summary information by inverse operation. Moreover, any slight modification in the original resource lineage data will cause a significant change in the hash value. The hash value algorithm can accurately capture the modification changes of the original data and prevent errors in the transmitted content. The digital signature generated in this way is unique and difficult to crack. It is a safe encryption method while ensuring that the encryption algorithm parameters are not leaked.

[0087] The ownership confirmation method for experimental resource lineage involved in this application can safely record the lineage information of resources, provide a strong basis for confirming the ownership of experimental resources, and improve the system disaster recovery capability and effectively prevent malicious behavior through distributed storage and encryption technology.

[0088] The present invention adopts the method of recording resource lineage information to provide a basis for confirming resource ownership. A distributed resource lineage information management system is adopted to ensure the security of resource lineage management through a decentralized topological structure. Resource services are encapsulated to prevent users from modifying resources privately. Resource lineage information is injected into the encapsulated resource service to bind ownership to content. Asymmetric encryption is used to encrypt resource information, and digital signatures are introduced to authenticate operating users to prevent malicious attacks.

[0089] The experimental resource title confirmation method involved in the present invention is based on actual needs. In order to solve the problem that the existing resource title confirmation methods are not applicable to joint test environments with high update frequency and scattered experimental resources, a decentralized dynamic resource lineage database is established to record the resources in the joint test throughout their life cycle, perform real-time synchronization when resources are created, updated, inherited, and destroyed, and provide resource traceability when confirming the ownership of experimental resources.

[0090] The resource right confirmation method based on resource lineage builds lineage relationships for the unified description definition model of experimental resources, resource digital construction, resource verification, and update and iteration processes, providing support for applications such as relationship combing, tracking and evidence storage throughout the entire process of experimental resource generation and resource governance.

[0091] The resource lineage-based property rights confirmation method proposed in the present invention can safely record the lineage information of resources, provide a strong basis for confirming the ownership of experimental resources, and improve the system disaster recovery capability and effectively prevent malicious behavior through distributed storage and encryption technology.

[0092] The present invention provides a specific embodiment of an intelligent test task right confirmation method oriented to test resource lineage.

[0093] The ownership confirmation method for the test resource lineage proposed in the present invention is used to manage the lineage of resources in a certain seeker anti-interference joint test to confirm the ownership of the test resources. In this embodiment, the test resources come from different participating units and have been modified, merged and branched for many times during the test development and deployment stage.

[0094] The following is a description of the device used to execute the present application. The specific implementation process and technical effects are described above and will not be repeated below.

[0095] Optionally, an embodiment of the present application provides an intelligent test task right confirmation device for test resource lineage, the device comprising:

[0096] Initialization module: configured to build a decentralized, distributed resource lineage data platform, the resource lineage data platform is used to store the interface provided after the test resource is encapsulated, the lineage relationship of the test resource and the operation record of the test resource, the test resource is generated by the test task, including the equipment participating in the test and its proxy forwarding program, simulation program, and simulation program; the resource lineage data platform includes multiple distributed server nodes, and one of the distributed server nodes is selected as the main node; among the other distributed server nodes, some nodes are used as client nodes for human-computer interaction, and the remaining nodes are used as backup nodes responsible for storing the lineage relationship of the test resources, wherein each backup node stores the complete lineage relationship of all test resources;

[0097] Synchronization module: configured to monitor the input of the client node. When the client node sends an operation request, the master node starts to check the lineage relationship of the test resources stored in each backup node, and regards the backup node with abnormal lineage relationship of the stored test resources as an abnormal node. The correct lineage relationship of the test resources is determined by the error correction algorithm, and the content stored in the abnormal node is corrected according to the correct lineage relationship of the test resources, so as to realize the synchronization of the lineage relationship of the test resources stored in each backup node.

[0098] The ownership determination module is configured to determine the ownership of each test resource based on the lineage relationship of the test resources in the backup node and the developer information of each test resource.

[0099] The above-mentioned device is used to execute the method provided by the aforementioned embodiment, and its implementation principle and technical effect are similar, which will not be repeated here.

[0100] The above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASIC), or one or more digital singnal processors (DSP), or one or more field programmable gate arrays (FPGA). For another example, when a module is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0101] The above modules can be connected or communicated with each other via a wired connection or a wireless connection. The wired connection may include a metal cable, an optical cable, a hybrid cable, etc., or any combination thereof. The wireless connection may include a connection in the form of a LAN, a WAN, Bluetooth, a ZigBee, or NFC, or any combination thereof. Two or more modules may be combined into a single module, and any one module may be divided into two or more units. Those skilled in the art will clearly understand that for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the method embodiment, and will not be repeated in this application.

[0102] It should be noted that the above modules can be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASIC), or one or more digital singnal processors (DSP), or one or more field programmable gate arrays (FPGA). For another example, when a module above is implemented in the form of a processing element scheduling program code, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call program codes. For another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0103] The electronic device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Among them, the processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the electronic device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, near field communication (NFC) or other technologies. The display screen of the electronic device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic device can be a touch layer covered on the display screen, or a button, trackball or touchpad set on the housing of the electronic device, or an external keyboard, touchpad or mouse, etc.

[0104] The present application also provides a program product, such as a computer-readable storage medium, including a program, which is used to execute the above method embodiment when executed by a processor.

[0105] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0106] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0107] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0108] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (English: processor) to perform some steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (English: Read-Only Memory, abbreviated: ROM), random access memory (English: Random Access Memory, abbreviated: RAM), disk or optical disk and other media that can store program codes.

Claims

1. An intelligent test task right confirmation method for test resource lineage, characterized in that: The method comprises the following steps: Step S1: construct a decentralized, distributed resource lineage data platform, which is used to store interfaces provided after the test resources are encapsulated, lineage relationships of the test resources, and operation records of the test resources. The test resources are generated by the test tasks, including the equipment participating in the test and its proxy forwarding program, simulation program, and simulation program; the resource lineage data platform includes multiple distributed server nodes, and one of the distributed server nodes is selected as the master node; Among other distributed server nodes, some nodes serve as client nodes for human-computer interaction, and the rest serve as backup nodes responsible for storing the lineage relationship of experimental resources, where each backup node stores the complete lineage relationship of all experimental resources; Step S2: Listen to the input of the client node. When the client node sends an operation request, the master node starts to check the lineage relationship of the test resources stored in each backup node, and regards the backup node with abnormal lineage relationship of the stored test resources as an abnormal node. The correct lineage relationship of the test resources is determined by the error correction algorithm, and the content stored in the abnormal node is corrected according to the correct lineage relationship of the test resources, so as to achieve synchronization of the lineage relationship of the test resources stored in each backup node. Step S3: Determine the ownership of each test resource based on the lineage relationship of the test resources in the backup node and the developer information of each test resource.

2. The method according to claim 1, characterized in that The step S2 comprises: Step S21: The master node monitors that the client node sends an operation request to the master node<REQUEST,o,t,c> σc; where REQUEST is the instruction word, o is the operation content, t is the time when the operation request is issued, c is the client node information that issues the operation request, and σc is the identity verification information of the client that issues the operation request; Step S22: The master node receives the operation request and then sends a pre-preparation message to each backup node.<PRE-PREPARE,v,n,d> ,m>; where PRE-PREPARE is the instruction word, m is the message in the operation request, d is the summary of the message of the operation request, v is the view number corresponding to the operation request, and n is the number of the operation request; Step S23: The backup node receives the pre-prepare message and sends a prepare message to the other backup nodes.<PREPARE,v,n,d1,i> , and simultaneously receive preparation messages from the remaining backup nodes, wherein d1 is a summary of the lineage relationship of the test resources stored in the backup node that sends the preparation message and is identified by the backup node that sends the preparation message; compare whether the summary contents of the lineage relationship of the same test resource of the backup node that receives the preparation message and each backup node that sends the preparation message are the same; if they are the same, the corresponding backup node that sends the preparation message is used as a backup node that has passed the inspection, and the backup node that receives the preparation message writes the preparation message from the backup node that has passed the inspection into the message log; if they are not the same, the corresponding backup node that sends the preparation message is used as a backup node that has failed the inspection; For any backup node, when it is verified as a verified backup node by more than or equal to 2f+1 other backup nodes, the backup node is regarded as a normal node; otherwise, the backup node is regarded as an abnormal node, where N>3f+1, N is the total number of distributed service nodes, and f is a parameter; Step S24: Summarize all abnormal nodes, and modify the content stored in the abnormal nodes according to the lineage relationship of the test resources in the normal nodes; Step S25: The master node confirms that all abnormal nodes have been corrected, and after that stage, sends the processing results to the client node.

3. The method as claimed in claim 2, characterized in that The selection formula of the master node is: p=v mod|R| Where v is the view number; R is the total number of distributed server nodes. When the master node fails or is overthrown, the view change is initiated, the view number is assigned the value of the original view number plus 1, and then the master node is selected according to the selection formula, and the tasks that have not been processed by the previous master node are inherited.

4. The method according to claim 1, characterized in that The lineage relationship of the test resources includes an iteration relationship, an inheritance relationship, and a derivative relationship.

5. The method according to claim 3, characterized in that The test resources are stored on several distributed service nodes. Each test resource is encapsulated and provides an interface. The interface is stored in the distributed service node that stores the test resources corresponding to the interface. When the test resources are secondary developed, the test resources are called according to the interface and the lineage information of the test resources is updated; the lineage information of the test resources is encapsulated on the backup node.

6. An intelligent test task right confirmation device for test resource lineage, characterized in that: The device comprises: Initialization module: configured to build a decentralized, distributed resource lineage data platform, the resource lineage data platform is used to store the interface provided after the test resource is encapsulated, the lineage relationship of the test resource and the operation record of the test resource, the test resource is generated by the test task, including the equipment participating in the test and its proxy forwarding program, simulation program, and simulation program; the resource lineage data platform includes multiple distributed server nodes, and one of the distributed server nodes is selected as the main node; among the other distributed server nodes, some nodes are used as client nodes for human-computer interaction, and the remaining nodes are used as backup nodes responsible for storing the lineage relationship of the test resources, wherein each backup node stores the complete lineage relationship of all test resources; Synchronization module: configured to monitor the input of the client node. When the client node sends an operation request, the master node starts to check the lineage relationship of the test resources stored in each backup node, and regards the backup node with abnormal lineage relationship of the stored test resources as an abnormal node. The correct lineage relationship of the test resources is determined by the error correction algorithm, and the content stored in the abnormal node is corrected according to the correct lineage relationship of the test resources, so as to realize the synchronization of the lineage relationship of the test resources stored in each backup node. The ownership determination module is configured to determine the ownership of each test resource based on the lineage relationship of the test resources in the backup node and the developer information of each test resource.

7. An electronic device, comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 5.

8. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 5.

Images