Curious how others here are handling API integrations between MVNO systems and the MNO/MVNE layer.
In our setup, APIs are turning into the real backbone — everything from provisioning and SIM management to billing updates and usage tracking. When they work smoothly, life’s easy. When they don’t, every little mismatch causes hours of chasing data.
Wondering what’s working best for you — do you build custom integrations or rely on standard interfaces from the MVNE side?
1 Like
So the for online charging there is no difference in MVNO or MNO .I have seen MVNOs comes up with there own OCS but that is way too expensive and way too much work for the concept of MVNO so most common way is to use the same OCS as your MNO and give them you tariff plans.But for the offline charging or CDR generation,(By ther way CDR is used for so many applications not only for charging).There is a difference.You will have a totally seperate down stream for each MVNO not the retail rated CDR down stream.Usually these whole sale CDRs are written and transfered as files such as Xml or Jason not like a events in BRM down stream.thats the key difference between those two streams.Provisioning subscribers etc is a seperate layer which is usually called CDIL and usually not a part of BSS(Billing Sub system) but like you have mentioned we can integrate them all in one unit and nothing there to suggest that cannot be done.
1 Like