background image

Multiplexer User's Guide

 

Confidential / Released 

s

 

m

o

 

b

 

i

 

l

 

e

 

Mux_guide_v06 

Page 2 of 36 

30.06.2004 

 
 

Document Name: 

Multiplexer User's Guide  

 

 

Version: 

06 

 

 

Date: 

June 30, 2004 

 

 

DocId: 

Mux_guide_v06 

 

 

Status: 

Confidential / Released  

 
 
 

 
 
 

General notes 

Product

 

is

 

deemed

 

accepted

 

by

 

Recipient

 

and

 

is

 

provided

 

without

 

interface

 

to

 

Recipient’s

 

products.

 

The

 

documentation

 

and/or

 

Product

 

are

 

provided

 

for

 

testing,

 

evaluation,

 

integration

 

and

 

information

 

purposes.

 

The

 

documentation

 

and/or

 

Product

 

are

 

provided

 

on

 

an

 

“as

 

is”

 

basis

 

only

 

and

 

may

 

contain

 

deficiencies

 

or

 

inadequacies.

 

The

 

Documentation

 

and/or

 

Product

 

are

 

provided

 

without

 

warranty

 

of

 

any

 

kind,

 

express

 

or

 

implied.

 

To

 

the

 

maximum

 

extent

 

permitted

 

by

 

applicable

 

law,

 

Siemens

 

further

 

disclaims

 

all

 

warranties,

 

including

 

without

 

limitation

 

any

 

implied

 

warranties

 

of

 

merchantability,

 

completeness,

 

fitness

 

for

 

a

 

particular

 

purpose

 

and

 

non-infringement

 

of

 

third-party

 

rights.

 

The

 

entire

 

risk

 

arising

 

out

 

of

 

the

 

use

 

or

 

performance

 

of

 

the

 

Product

 

and

 

documentation

 

remains

 

with

 

Recipient.

 

This

 

Product

 

is

 

not

 

intended

 

for

 

use

 

in

 

life

 

support

 

appliances,

 

devices

 

or

 

systems

 

where

 

a

 

malfunction

 

of

 

the

 

product

 

can

 

reasonably

 

be

 

expected

 

to

 

result

 

in

 

personal

 

injury.

 

Applications

 

incorporating

 

the

 

described

 

product

 

must

 

be

 

designed

 

to

 

be

 

in

 

accordance

 

with

 

the

 

technical

 

specifications

 

provided

 

in

 

these

 

guidelines.

 

Failure

 

to

 

comply

 

with

 

any

 

of

 

the

 

required

 

procedures

 

can

 

result

 

in

 

malfunctions

 

or

 

serious

 

discrepancies

 

in

 

results.

 

Furthermore,

 

all

 

safety

 

instructions

 

regarding

 

the

 

use

 

of

 

mobile

 

technical

 

systems,

 

including

 

GSM

 

products,

 

which

 

also

 

apply

 

to

 

cellular

 

phones

 

must

 

be

 

followed.

 

Siemens

 

or

 

its

 

suppliers

 

shall,

 

regardless

 

of

 

any

 

legal

 

theory

 

upon

 

which

 

the

 

claim

 

is

 

based,

 

not

 

be

 

liable

 

for

 

any

 

consequential,

 

incidental,

 

direct,

 

indirect,

 

punitive

 

or

 

other

 

damages

 

whatsoever

 

(including,

 

without

 

limitation,

 

damages

 

for

 

loss

 

of

 

business

 

profits,

 

business

 

interruption,

 

loss

 

of

 

business

 

information

 

or

 

data,

 

or

 

other

 

pecuniary

 

loss)

 

arising

 

out

 

the

 

use

 

of

 

or

 

inability

 

to

 

use

 

the

 

Documentation

 

and/or

 

Product,

 

even

 

if

 

Siemens

 

has

 

been

 

advised

 

of

 

the

 

possibility

 

of

 

such

 

damages.

 

The

 

foregoing

 

limitations

 

of

 

liability

 

shall

 

not

 

apply

 

in

 

case

 

of

 

mandatory

 

liability,

 

e.g.

 

under

 

the

 

German

 

Product

 

Liability

 

Act,

 

in

 

case

 

of

 

intent,

 

gross

 

negligence,

 

injury

 

of

 

life,

 

body

 

or

 

health,

 

or

 

breach

 

of

 

a

 

condition

 

which

 

goes

 

to

 

the

 

root

 

of

 

the

 

contract.

 

However,

 

Claims

 

for

 

Damages

 

arising

 

from

 

a

 

breach

 

of

 

a

 

condition

 

which

 

goes

 

to

 

the

 

root

 

of

 

the

 

contract

 

