KT: “Someone should optimise the mobile traffic”

Minhyuk Choi, KT

Minhyuk Choi, KT

Minhyuk Choi, Product Manager of CDN Business Management at Korean telco KT, on recent CDN initiatives, the role of caches and content optimisation, and dealing with mobile traffic that has not yet been optimised for delivery.

Minhyuk will be speaking at the CDN Asia 2013 event taking place in Singapore on 29-30 January. For more information and to register, please visit

Hi Minhyuk, first off can you tell us a little more about KT’s recent work on CDN services in the mobile environment?

Over the past six months we’ve been doing a Proof of Concept and analysing the performance enhancements delivered by caching in the backhaul and QoS handling on the test and real networks.

We will get real data for the value proposition for content providers, and get the optimised QoS handling set point for performance enhancement without results being affected by other communications providers who are not using our service.

How close to its limits is KT’s mobile network being pushed by rising data consumption patterns?

I’m not sure, but people say the mobile network will be full by the end of this year. Before then, there will be frequency allocation and other solutions to mitigate this possibility.

What role do caches and content optimisation play here?

Caches reduces the routing distance and transit traffic, and optimisation reduces the traffic volume of the radio access network and improves efficiency.

How does KT deal with mobile traffic that has not been optimised?

The company is considering various methods, including standardisation of traffic entering into mobile network – I think that someone should optimise the mobile traffic, whether that is the CDN provider or mobile network operator itself.

In the best case scenario, if we can charge for traffic into the mobile network, the communications provider will optimise it for themselves or use a CDN service supporting optimisation.

In the worst case, if nobody optimises the traffic, the operator should limit the bandwidth per connection.

Tags: ,

We welcome reader discussion and request that you please comment using an authentic name. Comments will appear on the live site as soon as they are approved by the moderator (within 24 hours). Spam, promotional and derogatory comments will not be approved


Post a comment

  • Very interesting discussion; I fully agree with the issue ( ie, to much mobile traffic, too expensive to carry), and with the benefit of caching ( ie, carry once and play many).
    However, if you cache at level of the backhaul ( BTS I suppose ?) youmiss a big optimization area = cell, spectrum.
    The aletrantive concept we promote is the onne of Broadcast off-load; ie for one content that is popular ( ie, the one sthat would be candidate for caching in the KT apoproach), you will do better than cache it at the backhaul; you will broadcast ( yes, the good old TV broadcasting !) and you will thus remove with one broadcast “cell” ( typically 50 km range) remove the need for 100s mobile cells to each carry 10s times the content ; our model suggest the cost / delivered GB will be reducved by a factor 30x to 50x.
    I would be happy to share further thoughts and info on the topic.
    Vincent GRIVET at TDF ( FRance)

    VincentG75 on KT: “Someone should optimise the mobile traffic”

Post your comment

Facebook, Instagram and Sky case study: Game of Thrones

BT at IBC: 'unlocking the power of fibre IPTV'

IP&TV News tries out 4G Broadcast at the FA Cup Final

Thomas Riedl: “Google TV has evolved into Android TV”

Tesco and blinkbox: what went wrong?

Reed Hastings and 2030: is he right?