- RSS Channel Showcase 1423837
- RSS Channel Showcase 4476181
- RSS Channel Showcase 1582568
- RSS Channel Showcase 4396453
Articles on this Page
- 12/01/13--04:00: _Quick summary on LT...
- 12/09/13--04:00: _Rise of the "Thing"
- 12/13/13--05:30: _Advancements in Con...
- 12/19/13--00:30: _The futuristic conc...
- 12/21/13--06:00: _Top 15 blog posts f...
- 01/03/14--03:00: _2014 Mobile Interne...
- 01/08/14--13:00: _LTE-Broadcast (eMBM...
- 01/13/14--00:00: _My observations on ...
- 01/16/14--03:00: _3GPP Rel-12 and Fut...
- 01/20/14--04:00: _Different flavours ...
- 01/25/14--09:30: _Security and other ...
- 01/30/14--15:00: _Multi-SIM: The Jargon
- 02/03/14--12:00: _5G and the ‘Millime...
- 02/08/14--04:00: _100 years of Wirele...
- 02/13/14--13:00: _VoLTE Roaming with ...
- 02/18/14--09:00: _The Rise and Rise o...
- 02/25/14--04:00: _Beacons, Bluetooth,...
- 03/01/14--01:30: _Mobile, Context and...
- 03/04/14--04:00: _LTE Radar - LTE pro...
- 03/08/14--10:31: _Mobile World Congre...
- 12/01/13--04:00: Quick summary on LTE and UMTS / HSPA Release-12 evolution by 3GPP
- 12/09/13--04:00: Rise of the "Thing"
- 12/13/13--05:30: Advancements in Congestion control technology for M2M
- 12/19/13--00:30: The futuristic concept of 'Smart Batteries'
- Li-Ion vs Li-Poly, plus how do Lithium batteries work anyway?
- Lithium-ion Batteries - Apple
- Battle of the smartphone batteries - Daily Mail
- New battery alternative emerges for hybrid cars
- Technology companies charge towards next generation battery future
- Light-weight body parts will be the battery of future cars
- These transparent solar cells provide 50% more battery life for your phone — and ‘infinite’ standby time
- Smartphone battery life: 2 problems, 4 fixes (Smartphones Unlocked)
- New lithium-ion battery design that’s 2,000 times more powerful, recharges 1,000 times faster
- The Power Treadmill
- 12/21/13--06:00: Top 15 blog posts from 2013
- VoLTE Bearers
- C-RAN Architecture and Challenges
- What is WebRTC and where does it fit with LTE and IMS
- 5G: Your Questions Answered
- LTE-A: Downlink Transmission Mode 9 (TM-9)
- 3GPP Rel.11 Technology Introduction whitepaper
- New Carrier Type (NCT) in Release-12 and Band 29
- Key challenges with automatic Wi-Fi / Cellular handover
- The Relentless Rise of Mobile Technology
- Access Class Barring in LTE using System Information Block Type 2
- LTE-B, LTE-C, ... , LTE-X
- China Mobile: A peek at 5G
- Summary of Network Security Conference (#NetworkSecurity) 2013
- Quick summary on LTE and UMTS / HSPA Release-12 evolution by 3GPP
- Introduction to M2M and its developments in LTE
- 01/03/14--03:00: 2014 Mobile Internet Prediction Survey
- 01/08/14--13:00: LTE-Broadcast (eMBMS) may fail again
- 01/13/14--00:00: My observations on Mobiles and OTT Apps in India
- 01/16/14--03:00: 3GPP Rel-12 and Future Security Work
- 01/20/14--04:00: Different flavours of SRVCC (Single Radio Voice Call Continuity)
- 01/25/14--09:30: Security and other development on the Embedded SIM
- Soft SIM would store the Operator secret credentials in software within the Mobile device operating system - the same system that is often attacked to modify the handset IMEI, perform SIM-Lock hacking and ‘jail-break’ mobile OS’s
- Operators are very concerned about the reduction in security of their credentials through the use of Soft SIM. Any SIM approach not based on a certified hardware secure element will be subject to continual attack by the hacking community and if compromised result in a serious loss of customer confidence in the security of Operator systems
- Multiple Soft SIM platforms carrying credentials in differing physical platforms, all requiring security certification and accreditation would become an unmanageable overhead – both in terms of resource, and proving their security in a non-standardised virtual environment
- 01/30/14--15:00: Multi-SIM: The Jargon
- 02/03/14--12:00: 5G and the ‘Millimeter-Wave' Radios
- 02/08/14--04:00: 100 years of Wireless History
- Colin Smithers, Chairman, Plextek - 1914 to 1934: The wireless wave
- Geoff Varrall, Director, RTT Online - 1934 to 1945: The wireless war
- Steve Haseldine, Chairman, Deaf Alerter - 1945 to 1974: The cold war - radio goes underground
- Prof Nigel Linge, Professor of Telecommunications, University of Salford - 1974 to 1994
- Andy Sutton, Principal Network Architect, EE and Visiting Professor, University of Salford - 1994 to 2014: Mass consumer cellular and the mobile broadband revolution - Broadband radio, digital radio, smart phone and smart networks
- 8-carrier downlink operation (HSDPA)
- Downlink (DL) 4-branch Multiple Input Multiple Output (MIMO) antennas
- DL Multi-Flow Transmission
- Uplink (UL) dual antenna beamforming (both closed and open loop transmit diversity)
- UL MIMO with 64 Quadrature Amplitude Modulation (64-QAM)
- Several CELL_FACH (Forward Access Channel) state enhancements (for smartphone type traffic) and non-contiguous HSDPA Carrier Aggregation (CA)
- Carrier Aggregation (CA)
- Multimedia Broadcast Multicast Services (MBMS) and Self Organizing Networks (SON)
- Introduction to the Coordinated Multi-Point (CoMP) feature for enabling coordinated scheduling and/or beamforming
- Enhanced Physical Control Channel (EPDCCH)
- Further enhanced Inter-Cell Interference Coordination (FeICIC) for devices with interference cancellation
- Machine Type Communications (MTC)
- IP Multimedia Systems (IMS)
- Wi-Fi integration
- Home NodeB (HNB) and Home e-NodeB (HeNB)
- Universal Mobile Telecommunication System (UMTS) Heterogeneous Networks (HetNet)
- Scalable UMTS Frequency Division Duplex (FDD) bandwidth
- Enhanced Uplink (EUL) enhancements
- Emergency warning for Universal Terrestrial Radio Access Network (UTRAN)
- HNB mobility
- HNB positioning for Universal Terrestrial Radio Access (UTRA)
- Machine Type Communications (MTC)
- Dedicated Channel (DCH) enhancements
- Active Antenna Systems (AAS)
- Downlink enhancements for MIMO antenna systems
- Small cell and femtocell enhancements
- Machine Type Communication (MTC)
- Proximity Service (ProSe)
- User Equipment (UE)
- Self-Optimizing Networks (SON)
- Heterogeneous Network (HetNet) mobility
- Multimedia Broadcast/Multicast Services (MBMS)
- Local Internet Protocol Access/Selected Internet Protocol Traffic Offload (LIPA/SIPTO)
- Enhanced International Mobile Telecommunications Advanced (eIMTA) and Frequency Division Duplex-Time Division Duplex Carrier Aggregation (FDD-TDD CA)
- 02/25/14--04:00: Beacons, Bluetooth, NFC and WiFi
- 03/01/14--01:30: Mobile, Context and Discovery - Ben Evans
- 03/04/14--04:00: LTE Radar - LTE proximity services
- 03/08/14--10:31: Mobile World Congress 2014 (#MWC14) Roundups
- GiffGaff Blog
- Alan Quayle Blog
- Cisco SP 360 Blog
- Frank Rayal Blog
- Mobile OS Summary from MWC 2014
- Informa T&M Day 1, Day 2 and Day 3
- CCS Insight Day 0, Day 1 and Day 2
A quick summary from 3GPP about the Release-12 progress (Jun. 2014 release planned) from the recent ETSI Future Mobile Summit. Presentation and video embedded below
The EE presentation is embedded as follows:
Another good example website I was recently made aware of is http://postscapes.com/internet-of-things-examples/ - worth checking how IoT would help us in the future.
NTT Docomo recently published a new article (embedded below) on congestion control approaches for M2M. In their own words:
Since 3GPP Release 10 (Rel. 10) in 2010, there has been active study of technical specifications to develop M2M communications further, and NTT DOCOMO has been contributing proactively to creating these technical specifications. In this article, we describe two of the most significant functions standardized between 3GPP Rel. 10 and Rel. 11: the M2M Core network communications infrastructure, which enables M2M service operators to introduce solutions more easily, and congestion handling technologies, which improve reliability on networks accommodating a large number of terminals.
Complete article as follows:
Other related posts:
I did a presentation in the Cambridge Wireless Future technology SIG about what we call 'Smart Batteries'. The presentation is self-explanatory and is embedded below. I would be interested in hearing your thoughts about this idea.
Other links if you want to dig further on batteries:
Here is a list of most popular blog posts from 2013. In descending order:
Interesting presentation by Chetan Sharma listing what we can expect in 2014. Slide 9 as shown in the picture above highlights the breakthrough categories. Good to see that LTE-B ('B' for broadcast) has not made it into this list. My guess is that connected cars and wearable computing will be in the news constantly throughout the year.
The complete presentation as follows:
Anyway, I came across this picture below from the recent Ericsson Mobility report:
A recent Business Insider article says that "One In Every 5 People In The World Own A Smartphone, One In Every 17 Own A Tablet". Once the users move to using bigger screens, their preferences on how they watch videos will definitely change.
A real interesting chart would be to show users viewing habits based on the screen size. Phablets are generally classified as smartphones but can be substitutes for tablets in many scenarios. They could definitely help the Mobile TV viewing habits on the smartphones.
Anyway, here is the complete article:
This time a lot of things were very different. I found that there was a Phablet craze going on. No sooner were people starting to get used to these big screen devices they realised how many things they could do. The well to do were buying Samsung devices and the people who did not want to spend big bucks were content with the little known brands.
The Domo phablet on the left in the picture above costs around ₹8000 (£80/$130) and the Maxx on the right is roughly ₹5500 (£55/$90). Both these come with 1 year warranty.
There were also quite a few ads using celebrities promoting Phablets. Its good to see people spending on these devices. Unlike UK where most of these devices are subsidised on a contract, people in India prefer pre-paid option and buying the phone outright.
I have to admit that even though I am a fan of these big screen devices, I find the Samsung Galaxy Tab just a bit too big for the use as a phone (see pic above).
It was also good to see that people have embraced the 3G data usage as well. I got a 6GB package for roughly ₹1000 (£10/$16). I found that people complained about the speeds and were prepared to pay more for 4G (faster data rates). I also noticed that a few people were not aware of Wi-Fi and the fixed broadband. I was told that the fixed broadband was capped, offered similar prices and could be quite unreliable. I guess Wireless is helping in India where the fixed Infrastructure may still be an issue in many places.
I have to mention here that I did not meet anyone who was using an iPhone. This could be due to iPhone being ridiculously expensive and people may be thinking why pay a high price for such a small screen. A comparison of iPhone prices worldwide showed that the price of iPhone 5S as % of GDP per capita (PPP) is the highest in India. See here.
Another area of observation was SMS and OTT apps. I remember spending a lot of time trying to convince people to use OTT apps for messaging as it would be cheaper for International messages. Well, now it seems everyone has adopted it whole heartedly. One of the problems with SMS in India is that you get too much Spam SMS and sometimes the operators are the culprits. There is no way to send a stop for these SMS messages. With OTT Apps, you know who is sending you messages and you can block the offenders.
There are many OTT Apps which are popular like Hike, Line, WeChat, WhatsApp, etc. The winner though is undoubtedly WhatsApp. I met an acquaintance whose has stopped using emails for business and now relies completely on WhatsApp. Then there were others who loved it because of Group chat facility.
There were many reasons why WhatsApp is a winner. Along with a simple interface and Group chat facility, one of the other reasons pointed out was that the facility to see when the person was last online was very useful. Recently WhatsApp introduced facility to send Voice messages. This helped it acquire some of the WeChat users.
It was good to see the beginnings of the mobile revolution in India. Wonder what my next trip will show me.
Please note that this article is based on what I observed in Mumbai among friends and family. In no way should this be treated as detailed research.
Here is the 3GPP presentation from the 9th ETSI Security workshop. Quite a few bits on IMS and IMS Services and also good to see new Authentication algorithm TUAK as an alternative to the widely used Milenage algorithm.
Single Radio Voice Call Continuity (SRVCC) has been quietly evolving with the different 3GPP releases. Here is a quick summary of these different flavors
The book "LTE-Advanced: A Practical Systems Approach to Understanding 3GPP LTE Releases 10 and 11 Radio Access Technologies" by Sassan Ahmadi has some detailed information on SRVCC, the following is an edited version from the book:
SRVCC is built on the IMS centralized services (ICS) framework for delivering voice and messaging services to the users regardless of the type of network to which they are attached, and for maintaining service continuity for moving terminals.
To support GSM and UMTS, some modifications in the MSC server are required. When the E-UTRAN selects a target cell for SRVCC handover, it needs to indicate to the MME that this handover procedure requires SRVCC. Upon receiving the handover request, the MME triggers the SRVCC procedure with the MSC server. The MSC then initiates the session transfer procedure to IMS and coordinates it with the circuit-switched handover procedure to the target cell.
Handling of any non-voice packet-switched bearer is by the packet-switched bearer splitting function in the MME. The handover of non-voice packet-switched bearers, if performed, is according to a regular inter-RAT packet-switched handover procedure.
When SRVCC is enacted, the downlink flow of voice packets is switched toward the target circuit-switched network. The call is moved from the packet-switched to the circuit-switched domain, and the UE switches from VoIP to circuit-switched voice.
3GPP Rel-10 architecture has been recommended by GSMA for SRVCC because it reduces both voice interruption time during handover and the dropped call rate compared to earlier configurations. The network controls and moves the UE from E-UTRAN to UTRAN/GERAN as the user moves out of the LTE network coverage area. The SRVCC handover mechanism is entirely network-controlled and calls remain under the control of the IMS core network, which maintains access to subscribed services implemented in the IMS service engine throughout the handover process. 3GPP Rel-10 configuration includes all components needed to manage the time-critical signaling between the user’s device and the network, and between network elements within the serving network, including visited networks during roaming. As a result, signaling follows the shortest possible path and is as robust as possible, minimizing voice interruption time caused by switching from the packet-switched core network to the circuit-switched core network, whether the UE is in its home network or roaming. With the industry aligned around the 3GPP standard and GSMA recommendations, SRVCC-enabled user devices and networks will be interoperable, ensuring that solutions work in many scenarios of interest.
Along with the introduction of the LTE radio access network, 3GPP also standardized SRVCC in Rel-8 specifications to provide seamless service continuity when a UE performs a handover from the E-UTRAN to UTRAN/GERAN. With SRVCC, calls are anchored in the IMS network while the UE is capable of transmitting/ receiving on only one of those access networks at a given time, where a call anchored in the IMS core can continue in UMTS/GSM networks and outside of the LTE coverage area. Since its introduction in Rel-8, the SRVCC has evolved with each new release, a brief summary of SRVCC capability and enhancements are noted below
3GPP Rel-8: Introduces SRVCC for voice calls that are anchored in the IMS core network from E-UTRAN to CDMA2000 and from E-UTRAN/UTRAN (HSPA) to UTRAN/GERAN circuit-switched. To support this functionality, 3GPP introduced new protocol interface and procedures between MME and MSC for SRVCC from E-UTRAN to UTRAN/GERAN, between SGSN and MSC for SRVCC from UTRAN (HSPA) to UTRAN/GERAN, and between the MME and a 3GPP2-defined interworking function for SRVCC from E-UTRAN to CDMA 2000.
• 3GPP Rel-9: Introduces the SRVCC support for emergency calls that are anchored in the IMS core network. IMS emergency calls, placed via LTE access, need to continue when SRVCC handover occurs from the LTE network to GSM/UMTS/CDMA2000 networks. This evolution resolves a key regulatory exception. This enhancement supports IMS emergency call continuity from E-UTRAN to CDMA2000 and from E-UTRAN/UTRAN (HSPA) to UTRAN/ GERAN circuit-switched network. Functional and interface evolution of EPS entities were needed to support IMS emergency calls with SRVCC.
• 3GPP Rel-10: Introduces procedures of enhanced SRVCC including support of mid-call feature during SRVCC handover (eSRVCC); support of SRVCC packet-switched to circuit-switched transfer of a call in alerting phase (aSRVCC); MSC server-assisted mid-call feature enables packet-switched/ circuit-switched access transfer for the UEs not using IMS centralized service capabilities, while preserving the provision of mid-call services (inactive sessions or sessions using the conference service). The SRVCC in alerting phase feature adds the ability to perform access transfer of media of an instant message session in packet-switched to circuit-switched direction in alerting phase for access transfers.
• 3GPP Rel-11: Introduces two new capabilities: single radio video call continuity for 3G-circuit-switched network (vSRVCC); and SRVCC from UTRAN/GERAN to E-UTRAN/HSPA (rSRVCC). The vSRVCC feature provides support of video call handover from E-UTRAN to UTRAN-circuitswitched network for service continuity when the video call is anchored in IMS and the UE is capable of transmitting/receiving on only one of those access networks at a given time. Service continuity from UTRAN/GERAN circuitswitched access to E-UTRAN/HSPA was not specified in 3GPP Rel-8/9/10. To overcome this drawback, 3GPP Rel-11 provided support of voice call continuity from UTRAN/GERAN to E-UTRAN/HSPA. To enable video call transfer from E-UTRAN to UTRAN-circuit-switched network, IMS/EPC is evolved to pass relevant information to the EPC side and S5/S11/Sv/Gx/Gxx interfaces are enhanced for video bearer-related information transfer. To support SRVCC from GERAN to E-UTRAN/HSPA, GERAN specifications are evolved to enable a mobile station and base station sub-system to support seamless service continuity when a mobile station hands over from GERAN circuit-switched access to EUTRAN/ HSPA for a voice call. To support SRVCC from UTRAN to EUTRAN/ HSPA, UTRAN specifications are evolved to enable the RNC to perform rSRVCC handover and to provide relative UE capability information to the RNC.
NTT Docomo has a presentation on SRVCC and eSRVCC which is embedded below:
Its no surprise that GSMA has started working on Embedded SIM specifications. With M2M getting more popular every day, it would make sense to have the SIM (or UICC) embedded in them during the manufacturing process. The GSMA website states:
The last time I talked about embedded SIM was couple of years back, after the ETSI security workshop here. Well, there was another of these workshops recently and an update to these information.
The ETSI presentation is not embedded here but is available on Slideshare here. As the slide says:
An embedded UICC is a “UICC which is not easily accessible or replaceable, is not intended to be removed or replaced in the terminal, and enables the secure changing of subscriptions” (ETSI TS 103 383)
Finally, Embedded SIM should not be confused with Soft-SIM. My last post on Soft-SIM, some couple of years back here, has over 15K views which shows how much interest is there in the soft SIM. As the slide says:
Soft or Virtual SIM is a completely different concept that does not use existing SIM hardware form factors and it raises a number of strong security issues:
The complete GSMA presentation is as follows:
You may also like my old paper:
I had been having some discussions regarding Multi-SIM phones and there is a bit of misunderstanding so here is my clarification about them. Anyway, a lot of information is just an understanding so feel free to correct any mistakes you think I may have made.
This post is about multiple SIM cards, physical UICC cards rather than single UICC with multiple SIM applications. We will look at Dual IMSI later on in the post. In case you do not know about the multiple SIM applications in a UICC, see this old post here. In this post, I will refer to UICC cards as SIM cards to avoid confusion.
Back in the old days, the Dual-SIM phones allowed only one SIM on standby at any time. The other SIM was switched off. If someone would call the number that was switched off, a message saying that the number is switched off would come or it would go in the voicemail. To make this SIM in standby, you would have to select it from the Menu. The first SIM is now switched off. The way around it was to have one SIM card calls forwarded the other when switched off. This wasn't convenient and efficient, money wise. The reason people use multiple SIM phones is to have cheaper calls using different SIMs. So in this case forwarding calls from one SIM to another wont be cost effective. These type of phones were known as Dual SIM Single Standby or DSSS. These devices had a single transceiver.
So as the technology got cheaper and more power efficient, the new multi-SIM devices could incorporate two receivers but only one transmitter was used. The main reason being that using two transmitters would consume much more power. As a result, these devices can now have both the SIM's on standby at the same time. These kind of devices were known as Dual SIM Dual Standby or DSDS. Wikipedia also calls then Dual SIM Standby or DSS. This concept could be extended further to Triple SIM Triple Standby or TSTS in case of the device with three SIM cards and Quad SIM Quad Standby or QSQS in case of four SIM cards. One thing to remember is that when a call is received and a SIM becomes active, the other SIM cards are in receive only more. So if a call is received on another SIM card, the device will allow you to keep the first call on hold and then take the second call.
Another category of devices that are now available are the Dual SIM Dual Active or DSDA. In this case there are two transceivers in the device. Both the SIM cards are active at the same time so each SIM card can handle the call independently of each other. It would even be possible to conference both these calls.
There were quite a few interesting talks in the Cambridge Wireless Radio Technology SIG event last week. The ones that caught my attention and I want to highlight here are as follows.
The mobile operator EE and 5GIC centre explained the challenges faced during the Practical deployments. Of particular interest was the considerations during deployments. The outdoor environments can change in no time with things like foliage, signage or even during certain festivals. This can impact the radio path and may knock out certain small cells or backhaul. The presentation is available to view and download here.
Another interesting presentation was from Bluwireless on the 60GHz for backhaul. The slide that was really shocking was the impact of regulation in the US and the EU. This regulation difference means that a backhaul link could be expensive and impractical in certain scenarios in the EU while similar deployments in the US would be considerably cheaper. This presentation is available here.
Finally, the presentation from Samsung highlighted their vision and showed the test results of their mmWave prototype. The presentation is embedded below and is available here.
Finally, our 5G presentation summarising our opinion and what 5G may contain is available here. Dont forget to see the interesting discussion in the comments area.
Voice over LTE or VoLTE has many problems to solve. One of the issues that did not have a clear solution initially was Roaming. iBasis has a whitepaper on this topic here, from which the above picture is taken. The following is what is said above:
The routing of international calls has always been a problem for mobile operators. All too often the answer—particularly in the case of ‘tromboning’ calls all the way back to the home network—has been inelegant and costly. LTE data sessions can be broken out locally, negating the need for convoluted routing solutions. But in a VoIMS environment all of the intelligence that decides how to route the call resides in the home network, meaning that the call still has to be routed back.
The industry’s solution to this issue is Roaming Architecture for Voice over LTE with Local Breakout (RAVEL). Currently in the midst of standardisation at 3GPP, RAVEL is intended to enable the home network to decide, where appropriate, for the VoIMS call to be broken out locally.
Three quarters of respondents to the survey said they support an industry-wide move to RAVEL for VoLTE roaming. This is emphatic in its enthusiasm but 25 per cent remains a significant share of respondents still to be convinced. Just over half of respondents said they plan to support VoIMS for LTE roaming using the RAVEL architecture, while 12.3 per cent said they would support it, but not using RAVEL.
Until RAVEL is available, 27.4 per cent of respondents said they plan to use home-routing for all VoLTE traffic, while just under one fifth said they would use a non-standard VoLTE roaming solution.
Well, the solution was standardised in 3GPP Release-11. NTT Docomo has an excellent whitepaper (embedded below) explaining the issue and the proposed solution.
In 3GPP Release 11, the VoLTE roaming and interconnection architecture was standardized in cooperation with the GSMA Association. The new architecture is able to implement voice call charging in the same way as circuit-switched voice roaming and interconnection models by routing both C-Plane messages and voice data on the same path. This was not possible with the earlier VoLTE roaming and interconnection architecture.
Anyway, here is the complete whitepaper
4G Americas predicts that by the end of 2018, HSPA/HSPA+ would be the most popular technology whereas LTE would be making an impact with 1.3 Billion connected devices. The main reason for HSPA being so dominant is due to the fact that HSPA devices are mature and are available now. LTE devices, even though available are still slightly expensive. At the same time, operators are taking time having a seamless 4G coverage throughout the region. My guess would be that the number of devices that are 4G ready would be much higher than 1.3 Billion.
Phablets' and 'non-Phablets' category.
Anyway, the 4G Americas report from which the information above is extracted contains lots of interesting details about Release-11 and Release-12 HSPA+ and LTE. The only problem I found is that its too long for most people to go through completely.
The whitepaper contains the following information:
Not sure if you have heard about some kind of Beacons that will be used to guide us everywhere. There are Bluetooth Beeacons, iBeacon, Paypal Beacon, probably more. So here is an attempt to understand some of these things.
The first is this introductory presentation which seems to be extremely popular on Slideshare:
Once we understand the concept of Beacons, there is another presentation that helps us understand iBeacons and Paypal Beacons as follows:
Bluetooth Beacons vs Wifi vs NFC is an interesting article comparing the Beacons with WiFi & NFC. Read it here
Why Beacons may be NFC killer, GigaOm has a good answer here:
iBeacon could be a NFC killer because of its range. NFC tags are pretty cheap compared to NFC chips, but NFC tags are required on each product because NFC works only in very close proximity. In theory, NFC range is up to 20cm (7.87 inches), but the actual optimal range is less than 4cm (1.57 inches). Also, mobile devices need to contain a NFC chip that can handle any NFC communications. On the other hand, iBeacons are a little expensive compared to NFC chips, but iBeacons range is up to 50 meters. Not all phones have NFC chips, but almost all have Bluetooth capability.Many years back there was a proximity marketing craze using Bluetooth. Then the craze died down and everyone started focussing on other approaches for LBS. I also suggested a Small Cells based approach here. Its good to see that we are going to use a new Bluetooth based approach for similar functions.
By the end of the year we will hopefully know if this is a new hype or a successful technology. Issues with battery drains, security, interoperability, etc. will need to be sorted asap for its success.
An Interesting presentation and Video from Benedict Evans, both embedded below:
There is an interesting Q&A at the end of the talk in the video. You can directly jump to 27:30 marker for the Q&A. One of the interesting points highlighted by him, that I always knew but was not able to convey it across is there is no real point comparing Google and Apple. I am too lazy to type down so please jump to 45:10. One of the comment on the Youtube summarises it well:
"Google is a vast machine learning engine... and it spent 10-15 years building that learning engine and feeding it data"
So true. It is not Apple vs Google; it is not about the present. It is about the future (see Google's recent acquisitions for context). As Benedict says, if Google creates beautiful, meaningful and unique experiences for users, why would they do it only for Android, they would also have it on Apple devices.
In the end, comparing Apple and Google is like comparing Apple(s) and Oranges :)
The picture below summarises how this will work:
It is interesting to note that these problems are already being solved using Apps and other technologies. Once the 3GPP standard is finalised, it would be a challenge to get this to mass adoption. An example would be Bluetooth based Beacons that I blogged about earlier here. Nevertheless, it would be interesting to see how compelling the use cases would be once this is standardised. The complete DT presentation is embedded below:
The best way is to start with this Video of different gadgets by Orange (excuse their adverts)
Maravedis-Rethink has an excellent summary from Network point of view:
Complete summary here.
Chetan Sharma has written a brilliant summary and covers all different topics:
All the progress that has been on the mobile economy has been on the back of trillions of dollars of investment over the last couple of decades. With declining margins, how long do operators continue to invest and at what pace? What’s the margin profile they are willing to live with? What’s the role of government in building out the infrastructure when high-speed mobile networks are concerned? Japan, Korea, Israel have all based their competitiveness on connected broadband world. Can others follow? The impact of Whatsapp launching voice services and Netflix/Comcast deal were hotly debated in the hallways. It is one thing to put out national broadband plans and it is entirely another reality to have an execution path to deliver on the plan. The broadband investment has much far reaching implications than most people and governments realize.
Complete article here.
Ian Poole from Radio Electronics has done a good job too with the summary and video:
Complete report and the video here.
Finally, an excellent summary on Small Cells and related by ThinkSmallCell:
Ronald Gruia from Frost&Sullivan has created a summary presentation on Slideshare that is embedded below:
Other Summaries worth reading:
There was also a Carrier Wi-Fi Summit going on in parallel to the main MWC. A summary of that is available on the WBA website here: Day 1, Day 2, Day 3 and Day 4.
Claus Hetting has also added an excellent summary of the Carrier Wi-Fi Summit on his blog here.