Related Manuals for Siemens Mux_guide_v06
Summary of Contents for Siemens Mux_guide_v06
- Page 1 Multiplexer User's Guide Siemens Cellular Engines Version: DocID: Mux_guide_v06...
- Page 2 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...
-
Page 3: Table Of Contents
Multiplexer close down (CLD) ...27 4.3.8 Test command (Test)...27 4.3.9 Modem status command (MSC) ...28 4.3.10 Power saving control (PSC)...30 4.3.11 Non-supported command response (NSC)...31 Example: Establishing logical channels without parameter negotiation ...32 Mux_guide_v06 Page 3 of 36 o b i l e 30.06.2004... - Page 4 Table 5: Coding of the control field... 19 Table 6: Version differences for MSC ... 34 Table 7: IEI coding ... 36 Table 8: Coding of “TestCommand” (Example)... 36 Mux_guide_v06 Page 4 of 36 o b i l e 30.06.2004...
-
Page 5: Document History
What is new Added further supported products. 3 - 3.4 Restructured and revised all chapters. 3.1.2, 3.3, To control SLEEP mode use PSC messages rather than entering AT+CFUN=<n> 4.3.10 Mux_guide_v06 Page 5 of 36 o b i l e 30.06.2004... -
Page 6: Introduction
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. Multiplexer protocol sources (WinMux2k), provided by Siemens AG, can be obtained on request from your local distributor. -
Page 7: Supported Products And Related Documents
[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 References Digital Cellular Telecommunications Systems (Phase 2+);... -
Page 8: Term And Abbreviations
Mobile originated Multiplexer Protocol Mobile Station MSDN Microsoft Developer Network Mobile terminated Multiplexer Operating System Personal Computer Power saving control Request to Send Terminal Equipment UART Universal Asynchronous Receiver Transmitter Mux_guide_v06 Page 8 of 36 o b i l e 30.06.2004... -
Page 9: Multiplexer Protocol - An Overview
In multiplexer mode, AT commands and data are encapsulated into packets. Each packet has a channel identification and may vary in length. Note: All statements regarding GPRS are valid only for Siemens wireless products capable of GPRS. Terminal programs or internal programs... -
Page 10: Virtual Channels And At Commands
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 GPRS incoming connection... -
Page 11: Integrating Multiplexer Into The Customer Application
When designing a multiplexer application, you can create your own sources or take advantage of the sources delivered upon request by Siemens. The Siemens sources are packed in a *.zip file which includes a driver for Windows 2000 and Windows XP. See [5] for a detailed description. -
Page 12: Dependencies Between Multiplexer Channels And Restrictions Of Use
Example: • The battery capacity can be queried from channel 2 or 3 while a voice, fax or data call is made on channel 1. Mux_guide_v06 Page 12 of 36 o b i l e 30.06.2004... -
Page 13: Timing Conditions
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 has only one physical serial interface (ASC0) you can skip this chapter. -
Page 14: Multiplexer Control And Signaling Lines
1. RTS shall not be switched off to prevent loss of data (control data cannot be sent in this case). If flow control is needed, it is recommended to use logical flow control on every channel. Mux_guide_v06 Page 14 of 36 o b i l e... -
Page 15: Figure 2: Logical Flow Control And Rts/Cts Signaling Behind The Decoder
E.g. in some situations it may be advisable to display RING on channel 1 only. Please keep in mind that a call can be accepted on one channel only. Therefore some kind of mutual locking mechanism must be used. Mux_guide_v06 Module HW flow control logical flow control (FC) -
Page 16: Escape Sequence
In such a case if channel 2 and 3 were used for data transmissions, e.g. editing the phonebook, both channels would need to share a bandwidth of approximately 3 kByte per second. Mux_guide_v06 Page 16 of 36 o b i l e... -
Page 17: Structure Of The Multiplexer Protocol
Opening logical channels with parameter negotiation • Closing of logical channels 4.2 Data link layer following sections show the detailed structure a data link frame. Figure 3: Data link layer Mux_guide_v06 Flag Address Control Length 1 Octet 1 Octet 1 Octet 1 or 2 Octets... -
Page 18: Flag Sequence
Command/Response Command (SABM, DISC) Response (UA, DM) Every command expects a response. No provision is made to repeat the command if no response is received. Mux_guide_v06 DLCI number (decimal) Direction → GSM engine Customer µC GSM engine → Customer µC Customer µC →... -
Page 19: Control Field
(unnumbered information with header check) P/F: Poll/Final bit Commands: P = 1, Responses: F = 1 For each DLCI, only one frame with P = 1 may ever be expected. Mux_guide_v06 Page 19 of 36 o b i l e 30.06.2004... -
Page 20: Length Indicator
Chapter 3.1.2 for details on the maximum frame size. octet: Bit 1 Bit 2 Bit 3 octet (not supported by Siemens wireless modules): Bit 1 Bit 2 Bit 3 E/A = 1: only one octet for the Length Indicator E/A = 0: two octets for the Length Indicator 4.2.5 Information field... -
Page 21: State Diagrams
Disconnecting individual channels (DLC release) causes the state machine for those channels to revert to DISCONNECTED. Release of the multiplexer control channel DLCI = 0 corresponds to a CLOSE DOWN. The CLOSE DOWN command switches back. Mux_guide_v06 Page 21 of 36 o b i l e... -
Page 22: Figure 4: Relationship Between The Customer Μc And The Gsm Engine Μc
C O N N E C TE D Inform ation Transfer Figure 4: Relationship between the customer µC and the GSM engine µC Mux_guide_v06 C lose D own D IS - D LC R elease D LC E stablishm ent... -
Page 23: Figure 5: Mpi - Startup, Dlc Establishment And Information Transfer
RequestStartUp ConfirmStartUp Disconnected RequestSABM ConfirmDM Disconnected RequestSABM ConfirmUA Connected RequestUIH Connected IndicationUIH Connected Figure 5: MPI – Startup, DLC establishment and information transfer Mux_guide_v06 Serial interface GSM engine µC Closed Down IndicationStartUp ResponseStartUp Disconnected IndicationSABM ResponseDM Disconnected IndicationSABM ResponseUA Connected... -
Page 24: Figure 6: Mp - Dlc Release And Close Down
RequestDISC ConfirmUA Disconnected Disconnected/ Disconnected Negotiation/ Connected RequestCloseDown ConfirmCloseDown Closed Down Mux_guide_v06 Serial interface GSM engine µC IndicationDISC ResponseUA IndicationCloseDown ResponseCloseDown Figure 6: MP - DLC release and close down Page 24 of 36 o b i l e Connected... -
Page 25: Start-Up Procedure
UIH: Customer µC (Initiator) UIH: Mux_guide_v06 Figure 7: DLC establishment P = 0, C/R = 1 P = 0, C/R = 0 Figure 8: Information transfer Page 25 of 36 o b i l e... -
Page 26: Dlc Release
If there is only on octet, EA bit = 1 is set. C/R bit: Indicates whether the sequence is a command or a response. T-bits: Coding of the command type. Mux_guide_v06 responding station is already disconnected Figure 9: DLC release Length... -
Page 27: Multiplexer Close Down (Cld)
The length byte indicates the number of test bytes sent in the value bytes. The responding station should answer with exactly the same bit sequence. The test command is used for the version control. For more detailed information see Chapter 5. Mux_guide_v06 Bit 4 Bit 5... -
Page 28: Modem Status Command (Msc)
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 Mux_guide_v06 DLCI V.24 signals 1 octet 1 octet Bit 4... - Page 29 If the customer application detects an escape sequence (usually +++), it sends this optional octet with bit 1 set to 1. The module calls its original escape sequence. Mux_guide_v06 Bit 4 Bit 5...
-
Page 30: Power Saving Control (Psc)
Bit 3 All wake up events and details of the CYCLIC and NON-CYCLIC SLEEP mode are specified in [2]. In responses: Bit 1 Bit 2 Bit 3 Mux_guide_v06 Bit 4 Bit 5 Bit 6 Bit 4 Bit 5 Bit 6... -
Page 31: Non-Supported Command Response (Nsc)
Bit 1 Bit 2 Bit 3 C/R bit: Returns the same value as in the received, non-supported command Frames not recognized by the receiving entity are responded by a NSC-frame. Mux_guide_v06 Bit 4 Bit 5 Bit 6 Bit 4 Bit 5... -
Page 32: Example: Establishing Logical Channels Without Parameter Negotiation
Disconnected DLCI = 1 RequestSABM DLCI = 1 ConfirmUA DLCI = 1 Connected DLCI = 1 Figure 13: Establishing the multiplexer control channel and the logical channel Mux_guide_v06 Serial interface GSM engine µC Closed Down IndicationStartUp ResponseStartUp Disconnected Disconnected DLCI = 0... -
Page 33: Multiplexer Protocol Version Control
• TE version (e.g. version 1): • MS version (e.g. version 2): In multiplexer protocol sources delivered by Siemens AG version control is integrated. When designing an application based on other sources take care to implement the version check as well, especially if you wish to upgrade to later firmware releases. It is strongly recommended to implement the latest multiplexer version available. -
Page 34: Multiplexer Protocol Versions
Bit 1 Bit 2 Bit 3 Table 6: Version differences for MSC Version number Host application ⇒ Module If 0 is indicated, all calls are terminated Mux_guide_v06 DLCI V.24 signals 1 octet 1 octet Bit 4 Bit 5 Bit 6... -
Page 35: Implementing Version Control
However, it is possible to send test commands with “any contents” (except for test messages with the specific IEI for the version check). If a test command with “any contents” is sent, it has to be sent back to the originator with the same contents. Mux_guide_v06 expected, multiplexer... -
Page 36: Coding Of "Testcommand" Message
Confidential / Released 5.3.2 Coding of “TestCommand” message The coding of the multiplexer stack version is used specifically for SIEMENS equipment and is not defined in ETSI standards. The IEI values defined for the verification pattern of the “TestCommand” message are indicated in Table 7. See GSM recommendation 07.10, Section 5.4.6.3.4).