Calculating a subscriber's location coordinates:
- approximated, to an accuracy of the base station coordinates, taking its directivity pattern and coverage zones into account;
- improved, based on network radio metering data obtained from a SIM Toolkit applet from the mobile terminal.
Providing subscriber coordinates to service provider and roaming partner applications:
- caching requested data and storing them for the current period (Subscriber coordinate cache);
- supporting a list of subscribers who are prohibited from determining coordinates (MSISDN Blacklist);
- limiting privileges and service throughput for each service provider;
- servicing requests from partner operators to determine the coordinates of a roamer (an outside subscriber within the local network service zone), to an accuracy of the coordinates of the master database;
- detailed record-keeping, collection of statistics, and reporting for each application.
Data exchange with roaming partner LBS platforms to obtain the coordinates of subscribers in roaming mode.
Database support:
- a base station database, updated per a specified schedule;
- a database of providers (external applications) and their privileges;
- a database of roaming partners.
Administrating platform operation via a Web interface:
- modifying parameters without rebooting the platform;
- monitoring platform module performance;
- maintaining service provider accounting records;
- maintaining lists of subscribers who are prohibited from determining coordinates (MSISDN Blacklist);
Providing data for corporate user CRM systems (m.LBSCA):
- administration via a Web interface;
- a uniform, secure interface for connecting to client systems.
Monitoring platform functionality using the m.MAP process application:
- display of base stations, their characteristics, and coverage zones on geographic maps (built-in or provided by Google Maps);
- determining the location and tracking the mobile terminal;
- built-in interface performance tests;
Security and access control:
- maintaining access logs for each interface;
- maintaining an access list that manages content provider access privileges over settable parameters (MSISDN, IP provider);
- using the HTTPS secure protocol for all external connections.
Monitoring platform status (m.Check):
- monitoring platform module performance on the software level;
- tracking the amount of through traffic on all network interface platforms;
- remote monitoring of platform component status via a WEB/WAP interface;
- remote restarting of platform components;
- an SNMP/SNMP-trap interface for notification of external SNMP managers.
Collecting, storing, and processing statistics:
- logs maintained by each platform module, configurable levels of detail and a list of recorded events for each log;
- a centralized storage and processing system can be used for platform component statistics (m.Stat).
|
 |
