Siemens Mux_guide_v06 manual Customer, Engine, GSM engine, Responder, Initiator

Page 25

Multiplexer User's Guide

Confidential / Released

s

mobile

4.3.1 Start-up procedure

The only approach to activate the multiplexer protocol is entering the appropriate AT command AT+CMUX=0. This enables the multiplexer control channel. The next step is to set up the multiplexer control channel as described in Chapter 4.3.2.

4.3.2 DLC establishment

The multiplexer control channel must be set up as the first channel followed by all other DLCIs. To do so, a SABM frame (see Chapter 4.2.3) must be sent to the GSM engine.

The module responds either with a UA frame if the DLCI was set up, or with a DM frame if the DLCI was not set up.

No provision is made for repeating the request if a response is not received.

The state machine requesting the multiplexer control channel DLCI = 0 is the "initiating station", while the other is called the "responding station".

Customer

µC

SABM: P = 1

Address Field = DLCI of channel to be established

UA: F = 1, DLCI is being established

DM: F = 1, not ready, DLCI is not established Address Field = DLCI of requested channel

GSM

engine

Figure 7: DLC establishment

4.3.3 Information transfer

A response is not essential for every command – for example, an unsolicited result code does not require a response.

Customer

UIH:

P = 0, C/R = 1

 

GSM engine

µC

 

 

(Responder)

(Initiator)

 

UIH:

P = 0, C/R = 0

 

Figure 8: Information transfer

Mux_guide_v06

Page 25 of 36

30.06.2004

Image 25
Contents Siemens Cellular Engines Version DocID Muxguidev06Multiplexer Users Guide Document Name Multiplexer Users GuideJune 30 Muxguidev06Contents Multiplexer protocol version control TablesDocument history Chapter What is newIntroduction References Supported products and related documentsAbbreviation Description Term and abbreviationsProduct concept and architecture Multiplexer protocol an overviewVirtual channels and AT commands Integrating multiplexer into the customer application CharacteristicsBasic requirements RestrictionsFunctions without channel dependencies Timing conditions Flow control Multiplexer control and signaling linesLogical flow control RTS/CTS on the physical channelsCOM M COM N COM P RTS/CTS RTS/CTS on the logical channelsBandwidth of logical channels Power savingEscape sequence Introduction of the multiplexer protocol Structure of the multiplexer protocolData link layer Address field Flag sequenceFrame Type Control fieldInformation field Length indicatorFrame checking sequence field FCS BitState diagrams Relationship between the customer µC and the GSM engine µC AT+CMUX Serial Interface Customer GSM engineCustomer µC Serial interfaceEngine CustomerGSM engine ResponderDLC release Close-down procedureMultiplexer control channel Type fieldMultiplexer close down CLD Test command TestLength field Modem status command MSC Break signal optional Bit Not supported Commands Bit Description Power saving control PSCType Bit Value octet Length=1 BitValue octet Bit Command Type Non-supported command response NSCNon-supported command No Value octet Length=0AT+CMUX Customer GSM engine µCIntroduction Multiplexer protocol version controlSignals Break Signals Octet Optional Command Bit Modem status command MSCSignals Bit Multiplexer protocol versionsImplementing version control TroubleshootingExample of TestCommand message Coding of TestCommand message