Siemens Mux_guide_v06 manual Flag sequence, Address field

Page 18

Multiplexer User's Guide

Confidential / Released

s

mobile

4.2.1 Flag sequence

A flag sequence is a specific bit pattern (usually 11111001; hexadecimal: 0xF9) used to mark the beginning and the end of a frame of data.

Each frame begins and ends with a flag sequence. Only one flag sequence occurs between any two frames. If two successive flag sequences do occur, the frame is regarded as being empty and is discarded.

The flag sequence is used for the synchronization of frames.

4.2.2 Address field

Data link connection identifier is a frame relay term defining a 10-bit field of the address field. The DLCI identifies the data link and its service parameters, including the frame size.

The values for the Data Link Connection Identifier (DLCI) are dynamically defined apart from DLCI = 0.

Table 2: Address field

EA

C/R

DLCI

DLCI:

Data Link Connection Identifier

C/R:

Command / Response

EA:

extension bit; EA = 1

Table 3: Assignment of the DLCI

 

 

 

DLCI number (decimal)

Priority

 

 

 

 

 

Multiplexer

control

channel

0

0

(see chapter 4.3.6)

 

 

highest priority

 

 

 

 

 

 

 

AT commands, data, fax, GPRS

1

7

 

 

 

 

AT commands, GPRS

 

2,3

7

 

 

 

 

 

The command/response bit identifies the frame as a command or response. A command contains the address of the data link connection to which the command is sent. A response contains the address of the data link connection sending the frame.

Table 4: Use of the command/response bit

Command/Response

Direction

 

 

C/R

 

 

 

 

Command

Customer µC

GSM engine

1

(SABM, DISC)

 

 

 

 

GSM engine

Customer µC

0

 

 

 

 

 

Response

Customer µC

GSM engine

0

(UA, DM)

 

 

 

 

GSM engine

Customer µC

1

 

 

 

 

 

Every command expects a response. No provision is made to repeat the command if no response is received.

Mux_guide_v06

Page 18 of 36

30.06.2004

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