Feature #4983
openPERFORM LOCATION REQUEST / RESPONSE
0%
Description
Now that osmo-bsc + osmo-smlc support Location_Services, it would be great to also use that from the OsmoMSC side (currently we only test it via TTCN3 and it can be used with third-party MSCs).
- MSC would generate "PERFORM LOCATION REQUEST" to BSC
- MSC then subsequently receives "PERFORM LOCATION RESPONSE" from BSC
The simplest type of interface would be some kind of VTY command to trigger the request, and then print the response either on the VTY or even only in the log. In that first/initial implementation, it should also be sufficient to constrain its use to subscribers with active SCCP connection (no need to specifically create a SCCP connection just for LCS).
An optional, more advanced use case would be to have a programmatic interface (e.g. via CTRL) how external applications could request location requests and get the response.
Updated by laforge about 3 years ago
Note: In 3GPP LCS architecture (See TS 23.271), there's a "Lg" interface between MSC and the GMLC. The Lg interface is MAP based. So if we wanted to go towards that architecture, we'd have to expose the LCS functionality via our GSUP.
The related MAP services are:- MAP-SEND-ROUTING-INFO-FOR-LCS (like SRI-for-SM, ...)
- provided by the HLR
- used by GMLC to inquire which VMSC is serving a subscriber
- MAP-PROVIDE-SUBSCRIBER-LOCATION
- provided by the MSC/SGSN
- used by GMLC to request the location
- MAP-SUBSCRIBER-LOCATION-REPORT
- used by MSC/SGSN to provide location to GMLC for a previous request
