Non-intrusive Network Surveillance via Pre-loaded Instrumentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional debugging and troubleshooting methods in stored-program-controlled systems require direct access to processor devices, which can disrupt live systems and are costly due to the need for new software versions and physical connectivity, making it difficult to monitor and analyze communication channels without affecting user sessions or calls.
Innovation Solution
A method involving pre-configured instrumentation code loaded into a common memory, allowing surveillance elements to be executed without disrupting system operations, enabling monitoring and debugging of communication channels without modifying the instrumentation code, and allowing continued data transport over plural communication channels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Difficulty of detecting and measuring
If code instrumentation is implemented to access data structures for troubleshooting, then debugging capability is improved, but software version release cost and delay increase
Solution Approach 1:
The system pre-loads instrumentation code into common program memory before the system operates. This instrumentation code is prepared in advance and made available to processor units without requiring software version releases. When troubleshooting is needed, the instrumentation code can be immediately executed to access data structures and communication channels, eliminating the delay of preparing and deploying new instrumented software versions.
2Ease of operation
If commercial debug packages are used to access processor devices, then real-time debugging access is improved, but system operation disruption increases
Solution Approach 1:
The instrumentation code is merged with the system operation code and stored in the same common program memory. Both the system operation code and instrumentation code coexist in the same memory space and can be executed by processor units simultaneously. This integration allows debugging operations to be performed without requiring external debug equipment that would physically connect to and potentially disrupt the system, thereby maintaining system operation continuity while providing real-time debugging access.
3Ease of operation
If external equipment connectivity is established to the target under test, then debugging access is improved, but physical connectivity feasibility deteriorates
Solution Approach 1:
The debugging functionality is extracted from external commercial debug packages and integrated directly into the system's common program memory. The instrumentation code provides all necessary debugging capabilities internally, eliminating the need for external debug equipment and physical connectivity. Processor units can execute the instrumentation code to access communication channels and data structures without any external equipment connection, thereby simplifying the physical connectivity requirements while maintaining debugging accessibility.
Data Source
Figure 1
Figure 2
Figure 3-1
AI summary
In a system (20) handles plural communication channels (26), pre- configured instrumentation code (50) is loaded into a common program memory. The instrumentation code (50) is used to generate a surveillance element (70). The surveillance element (70) comprises multi-dimensional execution criteria (76) and executable surveillance code (78) configured to cause performance by a target processor unit of a surveillance element-specified surveillance action. The surveillance element (70) is executed by the target processor unit with respect to the respective subset of plural communication channels and permits continued transport of data over the plural communication channels.