The notion that mobile generations are inflexible is reasonable enough. But, in principle, the driving force is the same underlying connectivity standards in general: over time, silicon gets better; compression gets better; transceivers get better. So we have Ethernet at 10 Mbps, then 100 Mbps, then a gigabit, then multi-gigabit and 10 Gbps and 100 Gbps.
But mobile next-generation networks are designed around much more than layer two transport, including application layer services.
Obviously there are more complexities with mobile services in terms of app support that have to be accommodated. Ethernet is just transport (layer two).
The issue perhaps is how extensible the framework can be. As Ethernet has evolved to support higher speeds, it is obvious why many would want the same sort of development for mobile network speeds.
That is an understandable and easy argument for some to make. If layer two transport is the only requirement, an extensible layer two standard makes sense. Mobile operators also operate at the app layer, though. There is no reason that should necessarily interfere with ongoing development of transport layers, with some caveats. Radio technology advances.
So perhaps the issue is whether radio layers can be layered in a way that allows development in a more-graceful way.
Others in the ecosystem might well be happy with transport upgrades on the Ethernet model. Mobile service providers might have other reasons for wanting app layer additions.
No comments:
Post a Comment