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