Manuals / Brands / Cell Phone / Cell Phone / Siemens / Cell Phone / Cell Phone

Siemens Mux_guide_v06 4.3.9 Modem status command (MSC)

1 36

Download 36 pages, 1.05 Mb

Multiplexer User's Guide

Confidential / Released

s

mo b i l e

Mux_guide_v06 Page 28 of 36 30.06.2004

4.3.9 Modem status command (MSC)

The Modem Status Command is used for software flow control.

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 11: Modem status command (MSC)

C/R bit: Indicates whether the sequence is a command or a response.

Length: Length = 2 , EA-Bit = 1

DLCI:

Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8

1 1 DLCI

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 switch on the version 3, otherwise version 1 will be used, see

Chapter 5.2.

Direction host application" module (for request only) MUX V3:

RTC: mapped to DTR

RTR: mapped to RTS

Bit 5, 6, 7, 8 are not valid.

Direction module " host application (for request only) MUX V3:

RTC: mapped to DSR

RTR: mapped to CTS

RING: mapped to RING

DCD: mapped to DCD

Bit 5, 6 are not valid

Contents

Main Users Guide Multiplexer User's Guide Multiplexer User's Guide Confidential / Released Mux_guide_v06 Page 2 of 36 30.06.2004 Contents Figures Tables 0 Document history 1 Introduction 1.1 Supported products and related documents 1.2 References 1.3 Term and abbreviations 2 Multiplexer protocol an overview 2.1 Product concept and architecture 2.2 Virtual channels and AT commands 3 Integrating multiplexer into the customer application 3.1 Characteristics 3.1.1 Basic requirements 3.1.2 Restrictions 3.1.3 Dependencies between multiplexer channels and restrictions of use 3.1.4 Functions without channel dependencies 3.1.5 Timing conditions 3.1.6 Operation of a second physical serial interface ASC1 (if applicable) 3.2 Multiplexer control and signaling lines 3.2.1 Flow control Page 3.2.2 Escape sequence 3.3 Power saving 3.4 Bandwidth of logical channels 4 Structure of the multiplexer protocol 4.1 Introduction of the multiplexer protocol 4.2 Data link layer 4.2.1 Flag sequence 4.2.2 Address field 4.2.3 Control field 4.2.4 Length indicator 4.2.5 Information field 4.2.6 Frame checking sequence field (FCS) 4.3 State diagrams Figure 4: Relationship between the customer C and the GSM engine C Customer C Master state machine GSM engine C Slave state machine Customer C GSM engine C Figure 5: MPI Startup, DLC establishment and information transfer Serial interface Customer C GSM engine C Serial i nterface 4.3.1 Start-up procedure 4.3.2 DLC establishment Customer C GSM engine 4.3.3 Information transfer Customer C (Initiator) GSM engine (Responder) Customer C GSM engine 4.3.5 Close-down procedure 4.3.6 Multiplexer control channel Information Field 4.3.7 Multiplexer close down (CLD) 4.3.8 Test command (Test) 4.3.9 Modem status command (MSC) Page 4.3.10 Power saving control (PSC) 4.3.11 Non-supported command response (NSC) Multiplexer User's Guide Confidential / Released 4.4 Example: Establishing logical channels without parameter negotiation Customer C Serial interface GSM engine C Figure 13: Establishing the multiplexer control channel and the logical channel 5 Multiplexer protocol version control 5.1 Introduction 5.2 Multiplexer protocol versions 5.3 Implementing version control 5.3.1 Troubleshooting 5.3.2 Coding of TestCommand message 5.3.3 Example of TestCommand message