Siemens Mux_guide_v06 manual Coding of TestCommand message, Example of TestCommand message

Page 36

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 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

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

Image 36
Contents Version DocID Muxguidev06 Siemens Cellular EnginesDocument Name Multiplexer Users Guide Multiplexer Users GuideJune 30 Muxguidev06Contents Tables Multiplexer protocol version controlChapter What is new Document historyIntroduction Supported products and related documents ReferencesTerm and abbreviations Abbreviation DescriptionMultiplexer protocol an overview Product concept and architectureVirtual channels and AT commands Characteristics Integrating multiplexer into the customer applicationBasic requirements RestrictionsFunctions without channel dependencies Timing conditions Multiplexer control and signaling lines Flow controlLogical flow control RTS/CTS on the physical channelsRTS/CTS on the logical channels COM M COM N COM P RTS/CTSPower saving Bandwidth of logical channelsEscape sequence Structure of the multiplexer protocol Introduction of the multiplexer protocolData link layer Flag sequence Address fieldControl field Frame TypeLength indicator Information fieldFrame checking sequence field FCS BitState diagrams Relationship between the customer µC and the GSM engine µC Serial Interface Customer GSM engine AT+CMUXSerial interface Customer µCCustomer EngineGSM engine ResponderClose-down procedure DLC releaseMultiplexer control channel Type fieldTest command Test Multiplexer close down CLDLength field Modem status command MSC Break signal optional Bit Not supported Power saving control PSC Commands Bit DescriptionType Bit Value octet Length=1 BitNon-supported command response NSC Value octet Bit Command TypeNon-supported command No Value octet Length=0Customer GSM engine µC AT+CMUXMultiplexer protocol version control IntroductionModem status command MSC Signals Break Signals Octet Optional Command BitSignals Bit Multiplexer protocol versionsTroubleshooting Implementing version controlCoding of TestCommand message Example of TestCommand message