1. DL manuals
  2. Wavecom
  3. Multiplexer
  4. GX64 GSM 27.010 Multiplexer Feature
  5. Application Note

Wavecom GX64 GSM 27.010 Multiplexer Feature Application Note

Summary of GX64 GSM 27.010 Multiplexer Feature

  • Page 1

    Gx64 application note gsm 27.010 multiplexer feature reference: wi_dev_gx64_apn_006 revision: 001 date: 2007/01/30

  • Page 2

    Trademarks ®, wavecom gx64 application note this document is the sole and exclusive property of wavecom. Not to be distributed or divulged without prior written agreement. Ce document est la propriété exclusive de wavecom. Il ne peut être communiqué ou divulgué à des tiers sans son autorisation préa...

  • Page 3

    Table of contents 1 overview................................................................................................. 5 2 glossary.................................................................................................. 5 3 introduction..................................................

  • Page 4

    Gx64 application note this document is the sole and exclusive property of wavecom. Not to be distributed or divulged without prior written agreement. Ce document est la propriété exclusive de wavecom. Il ne peut être communiqué ou divulgué à des tiers sans son autorisation préalable 6.5 ...............

  • Page 5

    1 overview this document provides an overview of gsm multiplexer feature defined by 3gpp 27.010 specification, details of 27.010 multiplexer features supported by wavecom gr/gs64 wireless cpu, and application design considerations. This document is intended as a reference for integrators, as an aid ...

  • Page 6

    3 introduction the 27.010 multiplexer protocol operates between an ms (e.G. Gr/gs64) and a te (i.E. A host application) and allows a number of simultaneous virtual channels over a serial asynchronous interface (e.G., a rs232 link). Gprs data, sms data, at commands, unsolicited responses, etc. Can be...

  • Page 7

    3.1 benefits of mux the existence of simultaneous virtual channels in mux mode creates advantages over serial mode where only one link is available. Some benefits are as follows: 1. A host application can parse at command results and unsolicited responses on different channels. 2. A gprs or a csd da...

  • Page 8

    4 use case examples in this section, we will examine several use case scenarios where mux channels are advantageous. Comparisons between serial mode and mux mode are also provided. In following scenarios, a gprs data connection could be an on-board tcp/ip socket connection or a dial up gprs connecti...

  • Page 9

    Scenario 3: at commands and unsolicited responses in different channels serial mode: a host application has to parse both at commands and unsolicited messages, which can be complex. Mux mode: the host application uses two virtual channels, first one for at commands and second one for unsolicited res...

  • Page 10

    5 gr/gs64 27.010 mux implementation gr/gs64 27.010 implementation conforms to the release 99 gsm specification 3gpp 27.010 version 3.4.0. 3gpp 27.010 defines three operating options: basic, advanced without error recovery and advanced with error recovery. The gr/gs64 supports basic option. 3gpp 27.0...

  • Page 11

    5.4 parameter negotiation individual channel parameters such as priority, acknowledgement timer, maximum frame size, and maximum number of retransmissions are optional for negotiation according to 27.010 standard. Gr/gs64 only supports maximum frame size negotiation. The upper limit of the negotiabl...

  • Page 12

    5.6 baud rate gr/gs64 supports baud rates ranging from 9600 to 230400. They correspond to the third parameter of the at+cmux command. If autobaud is active (i.E. At+ipr=0) when the mux is started, it is automatically turned off and the mux continues to operate at the baud rate in which the +cmux com...

  • Page 13

    6 application design considerations when designing a host application that uses mux, following have to be taken into considerations up front. 6.1 local and global settings integrators must take local and global settings into consideration when designing host application that utilizes mux. At command...

  • Page 14

    Some local settings may cause “global” activities and should only be set in one channel. For instance ats0 and at+cgauto should not be used in more than one channel. 6.2 at commands not applicable in mux mode some at commands are not applicable in mux mode. One such an example is at+cmux command – a...

  • Page 15

    Although in most practical situations serial links have very good quality and thus have very rare instances of transmission errors, host applications still have to make sure there are application level error detection and recovery mechanisms in place. 6.5 flow control and buffer management figure 2 ...

  • Page 16

    Channels in the uart io buffer. As a result, individual data flow can not be stopped right away. This constraint is inherent to 27.010 standard and a host application should size its receiving buffers accordingly and carefully manage the data flow. This can typically be accomplished by using a large...

  • Page 17

    6.7 optimal channel usage a host application can choose to use more than two channels. For example, one for at commands such as sms commands and +csq command, one for unsolicited responses, and one or more for on board tcp/ip socket connections, where each socket connection runs in a separate channe...

  • Page 18

    Dte application dce port emulation entity write read 27.010 27.010 control request confirm control parameters parameter setting response indication port interface e.G. Wavecom cmux dirver control parameters parameter setting 27.010 service interface figure 3: 27.010 interfaces wavecom provides a mic...

  • Page 19

    Appendix a – basic mux procedures to facilitate the understanding of the 27.010 specification and the basic mux procedures, an example sequence of mux frames is provided below. Note in the following examples: Î stands for the flow from te to ms and Í stands for flows from ms to te. If not otherwise ...

  • Page 20

    N1: 31 n1: 0 n2: 3 k: 1 fcs closing flag priority: 1 t1: 10 lower 8 bit higher 8 bits Í f9 03 ff 15 81 11 01 00 01 0a 1f 00 00 00 fb f9 f9 03 ff 15 81 11 01 00 parameter negotiation response length 8 dlc 1 covergence layer type 1 length 10 opening flag dlc 0 uih 01 0a 1f 00 00 00 fb f9 n1: 31 n1: 0 ...

  • Page 21

    Parameter negotiation command length 8 dlc 2 covergence layer type 1 length 10 opening flag dlc 0 uih 01 0a 1f 00 03 01 fb f9 n1: 31 n1 n2: 3 k: 1 fcs closing flag priority: 1 t1: 10 lower 8 bit higher 8 bits Í f9 03 ff 15 81 11 02 00 01 0a 1f 00 00 00 fb f9 f9 03 ff 15 81 11 02 00 parameter negotia...

  • Page 22

    Closing flag opening flag dlc 2 ua length = 0 fcs 4) dlc1 modem status command Î f9 03 ff 09 e3 05 07 09 ee f9 f9 03 ff 09 e3 05 msc type command length=2 uih type opening flag length = 4 dlc 0 07 09 ee f9 closing flag v.24 signal fcs dlc 1 Í f9 03 ff 09 e1 05 07 09 ee f9 f9 03 ff 09 e1 05 msc type ...

  • Page 23

    5) close down mux Î f9 03 53 01 fd f9 f9 03 53 01 fd f9 closing flag opening flag dlc 0 disc length = 0 fcs Í f9 07 73 01 15 f9 f9 0b 73 01 92 f9 f9 03 73 01 d7 f9 f9 07 73 01 15 f9 closing flag opening flag dlc 1 ua length = 0 fcs f9 0b 73 01 92 f9 closing flag opening flag dlc 2 ua length = 0 fcs ...

  • Page 24

    27.010 mux feature page: 24/24 gx64 application note this document is the sole and exclusive property of wavecom. Not to be distributed or divulged without prior written agreement. Ce document est la propriété exclusive de wavecom. Il ne peut être communiqué ou divulgué à des tiers sans son autorisa...