
Multiplexer User's Guide
Confidential / Released
s
mobile
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 |
|
| Information element name | |||
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
|
0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 |
|
TEMUX_VERSION | ||||||||
0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | MSMUX_VERSION |
|
| Other values |
|
| reserved for future use |
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
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
03Address Field DLCI=0,C/R=0,EA=0 EF Control Field UIH Frame, P/F=0
25Length LENGTH=18, EA=1
23Type Field TestCommand, C/R=1, EA=1
21Length Length=16, EA=1
04TEMUX_VERSION
54T
45E
4D M
55U
58X
56V
45E
52R
53S
49I
4F O
4E N
39Version number = 999
XX FCS (is calculated)
F9 END Flag
Mux_guide_v06 | Page 36 of 36 | 30.06.2004 |