Coding Of "Testcommand" Message; Example Of "Testcommand" Message; Table 7: Iei Coding; Table 8: Coding Of "Testcommand" (Example) - Siemens Mux_guide_v06 User Manual

Multiplexer User's Guide
Confidential / Released

5.3.2 Coding of "TestCommand" message

The coding of the multiplexer stack version is used specifically for SIEMENS equipment and
is not defined in ETSI standards. The IEI values defined for the verification pattern of the
"TestCommand" message are indicated in Table 7. See GSM recommendation 07.10,
Section 5.4.6.3.4).

Table 7: IEI coding

IEI coding
8 7 6 5
0 0 0 0
0 0 0 0
Other values
For easier analysis of multiplexer traces the message shall be sent in the following format:
(1.) Version IEI
(2.) TEMUXVERSION/MSMUXVERSION (send as ASCII)
(3.) Version Number (1...999 send as ASCII)
The message part after the Version IEI is coded with ASCII characters. This allows to read
the version information from the trace file.
The version number must have a value between 1-999. If not all digits of the version number
are used only the used digits are coded as ASCII sign(s). Digits that are not used are sent as
zero string in the test message.

5.3.3 Example of "TestCommand" message

An example for coding a "TestCommand" message is illustrated in Table 8.
Table 8:
Coding of "TestCommand" (Example
Information element name
0x
F9 START Flag
03 Address Field DLCI=0,C/R=0,EA=0
EF Control Field UIH Frame, P/F=0
25 Length LENGTH=18, EA=1
23 Type Field TestCommand, C/R=1, EA=1
21
Length Length=16, EA=1
04 TEMUX_VERSION
54 T
45 E
4D M
55 U
58 X
56 V
45 E
52 R
53 S
49 I
4F O
4E N
39 Version number = 999
39
39
XX FCS (is calculated)
F9 END Flag
Mux_guide_v06
4 3 2 1
0 1 0 0
1 0 0 0
)
Page 36 of 36
Information element name
TEMUX_VERSION
MSMUX_VERSION
reserved for future use
s
m
o b i l e
30.06.2004