Siemens Mux_guide_v06 manual Structure of the multiplexer protocol, Data link layer

Page 17

Multiplexer User's Guide

Confidential / Released

s

mobile

4 Structure of the multiplexer 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 = 1 (DLCI: Data Link Connection Identifier). The remaining DLCIs are in AT command mode; two GPRS connections can be established simultaneously on every channel.

The multiplexer protocol must be started and the logical channels opened in compliance with specified procedures.

This chapter also discusses the following issues:

Opening logical channels without parameter negotiation

Opening logical channels with parameter negotiation

Closing of logical channels

4.2 Data link layer

The following sections show the detailed structure a data link frame.

Figure 3: Data link layer

Flag

Address

Control

Length

Information

FCS

Flag

 

1 Octet

1 Octet

1 Octet

1 or 2 Octets

n Octets

1 Octet

1 Octet

of

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

0xF9

 

 

 

 

 

 

 

 

 

Checksum for address, control and length fields, also for the information field in the case of UI frames FCS.

EA

 

Length

 

Length: Length Information

EA:

extension bit;

 

EA = 1

-> 1 octet length information

 

EA = 0

-> >2 octets length information

 

 

 

Frame type:

 

 

 

 

 

 

SABM

Set Asynchronous Balanced Mode

 

 

 

UA

Unnumbered Acknowledgement

 

 

 

DM

Disconnected Mode

 

 

 

DISC

Disconnect

 

 

 

UIH

Unnumbered Information with Header check

 

 

 

UI

Unnumbered Information

 

 

 

P/F-Bit

Poll- /Final - Bit

 

 

 

 

 

 

EA

 

C/R

 

DLCI

 

 

 

 

 

 

DLCI:

Data Link Connection Identifier

C/R:

Command / Response

EA:

extension bit; EA = 1

0xF9

Mux_guide_v06

Page 17 of 36

30.06.2004

Image 17
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 channelsEscape sequence Power savingBandwidth of logical channels Data link layer Structure of the multiplexer protocolIntroduction of the multiplexer protocol 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 fieldLength field Test command TestMultiplexer close down CLD 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