Definition
LBS (Location Based Service) is a service based on location, acquiring position through base station positioning or GNSS, used for auxiliary positioning in indoor/weak GNSS scenarios, such as shared bicycles, children's watches, etc.
Positioning Technology
LBS positioning methods include: cellular base station positioning (Cell-ID, ECID, OTDOA), which estimates the terminal location using base station positions and signal characteristics, with an accuracy of about 50–500 meters; Wi-Fi positioning, based on hotspot fingerprints or triangulation; Bluetooth Beacon positioning, used for precise indoor positioning. Compared with GNSS, LBS has lower accuracy but lower power consumption, is usable indoors, requires no additional hardware, and is suitable for scenarios where high accuracy is not required.
Module Capabilities
4G/5G modules usually support obtaining base station positioning information via AT commands (such as MCC, MNC, LAC, Cell ID), and the terminal or platform can use this to call the operator's or third-party location API to obtain latitude and longitude. Some modules integrate GNSS and can automatically switch between GNSS and LBS: preferring GNSS outdoors, and falling back to LBS indoors or under weak signals to ensure positioning availability.
Use Cases
Shared bikes use LBS to provide approximate locations for illegal parking judgment and finding bikes in no-parking zones, underground garages, and other areas where GNSS is unavailable; children's watches and elderly wristbands rely on LBS in indoor scenarios; logistics tracking uses LBS for assistance in warehouses, tunnels, and other scenarios. LBS combined with geofencing can determine entry and exit based on approximate locations, meeting the needs of some businesses where high accuracy is not required.
Engineering Practice Supplement
Cross-team collaboration for "LBS": hardware provides impedance and power budget, RF provides spurious and sensitivity margin, embedded clearly defines thread model and memory lifetime, and cloud defines SLA and throttling. For scenarios like NB-IoT, the business model needs to match the wake-up cycle, packet length, and downlink capacity; for automotive and mobile scenarios, session continuity during handover and roaming needs to be considered. At project closure, conduct a "red team" style review: whether weak network, power loss, certificate expiration, clock jumps, and full storage all have defined behaviors.
From a cell identity to coordinates
A location-based service on the cellular side is usually not the module solving latitude and longitude itself. The module reads, by command, the country code, network code, location area or tracking area, and cell identity of the registered cell and of neighbors, and sometimes a signal delay or level. The coordinates come from a cell-location database, run by the operator or a third party, which weights the serving cell plus several neighbors or matches them as a feature. Reporting only one cell identity places the result on a representative point inside that cell’s coverage. In a city that may be a block. In suburbs and on a highway it can be much larger. It does not need satellites in view, so it can still give a coarse position indoors and under blockage, but accuracy is set by base-station density and by how current the database is.
It is suitable as the primary fix only when the service can accept cell-level error: finding a rough area, counting how devices are spread, or keeping “a position exists” when satellites are unavailable. Lane level or doorway level can use cell positioning only as a fallback, and the record must name the source and the accuracy class. Before use, confirm that the location database at the roaming site covers that network code. Otherwise a foreign cell solves to an empty coordinate or the wrong country.
Position jumps after a neighbor cache expires
The module cached the previous neighbor list. The person is already in an underground garage, the report is still the old cell by the road, and the platform shows a fresh update. The location database has not followed a site move, the same cell identity still solves to the old site, and a whole batch of devices shifts on the map. Feeding a cell fix straight into a very small geofence produces a stream of enter and exit events on every neighbor reselection. A multi-SIM device reports the cell of SIM A while the session is bound to SIM B, and the coordinate does not match the session. If the interface is billed per call, requesting a high-accuracy location API on every report costs more and takes longer than the service needs, and calling it again does not turn the result into meters.
Report fields should distinguish a satellite point, a cell point, and the last valid point. Do not erase the source when the record is stored. Indoors, use anchors from indoor positioning (BLE/Wi-Fi) instead of drawing the cell radius smaller and smaller. When satellites are unavailable but a faster recovery is still wanted, assistance data goes through A-GNSS. That is another path. A cell coordinate is not an ephemeris.
When calling the location service, send the serving cell, neighbor levels, and a timestamp together. One cell identity alone can land only on a representative point of the coverage. Keep the accuracy radius and the coordinate system in the result, and let the display decide how to draw it. Do not store it as a point with no error. If the roaming location database has no site for that network, fail explicitly instead of returning the previous domestic coordinate. When the interface is priced per call, choose a cell-level or a finer solution according to the service. Repeating the request does not turn base-station geometry into lane level. When a satellite fix is also available, write which one is in use. At the switch, do not average the two into a point that is neither on the road nor in the cell.
After a site move, the same cell identity may mean a new site. Until the location database is updated, allow an empty result rather than keeping the old coordinate. When the neighbor list is stale, record the measurement time. A roadside cell still reported from a garage should not refresh “just online” on the map. A multi-SIM device should say which SIM the position came from. A coarse position is only for a service that can accept cell scale. A fine fence should not consume this coordinate directly.