Open APIs

Expand all | Collapse all

TMF673 Geographic Address Management API

  • 1.  TMF673 Geographic Address Management API

    TM Forum Member
    Posted 15 days ago
    Hi,

    We have a requirement to expose APIs with below purpose
    1. The API should return local area codes corresponding to given address.
    2. The API should validate whether the given number actually belongs to given address.
    I believe, the "TMF673 Geographic Address Management API" is not supporting above operations as is. How could we expose these functionalities  by adhering to Open API guidelines?

    Thank you.

    Best Regards,

    ------------------------------
    Kalpana HV
    Colt Technology Services
    ------------------------------


  • 2.  RE: TMF673 Geographic Address Management API

    TM Forum Member
    Posted 14 days ago
    @Jonathan Goldberg, could you please let me know your inputs.

    Best Regards,​

    ------------------------------
    Kalpana HV
    Colt Technology Services
    ------------------------------



  • 3.  RE: TMF673 Geographic Address Management API

    TM Forum Member
    Posted 12 days ago
    Hi Kalpana

    This is a great question and not easy to answer.

    First we have to manage the perimeter of a local area code - Here probably the geographic location API will be helpful --> you can define a geographical surface/volume based on coordinates.

    Then we have to associate this location with an area code as an 'entity' - 2 ideas but probably other could emerge:  first one is to manage the local area as a specific geographic site and associate it with the geographic location defined above - second one is manage a local area as a (logical) resource and associate the geographic location to this one.

    Then in order to check if an addres is within a local area we need to check the relationship between 2 geo location: the one corresponding to the address and the other for the local area. They was a resource on the previous version of the Geographic Location API (v1) doing this operation:RetrieveLocationRelation --> you can provide 2 geographic location as input and get as a result an intersection (if any). I do know why this resource has been dropped from latest version - I add @Stephen Harrop who leading this API.

    Hope it helps

    Ludovic







    ------------------------------
    Ludovic Robert
    Orange
    My answer are my own & don't represent necessarily my company or the TMF
    ------------------------------



  • 4.  RE: TMF673 Geographic Address Management API

    TM Forum Member
    Posted 11 days ago
    Thank you @Ludovic Robert.  I was able to get your views on first question and that helps. The second question is to check whether the given telephone number belongs to given address. I should have been more specific....... I was thinking numbers to be treated as logical resources and Resource model of  "Resource Inventory Management API - TMF 639" to be extended to have address in "Resource Characteristic" name-value pairs...... Awaiting your and community's thoughts on the same. Best regards,

    ------------------------------
    Kalpana HV
    Colt Technology Services
    ------------------------------


  • 5.  RE: TMF673 Geographic Address Management API

    TM Forum Member
    Posted 9 days ago
    Hi Kalpana
    This is quite complex, since the tie between geographic location and telephone number is looser than perhaps it was 20 years ago (what with VoIP, number portability, etc.).
    In the resource inventory (TMF639) you have a reference to Place, which could perhaps be used for TNs that are in service. But more likely you would want to have this functionality in the Resource Pool TMF685, perhaps @Kiyotaka Mizuno has a view on this.
    Hope it helps.​

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------