Open APIs

 View Only
  • 1.  Use of 639 and/or 685 for mobile number management

    TM Forum Member
    Posted Jun 20, 2022 11:33
    Hi All,

    does anybody know of any practical examples/implementations where these APIs have been seriously evaluated for use with mobile number management including pairing/unpairing of MSISDN and SIM/IMSI as well as reservations, change MSISDN, change SIM, management of number pools, vanity numbers and the other mobile use cases?

    Thanks

    Tony

    ------------------------------
    Anthony Melvin
    Amdocs Management Limited
    ------------------------------


  • 2.  RE: Use of 639 and/or 685 for mobile number management

    TM Forum Member
    Posted Jun 21, 2022 03:30
    Hi Anthony,

    In Use Case 008 of IG1228 (section 6.2), we considered those APIs in the context of mobile number management. I am not sure it qualifies as "serious evaluations" as we have not implemented the use case in actual software.

    Best regards,

    ------------------------------
    Roland Leners
    alvatross by SATEC
    ------------------------------



  • 3.  RE: Use of 639 and/or 685 for mobile number management

    TM Forum Member
    Posted Jun 21, 2022 05:09
    Thanks Ronald
    Anthony - the use case is available here
    It mainly concerns the provisioning of services and resources, I think Anthony is more interested in the resource management aspects during order capture. But the current use cases for order capture deal with fiber, not with mobile or fixed voice. So there is still work to do there.

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



  • 4.  RE: Use of 639 and/or 685 for mobile number management

    Posted Jun 21, 2022 08:30
    Hi Jonathan,
    Interesting topic!
    There will be 3 aspects to consider when this is eventually detailed as an API spec.
    1. Reservation of the resource will happen during Order Capture as you mentioned. If we treat the MSISN and IMSI as RS (and they should be treated as RS -Logical), the Order Capture APIs will have to be extended beyond the PS into the RS.
    2. Do we do the pairing during Order Capture? If yes, what if the Order is not submitted? fire an Unpair? Hence suggest that pairing be part of Orchestration
    3. Lifecycle management of the resources. If reservation is triggered as part of No.1, and the Order is submitted, then the MSISDN - IMSI pairing and the Resource allocation (reservation done was only a soft allocation) need to be done as part of Order Orchestration during the Fulfillment (before the orchestration triggers the 641).

    So, while a separate API for MSISDN, IMSI management during the order journey is helpful, request to consider the fitment and calling of this API within the e2e process.
    Regards,
    Jag

    ------------------------------
    Jag Baddukonda
    CSG
    ------------------------------



  • 5.  RE: Use of 639 and/or 685 for mobile number management

    TM Forum Member
    Posted Jun 21, 2022 16:14
    TMF685 is in production use for number management at several service providers.
    This includes:
    • creation of geographic number pools
    • creation of pools with vanity numbers
    • adding/deleting numbers to these pools
    • availabilityCheck for showing available numbers to customers in engagement portals
    • reservation of selected numbers
    It is even possible to map TMF685 concepts to a number portability.
    In that case a AvailabilityCheck and Reservations can be linked to a "portability pool" for communication with portability databases.

    During the ordering process a ResourceOrder TMF652 can be used to move the reserved number from the pool to the resource inventory using TMF638.

    TMF639 can be used to
    • create composite resources (with number resource & SIM card resource)
    The whole process works smoothly if you hide the process behind a product that realises the resource (NumberProductSpecification).

    I hope this helps.

    ------------------------------
    Koen Peeters
    OryxGateway
    ------------------------------



  • 6.  RE: Use of 639 and/or 685 for mobile number management

    Posted Jun 21, 2022 17:45
    Hi Kooen,
    Agree that 638, 639 can be extended ( conceptually)
    However both are dependant on CFS - RFS mapping and IMSI and MISDN are candidates for RS and not RFS.
    Hence we may need to analyze this deeper.
    Regards
    Jag

    Sent from iPhone
    All emails in this message string and any attachments are the confidential information of CSG Systems International, Inc. (CSG), or its affiliates and subsidiaries, and may contain privileged and/or confidential material. If you are not an intended recipient, please delete it immediately and notify the sender; unintended recipients are not authorized to read or otherwise use the information contained herein.