Tag-Based Testing for Virtual Services in NFV

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a need for cost-effective 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 inefficient, and users require assurance that new or updated virtual services function correctly without causing issues.

Innovation Solution

A tag-based testing method is implemented, where input data is duplicated and tagged as testing or regular data, processed through both updated and original system portions, with common services used for comparison to ensure outputs match, utilizing comparators to verify functionality and performance.

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 the process is inefficient

Engineering Contradiction:
Improvequality assurance of virtual servicesVSAvoidtesting cost
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent creates a copy of the original system portion that includes the virtual service under test. This copy runs in parallel and receives the same input data, allowing for comparison of outputs. The copying principle enables testing without requiring complete system shutdown or complex test infrastructure, thereby reducing testing costs while maintaining reliability.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system is divided into an original portion and an updated portion, each processing data independently. This segmentation allows the testing process to focus only on the modified virtual service components rather than testing the entire system, reducing testing complexity and cost while ensuring quality of the specific service being tested.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If new or updated virtual services are deployed to improve system functionality, then service capabilities are enhanced, but the risk of introducing new problems or reducing quality increases

Engineering Contradiction:
Improveservice update capabilityVSAvoidsystem quality
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the output of the updated system portion is compared with the output of the original system portion. This comparison provides immediate feedback on whether the updated virtual service produces correct results, allowing for validation of service updates while maintaining system quality through automated verification.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The testing process is performed preliminarily before full deployment of updated virtual services. By running the updated portion in parallel with the original and comparing outputs, the system validates changes before they fully replace the existing service, preventing quality degradation while enabling service adaptability.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If comprehensive testing is performed to ensure quality, then system reliability is improved, but testing time and system disruption increase

Engineering Contradiction:
Improvevirtual service qualityVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent enables continuous operation of both the original and updated system portions during testing. Neither system needs to be stopped or taken offline, as both process data simultaneously in parallel. This continuity of useful action allows comprehensive quality testing to occur without time loss or service disruption.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The testing process uses partial action by focusing only on the specific virtual service components that were updated, rather than testing the entire system. The updated portion processes the same data as the original, and comparison is performed only on relevant outputs, reducing testing time while maintaining reliability of the modified services.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10063453B1System, method, and computer program for tag based testing of virtual services
Publication Date: 2018.08.28 AMDOCS DEV LTD
  • US10063453B1 patent drawing
  • US10063453B1 patent drawing
  • US10063453B1 patent drawing

AI summary

A system, method, and computer program product are provided for tag based testing of virtual services. In use, an original portion of a system within a network in which to implement at least one modification is identified, the original portion of the system including a first virtual service and a second virtual service. Additionally, the original portion of the system is duplicated implemented within the network to form an updated portion of the system. Both the original portion and the updated portion share a single instance of a third service. The updated portion is then tested by processing the same data through the original portion, including the single instance of the third service, and through the updated portion, including the single instance of the third service, and comparing the outputs thereof.