SIM5360 CSD Application Note V0.01

CSD Application Note
Document Title: CSD Application Note

Version: 0.01
Date: 2014-02-21
Status: Developing
Document ID: SIM5360_CSD_Application_Note_V0.01
General Notes
SIMCom offers this information as a service to its customers, to support application and engineering efforts
that use the products designed by SIMCom. The information provided is based upon requirements
specifically provided to SIMCom by the customers. SIMCom has not undertaken any independent search
for additional relevant information, including any information that may be in the customer’s possession.
Furthermore, system validation of this product designed by SIMCom within a larger electronic system
remains the responsibility of the customer or the customer’s system integrator. All specifications supplied
herein are subject to change.
Copyright
This document contains proprietary technical information which is the property of SIMCom Limited.,
copying of this document and giving it to others and the using or communication of the contents thereof,
are forbidden without express authority. Offenders are liable to the payment of damages. All rights reserved
in the event of grant of a patent or the registration of a utility model or design. All specification supplied
herein are subject to change without notice at any time.
Copyright © Shanghai SIMCom Wireless Solutions Ltd. 2013
SIM5360_CSD_Application_Note_V0.01 1 2014-02-21
Version History
Version Chapter Comments
V0.01 New Version
Contents
V e r s i o n H i s t o r y .................................................................................................................................. 2
C o n t e n t s ................................................................................................................................................... 3
CSD Application Note ................................................................................................................................... 4
1. Introduction ........................................................................................................................................... 4
1.1 Overview....................................................................................................................................................... 4
1.2 References..................................................................................................................................................... 4
1.3 Terms and Abbreviations .............................................................................................................................. 4
2. CSD Call Setting.................................................................................................................................... 5
2.1 CSD mode..................................................................................................................................................... 5
2.2 Select bearer service type.............................................................................................................................. 5
3. CSD Call Control .................................................................................................................................. 6
3.1 CSD call Origination..................................................................................................................................... 6
3.2 CSD call Hang up ......................................................................................................................................... 6
3.3 CSD call Incoming........................................................................................................................................ 6
3.4 CSD call status.............................................................................................................................................. 6
4. CSD Call Follow .................................................................................................................................... 6
4.1 MO Call ........................................................................................................................................................ 7
4.2 MT Call......................................................................................................................................................... 8
5. Typical Samples ..................................................................................................................................... 8
6. Q&A ....................................................................................................................................................... 9
Contact Us.................................................................................................................................................... 11
1. Introduction
1.1 Overview
This document gives the usage of CSD data call functions. Users can get useful information about the
function quickly through this document.
Circuit Switched Data (CSD) is the original form of data transmission developed for mobile
phone systems like GSM and WCDMA. A CSD call functions in a very similar way to a normal voice call.
SIM5360 CSD features:

z Supports data rates up to 64kbps.
z Supports Both Synchronous/transparent and Asynchronous/nontransparent
z Supports CSD call status query/URC.
1.2 References
The present document is based on the following documents:

[1] SIMCOM_SIM5360_ATC_EN_V0.05.pdf
1.3 Terms and Abbreviations
For the purposes of the present document, the following abbreviations apply:
AT ATtention; the two-character abbreviation is used to start a command line to be sent from
TE/DTE to TA/DCE
CSD Circuit Switched Data
GSM Global system for mobile communications
WCDMA Wideband code division multiple access
RLP Radio Link Protocol
URC Unsolicited Result Code
2. CSD Call Setting

The purpose of this section is to help get you start with CSD setting.
2.1 CSD mode
The SIM5215/SIM5216/SIM5218 module supports CSD and video call over CSD function, so if you
want use CSD function to transfer data in stand of using integrated video call function, you should use
AT+VPSM=1 command to switch off video call function.
The SIM5320/SIM5310 module support CSD data call only, does not supports video call over CSD
function, so the CSD mode is default mode
2.2 Select bearer service type
Following table show the supported CSD bearer service type:
The CSD should support by operator network, please contact the operator for supported feature.
Synchronous/transparent bearers ensure constant throughput but are best effort for frame transmission
so some data loss is expected. This configuration is used for video telephony call on WCDMA and
facsimile on GSM. Asynchronous/nontransparent bearers ensure reliable data transmission via Reliable
Link Protocol RLP which is an implementation of the classic Sliding Window protocol. This configuration
is used for data transfer on both GSM and WCDMA.
For example:
If user want to implement video call use 64kbps CSD channel, the suggested configuration is:
AT+CBST=134,1,0
3. CSD Call Control

The CSD call control and the state monitor are basically the same as voice calls.
3.1 CSD call Origination
User can originate a CSD data call by ATD command, the termination character ‘:’ should not be used.
3.2 CSD call Hang up
User can hang up a CSD data call by ATH command or drop DTR pin.
3.3 CSD call Incoming
When there is a CSD call incoming, the RING/CRING URC should received by user. In order to
distinguish between voice call and data call, send command AT+CRC=1 to enable the extended format of
incoming call indication.
3.4 CSD call status
User can query the CSD call state by AT+CLCC command, or enable the +CLCC URC by setting
AT+CLCC=1 command.
Note that if the CSD data call is in transparent mode, the COM port (ATD or ATA command send to)
used by CSD is enter data mode, the AT command should not send to COM port when it’s in data mode, in
such case, there are two methods to send AT command:
Use +++ and ATO command to switch between data mode and command mode.
Send AT command via another COM port.
4. CSD Call Follow

