Open APIs

 View Only

  • 1.  GeoLocation API

    TM Forum Member
    Posted May 31, 2023 15:09

    Hello,

    I am wondering if there are plans to work on GeoLocation APIs to enable Location Based services.
    First step could be an API to check if the location of a given mobile device is correct.
    It can then be extended to retrieve the location of a given device, based on its IMSI, IMEI or MSISDN.

     Would anyone be interested in standardizing such API?

    Best Regards,

    Sébastien



    ------------------------------
    sebastien synold
    Intersec
    ------------------------------


  • 2.  RE: GeoLocation API

    TM Forum Member
    Posted Jun 01, 2023 03:18
    Edited by Matthieu Hattab Jun 01, 2023 07:57

    seach "geolocation" in TM Forum wiki, there are some results about a draft API but the documents are quite old, and TMF675 Geographic Location Management is still in beta.



    ------------------------------
    Kind regards,

    Matthieu Hattab
    Lyse Platform
    ------------------------------

    Original Message


  • 3.  RE: GeoLocation API

    TM Forum Member
    Posted Jun 02, 2023 06:04

    There is a device  management  API that could be looked at which uses Geolocation as part of what can be managed and monitored .
    See TMF908B IoT Agent and Device Component Suite Conformance Profile v4.0.0 | TM Forum



    ------------------------------
    Dave Milham
    TM Forum, Chief Architect
    ------------------------------

    Original Message


  • 4.  RE: GeoLocation API

    Posted Jun 05, 2023 05:47

    Hello everyone,

    I have a followup clarification on this. How does the TMForum TMF908B compare with the CAMARA northbound API for location(below link). Can you pls provide an example of how the TMF908B is integrated in a commercial software/product offering?  Is the TMF908B supposedly be implemented by the Telco connectivity management platforms (CMP platform). Can help to share some thoughts around this

    https://github.com/camaraproject/DeviceLocation

    thank you

    th



    ------------------------------
    Vanitha Ramaswami
    StarHub
    ------------------------------

    Original Message


  • 5.  RE: GeoLocation API

    TM Forum Member
    Posted Jun 05, 2023 06:18

    HI Vanitha,

    For now, CAMARA API for geolocation is mainly intended to check the location of a device. This is very useful for fraud detection for instance.

    We can have a quick call to ellaborate on the use cases of location APIs if you wish.

    Regards,



    ------------------------------
    sebastien synold
    Intersec
    ------------------------------

    Original Message


  • 6.  RE: GeoLocation API

    TM Forum Member
    Posted Jun 05, 2023 06:13
    Edited by Sebastien Synold Jun 05, 2023 06:14

    Hi Dave,

    Thanks for your response.
    TMF908B API gives the possbility to retrieve a preconfigured Location for a device. It does not seem to be made for retrieving the location of the device in case of mobility (with CellID identification for instance).

    Is it right?



    ------------------------------
    sebastien synold
    Intersec
    ------------------------------

    Original Message


  • 7.  RE: GeoLocation API

    TM Forum Member
    Posted Jun 05, 2023 10:18
    Edited by Dave Milham Jun 06, 2023 04:37

    It is true that this is based on Geo location as defined in the TM Forum Information framework . But that does not imply that the information is static and cannot change as a device moves. (One would have to configure API notifications for Location state change). To add in a Cell ID which is what I think you might be locking for, you can create  polymorphic extension to the APIs as described in 

    TMF630 REST API Design Guidelines 4.2.0 | TM Forum  Part 2 and 3

    New work on a domain context specialisation approach is being worked on and those guidelines are on Github  but not sure if they are public. 



    ------------------------------
    Dave Milham
    TM Forum, Chief Architect
    ------------------------------

    Original Message


  • 8.  RE: GeoLocation API

    Posted Jun 06, 2023 03:58

    In a practical use cases these API's need to be asynchronous (Pub/sub) notifications, only then the data is easier for the IoT applications to consume. The IoT data management is quite complex (as it might involve different transport and application protocols). So, I would think the TMForum data mgmt. REST APIs might be harder to be adopted in commercial products, however segregating the attributes that come directly from the telecom network (e.g. location) could be exposed via a simple standard interface for the IOT platform providers.

    Are there any references to products/platforms that are leveraging the TMForum IoT APi's ? If so, can help to share ? thanks



    ------------------------------
    Vanitha Ramaswami
    StarHub
    ------------------------------

    Original Message


  • 9.  RE: GeoLocation API

    TM Forum Member
    Posted Jun 07, 2023 11:06
    Edited by Ilyas Premji Jun 08, 2023 04:38

    Hello Sebastien,

    I worked on one of such requirements to identify whether a device location is serviceable or not. If it is serviceable, then which service provider will service it? One of the major challenges in such standardization is how we get the geo fencing data of each of the service providers? There may be also clashes in such geo fences of two or more service providers. There is one more challenge, if we are creating the geo fencing data based on the geo co-ordinates details of any service provider then it will just mention the radius it is going to cover from the central location. This area coverage based on serviceable radius may have the terrain constraints (water/mountains/tunnels, etc). If the geo fencing data of every service provider is available then it is possible to create standard APIs. Any GPS enabled device will be able to generate its own co-ordinates and using these co-ordinates we can find the nearest service provider.



    ------------------------------
    Sudeep Banerjee
    Tech Mahindra Limited
    ------------------------------

    Original Message