Fault test generation support device and fault test generation support method
The fault test generation support device efficiently generates comprehensive tests for cloud-based systems by combining system configuration and failure reproduction methods, addressing network delays and service errors, and optimizing test combinations.
Patent Information
- Application Number
- JP2021105389
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-06-25
- Publication Date
- 2024-11-20
- Estimated Expiration
- 2041-06-25
AI Technical Summary
Existing failure test technologies for cloud-based systems fail to account for network delays and specific error responses from services, and do not efficiently handle communication path failures, leading to an exponential increase in test combinations as the number of components increases.
A fault test generation support device and method that combines system configuration information with failure reproduction method definitions to efficiently generate comprehensive tests by identifying and setting failure patterns based on communication routes and service interactions.
Enables efficient and comprehensive test generation for arbitrary failures in cloud-based systems by accurately determining communicable combinations and setting failure patterns, reducing the number of necessary tests.
Smart Images

Figure 0007587479000001 
Figure 0007587479000002 
Figure 0007587479000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a fault test generation support device and a fault test generation support method. [Background technology]
[0002] The number of projects to build systems by combining multiple cloud services is increasing. Therefore, in order to improve the efficiency of the system construction, the infrastructure configuration is often defined as IaC (Infrastructure as Code) and the construction is automated. Among such system developments, in the development of systems that require high reliability, such as financial systems, fault testing is carried out. Fault testing involves intentionally causing faults to ensure reliability and verifying the operation of the system. Specifically, this includes stopping the server, stopping the network switch, and pulling out the disk.
[0003] As a conventional technique related to such fault testing, for example, a technique for evaluating the resiliency of a distributed computing service provided by a group of interacting servers (see Patent Document 1) has been proposed.
[0004] The technique is a computer-implemented method for verifying the resiliency of a networked application, comprising identifying a plurality of active application components within a network used to provide the networked application, selecting at least one of the identified application components based on one or more selection criteria, terminating the selected active application component, and monitoring one or more remaining active application components within the network following the termination of the selected active application component.
[0005] Also, a test control device that appropriately controls the automation of non-functional tests (see Patent Document 2) has been proposed.
[0006] This technology relates to a test control device that includes a memory unit that stores fault configuration information, which is information regarding the location at which a fault will be generated for testing of the system, for each configuration type of the system; an acquisition unit that acquires the configuration type of a test target system to be tested; a determination unit that acquires from the memory unit fault configuration information corresponding to the configuration type of the test target system acquired by the acquisition unit and uses the fault configuration information to determine the location at which a fault will be generated in the test target system; and a test unit that tests the test target system by generating a fault at the location at which a fault will be generated determined by the determination unit. [Prior art documents] [Patent documents]
[0007] [Patent Document 1] Special Publication No. 2013-537344 [Patent Document 2] JP 2015-26328 A Summary of the Invention [Problem to be solved by the invention]
[0008] In a system that combines cloud services, in addition to simple server shutdowns, fault testing tailored to the cloud service in question (e.g., simulating communication outages within the cloud, reproducing specific error responses from the service, etc.) is also necessary. However, in the conventional technology, the target failure is limited to the disappearance of a VM (Virtual Machine) or a process. It does not cover other failures, such as error responses from the service.
[0009] In addition, cases where a failure occurs in a communication path are not taken into consideration. Even if such a communication path failure is handled, a failure test is performed simply assuming that a communication path exists between all combinations of system components.
[0010] On the other hand, in systems built on the cloud, it is easy to increase the number of components (services used) as needed due to the excellent scalability and rapid service introduction that come with the cloud. As a result, different testing methods are required for each of these components, which tend to increase in number, and if fault testing is performed for all combinations of components, the number of tests can increase explosively.
[0011] Therefore, an object of the present invention is to provide a technique for efficiently generating comprehensive tests for any fault by combining system configuration information and fault reproduction method definitions. [Means for solving the problem]
[0012] The fault test generation support device of the present invention, which solves the above-mentioned problems, is characterized in that it comprises a storage device that stores configuration information regarding a system configured by combining multiple cloud services and a fault reproduction method definition defined for the system, a process for extracting information regarding the communication paths in each service defined in the configuration information, a process for referring to a fault pattern defined in the fault reproduction method definition and identifying information about the communication paths of a service corresponding to each service of the source and destination of communication indicated by the fault pattern, a process for generating combinations of the source and the destination based on the identified information about the communication paths and determining whether communication is possible for each combination, and a calculation device that executes a process for setting the combination that is found to be communication possible as a result of the determination to the fault pattern as information about the insertion point of a fault test. Furthermore, the fault test generation support method of the present invention is characterized in that an information processing device retains configuration information regarding a system configured by combining multiple cloud services and a fault reproduction method definition defined for the system, and executes a process of extracting information regarding the communication paths in each service defined in the configuration information, a process of referring to a fault pattern defined in the fault reproduction method definition and identifying information regarding the communication paths of services corresponding to the source and destination services of the communication indicated by the fault pattern, a process of generating combinations of the source and the destination based on the identified information on the communication paths, and a process of determining whether communication is possible for each combination, and a process of setting the combination that is found to be capable of communication as information on the insertion point of a fault test in the fault pattern. Effect of the Invention
[0013] According to the present invention, by combining system configuration information with a fault reproduction method definition, it is possible to efficiently generate comprehensive tests for any fault. [Brief description of the drawings]
[0014] [Figure 1] FIG. 2 is a diagram illustrating a functional configuration of a fault test generation support device according to the present embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a fault test generation support device according to the present embodiment. [Diagram 3] FIG. 2 is a diagram illustrating an example of a flow of a fault test generation support method according to the present embodiment. [Figure 4A] FIG. 11 is a diagram illustrating an example of a failure reproduction method definition according to the present embodiment. [Figure 4B] FIG. 4 is a diagram illustrating an example of system configuration information according to the present embodiment. [Figure 4C] FIG. 13 is a diagram illustrating an example of a fault test list according to the present embodiment. [Diagram 5] FIG. 2 is a diagram illustrating an example of a flow of a fault test generation support method according to the present embodiment. [Figure 6] FIG. 4 is a diagram illustrating an example of system configuration information according to the present embodiment. [Figure 7] FIG. 4 is a diagram illustrating an example of system configuration information according to the present embodiment. [Figure 8] FIG. 2 is a diagram illustrating an example of a concept of extracting communication path information in the present embodiment. [Figure 9] FIG. 2 is a diagram illustrating an example of a concept of extracting communication path information in the present embodiment. [Figure 10] FIG. 4 is a diagram illustrating an example of communication path information in the present embodiment. [Figure 11] FIG. 4 is a diagram illustrating an example of communication path information in the present embodiment. [Figure 12] FIG. 2 is a diagram illustrating an example of a flow of a fault test generation support method according to the present embodiment. [Figure 13] FIG. 2 is a diagram illustrating an example of a flow of a fault test generation support method according to the present embodiment. [Figure 14] FIG. 2 is a diagram illustrating an example of a fault test generation concept in the present embodiment. [Figure 15] FIG. 2 is a diagram illustrating an example of a fault test generation concept in the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0015] <Functional configuration> Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. Fig. 1 is a diagram showing an example of a functional configuration of a fault test generation support device 100 according to this embodiment. The fault test generation support device 100 shown in Fig. 1 is a computer that combines system configuration information and fault reproduction method definitions to efficiently generate comprehensive tests for any fault.
[0016] 1, the fault test generation support device 100 of this embodiment includes, as functional units, a service information test generation unit 110, a communication path information extraction unit 111, and a communication fault test generation unit 112. In addition, in order for these functional units to operate, and as information generated as a result of their operation, the device holds information such as a fault reproduction method definition 125, system configuration information 126, communication path information 127, and a fault test list 128.
[0017] Among these, the service fault test generation unit 110 executes a series of processes, such as selecting one fault pattern from the fault reproduction method definition 125, acquiring the usage definition of the service targeted by that fault pattern from the system configuration information 126, and further registering the fault pattern and the information on the insertion point for each service usage definition in the fault test list 128. In other words, this is a function that generates fault tests for services in addition to fault tests for communication paths.
[0018] Moreover, the communication path information extraction unit 111 is a function that extracts information about the communication path for each service defined in the system configuration information 126 .
[0019] In addition, the communication fault test generation unit 112 refers to the fault pattern defined in the fault reproduction method definition 125, and identifies information on the communication paths (communication path information 127) of the services corresponding to the source and destination services of the communication indicated by the fault pattern.
[0020] The communication fault test generation unit 112 also generates combinations of source and destination based on the information of the communication path specified here, and judges whether communication is possible for each combination. The communication fault test generation unit 112 also sets the combinations that are found to be communicable as a result of the above judgment as the information of the insertion point of the fault test in the corresponding fault pattern, and registers them in the fault test list. <Hardware configuration> 2 shows the hardware configuration of the fault test generation support device 100 of this embodiment. That is, the fault test generation support device 100 includes a storage device 101, a memory 103, an arithmetic device 104, and a communication device 105.
[0021] Of these, the storage device 101 is configured with an appropriate non-volatile storage element such as an SSD (Solid State Drive) or a hard disk drive.
[0022] The memory 103 is composed of a volatile storage element such as a RAM.
[0023] The arithmetic device 104 is a CPU (Central Processing Unit) that reads out the program 102 stored in the storage device 101 into the memory 103 and executes the program, controls the device itself, and performs various types of judgment, calculation, and control processing.
[0024] The functions implemented by the execution of the program 102 by the arithmetic unit 104 are a service fault test generator 110 , a communication path information extractor 111 , and a communication fault test generator 112 .
[0025] The communication device 105 is assumed to be a network interface card or the like that is connected to an appropriate network and handles communication processing with external terminals and the like.
[0026] If the fault test generation support device 100 is a stand-alone machine, it is preferable that it further comprises an input device for accepting key input or voice input from the user, and an output device such as a display for displaying processed data.
[0027] In addition to the program 102 for implementing the functions required for the fault test generation support device of this embodiment, at least a fault reproduction method definition 125, system configuration information 126, communication path information 127, and a fault test list 128 are stored in the storage device 101. However, the details of these pieces of information will be described later. <Flow example: Service failure test generation> The actual procedure of the fault test generation support method in this embodiment will be described below with reference to the drawings. Various operations corresponding to the fault test generation support method described below are realized by a program that the fault test generation support device 100 reads into a memory or the like and executes. This program is composed of codes for performing the various operations described below.
[0028] 3 is a diagram showing an example of a flow of the fault test generation support method in this embodiment. In this case, the service fault test generation unit 110 of the fault test generation support device 100 determines whether or not there is any fault pattern in the fault reproduction method definition 125 (e.g., FIG. 4A) that has not been processed as a target of this flow (s10).
[0029] For this reason, the service fault test generation unit 110 assigns a flag to each record of the fault reproduction method definition 125, i.e., information of the fault patterns that have been processed in this flow (e.g., identification information such as #), and stores and manages the information in the memory 103.
[0030] If it is determined that there are no unprocessed fault patterns (s10: No), the service fault test generator 110 ends this flow.
[0031] On the other hand, if the result of the above determination is that there is an unprocessed fault pattern (s10: Yes), the service fault test generator 110 appropriately selects (s11) one of the unprocessed fault patterns in the fault reproduction method definition 125. The selection method is assumed to be one in which the fault pattern with the smallest value of the identification information is selected.
[0032] The service fault test generator 110 also acquires (s12) from the system configuration information 126 (FIG. 4B) the usage definition of the service targeted by the fault pattern selected in s11. In the specific example shown in FIG. 4B, the system configuration information of "AP1" and "AP2" (enclosed by dashed lines in the figure) describing "EC2" is extracted as the usage definition of the service corresponding to the record #001 of the fault pattern "target: service-EC2, fault: no response, method: instance shutdown" selected in s11.
[0033] Next, the service fault test generation unit 110 registers the fault pattern (in the above case, "Service-EC2, Fault: No Response, Method: Instance Stopped") and insertion point information (in the above case, "AP1", "AP2", etc.) for each service usage definition obtained in s12 in the fault test list 128 (Figure 4C), marks the fault pattern selected for processing this time as having been processed (for example, by adding a corresponding flag to the information managed in memory 103) (s13), and terminates this flow. <Flow example: Extracting communication route information> Next, the flow of extracting communication path information will be described. Fig. 5 is a diagram showing an example of the flow of the fault test generation support method in this embodiment. In this case, the communication path information extraction unit 111 of the fault test generation support device 100 acquires a list of services defined in the system configuration information 126 (Fig. 6) (s20). Note that it is also possible to assume a case where the identification information configuration information 126 has the configuration shown in Fig. 7. In the example of Fig. 7, a description of the connection definition between virtual networks is included.
[0034] In addition, the communication path information extraction unit 111 determines whether there is any service definition that has not been processed in this flow among the list acquired in s20 (s21). Note that the management of processed / unprocessed can be performed in the same manner as described in the above flow (FIG. 3).
[0035] If the result of this determination is that there is no unprocessed service definition (s21: No), the communication path information extraction unit 111 ends this flow.
[0036] On the other hand, if the result of the above determination is that there is an unprocessed service definition (s21: Yes), the communication path information extraction unit 111 selects one of the unprocessed service definitions (s22).
[0037] Next, the communication path information extraction unit 111 acquires (s23) security group information associated with the selected service from the system configuration information 126. In the system configuration information 126 illustrated in Fig. 8, this information is described in association with "#stateful communication control (security group) definition."
[0038] In addition, the communication path information extraction unit 111 acquires subnet information associated with the selected service from the system configuration information (s24). In the system configuration information 126 illustrated in FIG. 8, this information is described in association with "#subnet definition."
[0039] Next, the communication path information extraction unit 111 acquires communication control information associated with the subnet acquired in the previous step from the system configuration information (s25). In the system configuration information 126 illustrated in Fig. 8, this information is described in association with "#Stateless communication control (subnet communication control) definition."
[0040] In addition, the communication path information extraction unit 111 acquires information on the network (VPC) to which the selected service belongs from the system configuration information (s26). In the system configuration information 126 illustrated in FIG. 8, this information is described in relation to "#Virtual network definition."
[0041] Next, the communication path information extraction unit 111 acquires connection information between the VPC acquired in the previous step and other VPCs from the system configuration information (s27). In the system configuration information 126 illustrated in FIG. 9, this information is described in relation to "#Inter-virtual network connection definition."
[0042] The communication path information extraction unit 111 holds the acquired information as the communication path information 127, and marks the selected service as processed (s28), and ends the process. The communication path information 127 generated based on the concept illustrated in FIG. 8 is shown in FIG. 10. The communication path information generated based on the concept illustrated in FIG. 9 is shown in FIG. The communication path information 127 thus obtained is shown in Fig. 11. The difference is the presence or absence of the "VPC Peering" item. <Flow example: Communication failure test generation> Next, the flow of communication feasibility determination will be described. Fig. 12 is a diagram showing an example of the flow of the fault test generation support method in this embodiment. In this case, the communication fault test generation unit 112 of the fault test generation support device 100 determines whether there are any unprocessed fault patterns among the records, i.e., fault patterns, of the fault reproduction method definition 125 (s30). For the management of processed / unprocessed, an appropriate existing technology such as the method already described above may be adopted.
[0043] If the result of this determination is that there are no unprocessed fault patterns (s30: No), the communication fault test generator 112 ends this flow.
[0044] On the other hand, if the result of the above determination indicates that there is an unprocessed fault pattern (s30: Yes), the communication fault test generation unit 112 selects (s31) one of the unprocessed fault patterns from the fault reproduction method definition 125. In the example shown in Fig. 14, for example, "target: between communication and EC2, fault: communication delay, method: qdisc rule setting" is selected.
[0045] The communication fault test generation unit 112 also acquires (s32) communication path information 127 for all services that match the source service in the fault pattern selected in s31. This communication path information 127 is generated in the flow of Fig. 5 (Figs. 10 and 11). In the example shown in Fig. 14, "#1AP1" and "#1AP2" are acquired as "source candidates".
[0046] Next, the communication fault test generator 112 acquires communication path information for all services that match the destination service in the fault pattern selected in s32 (s33). In the example shown in Fig. 14, "#1AP1" and "#1AP2" are acquired as "destination candidates".
[0047] Furthermore, the communication fault test generation unit 112 generates all combinations of source-destination pairs using the communication path information 127 acquired in s32 and s33, and checks whether communication is possible (s34). Details of this process of checking whether communication is possible will be described later with reference to FIG.
[0048] Furthermore, the communication fault test generator 112 registers, for pairs that are communicable as a result of the check in s34, information on fault patterns and insertion points in the fault test list 128 (s35).
[0049] Next, the communication fault test generator 112 determines that the selected fault pattern has been processed (s36), and ends this flow. <Flow example: Determining whether communication is possible> Next, the flow of communication feasibility determination will be described. Fig. 13 is a diagram showing an example of the flow of the fault test generation support method in this embodiment. In this case, the communication fault test generation unit 112 of the fault test generation support device 100 generates all source-destination service pairs (s40), as explained in s34 in the above flow.
[0050] Next, the communication fault test generator 112 determines whether or not there are any unprocessed pairs among the pairs obtained in s40 (s41).
[0051] If the above-mentioned determination result indicates that there is no unprocessed pair (s41: No), the communication fault test generator 112 ends this flow.
[0052] On the other hand, if it is determined that there is an unprocessed pair (s41: Yes), the communication fault test generator 112 selects a pair (a source-destination service pair) from the unprocessed pairs. ) is selected (s42).
[0053] Furthermore, the communication fault test generation unit 112 judges whether communication from the source IP and security group to the destination IP and security group is permitted by the source security group for the pair selected in s42 (s43). In the image shown in Fig. 14, for example, it is judged whether communication from the source "#AP1" IP "10.0.1.*" and security group "AP-SG_1" to the destination "#AP2" IP "10.0.2.*" is permitted by the security group of "#AP1".
[0054] If the result of this determination is that the pair is not permitted to communicate (s43: No), the communication fault test generator 112 stores the pair as not permitted to communicate, for example, in the storage device 101 (s48), and transitions the process to s50.
[0055] On the other hand, if the result of this determination is that the combination is permitted for communication (s43: Yes), the communication fault test generator 112 transitions the process to s44.
[0056] Next, the communication fault test generation unit 112 judges whether communication from the source IP to the destination IP is permitted by the source NACL (Network Access Control List) (s44). For example, if the value of "Network ACL" for the service "EC2-AP1" in the communication path information 127 is specified as "allow to 10.0.3.0 / 16, deny all", communication is denied for IP addresses other than "10.0.3.0 / 16", and therefore if the destination IP is other than the IP address, it is judged that communication is not permitted.
[0057] The communication fault test generation unit 112 also determines whether communication is possible from the source VPC to the destination VPC (s45). In this case, the communication fault test generation unit 112 determines whether the identification information of the destination VPC is set in the "VPC Peering" field (see FIG. 11) of the source VPC in the communication path information 127, that is, whether the destination VPC is permitted as a communication destination (see FIG. 15). Note that if the source and destination VPCs are the same, it is naturally determined that communication is possible.
[0058] If the result of this determination is that the combination is not permitted for communication (s45: No), the communication fault test generator 112 executes the above-mentioned s48 and transitions to s50.
[0059] On the other hand, if the result of this determination is that the combination is permitted for communication (s45: Yes), the communication fault test generator 112 transitions the process to s46.
[0060] Next, the communication fault test generator 112 judges whether communication from the source IP to the destination IP is permitted by the source NACL (Network Access Control List) (s46). This judgment is the same procedure as the method described in s44, and differs from s44 only in that it judges whether communication is permitted by the destination network access control list.
[0061] If the result of this determination is that the combination is not permitted for communication (s46: No), the communication fault test generator 112 executes the above-mentioned s48 and transitions to s50.
[0062] On the other hand, if the result of this determination is that the combination is permitted for communication (s46: Yes), the communication fault test generator 112 transitions the process to s47.
[0063] Next, the communication fault test generator 112 calculates the source IP It is then determined whether communication from the security group to the destination IP and security group is permitted by the destination security group (s47). This determination is the same as the method described in s43, and differs from s43 only in that it determines whether communication is permitted by the destination security group.
[0064] If the result of this determination is that the combination is not permitted for communication (s47: No), the communication fault test generator 112 executes the above-mentioned s48 and transitions to s50.
[0065] On the other hand, if the result of the above determination is that the combination is permitted for communication (s47: Yes), the communication fault test generation unit 112 registers information on the fault pattern and insertion point for the pair that can communicate in the fault test list 128 (s49).
[0066] Next, the communication fault test generator 112 determines that the selected fault pattern has been processed (s50), and ends this flow.
[0067] Although the best mode for carrying out the present invention has been specifically described above, the present invention is not limited to this, and various modifications are possible without departing from the spirit and scope of the present invention.
[0068] According to this embodiment, by combining system configuration information with a fault reproduction method definition, it is possible to efficiently generate comprehensive tests for any fault.
[0069] The description in this specification makes clear at least the following: That is, in the fault test generation support device of this embodiment, the arithmetic device may extract, as information about the communication path, a security group associated with the service, a subnet associated with the service, a communication control associated with the subnet, a network to which the service belongs, and connection information between the network and another network.
[0070] This makes it possible to more efficiently extract information about communication paths. Furthermore, by combining system configuration information with fault reproduction method definitions, it becomes possible to more efficiently generate comprehensive tests for any fault.
[0071] In addition, in the fault test generation support device of this embodiment, when determining whether communication is possible, the calculation device may determine whether communication is possible between security groups and between subnets between the source and the destination.
[0072] This makes it possible to more efficiently and accurately determine whether communication is possible. Furthermore, by combining the system configuration information with the fault reproduction method definition, it becomes possible to more efficiently generate comprehensive tests for any fault.
[0073] In addition, in the fault test generation support method of this embodiment, the information processing device may extract information regarding the communication path, such as a security group associated with the service, a subnet associated with the service, communication control associated with the subnet, a network to which the service belongs, and connection information between the network and other networks.
[0074] In addition, in the fault test generation support method of this embodiment, when determining whether communication is possible, the information processing device may determine whether communication is possible between security groups and between subnets between the source and destination. [Explanation of symbols]
[0075] 100 Fault test generation support 101 Storage device 102 Programs 103 Memory 104 Arithmetic equipment 105 Communication equipment 110 Service Fault Test Generation Unit 111 Communication path information extraction unit 112 Communication Fault Test Generation Unit 125 Definition of how to reproduce the problem 126 System configuration information 127 Communication Route Information 128 Disability Test List
Claims
1. A storage device that stores configuration information regarding a system configured by combining a plurality of cloud services and a failure reproduction method definition defined for the system; a computing device which executes a process of extracting information on communication paths for each service defined in the configuration information, a process of referring to a failure pattern defined in the failure reproduction method definition and identifying information on the communication paths for a service corresponding to each service of a source and destination of communication indicated by the failure pattern, a process of generating combinations of the source and destination based on the identified information on the communication paths and judging whether communication is possible for each combination, and a process of setting the combinations which are found to be communicable as a result of the judgment in the failure pattern as information on an insertion point of a failure test; A fault test generation support device comprising:
2. The computing device includes: As the information regarding the communication path, a security group associated with the service, a subnet associated with the service, a communication control associated with the subnet, a network to which the service belongs, and connection information between the network and other networks are extracted.
2. The fault test generation support device according to claim 1.
3. The computing device includes: When determining whether or not the communication is possible, a determination is made as to whether or not communication between security groups and between subnets is possible between the source and the destination.
3. The fault test generation support device according to claim 2.
4. An information processing device, A system is configured by combining a plurality of cloud services. The system is configured to store configuration information and a failure reproduction method definition for the system. a process of extracting information on communication paths for each service defined in the configuration information; a process of referring to a failure pattern defined in the failure reproduction method definition and identifying information on the communication paths for a service corresponding to each service of a source and destination of communication indicated by the failure pattern; a process of generating combinations of the source and destination based on the identified information on the communication paths and judging whether communication is possible for each combination; and a process of setting the combinations that are found to be capable of communication as information on the insertion point of a failure test in the failure pattern. A fault test generation support method comprising:
5. The information processing device, extracting, as information related to the communication path, a security group associated with the service, a subnet associated with the service, a communication control associated with the subnet, a network to which the service belongs, and connection information between the network and other networks; 5. The method for supporting fault test generation according to claim 4.
6. The information processing device, When determining whether or not communication is possible, a determination is made as to whether or not communication between security groups and between subnets is possible between the source and the destination.
6. The fault test generation support method according to claim 5.
Citation Information
Patent Citations
Communication network management apparatus, and traffic confirmation test method for communication network
JP2005244363A
Elasticity verification of networked applications
JP2013537344A
Test control device, test control method, and test control program
JP2015026328A
Virtual apparatus testing device, virtual apparatus testing method, and virtual apparatus testing program
JP2016133885A
Systems, methods, and devices for securely managing network connections
JP2019511172A
