Unified Data Generation Adapter for Protocol Emulator Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network communication device testing methods require large storage for diverse data patterns and are inefficient due to the need for multiple data files and complex logic in protocol emulators, leading to scalability issues and high maintenance overhead.
Innovation Solution
A unified framework is provided that uses a data generation adapter to manage diverse data generation engines, allowing protocol emulators to access data through a single interface, simplifying the design by eliminating the need for emulators to know data storage locations or generator types, and enabling easy addition of new data types without recoding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If large collection of data files is used to feed protocol emulators, then diverse payload patterns can be generated, but storage volume and disk read speeds become problematic
Solution Approach 1:
The patent extracts the data generation logic from the protocol emulators and places it in separate data generation engines. This allows the emulators to focus on protocol handling while external engines generate diverse payloads on demand, reducing the need for large static data file collections.
Solution Approach 2:
The patent introduces a data generation adapter as an intermediary component between protocol emulators and data sources. The adapter manages data generation engines and provides a unified interface to emulators, enabling diverse payload generation without requiring emulators to directly handle complex data storage and retrieval operations.
2Adaptability or versatility
If complex data generation logic is included in protocol emulators, then diverse data can be generated, but redundancy and maintenance overhead increase
Solution Approach 1:
The patent segments the system into separate functional components: protocol emulators handle protocol-specific operations, data generation engines handle payload generation, and a adapter layer manages communication between them. This segmentation eliminates redundancy and simplifies maintenance by allowing independent updates to each component.
Solution Approach 2:
The patent creates a universal data generation adapter that can interface with multiple types of data generation engines through a standardized interface. This multi-functional adapter eliminates the need for each emulator to implement multiple data generation capabilities, reducing complexity while maintaining versatility.
3Adaptability or versatility
If code modifications are made to each emulator for protocol changes, then protocol updates can be implemented, but scalability and efficiency decrease
Solution Approach 1:
The data generation adapter serves as an intermediary that centralizes protocol update logic. When protocol changes are needed, modifications are made at the adapter level or in the data generation engines, and these changes automatically propagate to all emulators through the standardized interface, eliminating the need to modify each emulator individually.
4Speed
If RAM is used to increase read speeds, then data access performance improves, but cost becomes prohibitively expensive
Solution Approach 1:
The patent extracts data generation responsibilities from the emulator system and places them in separate data generation engines that can be implemented as software libraries or external services. This allows the system to generate data on-demand rather than requiring large volumes of high-speed RAM for data storage.
Data Source
AI summary
Methods, systems, and computer readable media for providing a unified framework to support diverse data generation engines are provided. One exemplary system includes a protocol emulator that transmits data to a device under test. The protocol emulator sends a request including a data profile identifier to a data generation adapter. The data generation adaptor identifies a data generation engine of a plurality of data generation engines to provide data corresponding to the data profile identifier and requests the data from the identified data generation engine. The data generation engine that receives the request provides the data to the emulator, and the emulator forwards the data to the device under test.