
See "Mobile data: The only way is uplink" - here.
I am not sure I follow the logic, as we need to know first whether people are generally use mobile data services to upload (or do it more from their home fixed connection), and if the ratio of download:upload is less than 2:1, meaning an average of less than 2 views to each video byte uploaded. Note that other applications, totaling to 40% of the capacity (according to Bytemobile itself - here), are also generating primarily download traffic.
Back to the article - "You can't double your capacity by tossing raw bandwidth at it .. For a large operator with a subscriber base of 100 million it would cost $4 billion to add 40% capacity to the network through adding bandwidth alone, Alternatively, the same operator could spend $2 billion to add 20% capacity then put optimisation on top of that, which would leave it with a total capacity increase of 60%. The cost of optimisation would be up to $10 million"
It is not clear how Bytemobile type optimization can help carriers on the uplink, as optimization is placed on the packet core and would not help uploads. I guess Ronny means that with optimization, carriers will be able to set the capacity to a different ratio. Sounds complicated.
You state that optimization in the core does not help uploads. This is an incorrect statement. Server-only optimization can in fact reduce upload bandwidth requirements. A simple example is by causing a reduced number of http requests, total upload traffic is also reduced. There are other examples.
ReplyDeletein the case of mobile users that become broadcasters optimization in the core alone will be very limited
ReplyDeleteByte probably has a client solution in mind or in the case of LTE which is all IP: some software solution that will reside in the eNodeB area.
Not as simple as core only solution but can be done if the motivation is strong enough...