Object-Oriented ASN.1 Management Device for Persistent Message Saving
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
ASN.1 message structures require re-establishment after persistent saving, and existing platforms like DSET and ESNACC struggle with decoding bit streams without knowing the data type in advance, making message construction and maintenance cumbersome.
Innovation Solution
An object-oriented management device with an ASN.1 bottom support module, common manipulation module, and message plug-in that generates programming language code, supports class manipulation, and converts between ASN.1 and VAL formats, enabling persistent saving and decoding of ANY data, with graphic and script interfaces for message editing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If ASN.1 message is compiled into intermediate programming language structure and encoded into bit stream, then the message can be transmitted and decoded, but the decoded message cannot be directly saved persistently because the structure information is lost
Solution Approach 1:
The patent applies preliminary action by generating a mapping relationship between ASN.1 structure and programming language structure during the compilation phase. This mapping information is stored and reused during decoding and persistent saving operations, eliminating the need to re-establish message structures from bit streams later. The structure information is prepared in advance rather than reconstructed on-demand.
2Ease of manufacture
If the message structure is re-established after persistent saving, then the message can be stored and retrieved, but the workload of message construction and maintenance increases significantly
Solution Approach 1:
The patent uses copying by creating and storing a mapping relationship (copy of structure information) between ASN.1 definition and generated programming language structures. This mapping copy is preserved and directly applied during message decoding and persistent saving operations, avoiding the need to recreate message structures from scratch each time, thereby reducing development and maintenance workload.
3Adaptability or versatility
If ANY type data is decoded without knowing its specific type in advance, then the decoding process can proceed, but the data cannot be further decoded or modified until its type is determined
Solution Approach 1:
The patent introduces an intermediary mapping relationship that stores the correspondence between ASN.1 structure elements and programming language structures. This mapping acts as a mediator that provides type information for ANY type data during decoding, enabling the system to determine specific types and perform further decoding or modification operations without losing flexibility in handling unknown data types.
4Productivity
If BER encoding is used for network transmission, then the message can be transmitted efficiently, but the message is unreadable and cannot be directly recovered as persistent storage format
Solution Approach 1:
The patent applies segmentation by separating the transmission format (BER bit stream) from the persistent storage format (VAL or other readable formats). The mapping relationship enables the system to decode BER-encoded messages and convert them to appropriate persistent storage formats, allowing efficient transmission while maintaining readability and ease of recovery for stored messages.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An object-oriented management device for ASN.1 message is provided, which includes: an ASN.1 bottom supporting module for compiling the ASN.1 message into programming language example code; a common manipulation module for processing the message to support the message applications; a message plug-in for creating the message corpus plug-in from the code generated by the common manipulation module, with the class description table being the plug-in interface; the said common manipulation module or the message plug-in is used for modifying the generated programming language example code, supplementing the class description information, adding the support of class example manipulation for the generated code and establishing the TopClass class description table in the generated code. The present invention solves the problem that the message structure example should be re-established after the message is persistently saved, overcomes the disadvantage that the data type of the bit stream must be known in advance for decoding, decreases the difficulty of message construction, and significantly lessens the workload of the message development and maintenance.