Open APIs

Hello Team

Is there any guiding principles / rules to have an ProductCharacteristics in TMF622. When a TMF622 ProductOrder carries productCharacteristics, should the characteristics name should have been defined in TMF620 as prodSpecCharValueUse?. For any reason if a productOrder carries a characteristics that is not defined in TMF620 prodSpecCharValueUse - does this violate any TMF guidelines. Please let me know. Sorry if this is already answered on any posts.

Thanks

Raj

Hi.

From my point of view the catalog is the authoritative source of product specifications, and ensuring that characteristics in orders are catalog‑driven guarantees consistency, validation, and interoperability across systems. By keeping all characteristics tied back to the catalog, we maintain a clear, repeatable workflow and ensure that downstream systems can interpret and act on the order data.

In our case, the Product Order Management system enforces this check, guaranteeing consistency and data integrity.

Hello Team

Is there any guiding principles / rules to have an ProductCharacteristics in TMF622. When a TMF622 ProductOrder carries productCharacteristics, should the characteristics name should have been defined in TMF620 as prodSpecCharValueUse?. For any reason if a productOrder carries a characteristics that is not defined in TMF620 prodSpecCharValueUse - does this violate any TMF guidelines. Please let me know. Sorry if this is already answered on any posts.

Thanks

Raj

Hello Team

Is there any guiding principles / rules to have an ProductCharacteristics in TMF622. When a TMF622 ProductOrder carries productCharacteristics, should the characteristics name should have been defined in TMF620 as prodSpecCharValueUse?. For any reason if a productOrder carries a characteristics that is not defined in TMF620 prodSpecCharValueUse - does this violate any TMF guidelines. Please let me know. Sorry if this is already answered on any posts.

Thanks

Raj

Hi,

A TMF622 ProductOrder API doesn't prescribe how productCharacteristics are used. But in a fully catalog driven environment additional rules obviously apply.

In the TMF620 ProductSpecification the prodSpecCharacteristics define the characteristics understood by the underlying services, resources, etc. e.g. upstreamBandwidth, downstreamBandwidth and color

In the TMF620 ProductOffering might restrict the values used for a subset of these characteristics using the prodSpecCharValueUse. E.g. for the Internet XL, the upstreamBandwidth=500Mbps, downstreamBandwidth=1Gbps and links this to specific ProductOfferingPrices.

In the above setup the use of the characteristic packetSize in the ProductOrder is not allowed (not specified)

The use of the characteristic upstreamBandwidth or downstreamBandwidth is also not allowed (already fixed in the productOffering XL)

The use of the characteristic color is allowed in the productOffer.

The ProductOrder is defined to be flexible, so that it can be used without catalog. However, when a catalog is used properly, it is unlikely that the ProductOrder will contain characteristics.

Best Regards

Hello Team

Is there any guiding principles / rules to have an ProductCharacteristics in TMF622. When a TMF622 ProductOrder carries productCharacteristics, should the characteristics name should have been defined in TMF620 as prodSpecCharValueUse?. For any reason if a productOrder carries a characteristics that is not defined in TMF620 prodSpecCharValueUse - does this violate any TMF guidelines. Please let me know. Sorry if this is already answered on any posts.

Thanks

Raj