Test Access Matrix for 20CN to 21CN Circuit Transfer Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is a need for new tests to verify the connection and operation of pairs of circuits between old technology networks (20CN) and new technology networks (21CN) and to check configuration data for these circuits, as existing tests do not adequately address the transition from 20CN to 21CN during transfer engineering.
Innovation Solution
A method and system that involve sending requests with a user line parameter through both 20CN and 21CN access networks to receive identifiers, comparing these identifiers, and using test equipment to diagnose fault conditions, with the system including a modified test access matrix (EvoTAM) and a transfer connection point (TCP) to interconnect both networks for testing purposes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing tests are used for 20CN access networks, then basic circuit functionality can be verified, but configuration data accuracy and physical connection correctness between 20CN and 21CN cannot be adequately verified during transfer engineering
Solution Approach 1:
The test process is segmented into distinct phases: first phase sends requests through 20CN access network to obtain identifiers, second phase sends requests through 21CN access network to obtain identifiers, and finally compares the identifiers. This segmentation allows each network to be tested independently while verifying their correspondence, resolving the contradiction between verification accuracy and test applicability.
Solution Approach 2:
A test access matrix (TAM) is introduced as an intermediary device that can connect to both 20CN and 21CN access networks. The TAM facilitates the sending of test requests through both networks and the comparison of results, enabling comprehensive verification without requiring separate testing infrastructure for each network type.
2Measurement precision
If transfer engineering testing is implemented to verify configuration data and physical connections, then accuracy of transfer verification is improved, but test system complexity increases due to need for dual network access
Solution Approach 1:
The test access matrix is designed with multi-functionality to access both 20CN and 21CN networks through a single interface. The TAM can configure itself to connect to different networks based on testing requirements, eliminating the need for separate dedicated testing equipment for each network type and reducing overall system complexity.
Solution Approach 2:
The test system performs preliminary configuration of the test access matrix to establish appropriate connections to either 20CN or 21CN networks before executing test requests. This preliminary setup automates the complexity of dual-network access configuration, allowing the actual verification process to focus on comparing identifiers rather than managing connection complexity.
Data Source
AI summary
A test system for testing a pair of telecommunications access networks, e.g. as part of transfer engineering. The system comprises a test head for connection, via an access arrangement, to first and second access networks. In a first phase, the access arrangement is arranged to connect the test head to the first access network for sending a first request from the tester to, for example, a CLI server via the first access network. The first request comprises a parameter associated with a user line. The tester is arranged to receive in response to the first request a first identifier from the server. In a second phase, the access arrangement is arranged to connect the test head to the second access network for sending a second request from the test head through the second access network to, for example, a CLI server. The second request also comprises the parameter. The tester is arranged to receive, in response to the second request, a second identifier from the target server and is arranged to carry out a comparison operation involving the first and second identifiers received in response to the two requests. A mismatch can indicate a fault or misconnection in either access network or a problem with network configuration data.