Content:
Details:
line interface | AXD EM Type | MSS Name | AXD Port Address |
---|---|---|---|
E1 (PCM) | ET2 CE 32 CT | b211 | 1/3/2 (1-3-2) |
STM-1/VC-12 | ET2x155-S1.1 CE CT | b211 | 1/4/2 (1-4-2) subport: 2(1.1.1) |
1000BASE-F | GBE & FE | b211 | 1/5/2 (1-5-2) |
We can access the lower level (physical and data link layer) attributes of the interfaces in the Equipment/Configuration menu of the AMS. To obtain the information required in the above questions one can follow the next steps:
Attribute | Set of the possible values | Recent value |
---|---|---|
Is the interface (link) available? | yes? no? | |
Does the interface (link) operable? If not, what is the cause? | yes? no? | |
Transmission frame format | PCM 30/31?, CRC? | |
Line coding | AMI?, HDB3? | |
Transmission clock source | internal?, Rx PCM? | |
Implemented maintenance signals | LOS?, AIS?, RAI? | |
Loopback | off?, line?, local? |
To access the information required in the above questions, please, continue the steps of the previous task:
The aim of the instrumental testing of the interface to decide that if interface corresponds to the relating standards or not? This correspondence is the fundamental requirement of connectivity of interfaces made by different vendors.
Tests presented in this task was choosen from the test cases of the standardized Conformance Test related to the physical layer (OSI Layer1) of E1 interface.
These test can be interpreted and extended to STM-1 and GBE interfaces, too. However, these tests will not be performed because of lack of time and measuring equipment.
A theoretical draft of the instrumental measurements:
Draft of the real measuring alignment:
Short summary of the operation of the interface as receiver:
Line Rx (receiver) conditions the PCM signal provided by the interface tester, recovers the clock signal from it, decodes line coding and regenerates it by sampling.
Deframer cut off header from the received E1 frames and forwards the contain of the remaining time slots to the ATM Termination Functions modul. Here E1 signal steam will be transformed to a stream of ATM AAL1 frames.
The swithing field of MSS (SC) switches the AAL1 frames arriving from the management and labelled with ATM VPI and VCI towards the destination interface. The E1 - AAL1 conversion can be made for the full frame (ustructured mode) or by time slots (64 kbit/s structured mode). For the VoIP only the second method cvan be used.
The Rx Overhead modul of interface checks frame synchonization, monitors bit errors (CRC-4) within the frame, indicates the received alarms (AIS, RAI) towards mangement and handles service channel.
Short summary of the operation of the interface as transmitter:
The AAL1 frames arriving from the SC will be converted into E1 signal stream by ATM Termination Functions modul, then Framer puts them into the time slots of the E1 frame to be transmitt based on the VPI and VCI. The contain of the 0. time slot will be compiled by the Tx Overhead modul.
The output signal of the interface will be made by line coding by the Line Tx modul.
The object of the test is the line transmitter of the interface (Line Tx) which determines the quality of the PCM signal transmitted by the interface. The measuring signal origins from the interface tester, received by the line receiver of the interface (Line Rx). This signal is connected - looped back - to the input of the line transmitter.
Loopback can be activated in the AMS: PDH2 Sublayer/Loopback -> Line. The mask function can be actived in the oscilloscope with the help of the SETUP/SEQUENCE MENU button. For the examination of the signal shape we must use the STEP 4 masking! We should pay attention to the joint closing of the interface (measuring head of 120 Ohm which is the same as the input impedance of the interface tester)! During the measuring the multiplication of the signal with a constant is allowed!
Measure the output jitter of the E1 interface!
Now, the object of the test is the line transmitter of the interface (Line Tx), which determines the phase jitter of the PCM signal transmitted by the interface.
The measuring signal in this test is the (jitterless) PCM signal provided by the protocol tester and received by the line receiver of the interface (Line Rx).
This signal will be connected - loopbacked - to the input of the line transmitter for the measurement.
Loopback can be activated using the AMS: PDH2 Sublayer/Loopback -> Line.
Measuring signal must be given from the transmission unit of ME520B. ME520B provides only unframed measuring
signal and the interface under test considers this as a wrong signal
(Operational State=Down) because its operation mode is framed.
However, we do not need to pay attention to the change of the framing type of
the interface, because Line Tx and Line Rx remain operational.
Jitter must be analyzed with the receiving unit of ME520B.
Set the measuring domain of the jitter according to the measured value!
How will reduce the value of the jitter, if we filter the contents with low frequencies?
Check that wether the input jitter endurance of the E1 interface corresponds
to the minimum specification at 10 kHz or not.
Now, the object of the test is the line receiver of the interface (Line Rx).
The measuring PCM signal containing jitter provided by the tester.
In order to recognise the errors the signal received by the line receiver
will be connected - loopbacked - to the input of the line transmitter for the
measurement.
Loopback can be activated using the AMS: PDH2 Sublayer/Loopback -> Line.
Measuring signal must be given from the transmission unit of ME520B. The modulating signal will be generated with
the EMS 10 equipment.
ME520B provides only unframed measuring
signal and the interface under test considers this as a wrong signal
(Operational State=Down) because its operation mode is framed.
However, we do not need to pay attention to the change of the framing type of
the interface, because Line Tx and Line Rx remain operational.
Errors must be counted with the receiving unit of ME520B.
How much is the input jitter endurance of the interface is better than th
minimum specification?
Check, if the bit rate of the PCM signal given by the interface is within the
tolerance or not?
Bit rate (and together with it the clock signal generator of the interface) must be within the same value domain, so that the bit-synch between the interfaces could be realized.
Determination of the bit rate of a signal given by the interface is in menu point of HP37732A Result: BER MEASUREMENTS Display:SIGNAL.
During this test we must take care of, that the transmission unit of the tested interface could get the timing signal from the own clock of the MSS (PDH2 Sublayer/Tx Clock Source -> Netsync)!
Loopback must be switched off in the AMS: PDH2 Sublayer/Loopback -> Off.
During these tests we do not measure electric signal, but we examine, if the interface operates appropriately, or not.
Examine the behavior of the interface if the frame type or line coding of the received signal is incompatible (Rx overhead processor and Line Rx test).
Let we set incompatible fram types and line coding methods (E.g: given frame: PCM31, expected frame: PCM31_CRC or line coding of the transmitted signal: HDB3, expected line coding: AMI) at the HP37732A interface tester, and at the examined PCM interface, and then examine the maintenance signals of the interface, whether they could indicate the incompatibility. The maintenance signals of the tested inteface can be seen in the AMS->Event&Alarm->Current_Alarm_List menu. Clicking on the relating line the detailed alarm signal can be read.
We should report an issue like this.
Examine if the content of the 0. time slot in the PCM signal transmitted by the interface corresponds to the standard, or not. (Tx overhead processor test)
We could make this examination at the menu of the Results: Timeslot Monitor of HP37732A.
Check the appropriate operation of the frame synchronous algorithm. (Tx, Rx overhead processor test)
We can make the examination using the HP37732A Settings: 2Mbit/s FMSIM measuring mode. Here, setting the test: FAS WORD mode we can put errors into the given frame synch code words. The test should be started from the errorless situation, then the amount of the errors should be increased until the loss of the synch. After that we should decrease the the amount of the errors until the recovery of the synch. The maintenance signals of the tested inteface can be seen in the AMS->Event&Alarm->Current_Alarm_List menu. Clicking on the relating line the detailed alarm signal can be read.
Beside this It provides an insight into the operation and user level programming of the switching field (SC) and the TDM/IP converter called Media Gateway of the MSS. With the help of the AMS find out that to which MSS application is the the tested interface assigned and where the several time slots of the tested inteface are connected? Fill out the empty column of the following table:
Attribute | Possible set of the values | Recent value |
---|---|---|
Is a CE application? | yes / no | |
Is a Voice application? | yes / no | |
Is a Media Gateway Device? | yes / no | |
Media Gateway Name | b211, b212, b213 | |
Connected time slots | E.g.: 6-7, 1-2... |
The above mentioned information can be read in the following menus:
We can perform out the test with previously connected time slots, but in the Create Semipermanent connections menu we can create a connection between the two time slots of the tested interface, too. We can check the operation of the test alignment with the bit errors put into the measuring signal (Continuity test)!
The STM-1 interface of the MSS has a significantly higher capacity than E1 interface,
because it is able to multiplex/demultiplex and transmit/receive 63 pieces of E1 signals
to/from external exchanges.
Accordingly, the STM-1 interface has a more complex (a more layered) structure than E1.
In the orientation of notations of the several components of the STM-1 used in the Tutorial
and in the AXD AMS will help us the following table:
SDH layers (Tutorial) | sublayer name (AMS) | interface type (AMS) | Frames, Containers | Overheads |
---|---|---|---|---|
circuit layer | E1 interface | PDH | here it is E1 | TS0=FAS, NFAS |
lower order path layer | VC-12 interface | SDH LOW PATH (LP) | LOVC here it is VC-12 | POH |
high order path layer | SDH path interface | SDH PATH (HP) | HOVC here it is VC-4 | POH |
transmission media layer | SDH interface | SDH | here it is STM-1 | SOH=RSOH+MSOH+AU4P |
STM-1 interface (SDH interface sublayer):
Attribute | Possible set of the values | Recent value |
---|---|---|
Is the interface (link) available? | yes? no? | |
Does the interface (link) operable? If not, what is the cause? | yes? no? | |
Transmission frame format | SDH? SONET? | |
Line coding | NRZ?, | |
Transmission clock source | internal?, Rx? | |
Implemented maintenance signals | LOS?, AIS?, RDI? ...? | |
Loopback | off?, line?, local? |
E1 interface sublayer
Attribute | Set of the possible values | Recent value |
---|---|---|
Is the interface (link) available? | yes? no? | |
Does the interface (link) operable? If not, what is the cause? | yes? no? | |
Transmission frame format | PCM 30/31?, CRC? | |
Line coding | AMI?, HDB3? | |
Transmission clock source | internal?, Rx PCM? | |
Implemented maintenance signals | LOS?, AIS?, RAI? | |
Loopback | off?, line?, local? |
The instrumental testing procedures (signal shape, phase jitter, and fuctional tests) of the GBE interface are similar to the testing procedures of the E1 interface. A principled draft of the measurement:
The fundamental difference is that testing of STM-1 requires two orders of magnitude higher speed measuring equipments than in the case of E1. Dashed line on the above figure indicates the lack of the oscilloscope having high rate optical inputs.
Draft of the functional measuring alignment:
Because of the lack of the testing tools we can not examine electrical caracteristics (signal shape, phase jitter, etc.) at this interface.
For the funcional testing of the STM-1 interface HP37724A interface tester will be used. The test cases selected for this task are mostly STM-1-specific.
In order to perform the test cases we have to set STM-1 interface of the HP37724A equipment according to the configuration of the tested interface. In this will help the following table:
Parameter | Transmit menu Main Settings | Receive menu Main Settings |
---|---|---|
Transmit/Receive Signal | STM-1 OPT | STM-1 OPT |
Payload | TU-12 | TU-12 |
TU mode | async | async |
Selected TU | 1.1.1 | 1.1.1 |
TU Payload | int CRC4 | int CRC4 |
Timeslot | all ts | all ts |
Pattern | 2^15-1 | 2^15-1 |
After setting the above parameters measuring equipment will transmitt/receive STM-1 frames on its optical interface. It multiplex a TU-12 component into the VC-4 container (into the first position (1.1.1) from the possible 63). Into the TU-12 components itmaps asynchronously 4-4 E1 frames. The source of the E1 frames is the HP37724A tester, too. (Internal payload generator). E1 frames contain CRC4 multiframe in their 0. time slots, while in the 1-31 time slots segments of a 15-bit PRBS signal will be transmitted. The receiver of the equipment waits for the errorless transmitted signal.
The received signal will be errorless if the tested interface loops back the test signals. There is two loopback possibility on the tested interface, please use the following settings:
As we do not use the SDH interface sublayer loopback it is possible to test line and multiplex part jointly.
Finally, please, check the interconnection of the measuring equipment and the tested interface according to the next figure::
10 dB optical attenuators are important parts of the interconnections, becasuse they prevent the overdriving and the consequent untimely failure of optical receivers.
After completion of the above settings we can start with functional tests.
During the test interface tester transmits STM-1 frames containing errors and alarms and
we will observe the behavior of the interface under test when receiving these frames.
Insertion of errors and alarms can be done in the Transmit/Test function/Errors & Alarms menu of the interface tester.
The maintenance signals of the interface under test can be seen in the AMS->Event&Alarm->Current_Alarm_List menu. (After the click we have to wait for a while.)
Clicking on the relating line the detailed alarm signal can be read.
Suggested test, as an example: transmit frames containing MS-AIS.
Suggested optional task: STM-1 frame synch test.
Reporting: maintenance signals (alarms).
The content of the overhead of frames of the tested interface can be studied using the tutorial (links can be find above). Interface tester provides the following possibilities for the testing:
After studying answer the following questions:
Using the above mentioned possibilities collect and write out the all trace identifier and signal label values given by the tested interface!
In this task we can test that how long series of bites of 1s or 0s cause loss of bit synch in the clock recovery circuit of the receiver of the tested STM-1 optical interface. In this case tester inserts series of bytes of 1s or 0s with programmable length into the STM-1 frames - simulating short time break downs.
The insertion can be made using Transmit/Test Function/Stress Test menu.
Examine how long series of bytes of 1s or 0s cause disorder in the operation of the tested interface?
In SDH frames (STM-1, TU-12) position of the payload (VC-4, VC-12) frame is unbound, it can vary. The start of the payload described to frame by pointers (AU-4 PTR, TU-12 PTR). Pointers receive value at the start of the operation of the interface and this value remains unchanged in the case of normal operation.
In the case of difficulties in timing or clock signal provisioning it may occurs that frame and payload are driven by different timing source: payload "moves" inside the frame. The interface seeks to compensate this phase shift by overriding the value of the pointer.
During the test interface tester transmit STM-1 frames in which there is rate difference between the clock sources of the frame and the payload (offset).
The above mentioned signal can be generated in the Transmit/Test function/Adjust pointer menu.
Examine how much offset causes disorder in the operation of the tested interface?
As a farewell to the above interfaces make an interconnection between the measuring connections used in Task 3 and Task 5 with the help of the AXD SC switch using the Task 3.2.4 as an example! Do not forget to switch off loopback at the STM-1 interface!
Reporting: connected ports, time slots, the result of the continuity test in both directions.
The MSS GBE interface has a significantly greater capacity than STM-1 interface becasue it able to transmit/receive ca. 9000 voice channels to/from external exchanges. Nonetheless, GBE interface is more simple than STM-1, it is only a little bit more complicated than E1.
Attribute | Set of the possible values | Recent value |
---|---|---|
Is the interface (link) available? | yes? no? | |
Does the interface (link) operable? If not, what is the cause? | yes? no? | |
Connected optical fiber? | monomode/multimode? | |
Optional interface procedures? |
The instrumental testing procedures (signal shape, phase jitter, and fuctional tests) of the GBE interface are similar to the testing procedures of the E1 and STM-1 interface. The fundamental difference is that in this case we do not have any equipment, neither an interface tester, nor a traffic generator for the testing of the GBE interface.
This insufficiency can be bridged by interconnecting two GBE interfaces and the tests can be executed on the link established in this way.
Draft of the real measuring alignment:
Because of the lack of the testing tools we can not examine electrical caracteristics (signal shape, phase jitter, etc.) at this interface.
On the other hand, type and particle number of the GBIC can be read in the AMS. Using the e.g. Google web search we can find the data sheet of the optical transmitter/receiver of the GBE interface. When studying this datasheet we can conceptualize which parameters may be tested here. To confirm that task was done fill the empty column of the following table:
Parameter | Value |
---|---|
Data Rate | |
Tx Eye Opening | |
PECL Signals Amplitude | |
PECL Signals Impedance | |
Power Voltage Range | |
Current Consumption |
We may generate alarm e.g. by the shut down of the remote interface. The pulling out of the optical fiber from the GBIC is strictly forbidden! Furthermore, this is an active link of the telecommunication test network of the department, which means that the link error may influence the work of the other students! So please take care about this task and consult with the teacher!
The maintenance signals of the interface under test can be seen in the AMS->Event&Alarm->Current_Alarm_List menu. (After the click we have to wait for a while.)
Frame errors detected by the interface as well as statistics relating to the transmitted and received frames can be studied in the
Link Data / Link statistics
menu of the AMS.