shall

 

be

 

limited

 

to

 

the

 

foreseeable

 

damage

 

which

 

is

 

intrinsic

 

to

 

the

 

contract,

 

unless

 

caused

 

by

 

intent

 

or

 

gross

 

negligence

 

or

 

based

 

on

 

liability

 

for

 

injury

 

of

 

life,

 

body

 

or

 

health.

 

The

 

above

 

provision

 

does

 

not

 

imply

 

a

 

change

 

on

 

the

 

burden

 

of

 

proof

 

to

 

the

 

detriment

 

of

 

the

 

Recipient.

 

Subject

 

to

 

change

 

without

 

notice

 

at

 

any

 

time.

 

The

 

interpretation

 

of

 

this

 

general

 

note

 

shall

 

be

 

governed

 

and

 

construed

 

according

 

to

 

German

 

law

 

without

 

reference

 

to

 

any

 

other

 

substantive

 

law. 

 
Copyright notice 

Transmittal, reproduction, dissemination and/or editing of this document as well as utilization of its 
contents and communication thereof to others without express authorization are prohibited. Offenders 
will be held liable for payment of damages. All rights created by patent grant or registration of a utility 
model or design patent are reserved.  
 
Copyright © Siemens AG 2004 

 
Trademark notice 

MS Windows

 is a registered trademark of Microsoft Corporation. 

Содержание AC43

Страница 1: ...User s Guide Multiplexer User s Guide Siemens Cellular Engines Version 06 DocID Mux_guide_v06 ...

Страница 2: ... followed Siemens or its suppliers shall regardless of any legal theory upon which the claim is based not be liable for any consequential incidental direct indirect punitive or other damages whatsoever including without limitation damages for loss of business profits business interruption loss of business information or data or other pecuniary loss arising out the use of or inability to use the Do...

Страница 3: ...if applicable 13 3 2 Multiplexer control and signaling lines 14 3 2 1 Flow control 14 3 2 2 Escape sequence 16 3 3 Power saving 16 3 4 Bandwidth of logical channels 16 4 Structure of the multiplexer protocol 17 4 1 Introduction of the multiplexer protocol 17 4 2 Data link layer 17 4 2 1 Flag sequence 18 4 2 2 Address field 18 4 2 3 Control field 19 4 2 4 Length indicator 20 4 2 5 Information field...

Страница 4: ...ngine µC 22 Figure 5 MPI Startup DLC establishment and information transfer 23 Figure 6 MP DLC release and close down 24 Figure 7 DLC establishment 25 Figure 8 Information transfer 25 Figure 9 DLC release 26 Figure 10 Multiplexer control channel 26 Figure 11 Modem status command MSC 28 Figure 12 Power Saving Control PSC 30 Figure 13 Establishing the multiplexer control channel and the logical chan...

Страница 5: ...not supported 4 3 5 Corrected description of Close down procedure 5 Corrected description of multiplexer version control 5 3 3 Corrected example Preceding document Multiplexer User s Guide Version 04 New document Multiplexer User s Guide Version 05 Chapter What is new 1 1 Added further supported products 3 1 4 Modified remark on AT W 3 1 6 Added chapter Operation of a second physical serial interf...

Страница 6: ...n side of the serial interface another multiplexer must be integrated in order to demultiplex the signal and distribute it on the three virtual channels The external multiplexer needs to be provided by the customer This document describes how to use the multiplexer and then explains how to design an external multiplexer and integrate it into an application on top of a Siemens GSM engine Multiplexe...

Страница 7: ...pplied with your GSM engine 4 Remote SAT User s Guide 5 Multiplexer Driver Developer s Guide for Windows 2000 and Windows XP 6 Multiplexer Driver Installation Guide for Windows 2000 and Windows XP For further documents regarding your GSM engine please refer to the latest Release Notes supplied with the module To visit the Siemens Website you can use the following link http www siemens com wm 1 2 R...

Страница 8: ... Ready DTR Data Terminal Ready FC Flow Control FFC Flat Flex Cable GPRS General Packet Radio Service GSM Global System of Mobile Communication IEI Information Element Identifier IP Internet Protocol MO Mobile originated MP Multiplexer Protocol MS Mobile Station MSDN Microsoft Developer Network MT Mobile terminated MUX Multiplexer OS Operating System PC Personal Computer PSC Power saving control RT...

Страница 9: ...an 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 identifica...

Страница 10: ...incoming outgoing SMS incoming outgoing GPRS connection Phonebook management AT commands 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 except for AT commands related to data and fax calls 2 only two channels can be used parallel to transmit GPRS data Examples While a data call is in progre...

