Location Services » History » Version 1
laforge, 03/28/2020 06:56 PM
1 | 1 | laforge | h1. Location Services |
---|---|---|---|
2 | |||
3 | *NOTE: This page describes our current understanding of the 3GPP specification; +none of this is implemented so far in Osmocom!+* |
||
4 | |||
5 | LCS includes a variety of different methods, such as |
||
6 | * Timing Advance |
||
7 | * E-OTD |
||
8 | * GNSS |
||
9 | * U-TDOA |
||
10 | * Multilateration TA |
||
11 | * Multilateration OTD |
||
12 | |||
13 | The most simple and hence most wide-spread approach is _Timing Advance_ |
||
14 | |||
15 | h2. Relevant specs |
||
16 | |||
17 | * 3GPP TS 43.059 "Functional stage 2 description of Location Services (LCS) in GERAN" |
||
18 | * 3GPP TS 48.031 (SMLCPP) |
||
19 | |||
20 | h2. Procedures |
||
21 | |||
22 | See 8.5.3 of TS 43.059 |
||
23 | |||
24 | h3. TA based positioning in CS domain for A interface |
||
25 | |||
26 | See Section 9.3 of 3GPP TS 43.059 |
||
27 | |||
28 | h4. MS in idle state |
||
29 | |||
30 | * MSC sends @BSSAP Perform Location Request@ |
||
31 | * BSC sends @SCCP-CR(BSSAP-LE Perform Location Request)@ to SMLC |
||
32 | * SMLC asks BSC to determine TA of MS via @SCCP-DT1(BSSMAP-LE Connection Oriented Info (TA Request))@ |
||
33 | * BSC sends PAGING REQUEST via BTS to MS |
||
34 | * MS sends PAGING RESPONSE via BTS to BSC; BTS adds timing offset information |
||
35 | * BSC reports CellID + TA value to SMLC @BSSMAP-LE Connection Oriented Info (TA Response)@ |
||
36 | * SMLC returns @BSSAP-LE Perform Location Response@ to BSC |
||
37 | * BSC returns result to MSC in @BSSAP Perform Location Response@ |
||
38 | |||
39 | |||
40 | h4. MS in dedicated state |
||
41 | |||
42 | * MSC sends @BSSAP Perforl Location Request@ |
||
43 | * BSC sends @SCCP-CR(BSSAP-LE Perform Location Request)@ |
||
44 | * SMLC asks BSC to determine TA of MS via @SCCP-DT1(BSSMAP-LE Connection Oriented Info (TA Request))@ |
||
45 | * BSC checks current TA (as per measurement processing) for lchan of MS |
||
46 | * BSC reports CellID + TA value to SMLC @BSSMAP-LE Connection Oriented Info (TA Response)@ |
||
47 | * SMLC returns @BSSAP-LE Perform Location Response@ to BSC |
||
48 | * BSC returns result to MSC in @BSSAP Perform Location Response@ |
||
49 | |||
50 | |||
51 | h2. Functionality in BSC |
||
52 | |||
53 | * BSC receives requests for LCS information from CN via A interface |
||
54 | * BSC passes those requests to the SMLC via Lb interface |
||
55 | ** BSSAP-LE protocol stack (on top of SCCP) implementatioon |
||
56 | |||
57 | h2. Functionality in SMLC |
||
58 | |||
59 | Protocol stack looks like this: |
||
60 | * BSSLAP (TS 48.071) |
||
61 | * BSSAP-LE |
||
62 | |||
63 | h3. Communication with MS |
||
64 | |||
65 | Protocol stack looks like this: |
||
66 | * RRLP (TS 48.031) |
||
67 | * BSSLAP (TS 48.071) |
||
68 | * BSSAP-LE (TS 49.031) |
||
69 | |||
70 | h3. Communication with peer SMLC |
||
71 | |||
72 | * SMLCPP (TS 48.031) |
||
73 | * BSSAP-LE (TS 49.031) |
||
74 | |||
75 | h3. Message Segmentation |
||
76 | |||
77 | LCS messages can be segmented either |
||
78 | * at the SMLCPP layer |
||
79 | * At RR layer (TS 44.018) and BSAP-LE Layer (TS 4.031) for segmentation of RRLP (TS 44.031) for legacy MS (<= Release 4) |
||
80 | |||
81 | |||
82 | h2. Functionality in SMLC |
||
83 | |||
84 | * |