Automated Event Test Generation for Telecommunication Software

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current telecommunication software testing is time-consuming and error-prone due to manual generation of event occurrences and lack of access to past event testing data for modifying tests based on previous experiences.

Innovation Solution

A system and method for generating event tests that automatically receive event types and parameters, create event files, and send them to processing systems for testing, storing fault information in a repository for generating testing rules, and producing reports, thereby automating the testing process and improving efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual generation of event occurrences is used, then testers can control testing parameters, but the process is time-consuming and error-prone

Engineering Contradiction:
Improvetesting accuracyVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service by allowing testers to select event types and parameters through a graphical user interface, while the system automatically generates the event occurrence files without requiring manual population of template files. This automation eliminates repetitive manual tasks while maintaining testing accuracy through systematic parameter generation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical manual process of populating template files with an automated computer-based system. The system uses software algorithms to generate event occurrence files automatically based on selected event types and parameters, substituting manual mechanical operations with automated digital processes that are both faster and more accurate.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If manual population of event data template files is used, then testers can create customized test events, but the process is error-prone

Engineering Contradiction:
Improvetest event customizationVSAvoidtesting accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system incorporates feedback mechanisms where the graphical user interface provides real-time validation and guidance as testers select event types and parameters. The system automatically validates the selected parameters against predefined templates, providing immediate feedback to ensure accuracy while maintaining customization capabilities.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system allows dynamic parameter changes by enabling testers to select from multiple event types and modify parameters through the graphical user interface. The automated system then generates customized event occurrence files based on these parameter changes, ensuring both adaptability and accuracy through systematic parameter handling.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If manual generation of event occurrences is used, then testers have direct control over test parameters, but access to past event testing data is limited

Engineering Contradiction:
Improveparameter controlVSAvoidpast testing data accessibility
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system achieves universality by creating a centralized platform that handles both the generation of new event occurrence files and the storage/access of past testing data. The graphical user interface serves multiple functions: it guides parameter selection for new tests while simultaneously providing access to historical data, making the system a multi-functional solution that addresses both needs.

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

Solution Approach 2:

The system introduces an intermediary layer in the form of a graphical user interface and centralized database that mediates between the tester and both the event generation process and historical data. This intermediary structure provides easy access to past testing data while maintaining direct control over new test parameter generation, solving the information accessibility problem.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If automated event file generation is implemented, then testing time is reduced, but system complexity increases

Engineering Contradiction:
Improvetesting efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system applies segmentation by dividing the testing process into distinct modular components: event type selection, parameter configuration, event file generation, and result analysis. Each component is handled separately through the graphical user interface, making the overall complex automated system more manageable and easier to operate through functional decomposition.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9787534B1System, method, and computer program for generating event tests associated with a testing project
Publication Date: 2017.10.10 AMDOCS DEV LTD
  • US9787534B1 patent drawing
  • US9787534B1 patent drawing
  • US9787534B1 patent drawing

AI summary

A system, method, and computer program product are provided for generating event tests associated with a testing project. In use, an indication of one or more event types is received for creating one or more events on which to perform event testing associated with at least one testing project. Additionally, an indication of one or more parameters associated with the one or more events on which to perform the event testing is received. Further, one or more event files are generated for testing the one or more events based on the one or more event types and the one or more parameters. In addition, the one or more event files are sent to one or more event processing systems for testing the one or more events, the testing of the one or more events including storing information associated with all faults resulting from the testing of the one or more events in a risky events repository that is capable of being utilized to generate testing rules for additional testing projects. Moreover, at least one report including information associated with a result of testing the one or more events is generated.