We use 64kbps CSD call for example in following flowchart, the bearer service type is setup by
AT+CBST=134,1,0
4.1 MO Call
MCU Module
ATD...
CONNECT 115200
CSD data(160 bytes every 20ms)
.
.
.
+++
ATH
NO CARRIRER
4.2 MT Call
MCU Module
+CRING:
SYNC
ATA
CONNECT
115200
.
.
.
+++
ATH
NO
CARRIRER
5. Typical Samples
AT+CRC=1
OK
AT+CBST=134,1,0
OK
+CRING: SYNC
+CRING: SYNC
AT+CLCC
+CLCC: 1,1,4,1,0,"18602102222",128
OK
ATH
OK
+CRING: SYNC
+CRING: SYNC
AT+CLCC
+CLCC: 1,1,4,1,0,"18602102222",128
OK
ATA
CONNECT 115200
……
+++
OK
……
ATH
OK
ATD18602102222
CONNECT 115200
……
NO CARRIER
6. Q&A
Some frequently asked questions may be helpful for using CSD.
In 64kbps CSD mode, why the peer can not receive data when data send to COM port successful?
Data will be buffered in module when there is no more than 80 bytes, so we recommend that sending data
in multiples of 80 bytes.
In some cases, you should add some padding data, for example, remaining undelivered data length of the
file is less than 80 bytes.
We use 64kbps CSD to implement video call function, if we need to reverse the bit order of
receiving/send data?
The data received/sent from/to our module is in the same bit order; you may need to reverse bit order
according your video call protocol.
You can use table look-up method to achieve the bit order reverse before sending data and after receiving
data, e.g.
BYTE reflect[] = {
0x00, 0x80, 0x40, 0xc0, 0x20, 0xa0, 0x60, 0xe0, 0x10, 0x90, 0x50, 0xd0, 0x30, 0xb0, 0x70, 0xf0,
0x0c, 0x8c, 0x4c, 0xcc, 0x2c, 0xac, 0x6c, 0xec, 0x1c, 0x9c, 0x5c, 0xdc, 0x3c, 0xbc, 0x7c, 0xfc,
0x0a, 0x8a, 0x4a, 0xca, 0x2a, 0xaa, 0x6a, 0xea, 0x1a, 0x9a, 0x5a, 0xda, 0x3a, 0xba, 0x7a, 0xfa,
0x0e, 0x8e, 0x4e, 0xce, 0x2e, 0xae, 0x6e, 0xee, 0x1e, 0x9e, 0x5e, 0xde, 0x3e, 0xbe, 0x7e, 0xfe,
0x0d, 0x8d, 0x4d, 0xcd, 0x2d, 0xad, 0x6d, 0xed, 0x1d, 0x9d, 0x5d, 0xdd, 0x3d, 0xbd, 0x7d, 0xfd,
0x0b, 0x8b, 0x4b, 0xcb, 0x2b, 0xab, 0x6b, 0xeb, 0x1b, 0x9b, 0x5b, 0xdb, 0x3b, 0xbb, 0x7b, 0xfb,
0x0f, 0x8f, 0x4f, 0xcf, 0x2f, 0xaf, 0x6f, 0xef, 0x1f, 0x9f, 0x5f, 0xdf, 0x3f, 0xbf, 0x7f, 0xff
};
for(i = 0; i < 160; i++) {
buffer[i] = reflect(buffer[i]);
}
How to confirm the CSD data is disconnect?

1. “NO CARRIRER” received indicates the CSD call is disconnect.
2. You can use AT+CLCC command to query the call state in another COM port, or you can use +CLCC
URC to determine the call status, please refer to section 3.4 of this document.
Why the command echo is turn on (ATE1) sometimes when the command echo is turn off (ATE0) at
the program Initializes?
When the CSD call is disconnected, the COM port exit data mode and enter command mode, the CSD
data wrote to COM port may treated as command, and the ATE1 string might just in CSD data, and cause
this problem.
We suggest:
1. Upper-layer protocol performs normal disconnecting process, do not send data to COM port when
connection is disconnect.
2. Detect COM port CD status change; do not send data to COM Port when there are no carriers.
The CSD data call refuse by peer, we just received a “NO CARRIRER”, is there some method to
confirm the call disconnect reason?
You can use AT+CEER command to query the call disconnect reason, more information please refer to
our AT commands manual.
Contact Us
Shanghai SIMCom Wireless Solutions Ltd.
Add: Building A, SIM Technology Building, No.633, Jinzhong Road, Changning District
200335
Tel: +86 21 3252 3300
Fax: +86 21 3252 3301
URL: http:/www.sim.com/wm/

SIM5360 CSD Application Note V0.01

Uploaded by

Copyright:

Available Formats

SIM5360 CSD Application Note V0.01

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SIM5360 CSD Application Note V0.01

Uploaded by

Copyright:

Available Formats

CSD Application Note

CSD Application Note

Document Title: CSD Application Note

Copyright © Shanghai SIMCom Wireless Solutions Ltd. 2013

CSD Application Note

SIM5360 CSD features:

The present document is based on the following documents:

1.3 Terms and Abbreviations

2. CSD Call Setting

2.1 CSD mode

2.2 Select bearer service type

Following table show the supported CSD bearer service type:

3. CSD Call Control

3.1 CSD call Origination

3.2 CSD call Hang up

3.3 CSD call Incoming

3.4 CSD call status

4. CSD Call Follow

CSD data(160 bytes every 20ms)

CSD data(160 bytes every 20ms)

CSD data(160 bytes every 20ms)

CSD data(160 bytes every 20ms)

CSD data(160 bytes every 20ms)

CSD data(160 bytes every 20ms)

How to confirm the CSD data is disconnect?

You might also like