Project

General

Profile

Local Call Local Switch » History » Version 5

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

1 5 laforge
{{>toc}}
2 5 laforge
3 1 laforge
h1. Local Call Local Switch
4 1 laforge
5 1 laforge
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 1 laforge
7 1 laforge
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 1 laforge
9 4 laforge
h2. Affected messages
10 4 laforge
11 4 laforge
h3. BSSMAP ASSIGNMENT REQUEST
12 4 laforge
13 4 laforge
This message may contain the following, LCLS related IEs:
14 4 laforge
* Global Call Reference
15 4 laforge
* LCLS Configuration
16 4 laforge
* LCLS Connection Status Control
17 4 laforge
* LCLS Correlation Not Needed
18 4 laforge
19 4 laforge
Using those LCLS related IEs, the MSC can grant the BSS to elect to use LCLS for this call [leg].
20 4 laforge
21 4 laforge
h3. BSSMAP ASSIGNMENT COMPLETE
22 4 laforge
23 4 laforge
* LCLS BSS Status
24 4 laforge
25 4 laforge
Using this, the BSC can inform the MSC on whether or not LCLS was enabled.
26 4 laforge
27 4 laforge
h3. BSSMAP HANDOVER REQUEST
28 4 laforge
29 4 laforge
* LCLS Configuration
30 4 laforge
* LCLS Connection Status Control
31 4 laforge
32 4 laforge
Request from MSC to target BSC. The MSC specifies which kind of LCLS (if any) is permitted and/or requested.
33 4 laforge
34 4 laforge
h3. BSSMAP HANDOVER REQUEST ACK
35 4 laforge
36 4 laforge
* LCLS BSS Status
37 4 laforge
38 4 laforge
Acknowledgement from targe BSC to MSC in response to a @BSSMAP HANDOVER REQUEST@.
39 4 laforge
The LCLS BSS Status contains the [possibly modified] LCLS status for the call.
40 4 laforge
41 4 laforge
h3. BSSMAP HANDOVER COMPLETE
42 4 laforge
43 4 laforge
* LCLS BSS Status
44 4 laforge
45 4 laforge
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 4 laforge
47 4 laforge
h3. BSSMAP HANDOVER PERFORMED
48 4 laforge
49 4 laforge
* LCLS BSS Status
50 4 laforge
51 4 laforge
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 4 laforge
53 4 laforge
h3. BSSMAP INTERNAL HANDOVER CMD
54 4 laforge
55 4 laforge
* LCLS Connection Status Control
56 4 laforge
57 4 laforge
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 4 laforge
59 4 laforge
h3. BSSMAP LCLS CONNECT CONTROL
60 4 laforge
61 4 laforge
* LCLS Configuration
62 4 laforge
* LCLS Connection Status Control
63 4 laforge
64 4 laforge
Sent by MSC to BSC in order to change the configuration/permission of LCLS during an ongoing call.
65 4 laforge
66 4 laforge
h3. BSSMAP LCLS CONNET CONTROL ACK
67 4 laforge
68 4 laforge
* LCLS BSS Status
69 4 laforge
70 4 laforge
Sent by BSC to MSC in response to a @BSSMAP LCLS CONNECT CONTROL@, indicating the [possibly updated] LCLS status.
71 4 laforge
72 4 laforge
h3. BSSMAP LCLS NOTIFICATION
73 4 laforge
74 4 laforge
* LCLS BSS Status
75 4 laforge
* LCLS Break Request
76 4 laforge
77 4 laforge
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 4 laforge
79 1 laforge
h2. Spec references
80 1 laforge
81 1 laforge
* 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 1 laforge
* http://www.3gpp.org/DynaReport/WiCr--430001.htm
85 3 laforge
86 3 laforge
h2. Other references
87 3 laforge
88 3 laforge
* OsmoDevCon 2018 video: https://media.ccc.de/v/DVE7UU
89 3 laforge
* OsmoDevCon 2018 slides: https://pretalx.sysmocom.de/media/osmodevcon2018-lcls.pdf
Add picture from clipboard (Maximum size: 48.8 MB)