Страница 11: ...ed whenever the module is powered up again In this case the multiplexer fails to start To avoid this it is recom mended to re synchronize all settings before using the multiplexer mode again Before closing the multiplexer make sure that there is no ongoing activity on one of the channels For example check that voice CSD or GPRS connections have ended and wait until all pending AT command responses...

Страница 12: ...essage text which may be specific to each channel The URC CALA will be issued only on the channel where the last alarm setting was made For details see 2 Device locks set with AT CLCK SIM card access RF settings Example An ongoing fax call has been established on channel 1 When answering an incoming voice call on channel 2 or 3 and terminating it the held fax call will be ended as well 3 1 4 Funct...

Страница 13: ...ook may cause problems if a fax transmission is ongoing at the same time When switching on the module after a firmware update we recommend to wait 5 seconds before entering the first AT command 3 1 6 Operation of a second physical serial interface ASC1 if applicable This chapter applies only to Siemens GSM modules equipped with a second physical serial interface referred to as ASC1 If your product...

Страница 14: ...As already pointed out the logical flow control operates like RTS CTS but with FC BIT on every channel The RTS CTS are not used for flow control because the traffic on the logical channels may cause a temporary loss of bandwidth on another channel This behavior has no impact on the handshake V 24 lines RTS CTS on the physical channels Hardware flow control AT Q3 is recommended for use with multipl...

Страница 15: ...flow Figure 2 Logical flow control and RTS CTS signaling behind the decoder RING DCD Unlike all other lines DCD and RING are transmitted additionally on the UART directly by the module These signals are logical ORs from the three logical channel status lines However the customer application must carefully decide how to handle these lines and ensure that no conflicts occur between the different cha...

Страница 16: ...e AT CFUN command which provides the choice of the functionality levels fun 0 1 5 6 7 or 8 For further details on power saving see 1 and 2 If the module is in multiplexer mode it is not recommended to activate SLEEP mode with AT CFUN n For products supporting Multiplexer Protocol version 3 the best approach to properly control SLEEP mode in this case is to issue the PSC messages described in Chapt...

Страница 17: ...plexer protocol 4 1 Introduction of the multiplexer protocol The supported multiplexer protocol conforms to the GSM 07 10 Multiplexer Protocol The non error recovery mode was implemented with the basic option The frames have a start and a stop byte A checksum is calculated to protect the transferred data Frame repetition is not enabled Data and fax calls are transferred in the logical channel DLCI...

Страница 18: ...for the Data Link Connection Identifier DLCI are dynamically defined apart from DLCI 0 DLCI DLCI Data Link Connection Identifier C R Command Response EA extension bit EA 1 EA C R Table 3 Assignment of the DLCI DLCI number decimal Priority Multiplexer control channel see chapter 4 3 6 0 0 highest priority AT commands data fax GPRS 1 7 AT commands GPRS 2 3 7 The command response bit identifies the f...

Страница 19: ...1 2 3 4 5 6 7 8 SABM set asynchronous balanced mode 1 1 1 1 P F 1 0 0 UA unnumbered acknowledgement 1 1 0 0 P F 1 1 0 DM disconnected mode 1 1 1 1 P F 0 0 0 DISC disconnect 1 1 0 0 P F 0 1 0 UIH unnumbered information with header check 1 1 1 1 P F 1 1 1 P F Poll Final bit Commands P 1 Responses F 1 For each DLCI only one frame with P 1 may ever be expected Table 5 Coding of the control field ...

Страница 20: ...ne octet for the Length Indicator E A 0 two octets for the Length Indicator 4 2 5 Information field The information field contains the data and has an octet structure The field only exists for UIH frames unnumbered information with header check To transfer information fields the P F bit is set to 0 a response is not necessarily expected 4 2 6 Frame checking sequence field FCS The Frame Checking Se...

Страница 21: ...nd immediately have the option of setting up the multiplexer control channel DLCI 0 and other logical channels The logical channels are then set up DLC establishment If the DLC has been established successfully the state machine for that particular channel changes to CONNECTED If the request is unsuccessful the logical channel cannot be established and the state machine remains in DISCONNECTED on ...

Страница 22: ...ION CONNECTED CLOSED DOW N Start Up DLC Establishm ent Close Down Close Down Close Down DLC param eter negotiation DLC Release Inform ation Transfer DIS CONNECTED DIS CONNECTED NEGOTIATION CONNECTED CLOSED DOW N Start Up DLC Establishm ent Close Down Close Down Close Down DLC param eter negotiation DLC Release Inform ation Transfer Customer µC Master state machine GSM engine µC Slave state machine...

