User Manual

Physical & protocol layer test
99-137719-D Confidential - For internal use 12-23
12121212
Use cases
• Reboot the RM for changes to take effect.
• It is only necessary to run this script once when setting up a user terminal for
protocol testing.
3. Execute the appropriate Python script, depending on which MTR script(s) must be
executed. As a rule of thumb, one Python file corresponds to a test suite, however it
is worth noting that some MTR scripts require a slightly different configuration and
is therefore associated with a different Python script than the suite it is a part of. A
complete list of MTR scripts with corresponding Python script is supplied in the
Python script package under the filename ScriptList.txt.
• When starting a new MTR test script, the related Python script must be executed.
• Several MTR tests sharing a Python setup script can normally be executed
without the need to run the Python setup script between tests.
4. Make sure the variables in the pixit files (.tsp files supplied by Inmarsat along with
the MTR scripts) contains the correct values in accordance with the User Terminal
under test. The following values must be set correctly (the parentheses indicates the
related field in the pixit file):
• IMEI number of the user terminal (px_IMEI_def)
• Combined IMEI and software version number (px_IMEISV_def)
• User terminal class (named differently in each MTR test suite, see specific MTR
suite documentation)
• For classes 6, 7, 10 and 11 set:
pxb_bganx = True
pxb_bplt_rx_bearer_type = 61
otherwise:
pxb_bganx = False
pxb_bplt_rx_bearer_type = 62
5. There must be a special protocol test (dummy) SIM card in the user terminal. The
px_AuthK and px_ck field in the pixit files must be adjusted to correspond with the
value on the SIM card.
The pixit files contain a large number of test-specific parameters. For further
information, refer to the specific MTR documentation from each test suite supplied by
Inmarsat.
12.7.3 VCTS testing
This use case presents a simplified description of how to perform VCTS end-to-end
testing. The test is performed as a part of the type approval to test the signal path from
the 2-wire connector to the output of the AMBE+2 voice codec and vice versa. The test
setup consists of a BPT, BPLT, VCTS, VCDS and the terminal under test as shown in the
figure below. It can be seen as a protocol test just with the addition of the VCTS and
therefore the preparations for a protocol test also apply here regarding IP addresses,