Open APIs

Hi Everyone,

We are currently working on several scenarios, including Port IN, Port Out, Port Out Reversal, CHOWN, and Move.

We are trying to determine how to indicate in the TMF622 Product Order that the order is created to support these scenarios.

For example, in a Port IN scenario, we need to execute different business logics compared to a normal Add scenario. The Product Order Item Actions have enum values of {add, modify, delete, noChange}. To illustrate, when a customer requests to port their number into our network (Port IN), we need to ensure that the Product Order reflects this specific scenario. This might involve additional validation steps, coordination with the previous service provider, and specific provisioning tasks that are not required for a standard Add scenario.

We are seeking guidance on which fields in the TMF622 Product Order could be used to indicate the specific scenario (e.g., Port IN) so that the order-related entities can execute the appropriate steps.

Since this is a common problem across Telcos, we are looking forward to guidance from the TMF community.

------------------------------
Vishnujith Harikumar
Telstra Corporation
------------------------------

Hi Vishnujith,

I have had similar issues with customer I supported. I would highlight here a set of means at your disposal to express more complex scenarios than simple add, modify delete at single order item level:

• you can use the OrderItemRelationship.relationshiptype to express dependencies between products at OrderItem level such as migrateFrom for a Porting or a move in addition to the add resp. delete at order item level
• you can extend the OrderItem.action enumeration with additional actions such as suspend, portOut, ...
• if this is not enough, you can use the Order.category to qualify the order type. This can be usefull for the Order Mgt system not to have to guess, resp. to derive from a potentially complex order structure which scenario is expected resp. which validations to run

Hope this helps, Iwan

------------------------------
Iwan Gramatikoff
Edelweiss Service Consulting SàRL
------------------------------

Original Message:
Sent: Mar 19, 2025 03:18
From: Vishnujith Harikumar
Subject: How to use TMF Product Order for scenarios like Port In/CHOWN/Move etc

Hi Everyone,

We are currently working on several scenarios, including Port IN, Port Out, Port Out Reversal, CHOWN, and Move.

We are trying to determine how to indicate in the TMF622 Product Order that the order is created to support these scenarios.

For example, in a Port IN scenario, we need to execute different business logics compared to a normal Add scenario. The Product Order Item Actions have enum values of {add, modify, delete, noChange}. To illustrate, when a customer requests to port their number into our network (Port IN), we need to ensure that the Product Order reflects this specific scenario. This might involve additional validation steps, coordination with the previous service provider, and specific provisioning tasks that are not required for a standard Add scenario.

We are seeking guidance on which fields in the TMF622 Product Order could be used to indicate the specific scenario (e.g., Port IN) so that the order-related entities can execute the appropriate steps.

Since this is a common problem across Telcos, we are looking forward to guidance from the TMF community.

------------------------------
Vishnujith Harikumar
Telstra Corporation
------------------------------

hi, 

we will start doing this with our new systems but I don't see much differences between port-in or new number on the specific topic if TM622.

we plan to reference the (port-in) phone number, porting date, some other fields in the order line items as a product characteristic value (same modelling as the one described in IG1228, there is a product model example for mobile). from a scenario perspective, it's the same as a "add" use case.

From an order capture perspective, I don't see what else you would need in TMF622.

your may have business rules If your order contains a product characteristic value related to port-in.

You can search the TMF wiki, there is quite a few articles on porting, including a now-abandoned portability API (tmf698) but the analysis was done and documented:

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

Matthieu Hattab
Lyse Tele AS
------------------------------

Original Message:
Sent: Mar 19, 2025 03:18
From: Vishnujith Harikumar
Subject: How to use TMF Product Order for scenarios like Port In/CHOWN/Move etc

Hi Everyone,

We are currently working on several scenarios, including Port IN, Port Out, Port Out Reversal, CHOWN, and Move.

We are trying to determine how to indicate in the TMF622 Product Order that the order is created to support these scenarios.

For example, in a Port IN scenario, we need to execute different business logics compared to a normal Add scenario. The Product Order Item Actions have enum values of {add, modify, delete, noChange}. To illustrate, when a customer requests to port their number into our network (Port IN), we need to ensure that the Product Order reflects this specific scenario. This might involve additional validation steps, coordination with the previous service provider, and specific provisioning tasks that are not required for a standard Add scenario.

We are seeking guidance on which fields in the TMF622 Product Order could be used to indicate the specific scenario (e.g., Port IN) so that the order-related entities can execute the appropriate steps.

Since this is a common problem across Telcos, we are looking forward to guidance from the TMF community.

------------------------------
Vishnujith Harikumar
Telstra Corporation
------------------------------