Cable operators becoming MVNO

Wanted to share good article. It's some promotional thing for their product, but it's decent piece of information.

Wanted to share good article. It's some promotional thing for their product, but it's decent piece of information. I cannot say if advertised products are good or bad, but article itself is a decent one. This is where the Telecom walks now.

Cable operators becoming MVNO: a win-win scenario

[...] As a 2014 report from Adobe already showed, more than 50% of browsing on smartphones and 93% of browsing on tablet comes from WiFi.

Even as they expand their offer, cable providers still see usage limited to home or office hours. On their side, mobile operators continue to upgrade their networks to 4G (and future 5G) technology to deliver more high-quality media content; this makes them competitive in terms of service quality but also results in rising infrastructure investment.

In this post we’ll see how cable companies and MNO can start providing data services using a shared infrastructure, with YateHSS/HLR and the YateUCN unified core.
Mobile data offloading can be an opportunity for both operators and cable companies to provide data access to more users without incurring large expenses. Offloading enables operators to reduce the traffic load on their networks and reallocate bandwidth to other users in case of congestion, by assigning part of the traffic to a WiFi network. For cable companies, it becomes possible to serve subscribers in-between existing hotspots, making them rely primarily on the WiFi network, rather than on the cellular one.

This can be done through MVNO agreements between cable operators and one or multiple MNO, so that the cable provider would share the network assets of the operator to provide carrier-class WiFi access.
As MVNO, a cable company will provide its own SIMs, and its customers will register to and receive data traffic from the MNO’s network. Though some MVNO may choose to also operate their own core network, they are usually likely to hold control over billing, subscriber management and policy control functions, in which case they will only deploy an HLR and/or HSS. In fact, reportsx suggest that it is preferable for MVNO who offer triple or quad-play operating to deploy their own HSS/HLR (to which they can integrate policy control and AAA), because they need to provide a ‘consistent treatment of the user’ across terminals and technologies.

[...]
Once the device is known to the core network, YateUCN communicates with the AuC in the YateHSS/HLR using the SS7 or Diameter protocol, depending on the type of services the user has access to. As soon as the SIM is authenticated, the HSS/HLR takes over and manages the SIM and its services. [...]

follow the link to get more - resource.

Source:
Internet