Siemens Mux_guide_v06 manual Multiplexer protocol an overview, Product concept and architecture

Page 9

Multiplexer User's Guide

Confidential / Released

s

mobile

2 Multiplexer protocol – an overview

2.1 Product concept and architecture

The multiplexer mode enables one serial interface to transmit data to three different custo- mer applications. This is achieved by providing three virtual channels using a multiplexer (Mux).

This is especially advantageous when a fax/data/GPRS call is ongoing. Using the multiplexer features, e.g. controlling the module or using the SMS service can be done via the additional channels without disturbing the data flow; access to the second UART is not necessary. Furthermore, several accesses to the module can be created with the multiplexer. This is of great advantage when several independent electronic devices or interfaces are used.

To access the three virtual interfaces, both the GSM engine and the customer application must contain Mux components which communicate over the multiplexer protocol.

In multiplexer mode, AT commands and data are encapsulated into packets. Each packet has a channel identification and may vary in length.

Note:

All statements regarding GPRS are valid only for Siemens wireless products capable of GPRS.

Terminal programs or internal programs integrated in cus- tomer application platform

User application

GSM engine

Terminal 1

Terminal 2

Terminal 3

Channel 1

Channel 2

Channel 3

MUX conforming to GSM 07.10

Serial

I/O

MP

Serial

I/O

MUX conforming to GSM 07.10

1

2

3

Data/Fax/

GPRS supported

Data/Fax not supported

Figure 1: Multiplexer architecture

Mux_guide_v06

Page 9 of 36

30.06.2004

Image 9
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 channelsPower saving Bandwidth of logical channelsEscape sequence Structure of the multiplexer protocol Introduction 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 fieldTest command Test Multiplexer close down CLDLength 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