Virtual Service Testing via Input Duplication and Output Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a need for cost-effective and efficient testing of virtual services in Network Function Virtualization (NFV) systems to ensure quality and scalability without disrupting existing systems, as current testing methods are costly and often require downtime.

Innovation Solution

A method and system for testing virtual services by duplicating input data and processing it through both an updated and original system, with comparators to ensure output consistency, allowing for real-time testing of new or updated virtual services within an NFV-based network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional testing methods are used for virtual services, then testing can be performed, but testing costs are very high and system downtime is required

Engineering Contradiction:
Improveservice quality validationVSAvoidsystem downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a copy of the original system configuration including virtual services, physical network functions, and network infrastructure. This copy is used for testing purposes while the original system continues to operate, eliminating downtime requirements and enabling continuous service validation.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent performs testing actions in advance by validating new virtual service configurations in a copied environment before deploying them to the production system. This preliminary testing ensures service quality is validated before actual deployment, preventing potential service disruptions.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If traditional testing methods are used for virtual services, then testing can be performed, but testing costs are very high

Engineering Contradiction:
Improveservice quality validationVSAvoidtesting costs
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

Instead of creating multiple physical test environments, the patent uses virtualization to create software-based copies of system configurations. This approach significantly reduces hardware costs and resource consumption while maintaining testing effectiveness.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent creates a multi-functional testing framework where a single copied system configuration can be used for multiple testing scenarios and validations. This universal testing environment reduces the need for separate dedicated test systems, thereby reducing overall testing costs.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If new virtual services are deployed to improve network flexibility, then service optimization is enhanced, but system quality and scalability become uncertain

Engineering Contradiction:
Improvenetwork flexibilityVSAvoidservice quality
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the copied system is used to test new virtual service configurations and validate their performance. The testing results provide feedback on whether the new configurations meet quality and scalability requirements before production deployment, ensuring reliable service optimization.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent performs quality validation and scalability assessment in advance using the copied system configuration. This preliminary action ensures that new virtual services meet required quality standards before being deployed to the production network, maintaining service reliability while enabling flexibility.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If system scaling is performed to enhance capacity, then network performance is improved, but system correctness cannot be guaranteed

Engineering Contradiction:
Improvenetwork capacityVSAvoidsystem correctness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent creates a copy of the scaled system configuration to validate correctness before production deployment. This allows capacity improvements to be tested in isolation, ensuring system correctness is maintained while enabling productivity enhancements.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent performs partial testing by focusing validation efforts on the specific scaled components and their interactions. Rather than re-testing the entire system, the approach validates only the modified portions, making the correctness verification process efficient while still ensuring reliability.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10027569B1System, method, and computer program for testing virtual services
Publication Date: 2018.07.17 AMDOCS DEV LTD
  • US10027569B1 patent drawing
  • US10027569B1 patent drawing
  • US10027569B1 patent drawing

AI summary

A system, method, and computer program product are provided for testing virtual services. In use, at least a portion of a system to implement at least one modification is identified, the system including a plurality of services and the modification including one or more of an addition of at least one new virtual service or an update of at least one existing virtual service. Further, the at least one modification is implemented to the at least a portion of the system to generate an updated portion of the system and an original portion of the system, the updated portion of the system including the one or more of the addition of the at least one new virtual service or the update of at least one existing virtual service. Additionally, the updated portion of the system is tested by: receiving input data associated with the updated portion of the system; duplicating the input data to generate a first input data and a second input data; processing the first input data with the updated portion of the system and processing the second input data with the original portion of the system; and comparing at least a portion of an output from the updated portion of the system with at least a portion of an output from the original portion of the system.