Hi Lasse
There is interest in the Resource Portability API (TMF689 or TMF698) but, as of yet, the API design has not been completed.
You can see the design being proposed here... TMF698 Number Portability - Open API Project - TM Forum Confluence
... which, as you have indicated, is a sub-class of Resource Order (TMF652). If you are in a hurry, then you can make your own extensions to TMF652 based on the proposed model.
------------------------------
Dan d'Albuquerque
Entronica Company Limited
------------------------------
Original Message:
Sent: Jan 16, 2025 06:27
From: Lasse Immonen
Subject: Which Open API interface is the best fit for MNP if any? TMF652, TMF641 or something else?
I'm looking for if any of the TM Forum Open API production or pre-production API contracts would be a good fit for modelling the MNP process – port in orders and port out orders and their usual surroundings. I'm not seeing any of the existing ones as a direct fit for the purpose but what's your view, folks?
I've been considering then TMF652 Resource Order Management and if I would create a layer on top of it focusing to the intricacies of port in and port out orders via utilising the polymorphism approach. That's perhaps the best candidate. But the downside there is that the beef would go to the custom parts and documenting that for smooth client use could actually be more expensive than rolling out a new API contract dedicated for MNP. A dedicated one would be simpler than TMF652 vanilla + MNP parts on top of it combination, I think.
Does anyone have experience with using any of the existing TM Forum Open API contracts for this purpose? If yes, how did it pan out? Did you like the experience?
How about does anyone have insights to TM Forum future plans on this area? Is there a dedicated MNP API in the works or something like that?
------------------------------
Lasse Immonen
Principal Architect
Qvantel Oy
------------------------------