Open APIs

Hi ,

Could you please advice on how SIM card No  has to be mapped in the TMF 622 API for Acquisiton of a Mobile?
Is it a productCharacteristic or  realizingResource  ?

Thanks

Maneksh

Hi ,

Could you please advice on how SIM card No  has to be mapped in the TMF 622 API for Acquisiton of a Mobile?
Is it a productCharacteristic or  realizingResource  ?

Thanks

Maneksh

Hi ,

Could you please advice on how SIM card No  has to be mapped in the TMF 622 API for Acquisiton of a Mobile?
Is it a productCharacteristic or  realizingResource  ?

Thanks

Maneksh

Hello,

After taken a look at use case approach description, I have some concern. The diagram for "Service and resource catalog view" displays relation "requires" between "[Network Service CFS] Mobile Line" and "[Compound Resource] SIM Card". It means, that within service ordering or inventory there shall be included resource supporting the CFS.

It is real situation, and also practical and obvious approach to it, as SIM card information is usually to be distributed over multiple RFSs. However SID model, and multiple Open API specifications displays disclaimers like "Note: only Service of type RFS can be associated with Resources".

I can add a note, that SIM card is also to be delivered somehow to the Customer. There are also some other examples of resources, like devices, that are "customer facing", and shall be shipped to the Customer, are subject for rental, and require configuration management that is to provide Customer side support for accessing or fulfilling multiple services. So it is to be shared by multiple product specifications, as resources, and among multiple CFSs /RFSs.

Doesn't it seems, that there is some inconsistency, and possible gap in the model?

Best Regards,

Grzegorz

Hi ,

Could you please advice on how SIM card No  has to be mapped in the TMF 622 API for Acquisiton of a Mobile?
Is it a productCharacteristic or  realizingResource  ?

Thanks

Maneksh

Thanks for the feedback Grzegorz

I've passed it on to the authors of the use case and I hope that they will relate to your concern.

Hello,

After taken a look at use case approach description, I have some concern. The diagram for "Service and resource catalog view" displays relation "requires" between "[Network Service CFS] Mobile Line" and "[Compound Resource] SIM Card". It means, that within service ordering or inventory there shall be included resource supporting the CFS.

It is real situation, and also practical and obvious approach to it, as SIM card information is usually to be distributed over multiple RFSs. However SID model, and multiple Open API specifications displays disclaimers like "Note: only Service of type RFS can be associated with Resources".

I can add a note, that SIM card is also to be delivered somehow to the Customer. There are also some other examples of resources, like devices, that are "customer facing", and shall be shipped to the Customer, are subject for rental, and require configuration management that is to provide Customer side support for accessing or fulfilling multiple services. So it is to be shared by multiple product specifications, as resources, and among multiple CFSs /RFSs.

Doesn't it seems, that there is some inconsistency, and possible gap in the model?

Best Regards,

Grzegorz

Hi ,

Could you please advice on how SIM card No  has to be mapped in the TMF 622 API for Acquisiton of a Mobile?
Is it a productCharacteristic or  realizingResource  ?

Thanks

Maneksh

Thanks for the feedback Grzegorz

I've passed it on to the authors of the use case and I hope that they will relate to your concern.

Hello,

After taken a look at use case approach description, I have some concern. The diagram for "Service and resource catalog view" displays relation "requires" between "[Network Service CFS] Mobile Line" and "[Compound Resource] SIM Card". It means, that within service ordering or inventory there shall be included resource supporting the CFS.

It is real situation, and also practical and obvious approach to it, as SIM card information is usually to be distributed over multiple RFSs. However SID model, and multiple Open API specifications displays disclaimers like "Note: only Service of type RFS can be associated with Resources".

I can add a note, that SIM card is also to be delivered somehow to the Customer. There are also some other examples of resources, like devices, that are "customer facing", and shall be shipped to the Customer, are subject for rental, and require configuration management that is to provide Customer side support for accessing or fulfilling multiple services. So it is to be shared by multiple product specifications, as resources, and among multiple CFSs /RFSs.

Doesn't it seems, that there is some inconsistency, and possible gap in the model?

Best Regards,

Grzegorz

Hi ,

Could you please advice on how SIM card No  has to be mapped in the TMF 622 API for Acquisiton of a Mobile?
Is it a productCharacteristic or  realizingResource  ?

Thanks

Maneksh