- RSS Channel Showcase 9151508
- RSS Channel Showcase 8549684
- RSS Channel Showcase 9917832
- RSS Channel Showcase 8294251
Articles on this Page
- 09/23/13--05:30: _Push to talk (PTT) ...
- 09/26/13--02:00: _Multi-stream aggreg...
- 09/29/13--14:14: _Telecom API's: The ...
- 10/03/13--09:00: _Case study of SKT d...
- 10/06/13--12:00: _China Mobile: A pee...
- 10/08/13--01:00: _SON in LTE Release-11
- 10/11/13--01:00: _3GPP Rel-12 SON Status
- 10/13/13--12:00: _Handset Antenna Design
- 10/15/13--10:30: _What is Network Fun...
- 10/22/13--04:00: _Korea Telecom ‘Rout...
- 10/27/13--13:00: _TDD-FDD Joint CA
- 10/29/13--07:00: _ANDSF: Evolution an...
- 11/03/13--23:30: _Key challenges with...
- 11/06/13--02:00: _The Relentless Rise...
- 11/10/13--11:30: _SIPTO Evolution
- 11/12/13--10:30: _Mobile Video Offloa...
- 11/16/13--07:00: _Agile IMS for the A...
- 11/21/13--04:00: _SON Periodical table
- 11/23/13--13:00: _Bandwidth is not th...
- 11/27/13--07:00: _ETSI Summit on Futu...
- 09/23/13--05:30: Push to talk (PTT) via eMBMS
- 09/26/13--02:00: Multi-stream aggregation (MSA): Key technology for future networks
- This is generally referred to as Multi-stream aggregation (MSA)
- We will see this much sooner than 5G, probably from LTE-A Rel-13 onwards
- 09/29/13--14:14: Telecom API's: The why and what
- Content formatting: Using APIs, video content from a company’s video library stored in the cloud can be easily optimized in near real-time for users to watch on almost any device and network.
- Communications services: To bring more efficiency and productivity to business operations, businesses can use APIs to automate voice and video calls, integrating speech and video services into applications.
- 10/03/13--09:00: Case study of SKT deployment using the C-RAN architecture
- Maximum re-use of existing fiber infrastructure to reduce the need for new fiber runs which ultimately reduced the time to market and capital costs.
- Ability to quickly add more ONTs to the fiber rings so as to support additional RAN capacity when needed.
- Support of multiple small cells on a single fiber strand. This is critical to reducing costs and having the flexibility to scale.
- Reduction of operating expenses.
- Increased reliability due to the use of fiber rings with redundancy.
- Support for both licensed and unlicensed RAN solutions, including WiFi. Thus, the fronthaul architecture could support LTE and WiFi RANs on the same system.
- 10/06/13--12:00: China Mobile: A peek at 5G
- 10/08/13--01:00: SON in LTE Release-11
- 10/11/13--01:00: 3GPP Rel-12 SON Status
- 10/13/13--12:00: Handset Antenna Design
- 10/15/13--10:30: What is Network Function Virtualisation (NFV)?
- 10/22/13--04:00: Korea Telecom ‘Route Decision System’ for midnight buses
- 10/27/13--13:00: TDD-FDD Joint CA
- 10/29/13--07:00: ANDSF: Evolution and Roaming with Hotspot 2.0
- 11/03/13--23:30: Key challenges with automatic Wi-Fi / Cellular handover
- 11/06/13--02:00: The Relentless Rise of Mobile Technology
- 11/10/13--11:30: SIPTO Evolution
- 11/16/13--07:00: Agile IMS for the All-IP Era
- 11/21/13--04:00: SON Periodical table
- 11/23/13--13:00: Bandwidth is not the answer – it’s stationarity
- 11/27/13--07:00: ETSI Summit on Future Mobile and Standards for 5G
I was talking about push to share back in 2007 here. Now, in a recent presentation (embedded below) from ALU, eMBMS has been suggested as a a solution for PTT like services in case of Public safety case. Not sure if or when we will see this but I hope that its sooner rather than later. Anyway, the presentation is embedded below. Feel free to add your comments:
Huawei have a few documents on this topic. One such document is embedded below and aanother more technical document is available on slideshare here.
This is from an AT&T press release not so long back:
I interviewed Alan earlier this week, and here is our joint “state of the telecom API nation” report.
MG: My early telecom API project crashed and burned, and past industry initiatives like ParlayX never took off. What has changed since the early 2000s that is triggering new and rapid growth?
AQ: Both the technology and the market have evolved. Large new developer communities have been created by Apple and Google, delivering value through those ecosystems. The need for such ecosystems and partnerships in telecoms is now driven by business demand, not technology supply, and thus is no longer seen as unusual or controversial.
Ten years ago there were developers, but the developer platforms were not as sophisticated. The technology was complex to consume, so you had to be a hardcore developer to use what was on offer. Today we have a mass developer market of people with Web development skills, and an Independent Software Vendor (ISV) market able to consume telecoms capabilities using their existing skills base.
The whole ICT industry – including ancillary services like consulting and equipment – is around a $5tn annual market. Yet it notably lacks a large-scale profitable developer ecosystem for networked service delivery. Why has it failed? Historically there have been too many silos, and too much friction to engage with them. What we are now seeing are companies like Apidaze, Bandwidth, OpenCloud, Plivo, Telestax, Tropo, and Twilio eliminating both of these. Lots of money is being spent on marketing to developers, creating a new business opportunity that telcos and broader ecosystem can take advantage of.
Notably this ecosystem is about more than just APIs. There's also the whole free and open source software arena too. Tools like FreeSWITCH, OpenCloud, Mobicents and WebRTC are becoming core to service innovation. Platforms like Tropo’s Ameche open up new opportunities for value-added voice services. We will be looking at the whole development stack at the Summit in Bangkok.
Who are the key consumers of telecoms APIs and what for?
Telecoms APIs are generally used by enterprises that are embedding communications into their core processes. The term “Communications Enabled Business Processes” was used in the past, but the name never took off, even if the concept did. As such, there is a quiet enterprise communications revolution going on. (See my recent articlefor more information.)
Lots of businesses are doing cool stuff, often to sell to other enterprises. These projects and platforms may not get much press individually, but collectively they add up to a significant market.
For example, Turkcell are a leader in this area of enterprise API delivery. However, they don’t talk about APIs, because it’s about the end user and the value from a better customer experience. They focus on promoting their enterprise services, all of which are (crucially) backed by sales team with technical support. Example services include FreeURL, where customers surf on your pages for free; customer device model and mobile number to support efficient and effective interaction regardless of end user device type; a “find the nearest store” capability to drive sales; and click to call services to capture leads.
That these telecoms services use APIs is about as interesting as them using electricity. The business value and innovation is in the enhanced customer experiences they enable.
Who makes money from producing telecoms APIs and how?
Everyone can! Telcos, intermediaries who work with the developers, enterprises and systems integrators. To make progress, however, telcos have to accept they can't do everything for themselves. For instance, you have to know what developers want – and that means Web scripting, not REST APIs. We will for the foreseeable future need middlemen who translate the value of telecoms APIs into a consumable form.
The greatest value is in customer interaction APIs. The need to communicate with suppliers and customers is fundamental to the human condition, we have been doing it for millennia, and will not stop any time soon. There are long-established markets like bulk SMS and automated calling, and these are ripe for new growth with new capabilities to interact and transact with customers.
What are the most promising areas for future growth?
The growth is around value-added services, notably around the current voice cash cow. It’s time for telcos to remember their heritage: you're the phone company. The distracting “digital lifestyle” stuff only makes money for the content companies. There are too many adjacent businesses being built where the telco doesn't have enough competence, and are competing against low-end competition (e.g. cheap webcams vs managed CCTV or home monitoring services).
Lots of consultants are selling future billion-dollar markets that don't exist. Telcos need to stick to the basic nuts and bolts of communications services, and do them better.
What are the key challenges facing this space?
The key challenge is that this game is that it requires an ecosystem, and telcos are islands. That doesn't mean they should copy Apple and Android, but instead they need to focus on segments where they have credible value and an advantage. A $5tn industry should be able to do this.
What it requires is a whole offering, including sales, business development and support. API-enablement is just a piece of technology, and this cannot be led from a network or IT function; it’s a line of business. The improvement and value to the customers has to come first, and getting the mindset right is hard. We have proof points that you can make money, thanks to companies like Telestax, Tropo and Twilio, if you build a whole supply chain.
Finally, Alan Quayle has posted his independent review of Telecom API's which is embedded below:
Do you have an opinion on Telecom API's? Feel free to add it in the comments.
Recently I came across this whitepaper by iGR, where they have done a case study on the SKT deployment using C-RAN. The main point can be summarised from the whitepaper as follows:
This approach created several advantages for SK Telecom – or for any operator that might implement a similar solution – including the:
Anyway, the paper is embedded below for your perusal and is available to download from the iGR website here.
I was hoping to draw a line under 5G for the time being after a prolonged discussion on my earlier post here and then after clarifying about MSA here. Then this CMCC lecture was brought to my attention and I thought this is a good lecture to listen to so I have embedded the video and slides below. Let me know what you think in the comments below.
Very timely of 4G Americas to release a whitepaper on SON, considering that the SON conference just got over last week. This whitepaper contains lots of interesting details and the status from Rel-11 which is the latest complete release available. I will probably look at some features in detail later on as separate posts. The complete paper is embedded below and is available from 4G Americas website here.
Considering how popular the Release-11 SON post have been, here is Rel-12 status that was presented in the SON Conference in October 2013. Complete presentation embedded below:
You may also be interested in reading a comprehensive report prepared by David Chambers here.
Came across this presentation on Handset Antenna design from a recent Cambridge Wireless event here. Its interesting to see how the antenna technology has evolved and is still evolving. Another recent whitepaper from 4G Americas on meeting the 1000x challenge (here) showed how the different wavelengths are affecting the antenna design.
Maybe its better to move to higher frequencies from the handset design point of view. Anyway, the Cambridge Wireless presentation is embedded below:
Software Defined Networking (SDN) and Network Function Virtualization (NFV) are the two recent buzzwords taking the telecoms market by storm. Every network vendor now has some kind of strategy to use this NFV and SDN to help operators save money. So what exactly is NFV? I found a good simple video by Spirent that explains this well. Here it is:
To add a description to this, I would borrow an explanation and a very good example from Wendy Zajack, Director Product Communications, Alcatel-Lucent in ALU blog:
Dimitris Mavrakis from Informa wrote an excellent summary from the IIR SDN and NFV conference in Informa blog here. Its worth reading his article but I want to highlight one section that shows how the operators think deployment would be done:
ETSI has just published first specifications on NFV. Their press release here says:
The ETSI specifications are available at: http://www.etsi.org/technologies-clusters/technologies/nfv
The first document that shows various use cases is embedded below:
From a recent NTT Docomo presentation (embedded below). Whereas right now 3GPP has only been working on FDD or TDD scenarios, this proposal is a combination of FDD as P-Cell and TDD as S-Cell. Inter-Technology carrier aggregation is another possible option. Anyway, the complete presentation is below.
Updated on 29/10/2013
3GPP has already started working on this work item. See RP-131399 for details.
Access Network Discovery and Selection Function (ANDSF) is still evolving and with the introduction of Hotspot 2.0 (HS 2), there is a good possibility to provide seamless roaming from Cellular to Wi-Fi, Wi-Fi to Wi-Fi and Wi-Fi to Cellular.
There is a good paper (not very recent) by Alcatel-Lucent and BT that explains these roaming scenarios and other ANDSF policies related information very well. Its embedded below:
I have been meaning to list the possible issues which could be present in this scenario of automatically handing over between Wi-Fi and cellular, luckily I found that they have been listed very well in the recent 4G Americas whitepaper. The whitepaper is embedded below but here are the issues I had been wanting to discuss:
In particular, many of the challenges facing Wi-Fi/Cellular integration have to do with realizing a complete intelligent network selection solution that allows operators to steer traffic in a manner that maximizes user experience and addresses some of the challenges at the boundaries between RATs (2G, 3G, LTE and Wi-Fi).Here is the paper:
Figure 1 (see above) below illustrates four of the key challenges at the Wi-Fi/Cellular boundary.
1) Premature Wi-Fi Selection: As devices with Wi-Fi enabled move into Wi-Fi coverage, they reselect to Wi-Fi without comparative evaluation of existing cellular and incoming Wi-Fi capabilities. This can result in degradation of end user experience due to premature reselection to Wi-Fi. Real time throughput based traffic steering can be used to mitigate this.
2) Unhealthy choices: In a mixed wireless network of LTE, HSPA and Wi-Fi, reselection may occur to a strong Wi-Fi network, which is under heavy load. The resulting ‘unhealthy’ choice results in a degradation of end user experience as performance on the cell edge of a lightly loaded cellular network may be superior to performance close to a heavily loaded Wi-Fi AP. Real time load based traffic steering can be used to mitigate this.
3) Lower capabilities: In some cases, reselection to a strong Wi-Fi AP may result in reduced performance (e.g. if the Wi-Fi AP is served by lower bandwidth in the backhaul than the cellular base station presently serving the device). Evaluation of criteria beyond wireless capabilities prior to access selection can be used to mitigate this.
4) Ping-Pong: This is an example of reduced end user experience due to ping-ponging between Wi-Fi and cellular accesses. This could be a result of premature Wi-Fi selection and mobility in a cellular environment with signal strengths very similar in both access types. Hysteresis concepts used in access selection similar to cellular IRAT, applied between Wi-Fi and cellular accesses can be used to mitigate this.
Mobiles have been rising and rising. Couple of weeks back I read 'Mobile is considered the first and most important screen by nearly half of the 18- to 34-year-old demographic, according to research commissioned by Weve.'
The finding placed mobile ahead of laptops or PCs (chosen by 30.6 per cent) and way ahead of TV (12.4 per cent) as the first and most important screen in the lives of people between the ages of 18 and 34.
Just 5.8 per cent of those surveyed in the age group chose a tablet as their "first screen".
The research also found that 45 per cent of 18- to 34-year-olds consider their mobile their first choice of device when interacting with online content, placing the platform just ahead of laptops and PCs, which scored 43 per cent.
Among the wider 18 to 55 age group surveyed, a PC or laptop was seen as the "first screen" with 39.8 per cent naming either computer as their most important screen, while smartphones came second on 28 per cent.
TV was in third place with 27 per cent of people naming it as their most important screen. Five per cent of the total group said they considered a tablet their "first screen".
Only a quarter of the 18 to 55 age group said mobile would be their first choice platform if they wanted to access the internet, while nearly two thirds preferred to use a PC or laptop.Tomi Ahonen has always been referring to Mobile as the 7th Mass Media.
So when I saw this above picture (and there are more of them) in Ben Evaans slide deck (embedded below), it just reiterated my belief that Mobile will take over the world sooner or later. Anyway, the slides are interesting to go through.
Couple of years back I did a post on SIPTO (Selected IP Traffic Offload) and related technologies coming as part of Rel-10. I also put up a comparison for SIPTO, LIPA and IFOM here. Having left it for couple of years, I found that there have been some enhancements to the architecture from the basic one described here.
I have embedded the NEC paper below for someone wanting to investigate further the different options shown in the picture above. I think that even though the operator may offload certain type of traffic locally, they would still consider that data as part of the bundle and would like to charge for it. At the same time there would be a requirement on the operator for lawful interception, so not sure how this will be managed for different architectures. Anyway, feel free to leave comments if you have any additional info.
Personally, I do watch quite a bit of video on my phone and tablet but only when connected using Wi-Fi. Occasionally when I am out, if someone sends me video clip on Whatsapp or some link to watch Video on youtube, I do try and see it. Most of the time the quality is too disappointing. It could be because my operator has been rated as the worst operator in UK. Anyway, as the infographic above suggests, there needs to be some kind of an optimisation done to make sure that end users are happy. OR, the users cn offload to Wi-Fi when possible to get a better experience.
This is one of the main reasons why operators are actively considering offloading to Wi-Fi and have carrier WiFi solutions in place. The standards are actively working in the same direction. Two of my recent posts on the topic of 'roaming using ANDSF' and 'challenges with seamless cellular/Wi-Fi handover' have been quite popular.
Recently I attended a webinar on the topic of 'Video Offload'. While the webinar reinforced my beliefs about why offload should be done, it did teach me a thing or two (like when is a Hotspot called a Homespot - see here). The presentation and the Video is embedded below. Before that, I want to show the result of a poll conducted during the webinar where the people present (and I would imagine there were quite a few people) were asked about how they think MNO will approach the WiFi solution in their network. Result as follows:
Here is the presentation:
Here is the video of the event:
Came across this in a presentation from the SON Conference back in Oct. 2013.
Martin Geddes did an interesting presentation in Future of Broadband workshop. The ITU has the following write-up on that workshop
His presentation is embedded as follows:
Edited from the original in 3GPP News:
The ETSI Future Mobile Summit has heard how the mobile internet will evolve over the next ten to fifteen years, and how 3GPP systems will ensure future stability as the network copes with an explosive growth in complexity and usage.
With 3GPP providing the evolutionary framework for mobility, via its Releases of new functionality and features, the more radical thinking, at the Summit, came in the form of Research projects and some future focused industry initiatives, such as the WWRF, the METIS Project and the DVB Project.
Mario Campolargo - of the European Commission -
ew device types significantly contribute to that increase (e.g., probes, sensors, meters, machines etc) and n
|3GPP RAN has started a new innovation cycle which will be shaping next generation cellular systems|
|A World Divided - The coverage world versus the capacity world|
|Can broadcasters and mobile industry cooperate to define a new worldwide standard that will benefit both broadcasters and mobile industry?|
|Architecture evolution, More new nodes, CS-domain removal?, new ways of design of networks?|
|The challenge for Operators, Suppliers and Standards Bodies|
|3D Chip-Stacks & High-Rate Inter-Chip Communications, Monitoring / Sensing, Tactile internet - Latency Goals|
| Includes the 'Standardization Challenges' raised by the Summit.