Project

General

Profile

Local Call Local Switch » History » Version 5

laforge, 05/28/2018 09:45 PM
add toc

1 5 laforge
{{>toc}}
2
3 1 laforge
h1. Local Call Local Switch
4
5
In the classic 3GPP architecture, all calls go from BTS to BSC to MSC, only then to go back all the same way in case the second call leg is also in the same cell.  Particularly in case of statellite or other expensive/slow back-haul this is far from ideal.
6
7
Using LCLS, a BSC can know which of the two call legs belong to one call, and can then directly bridge the RTP/media locally.
8
9 4 laforge
h2. Affected messages
10
11
h3. BSSMAP ASSIGNMENT REQUEST
12
13
This message may contain the following, LCLS related IEs:
14
* Global Call Reference
15
* LCLS Configuration
16
* LCLS Connection Status Control
17
* LCLS Correlation Not Needed
18
19
Using those LCLS related IEs, the MSC can grant the BSS to elect to use LCLS for this call [leg].
20
21
h3. BSSMAP ASSIGNMENT COMPLETE
22
23
* LCLS BSS Status
24
25
Using this, the BSC can inform the MSC on whether or not LCLS was enabled.
26
27
h3. BSSMAP HANDOVER REQUEST
28
29
* LCLS Configuration
30
* LCLS Connection Status Control
31
32
Request from MSC to target BSC. The MSC specifies which kind of LCLS (if any) is permitted and/or requested.
33
34
h3. BSSMAP HANDOVER REQUEST ACK
35
36
* LCLS BSS Status
37
38
Acknowledgement from targe BSC to MSC in response to a @BSSMAP HANDOVER REQUEST@.
39
The LCLS BSS Status contains the [possibly modified] LCLS status for the call.
40
41
h3. BSSMAP HANDOVER COMPLETE
42
43
* LCLS BSS Status
44
45
Informs the MSC that the MS has successfully accessed the target cell. The LCLS BSS Status contains the [possibly modified] LCLS status for the call.
46
47
h3. BSSMAP HANDOVER PERFORMED
48
49
* LCLS BSS Status
50
51
unilateral notification from BSC to MSC about an internal (intra-BSC) hand-over having been performed.  The LCLS BSS Status contains the [possibly modified] LCLS status for the call.
52
53
h3. BSSMAP INTERNAL HANDOVER CMD
54
55
* LCLS Connection Status Control
56
57
This is sent in AoIP from MSC to BSC in response to am earlier @BSMAP INTERNAL HANDOVER REQUIRED@. We don't implement this in OsmoBSC.
58
59
h3. BSSMAP LCLS CONNECT CONTROL
60
61
* LCLS Configuration
62
* LCLS Connection Status Control
63
64
Sent by MSC to BSC in order to change the configuration/permission of LCLS during an ongoing call.
65
66
h3. BSSMAP LCLS CONNET CONTROL ACK
67
68
* LCLS BSS Status
69
70
Sent by BSC to MSC in response to a @BSSMAP LCLS CONNECT CONTROL@, indicating the [possibly updated] LCLS status.
71
72
h3. BSSMAP LCLS NOTIFICATION
73
74
* LCLS BSS Status
75
* LCLS Break Request
76
77
This message is sent from the BSC to the MSC to inform it about some changes in the LCLS status.  This could e.g. be the case after a BSS-internal hand-over where the new BTS/channel doesn't support LCLS.
78
79 1 laforge
h2. Spec references
80
81
* http://www.3gpp.org/DynaReport/23284.htm
82 2 laforge
** "3GPP TS 23.284 Rel 14":http://www.etsi.org/deliver/etsi_ts/123200_123299/123284/14.00.00_60/ts_123284v140000p.pdf
83 1 laforge
* http://www.3gpp.org/DynaReport/WiCr--440021.htm
84
* http://www.3gpp.org/DynaReport/WiCr--430001.htm
85 3 laforge
86
h2. Other references
87
88
* OsmoDevCon 2018 video: https://media.ccc.de/v/DVE7UU
89
* OsmoDevCon 2018 slides: https://pretalx.sysmocom.de/media/osmodevcon2018-lcls.pdf
Add picture from clipboard (Maximum size: 48.8 MB)