Siemens Mux_guide_v06 manual Virtual channels and AT commands

Page 10

Multiplexer User's Guide

Confidential / Released

s

mobile

2.2 Virtual channels and AT commands

Please note that a cellular engine designed for multiplex operation does not include three different devices. Only one single air interface (RF part) is available.

As mentioned before the multiplexer enables one serial interface to run three sessions simultaneously. All incoming or outgoing calls are connected to the device.

Channel 1 supports the full range of functions, which is available without multiplexer tool. Channel 2 and 3 are connected to a different AT interpreter and support a subset of the functional range of channel 1, for more details refer to Table 1.

Table 1: Comparison of multiplexer channels

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Voice calls

 

Data / fax calls

 

SMS

 

GPRS

 

Phonebook

 

AT

 

 

 

incoming

 

incoming

 

incoming

 

connection

 

management

 

commands

 

 

 

outgoing

 

outgoing

 

outgoing

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Channel 1

 

!

 

!

 

!

 

!2)

 

!

 

!

 

 

 

 

 

 

 

 

 

Channel 2, 3

 

!

 

-

 

!

 

!2)

 

!

 

!1)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

!indicates that the functionality is available on the channel

---indicates that the functionality is not available on the channel

1)

2)

except for AT commands related to data and fax calls

only two channels can be used parallel to transmit GPRS data

Examples

While a data call is in progress on channel 1, you can send a short message on channel 2 and edit the phonebook on channel 3.

When receiving a fax on channel 1, you are able to check the battery capacity using the appropriate AT command on channel 2 or 3.

Note

Due to the technical requirements of multiplexer mode, data and fax calls can only be set up on logical channel 1 while GPRS connections can be established on every channel. Several AT commands have a different behavior on channels 2 and 3. Additional information regarding restrictions and interferences between the channels can be found in chapter 3.1 and in [2].

Mux_guide_v06

Page 10 of 36

30.06.2004

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