Project

General

Profile

CSD » History » Version 6

laforge, 11/21/2022 12:23 PM

1 6 laforge
{{>toc}}
2
3 1 laforge
{{include(MacroNotImplementedYet)}}
4
5
h1. Circuit Switched Data (CSD)
6
7
CSD is a way to transport user data over circuit-switched GSM calls.  It is the cellular equivalent of the use of analog modems or ISDN TA over wired telephony networks: You dial a number, the usual call control protocol for signaling creates a dedicated, circuit switched connection to the destination.  If they answer the call, a transparent communication channel is established between both sides.
8
9 3 laforge
GSM CSD (in its single-slot variants, excluding HSCSD) implements
10 1 laforge
11 3 laforge
|_.22.002 Bearer Service|_.22.003 Teleservice|_.43.010 model|_.Description|
12
|BS20T|?|2b|transparent synchronous data|
13
|BS30T|?|1b|transparent asynchronous data. first converted aysnc->sync, then treated like sync|
14
|BS20NT|?|3b|non-transparent asynchronous data. Uses RLP (ARQ) protocol for less erros, but creates variable delay.|
15
|?|TS62T|5a|transparent facsimile group 3|
16
17
18 6 laforge
h2. Bearer Services
19
20
|BS21|300|async|
21
|BS22|1200|async|
22
|BS23|1200/75|async|
23
|BS24|2400|async|
24
|BS25|4800|async|
25
|BS26|9600|async|
26
|BS31|1200|sync|
27
|BS32|2400|sync|
28
|BS33|4800|sync|
29
|BS34|9600|sync|
30
31 1 laforge
h2. Facsimile / Telefax
32
33
CSD is also what is used to implement Facsimile (Telefax) services over GSM.
34
35
h2. Interworking
36
37
When CSD services (sync/async/fax) are used between two GSM subscribers, no interworking is required.  The data is passed transparently end-to-end.
38
39
However, when interworking with the wired network is required, an interworking function (IWF) is required.
40
41
h3. Interworking with ISDN data calls
42
43
This is the situation where a GSM mobile subscriber is establishing a CSD call to a native ISDN subscriber.
44
45 4 laforge
In this case, the [[retronetworking:V110|V.110]] signal is rate-adapted at the IWF to the 64kBps of the ISDN bearer chanel.
46 1 laforge
47
h3. Interworking with analog modems in POTS or ISDN
48
49
In this case, the IWF terminates the V.110 from the GSM RAN and implements a modem towards the external POTS/ISDN subscriber.
50
51
h3. Interworking with analog Telefax in POTS or ISDN
52
53 2 laforge
This is similar to the analog modem situation above.
54
55 6 laforge
h2. Rate Adaptation functions
56
57
h3. RA0
58
59
* only used with asynchronous interfaces
60
* async data padded by stop elements to fit the nearest higher synchronous bit rate
61
62
h2. Radio channel types
63
64
h3. TCH/F2.4
65
66
* 3.6 kbit/s radio rate
67
* 2.4 kbit/s services
68
* TS 45.003 Section 3.6 (coding)
69
70
h3. TCH/F4.8
71
72
* 6.0 kbit/s radio rate
73
* 4.8 kbit/s services
74
* TS 45.003 Section 3.4 (coding)
75
* TS 43.010 Section 6.4.1
76
* V.110 based rate adaptation
77
78
h3. TCH/F9.6
79
80
* 12.0 kbit/s radio rate
81
* 9.6 kbit/s services
82
* TS 45.003 Section 3.3 (coding)
83
* TS 43.010 Section 6.4.1
84
* V.110 based rate adaptation
85
86
h3. TCH/F14.4
87
88
* 14.5 kbit/s radio rate
89
* 14.4 kbit/s services
90
* TS 45.003 Section 3.8 (coding)
91
* TS 43.010 Section 6.4.2
92
* PLMN specific rate adaptation
93
94
h3. TCH/H2.4
95
96
* 3.6 kbit/s radio rate
97
* 4.8 kbit/s services
98
* TS 45.003 Section 3.7 (coding)
99
100
h3. TCH/H4.8
101
102
* 6.0 kbit/s radio rate
103
* 4.8 kbit/s services
104
* TS 45.003 Section 3.5 (coding)
105
106
h2. Representation in RTP
107
108
CSData uses Clear mode pseudo-codec a per RFC4040
109
* without redundancy / RTP PT 120
110
* with redundancy / RTP PT 121
111
* SDP uses "CLEARMODE/8000"
112
* 64kBps stream, i.e. 160 octets every 20ms
113
114 1 laforge
h2. Implementation Status
115 3 laforge
116
We currently don't implement these features yet, but we are aiming at implementing them in 2023.  For details, see "all Issues tagged with CSD":https://osmocom.org/issues?f%5B%5D=tags&f%5B%5D=status_id&fields%5B%5D=tags&fields%5B%5D=status_id&op%5Bstatus_id%5D=o&op%5Btags%5D=%3D&operators%5Bstatus_id%5D=o&operators%5Btags%5D=%3D&set_filter=1&v%5Bstatus_id%5D%5B%5D=&v%5Btags%5D%5B%5D=ASCI&values%5Bstatus_id%5D%5B%5D=&values%5Btags%5D%5B%5D=CSD
117
118
h2. Relevant specifications
119
120
|_.Number|_.Description|
121
|3GPP TS 22.002|CS Bearer Services|
122
|3GPP TS 22.003|CS Teleservices|
123 6 laforge
|3GPP TS 22.004
124 5 laforge
|3GPP TS 43.010|Decription of connection types. Note particularly Table 4 + section  6.4|
125 3 laforge
|3GPP TS 43.045|Fax G3|
126 1 laforge
|3GPP TS 44.021|Rate adaptation on MS-BSS interface; RA0; RA1/RA1' single-slot|
127
|3GPP TS 44.022|RLP protocol (for non-transparent async)|
128 6 laforge
|3GPP TS 27.001|TA functions in MS (incl. filtering of status bits)|
129
|3GPP TS 27.002|TA functions for async bearers (incl. data compression)|
130 1 laforge
|3GPP TS 27.003|TA functions for sync bearers|
131 5 laforge
|3GPP TS 48.020|Rate adaptation on BSS-MSC interface; RA1/RA1' multi-slot, RA1''|
132 1 laforge
|3GPP TS 48.060|TRAU frame format for classic E1 BTS (Section 5.3, 5.5.3, 6.7)|
133
|3GPP TS 29.007|Interworking between PLMN and ISDN|
134 6 laforge
|IETF RFC4040|RTP payload format for  64kbps transparent call|
135
|ITU-T V.110|Rate adaptation|
Add picture from clipboard (Maximum size: 48.8 MB)