Open APIs

Expand all | Collapse all

TMF Standard for Number Range

  • 1.  TMF Standard for Number Range

    TM Forum Member
    Posted Sep 10, 2020 01:21
    Can anyone please help in identifying which TMF Standard to use for mapping the attributes as per TMF Standards.
    in my scenario, the Resource can be either Single Directory Number or Number Block or Number Range. If I follow TMF639, can anyone suggest how to map Number block/number Range, which has Start Number and End Number.​​

    ------------------------------
    Rajasekhar Kellampalli
    Tata Consultancy Services
    ------------------------------


  • 2.  RE: TMF Standard for Number Range

    TM Forum Member
    Posted Sep 10, 2020 01:45
    Hi Rajasekhar
    To the best of my knowledge, the Open API does not currently have treatments and semantics of semantics of specific resource types, including telephone numbers. Just LogicalResource and PhysicalResource.
    You could model the specific resource types as strongly-typed extensions of LogicalResource, adding attributes and schema definitions for these, as described in the Design Guidelines TMF630.
    Alternatively, you could model dynamically as characteristics, using ResourceSpecification.
    Refer to the introductory paragraph in TMF634 Resource Catalog, that explains these possibilities in more detail, you'll find the link on the early adopters page here.
    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.
    ------------------------------



  • 3.  RE: TMF Standard for Number Range

    TM Forum Member
    Posted Jul 13, 2021 10:59

    This is a really interesting point as we were looking at how to model Telephone Numbers and the only things i could find from TMF were the

    'Information_Framework_SIF_Excel_Formatv21.0' and this https://projects.tmforum.org/wiki/pages/worddav/preview.action?fileName=GB922_Resource_Order_Portability_R17.5.1.docx&pageId=88576606

    "This new entity called ResourceNumber exists not to only manage the specification, but to associate it with portability. The number is a very complex and broad entity, with specific things like format, ranges, area code and other characteristics for the number that vary for each country. Its purpose is to fill the number specification according to Number Portability, but it can be used for number inventory. The association with NumberPortability is to one and many, since a number can have many ports and a port can happen to a specific number. Nevertheless, they are already related through the order, for that reason the relationship they have is derived. Both, ResourceNumber and ResourceNumberSpecification, inherit from existing entities, LogicalResourceSpec (from LogicalResource Specification ABE) and LogicalResource (from LogicalResource ABE)."

    Both of these suggest a subclass of logical resource called 'ResourceNumber' with a strongly typed attribute 'dialedNumber'. Is this not the TMF defined best practice?

    Also we have had some inconsistent naming accross legacy data model implementations and therefore wanted to centre on a common and single way of naming this entity attribute (TelephoneNumber, TerminatingNumber, DirectoryNumber, CLI).

    I took it from this documentation that TMF were setting out that best practice is to call it 'dialedNumber', could anyone help confirm or challenge this understanding?



    ------------------------------
    David Whitfield
    TalkTalk Group
    ------------------------------



  • 4.  RE: TMF Standard for Number Range

    TM Forum Member
    Posted Jul 13, 2021 11:33
    David

    The challenge is that each country/regulatory framework has different rules for number plans. What's good for the UK won't work in North America, for example.
    As a global standards organization, I don't see that TM Forum can allow itself to start getting into this adventure.

    You will see that characteristic specification include the possibility of defining a regular expression. This could be used as part of implementation of TMF634 for example, to limit the format of logical resources of type fixed TN to meet the fixed TN number plan in the country.

    BTW same issue for address formats, and probably other places in the Open API model.

    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.
    ------------------------------



  • 5.  RE: TMF Standard for Number Range

    TM Forum Member
    Posted Jul 13, 2021 15:20
    Hey @Jonathan Goldberg for the swift response. Understood that formatting of the data item (charactistic value) can be managed through the catalog with RegEx.

    Perhaps ive not explained myself well enough, I am really asking does the documentation (https://projects.tmforum.org/wiki/pages/worddav/preview.action?fileName=GB922_Resource_Order_Portability_R17.5.1.docx&pageId=88576606) hold water and its the TMF view that this ResourceNumber derived type of logical resource is the one to use when modeling telephone numbers or this documentation is out of date and invalid?

    I did also want a pointer to whether Telephone number was considered the correct term for a string of digits used to make calls but understand that could be region specific and therefore reading between the lines of your response its the CP's decision as to how they name this data attribute.

    ------------------------------
    David Whitfield
    TalkTalk Group
    ------------------------------



  • 6.  RE: TMF Standard for Number Range

    TM Forum Member
    Posted Jul 14, 2021 03:33
    Hi David
    Unfortunately I'm not familiar with the referenced document, and it might be better to take the matter up with @Cecile Ludwichowski and @Avi Talmor of the Information Framework (SID) team, who appear to have been major contributors to this document.
    Bear in mind also that the document describes the particular case of number portability, and presumably was not intended to be a general discussion of how to model TN resources.​​​

    ------------------------------
    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.
    ------------------------------



  • 7.  RE: TMF Standard for Number Range

    TM Forum Member
    Posted Jul 14, 2021 07:48
    thanks again @Jonathan Goldberg.

    Agreed the focus is on number portability (which is also an interest of ours) but it does suggest use for number inventory "Its purpose is to fill the number specification according to Number Portability, but it can be used for number inventory."

    @Cecile Ludwichowski @Avi Talmor could you help out with some thoughts on the above queries please?​​

    ------------------------------
    David Whitfield
    TalkTalk Group
    ------------------------------