Siemens Mux_guide_v06 manual Relationship between the customer µC and the GSM engine µC

Page 22

Multiplexer User's Guide

Confidential / Released

s

mobile

Custom er µC

GSM engine µC

M aster state machine

Slave state m achine

CLO SED-

CLO S E D -

D O W N

DO W N

Close Down

Close Down

Start Up

Close Down

Start Up

Close Down

 

DLC

 

 

 

DLC

 

 

DIS-

param eter

DIS-

Close Down

D IS -

param eter

DIS-

Close Down

negotiation

 

negotiation

 

CO NNECTED-

 

CO NN ECTED-

 

CO NNECTED

 

 

C O NN E CTED

 

 

 

NEG O TIATIO N

 

 

NEG O TIATIO N

 

 

 

 

 

 

 

DLC Release

 

DLC Establishm ent

 

DLC Release

 

DLC Establishm ent

CO NNECTED

C O NN E CTED

Inform ation

Inform ation

Transfer

Transfer

Figure 4: Relationship between the customer µC and the GSM engine µC

Mux_guide_v06

Page 22 of 36

30.06.2004

Image 22
Contents Version DocID Muxguidev06 Siemens Cellular EnginesJune 30 Document Name Multiplexer Users GuideMultiplexer Users Guide 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 Basic requirements CharacteristicsIntegrating multiplexer into the customer application RestrictionsFunctions without channel dependencies Timing conditions Logical flow control Multiplexer control and signaling linesFlow control RTS/CTS on the physical channelsRTS/CTS on the logical channels COM M COM N COM P RTS/CTSBandwidth of logical channels Power savingEscape sequence Introduction of the multiplexer protocol Structure of the multiplexer protocolData link layer Flag sequence Address fieldControl field Frame TypeFrame checking sequence field FCS Length indicatorInformation field BitState diagrams Relationship between the customer µC and the GSM engine µC Serial Interface Customer GSM engine AT+CMUXSerial interface Customer µCGSM engine CustomerEngine ResponderMultiplexer control channel Close-down procedureDLC release Type fieldMultiplexer close down CLD Test command TestLength field Modem status command MSC Break signal optional Bit Not supported Type Bit Power saving control PSCCommands Bit Description Value octet Length=1 BitNon-supported command Non-supported command response NSCValue octet Bit Command Type No Value octet Length=0Customer GSM engine µC AT+CMUXMultiplexer protocol version control IntroductionSignals Bit Modem status command MSCSignals Break Signals Octet Optional Command Bit Multiplexer protocol versionsTroubleshooting Implementing version controlCoding of TestCommand message Example of TestCommand message