Страница 23: ...sconnected Serial interface Start Up AT CMUX Connected RequestSABM IndicationSABM ResponseDM ConfirmDM DLC Establishment DLC created Disconnected Disconnected RequestSABM IndicationSABM ResponseUA ConfirmUA DLC Establishment DLC not created Connected Connected Connected Connected RequestUIH IndicationUIH IndicationUIH RequestUIH Connected Information Transfer Figure 5 MPI Startup DLC establishment...

Страница 24: ...cted Serial interface DLC Release Connected Connected RequestDISC IndicationDISC ResponseUA ConfirmUA RequestCloseDown IndicationCloseDown ResponseCloseDown ConfirmCloseDown Close Down Closed Down Disconnected Disconnected Negotiation Connected Closed Down Disconnected Disconnected Negotiation Connected Figure 6 MP DLC release and close down ...

Страница 25: ...ither 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 GSM engine SABM P 1 Address Field DLCI of channel to be established UA F 1 DL...

Страница 26: ...he initiating station and the responding station revert to AT command mode Before closing the multiplexer make sure that there is no ongoing activity on one of the channels For example check that voice CSD or GPRS connections have ended and wait until all pending AT command responses are received 4 3 6 Multiplexer control channel DLCI 0 Type 1 Octet Length n Octets Value 1 1 Octet Value 2 1 Octet ...

Страница 27: ...nds can be sent in a single frame only 4 3 7 Multiplexer close down CLD Type field Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 1 C R 0 0 0 0 1 1 Length byte 0 no value octet 4 3 8 Test command Test The test command is intended to test the connection between MS and TE Type field Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 1 C R 0 0 0 1 0 0 The length byte indicates the number of test bytes ...

Страница 28: ...V 24 signals Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 1 FC RTC RTR reserved 0 reserved 0 RING DCD FC bit Flow control included in all multiplexer versions FC 1 no frames are accepted The following bits for V24 status lines as described in this chapter are included in multiplexer protocol version 3 only However if you wish to use the advantages of this version it is absolutely necessary to s...

Страница 29: ...n control handshake see Chapter 5 More detailed information on older multiplexer versions are available in Chapter 5 2 Break signal optional Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 1 Not supported Usually the break signal octet carries information about a break condition detected from the host application in the data stream for the DLC Note This command supports no parameters Instead we us...

Страница 30: ...arameter value In commands Bit 1 Bit 2 Bit 3 Bit 4 Description 0 0 0 0 Switches to the same mode as without a value octet 1 0 0 0 Switches into full functionality mode like AT CFUN 1 0 1 0 0 Switches into NON CYCLIC SLEEP mode like AT CFUN 0 1 1 0 0 Switches into CYCLIC SLEEP mode like AT CFUN 5 0 0 1 0 Switches into CYCLIC SLEEP mode like AT CFUN 6 1 0 1 0 Switches off like AT SMSO 0 1 1 0 Resets...

Страница 31: ... received URC the logical ring line has been activated for 1 second and deactivated again Please note that the behavior of the logical ring line is identical with the behavior of the physical RING0 line described in 1 4 3 11 Non supported command response NSC This response is sent whenever a command type is not supported by the receiving entity Type field Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 ...

Страница 32: ...Transfer Customer µC Closed Down Closed Down RequestStartUp ResponseStartUp ConfirmStartUp IndicationStartUp Disconnected Disconnected Serial interface Start Up AT CMUX Connected DLCI 0 DLC Establishment Create DLCI 0 Disconnected DLCI 0 Disconnected DLCI 0 RequestSABM DLCI 0 IndicationSABM DLCI 0 ResponseUA DLCI 0 ConfirmUA DLCI 0 Connected DLCI 0 Connected DLCI 1 DLC Establishment Create DLCI 1 ...

Страница 33: ...ultiplexer protocol the lower version will be agreed upon If no version check is done the TE reverts due to lack of version information to multiplexer version 1 This means that both sides only agree on version 1 even though they may have the same and even higher version The TE and MS multiplexer version numbers can be traced on the serial interface They appear as follows TE version e g version 1 T...

Страница 34: ... from module to host after version check on every channel to signal the initial state Modem status command MSC Command 1 octet Length 1 octet DLCI 1 octet V 24 signals 1 octet Break Signals optional 1 octet Command Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8 1 C R 0 0 0 1 1 1 Figure 14 MSC as used in version 3 Version specific differences in handling the modem status command MSC are explained ...

Страница 35: ...multiplexer protocol version 5 3 1 Troubleshooting When the MS realizes the implemented software but the TE does not respond correctly the following errors might occur The Request Test message is not sent from the TE No version check takes place No retransmission for Request Test message is triggered The multiplexer starts with protocol version 1 because no version information was exchanged betwee...

Страница 36: ...N 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 t...

Отзывы: