Telecommunication Network Compatibility Validation System

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Telecommunications carriers face the challenge of continuously revalidating compatibility of mobile devices with updated network architectures, particularly with legacy functionalities that may be inadvertently modified or damaged during OS updates, making it tedious and impractical to validate each new technology and ensure compatibility across various hardware components.

Innovation Solution

The development of systems and processes that generate legacy test protocols based on initial validations, allowing for the revalidation of carryover functionalities in updated OS versions, reducing the burden of revalidation and ensuring forward and backward compatibility with telecommunication network hardware.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full validation is performed on each new OS version and hardware technology, then compatibility reliability is improved, but time consumption and operational complexity increase significantly

Engineering Contradiction:

Improvecompatibility validation reliabilityVSAvoidvalidation time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary validation by recording test protocols during initial compatibility testing between a mobile device and network architecture. These recorded protocols capture the validation steps and results, which are then reused for subsequent validations, eliminating the need to repeat the entire validation process and significantly reducing time consumption while maintaining reliability

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system creates copies of validated test protocols and carries them forward to subsequent OS versions and hardware configurations. Instead of performing original validation from scratch each time, the system copies and adapts previously successful validation protocols, reducing validation time while preserving compatibility reliability through the use of proven test sequences

Inventive Principle:

Principle #26Copying

2Reliability

If comprehensive validation of all functionalities is performed, then compatibility coverage is improved, but device complexity and operational difficulty increase

Engineering Contradiction:

Improvecompatibility coverageVSAvoidvalidation operation ease

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The validation system segments the comprehensive validation process into distinct, manageable test protocols that can be independently recorded, stored, and executed. Each protocol focuses on specific functionality areas, making the overall validation process more manageable and easier to operate while maintaining comprehensive coverage through the collection of segmented test cases

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system enables self-service validation by automatically recording test protocols during initial validation runs and making them available for automatic reuse in subsequent validations. This automation reduces manual operational complexity while maintaining comprehensive compatibility coverage, as the system serves itself by generating and reusing validation protocols without requiring extensive manual intervention

Inventive Principle:

Principle #25Self-service

3Reliability

If revalidation of carryover functionalities is performed frequently, then functionality integrity is improved, but productivity decreases due to repeated validation cycles

Engineering Contradiction:

Improvefunctionality integrityVSAvoidvalidation productivity

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system copies validated test protocols from previous OS versions and applies them to validate carryover functionalities in updated versions. This copying approach ensures that functionalities intended to be carried over are properly validated for integrity, while significantly improving productivity by avoiding the need to recreate validation protocols for each OS update cycle

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system performs preliminary identification of carryover functionalities between OS versions and pre-preps the appropriate test protocols for revalidation. This preliminary action ensures that functionality integrity is maintained by targeting the right protocols for revalidation, while improving productivity by avoiding unnecessary validation of unchanged functionalities and focusing resources on carryover items

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9955368B2Telecommunicaton network architecture compatibility validation system

Publication Date: 2018.04.24 T MOBILE US INC

AI summary

Systems and processes may be implemented to revalidate carryover functionalities of a telecommunication device operating system (OS) with respect to updated telecommunication network architectures. Legacy test protocols may be generated based on an initial validation of a functionality prior to releasing an OS. Subsequently, the legacy test protocols may be executed for revalidation of the functionality when later carried over into a later version of the OS. The legacy test protocols may also be executed in response to telecommunication network hardware updates to validate existing functionalities with respect to new hardware components or technology. The later version of the OS may be analyzed to identify carryover functionalities and the identified carryover functionalities may ranked according to importance of being revalidated.