Showing posts with label LTE. Show all posts
Showing posts with label LTE. Show all posts

Friday 28 August 2015

MCPTT Off-network and UE to UE/Network Relays

3GPP SA6 recently held a workshop on Mission Critical Push To Talk (MCPTT) stage 3 development in Canada. You can look at the meeting report here and download any presentations from here.

An interesting presentation that caught my attention was one on "MCPTT Off-network Architecture". The presentation is embedded below where it is described technically what is meant by Off-network. From my understanding an off-network from MCPTT point of view is one where the UE does not have network coverage.

In such a situation a UE can connect to another UE that can connect to UE/network (if available) to relay the message. Its similar to another technology that I have talked about, Multihop Cellular Networks and ODMA. Anyway, here is the presentation:



Sometimes the standards can take too long to develop a feature and apps can come and deliver a similar service at a very short notice. One such App that does something similar is called Firechat, which played a big role in many protests worldwide. The video explaining it below is worth watching.


The problem with Apps is that they cannot be used by the emergency services or other governmental organisations, unless a standard feature is available. This is the expectation from this Off-network relays. It would work in combination with D2D/ProSe.


For anyone interested in the latest Public Safety (PS), here is a presentation by SA6 chairman from July

Sunday 9 August 2015

Diameter Security is worse than SS7 Security?


Back in December last year, there was a flurry of news about SS7 security flaw that allowed hackers to snoop on an unsuspecting users calls and SMS. The blog readers will also be aware that SS7 is being replaced by the Diameter protocol. The main reason being to simplify roaming while at the same time being able to manage the signalling storm in the networks.


The bad news is that while is case of SS7, security issues are due to network implementation and configuration (above pic), the security issues in Diameter seem to be due to the protocol and architecture themselves (below pic)


Diameter is very important for LTE network architecture and will possibly continue in the future networks too. It is very important to identify all such issues and iron them before some hackers start exploiting the network vulnerabilities causing issues for everyone.

The presentation by Cédric Bonnet, Roaming Technical Domain Manager, Orange at Signalling Focus Day of LTE World Summit 2015 is embedded below:


From SS7 to Diameter Security from Zahid Ghadialy

Some important information from this post has been removed due to a valid complaint.

Sunday 26 July 2015

LTE vs TETRA for Critical Communications

Sometime back I was reading this interview between Martin Geddes and Peter Clemons on 'The Crisis in UK Critical Communications'. If you haven't read it, I urge you to read it here. One thing that stuck out was as follows:

LTE was not designed for critical communications.

Commercial mobile operators have moved from GSM to UMTS to WCDMA networks to reflect the strong growth in demand for mobile data services. Smartphones are now used for social media and streaming video. LTE technology fulfils a need to supply cheap mass market data communications.

So LTE is a data service at heart, and reflects the consumer and enterprise market shift from being predominantly voice-centric to data-centric. In this wireless data world you can still control quality to a degree. So with OFDM-A modulation we have reduced latency. We have improved how we allocate different resource blocks to different uses.

The marketing story is that we should be able to allocate dedicated resources to emergency services, so we can assure voice communications and group calling even when the network is stressed. Unfortunately, this is not the case. Even the 3GPP standards bodies and mobile operators have recognised that there are serious technology limitations.
This means they face a reputational risk in delivering a like-for-like mission-critical voice service.

Won’t this be fixed by updated standards?
The TETRA Critical Communications association (TCCA) began to engage with the 3GPP standards process in 2012. 3GPP then reached out to peers in the USA and elsewhere: the ESMCP project here in the UK, the US FirstNet programme, and the various European associations.

These lobbied 3GPP for capabilities specifically aimed at critical communications requirements. At the Edinburgh meeting in September 2014, 3GPP set up the SA6specification group, the first new group in a decade.

The hope is that by taking the critical communications requirement into a separate stream, it will no longer hold up the mass market release 12 LTE standard. Even with six meetings a year, this SA6 process will be a long one. By the end of the second meeting it had (as might be expected) only got as far as electing the chairman.

It will take time to scope out what can be achieved, and develop the critical communications functionality. For many players in the 3GPP process this is not a priority, since they are focusing solely on mass market commercial applications.

Similar point was made in another Critical communications blog here:

LTE has emerged as a long term possible replacement for TETRA in this age of mobile broadband and data. LTE offer unrivalled broadband capabilities for such applications as body warn video streaming, digital imaging, automatic vehicle location, computer-assisted dispatch, mobile and command centre apps, web access, enriched e-mail, mobile video surveillance apps such as facial recognition, enhanced Telemetry/remote diagnostics, GIS and many more. However, Phil Kidner, CEO of the TCCA pointed out recently that it will take many LTE releases to get us to the point where LTE can match TETRA on key features such as group working, pre-emptive services, network resilience, call set-up times and direct mode.
The result being, we are at a point where we have two technologies, one offering what end users want, and the other offering what end users need. This has altered the discussion, where now instead of looking at LTE as a replacement, we can look at LTE as a complimentary technology, used alongside TETRA to give end users the best of both worlds. Now the challenge appears to be how we can integrate TETRA and LTE to meet the needs and wants of our emergency services, and it seems that if we want to look for guidance and lessons on the possible harmony of TETRA and LTE we should look at the Middle East.
While I was researching, I came across this interesting presentation (embedded below) from the LTE World Summit 2015





The above is an interesting SWOT (Strengths, Weaknesses, Opportunities and Threats) analysis for TETRA and LTE. While I can understand that LTE is yet unproven, I agree on the lack of spectrum and appropriate bands.

I have been told in the past that its not just the technology which is an issue, TETRA has many functionalities that would need to be duplicated in LTE.



As you can see from this timeline above, while Rel-13 and Rel-14 will have some of these features, there are still other features that need to be included. Without which, safety of the critical communication workers and public could be compromised.

The complete presentation as follows. Feel free to voice your opinions via comments.


Sunday 10 May 2015

LTE-Broadcast making a push while Terrestrial broadcast still popular as ever



"TV isn't dying, it's having babies." This quote made my day. I have argued a few times in the past that terrestrial broadcasting will continue working and will be probably the most popular approach for a long time to come. The way things work with it may change. Multi-screen is one possible approach but you may have more interactions like 'red button functionality', etc.
Anyway, in Europe 800MHz spectrum has been cleared for use by Mobile Broadband technologies (LTE mainly). 700MHz is planned to be cleared as well by 2020, as per the suggestion in Lamy report. The other UHF band from 470MHz to 694MHz would be left as it is until 2030, with a review planned in 2025.

This has forced even big players like BBC to start looking at other mechanisms to deliver TV. While BBC3 was moved to online only, BBC is also exploring how to use LTE-Multicast to deliver content. It has been working to have its very popular iPlayer work with eMBMS.

Embedded below is a presentation from Cambridge Wireless CWTEC 2015 conference.




eMBMS is gaining popularity with its presence in lot more chipsets and even more trials. GSA report has shown that there are quite a few trials going on worldwide but the question remains about the business models. Most operators would not like to become content providers and compete with the incumbents in their markets. Having someone like BBC in the UK is helpful but not sure how many such options are available worldwide. Embedded below is the GSA presentation




There were some nice pictures from MWC as can be seen above. Ericsson has a video as well (below) on how the app works.



D-Link is also working on M2M modules that could be used in billboards to dynamically update the ads at very regular intervals. There is a video here that explains this further.

Finally here is a Video from Visteon/Verizon that explains how LTE-Multicast can be used to deliver software updates in the connected car:



Finally, here are couple of presentations that may interest you too:



Monday 4 May 2015

New LTE UE Categories: 11, 12, 13 and 14 in 3GPP Rel-12

While checking 3GPP TS 36.306, I noticed some new LTE categories have been defined. We now have all the way up to category 14. I also noticed that Wikipedia page has up to Category 15, not sure how/where they got it from. 


The LG Space page has some more details for anyone interested in exploring further.

A Qualcomm demo from MWC for LTE Category 11, if interested.



Finally, other related posts:


Sunday 19 April 2015

3GPP Release-13 work started in earnest


The 3GPP news from some months back listed the main RAN features that have been approved for Release-13 and the work has already started on them. The following are the main features (links contain .zip files):

  • LTE in unlicensed spectrum (aka Licensed-Assisted Access) - RP-150055
  • Carrier Aggregation enhancements - RP-142286
  • LTE enhancements for Machine-Type Communications (MTC) - RP-141865
  • Enhancements for D2D - RP-142311
  • Study Item Elevation Beamforming / Full-Dimension MIMO - RP-141831
  • Study Item Enhanced multi-user transmission techniques - RP-142315
  • Study Item Indoor positioning - RP-141102
  • Study Item Single-cell Point-to-Multipoint (SC-PTM) - RP-142205


Another 3GPP presentation from late last year showed the system features that were being planned for Rel-13 as shown above.

I have also posted a few items earlier relating to Release13, as follows:


Ericsson has this week published a whitepaper on release 13, with a vision for 'Networked Society':
The vision of the Networked Society, where everything that benefits from being connected will be connected, places new requirements on connectivity. LTE is a key component in meeting these demands, and LTE release 13 is the next step in the LTE evolution.
Their whitepaper embedded below:



It should be pointed out that 5G work does not start until Release-15 as can be seen from my tweet

xoxoxo Added Later (26/04/2015) xoxoxo
I came across this presentation from Keysight (Agilent) where Moray Rumney has provided information in much more detail.


Sunday 12 April 2015

LTE-Hetnet (LTE-H) a.k.a. LTE Wi-Fi Link Aggregation (LWA)


We have talked about the unlicensed LTE (LTE-U), re-branded as LTE-LAA many times on this blog and the 3G4G Small Cells blog. In fact some analysts have decided to call the current Rel-12 non-standardised Rel-12 version as LTE-U and the standardised version that would be available as part of Release-13 as LTE-LAA.

There is a lot of unease in the WiFi camp because LTE-LAA may hog the 5GHz spectrum that is available as license-exempt for use of Wi-Fi and other similar (future) technologies. Even though LAA may be more efficient as claimed by some vendors, it would reduce the usage for WiFi users in that particular spectrum.

As a result, some vendors have recently proposed LTE/WiFi Link Aggregation as a new feature in Release-13. Alcatel-Lucent, Ruckus Wireless and Qualcomm have all been promoting this. In fact Qualcomm has a pre-MWC teaser video on Youtube. The demo video is embedded as follows:



The Korean operator KT was also involved in demoing this in MWC along with Samsung and Qualcomm. They have termed this feature as LTE-Hetnet or LTE-H.

The Korean analyst firm Netmanias have more detailed technical info on this topic.

Link aggregation by LTE-H demonstrated at MWC 2015 (Source: Netmanias)

As can be seen the data is split/combined in PDCP layer. While this example above shows the practical implementation using C-RAN with Remote Radio Head (RRH) and BaseBand Unit (BBU) being used, the picture at the top shows LTE Anchor in eNodeB. There would be a need for an ideal backhaul to keep latency in the eNodeB to minimum when combining cellular and WiFi data.

Comparison of link level Carrier Aggregation technologies (Source: Netmanias)

The above table shows comparison between the 3 main techniques for increasing data rates through aggregation; CA, LTE-U/LAA and LTE-H/LWA. While CA has been part of 3GPP Release-10 and is available in more of less all new LTE devices, LTE-U and LTE-H is new and would need modifications in the network as well as in the devices. LTE-H would in the end provide similar benefits to LTE-U but is a safer option from devices and spectrum point of view and would be a more agreeable solution by everyone, including the WiFi community.

A final word; last year we wrote a whitepaper laying out our vision of what 4.5G is. I think we put it simply that in 4.5G, you can use WiFi and LTE at the same time. I think LTE-H fulfills that vision much better than other proposals.

Sunday 15 March 2015

Air-Ground-Air communications in Mission Critical scenarios

In-flight communications have always fascinated me. While earlier the only possibility was to use Satellites, a hot topic for in the last few years has been Air-Ground-Air communications.

Some of you may remember that couple of years back Ericsson showed an example of using LTE in extreme conditions. The video below shows that LTE can work in these scenarios.



Now there are various acronyms being used for these type of communications but the one most commonly used is Direct-Air-to-Ground Communications (DA2GC), Air-to-Ground (A2G) and Ground-to-Air (G2A).


While for short distance communications, LTE or any cellular technology (see my post on Flying Small Cells) may be a good option, a complete solution including communication over sea would require satellite connectivity as well. As I have mentioned in a blog post before, 75Mbps connectivity would soon be possible with satellites.

For those interested in working of the Air-Ground-Air communications, would find the presentation below useful. A much detailed ECC CEPT report from last year is available here.



The next challenge is to explore whether LTE can be used for Mission Critical Air Ground Air communications. 3GPP TSG RAN recently conducted study on the feasibility and the conclusions are as follows:

There is a common understanding from companies interested in the topic that:

  1. Air-to-Ground communications can be provided using the LTE standards (rel-8 and beyond depending on the targeted scenarios).
  2. 3GPP UE RF requirements might need to be adapted
  3. It may be possible to enhance the performance of the communications with some standards changes, but these are in most cases expected to be non-fundamental optimizations
  4. Engineering and implementation adaptations are required depending on the deployment scenario. In particular, the ECC report [1] comments that from implementation point of view synchronization algorithms are to be modified compared to terrestrial mobile radio usage in order to cope with high Doppler frequency shift of the targeted scenario. In addition, some network management adaptations might be needed. From engineering perspective the Ground base station antenna adjustment has to be matched to cover indicated aircraft heights above ground up to 12 km by antenna up-tilt. It is also expected that the inter-site distances would be dominated by the altitudes to be supported [5].
  5. A2G technology using legacy LTE has been studied and successfully trialed covering different kinds of services: Surfing, downloading, e-mail transmission, use of Skype video, audio applications and Video conferencing. Related results can be found in several documents from ECC and from companies [1], [2], [3]. The trials in [1] and [2] assumed in general a dedicated spectrum, and the fact that the communications in the aircraft cabin are using WIFI or GSMOBA standards, while LTE is used for the Broadband Direct-Air-to-Ground connection between the Aircraft station and the Ground base station.
  6. It is understood that it is possible to operate A2G communications over spectrum that is shared with ground communications. However, due to interference it is expected that the ground communications would suffer from capacity losses depending on the deployment scenario. Therefore, it is recommended to operate A2G communication over a dedicated spectrum.
  7. It can be noted that ETSI studies concluded that Spectrum above 6 GHz is not appropriate for such applications [4].
  8. LTE already provides solutions to allow seamless mobility in between cells. Cells can be intended for terrestrial UEs and cells intended for A2G UEs which might operate in different frequencies.
  9. Cell range in LTE is limited by the maximum timing advance (around 100km). Larger ranges could be made possible by means of implementation adaptations. 

Sunday 8 March 2015

LTE Category-0 low power M2M devices


While we have talked about different LTE categories, especially higher speeds, we have not yet discussed Category-0 or Cat-0 for M2M.

A recent news report stated the following:

CAT-1 and CAT-0 are lower speed and power versions of the LTE standard which dramatically extend the addressable market for carriers and chip makers alike. They introduce new IoT targeted features, extend battery operation and lower the cost of adding LTE connectivity.
“While chipsets supporting these lower categories are essential for numerous applications, including wearable devices, smart home and smart metering, there has been an industry development gap that we had anticipated two years ago,” said Eran Eshed, co-founder and vice president of marketing and business development at Altair. “We’ve worked hard to address this gap by being first to market with true CAT-1 and 0 chipsets featuring a power/size/cost combination that is a massive game-changer.”
Ericsson has an interesting presentation that talks about LTE evolution for cellular IoT. While Rel-12 Cat-0 would use the normal allocated bandwidth (upto 20MHz), Rel-13 plans further enhancements to save even more power by reducing the bandwidth to 1.4Mhz. Another possible saving of power comes from the use of Half Duplex (but its optional). There is a very interesting presentation from Mstar semiconductors on half duplex that I have blogged about here. Anyway, the presentation from Ericsson is here:



When we talk about 50 billion M2M devices, a question that I regularly ask is how many of them will be using cellular and how many will use other technologies. Its good to see that my skepticism is shared by others as well, see the tweet below.

Click on the pic.twitter.com/Z7s6wqxkBM to see the actual media.

Nokia has also got an interesting whitepaper on this topic which talks about optimizing LTE and the architectural evolution that will lead cellular LTE to become a compelling technology so that it can be widely adopted. That paper is embedded as well below.



Sunday 1 March 2015

Monday 23 February 2015

Static/Dynamic IP Address Allocation in LTE


I recently came across a discussion on how static and dynamic IP address are allocated in LTE for a UE. Luckily, there is a recent document from Netmanias that discussed this topic. The document is embedded below.



If you enjoyed reading the document (part 1) above, then there is a part 2 here. While in part 1, we saw that IP addresses can be either dynamic or static depending on their allocators, part 2 presents a specific case of IP address allocation – allocation in geographically-separated locations within an LTE network. In case of dynamic allocation, no matter where a user accesses, a dynamically selected P-GW dynamically allocates an IP address to the user for PDN connection. In case of static allocation, however, there is always one specific P-GW and one IP address for a user - the designated P-GW allocates a static IP address for the user’s PDN connection. A case study shows an LTE network that serves two cities as an example to describe different ways and procedures of IP address allocation, and see how they are different from each other.

Wednesday 21 January 2015

Voice over WiFi (VoWiFi) technical details

VoWiFi is certainly a hot topic, thanks to the support of VoWiFi on iPhone 6. A presentation from LTE World Summit 2014 by Taqua on this topic has already crossed 13K views. In this post I intend to look at the different approaches for VoWiFi and throw in some technical details. I am by no means an expert so please feel free to add your input in the comments.

Anybody reading this post is not aware of S2a, S2b, Samog, TWAG, ePDG, etc. and what they are, please refer to our whitepaper on cellular and wi-fi integration here (section 3).

There are two approaches to VoWiFi, native client already in your device or an App that could be either downloaded from the app store or pre-installed. The UK operator '3' has an app known as ThreeInTouch. While on WiFi, this app can make and receive calls and texts. The only problem is that it does not handover an ongoing call from WiFi to cellular and and vice versa. Here are a few slides (slides 36-38) from them from a conference last year:



The other operators have a native client that can use Wi-Fi as the access network for voice calls as well as the data when the device is connected on the WLAN.

A simple architecture can be seen from the picture above. As can be seen, the device can connect to the network via a non-3GPP trusted wireless access network via the TWAG or via a non-3GPP untrusted wireless access network via ePDG. In the latter case, an IPSec tunnel would have to be established between the device and the ePDG. The SIM credentials would be used for authentication purposes so that an intruder cannot access ePDG and the core.

Now, I dont want to talk about VoLTE bearers establishment, etc. which I have already done here earlier. In order to establish S2a (trusted) and S2b (untrusted) connection, the AAA server selects an APN among those which are subscribed to in the HLR/HSS. The PDN-GW (generally referred to as PGW) dynamically assigns an IP address out of a pool of addresses which is associated with this APN. This UE IP address is used by the VoWiFi SIP UA (User Agent) as the contact information when registering to the SIP soft switch (which would typically be the operators IMS network).

If for any reason the SIP UA in the device is not able to use the SIM for authentication (needs ISIM?) then a username/password based authentication credentials can be used (SIP digest authentication).

Typically, there would be a seperate UA for VoLTE and VoWiFi. They would both be generally registering to the same IMS APN using different credentials and contact addresses. The IMS network can deal with multiple registrations from the same subscriber but from different IP addresses (see 3GPP TS 23.237 - 'IMS Service Continuity' for details).

Because of multiple UA's, a new element needs to be introduced in order to 'fork' the downstream media streams (RTP/RTCP packets) to different IP addresses over time.

3GPP has defined the Access Transfer Gateway (ATGW) which is controlled by the Access Transfer Control Function (ATCF); the ATCF interfaces to the IMS and Service Centralization and Continuity Application Server (SCC AS). All these are not shown in the picture above but is available in 3GPP TS 23.237. The IMS networks in use today as well as the one being deployed for VoLTE does not have ATGW/ATCF. As a result vendors have to come up with clever non-standardised solutions to solve the problem.

When there is a handover between 3GPP and non-3GPP networks, the UE IP address needs to be preserved. Solutions like MIP and IPSec have been used in the past but they are not flexible. The Release-12 solution of eSAMOG (see 3GPP TS 23.402) can be used but the solution requires changes in the UE. For the time being we will see proprietary solutions only but hopefully in future there would be standardised solutions available.

3GPP TS 23.234 describes more in detail the interworking of 3GPP based system and WLAN. Interested readers can refer to that for further insight.

Friday 21 November 2014

In-flight broadband connectivity service with speeds up to 75Mbps


Came across the following Inmarsat press release:

The new network represents two world-beating achievements for Inmarsat and its partners. It will be the world’s first truly hybrid aviation network, consisting of an S-band satellite (Europasat), constructed by Thales Alenia Space, and a Europe-wide S-band ground network. Over the integrated network, based on state-of-the-art LTE technology and access to sufficient spectrum resources, Inmarsat will be offering airlines the world’s fastest in-flight broadband connectivity service with speeds up to 75Mbps, far in excess of the limited capabilities of North American ATG systems.
Alcatel-Lucent and Inmarsat will work together to develop the ground infrastructure component of the new Europe-wide network. Alcatel-Lucent has proven expertise in the development of 4G LTE-based air-to-ground technology and was the world’s first company to field trial this technology in 2011. The initial contract awarded to Alcatel-Lucent will see the global telecommunications equipment company adapting their existing 4G LTE technology to support the S-band spectrum.
Recently Christophe WILHELM, Senior VP Strategy & Innovation, Thales Alenia Space gave a presentation in the Digiworld Summit 2014.



His presentation is above and the video is as follows. Please forward to 1:36:00 to watch his part



Wednesday 5 November 2014

2015 will finally be the year of Voice over LTE (VoLTE)


On 4th Nov. 2009, the One Voice initiative was published by 12 companies including AT&T, Orange, Telefonica, TeliaSonera, Verizon, Vodafone, Alcatel-Lucent, Ericsson, Nokia Siemens Networks, Nokia, Samsung and Sony Ericsson. These all agreed that the IMS based solution, as defined by 3GPP, is the most applicable approach to meet their consumers expectations for service quality, reliability and availability when moving from existing CS based voice services to IP based LTE services.

On 15th Feb 2010, GSMA announced that it has adopted the work of the One Voice initiative to drive the global mobile industry towards a standard way of delivering voice and messaging services for LTE. The GSMA’s VoLTE initiative was supported by more than 40 organisations from across the mobile ecosystem, including many of the world’s leading mobile communication service providers, handset manufacturers and equipment vendors, all of whom support the principle of a single, IMS-based voice solution for next-generation mobile broadband networks. This announcement was also supported by 3GPP, Next Generation Mobile Networks alliance (NGMN) and the International Multimedia Teleconferencing Consortium (IMTC).

GSMA has produces various reference documents that map to the 3GPP standards documents as can be seen above.



As per GSA71 operators are investing in VoLTE studies, trials or deployments, including 11 that have commercially launched HD voice service. The number of HD voice launches enabled by VoLTE is forecast to reach 19 by end-2014 and then double in 2015. In July 2014 GSA confirmed 92 smartphones (including carrier and frequency variants) support VoLTE, including products by Asus, Huawei, LG, Pantech, Samsung and Sony Mobile. The newly-announced Apple iPhone 6 & 6 Plus models support VoLTE.

Things are also moving quickly with many operators who have announced VoLTE launches and are getting more confident day by day. Du, Dubai recently announced Nokia as VoLTE partner. KDDI, Japan is launching au VoLTE in December. Telstra, Australia has already been doing trials and plans to launch VoLTE network in 2015. Finally, Verizon and AT&T will have interoperable VoLTE calls in 2015.

Below is my summary from the LTE Voice Summit 2014. Let me know if you like it.


Saturday 1 November 2014

4G Security and EPC Threats for LTE

This one is from the LTE World Summit 2014. Even though I was not there for this, I think this has some useful information about the 4G/LTE Security. Presentation as follows:


Sunday 19 October 2014

What is (pre-5G) 4.5G?

Before we look at what 4.5G is, lets look at what is not 4.5G. First and foremost, Carrier Aggregation is not 4.5G. Its the foundation for real 4G. I keep on showing this picture on Twitter


I am sure some people much be really bored by this picture of mine that I keep showing. LTE, rightly referred to as 3.9G or pre-4G by the South Korean and Japanese operators was the foundation of 'Real' 4G, a.k.a. LTE-Advanced. So who has been referring to LTE-A as 4.5G (and even 5G). Here you go:


So lets look at what 4.5G is.
Back in June, we published a whitepaper where we referred to 4.5G as LTE and WiFi working together. When we refer to LTE, it refers to LTE-A as well. The standards in Release-12 allow simultaneous use of LTE(-A) and WiFi with selected streams on WiFi and others on cellular.


Some people dont realise how much spectrum is available as part of 5GHz, hopefully the above picture will give an idea. This is exactly what has tempted the cellular community to come up with LTE-U (a.k.a LA-LTE, LAA)

In a recent event in London called 5G Huddle, Alcatel-Lucent presented their views on what 4.5G would mean. If you look at the slide above, it is quite a detailed view of what this intermediate step before 5G would be. Some tweets related to this discussion from 5G Huddle as follows:


Finally, in a recent GSMA event, Huawei used the term 4.5G to set out their vision and also propose a time-frame as follows:



While in Alcatel-Lucent slide, I could visualise 4.5G as our vision of LTE(-A) + WiFi + some more stuff, I am finding it difficult to visualise all the changes being proposed by Huawei. How are we going to see the peak rate of 10Gbps for example?

I have to mention that I have had companies that have told me that their vision of 5G is M2M and D2D so Huawei is is not very far from reality here.

We should keep in mind that this 4G, 4.5G and 5G are the terms we use to make the end users aware of what new cellular technology could do for them. Most of these people understand simple terms like speeds and latency. We may want to be careful what we tell them as we do not want to make things confusing, complicated and make false promises and not deliver on them.

xoxoxo Added on 2nd January 2015 oxoxox

Chinese vendor ZTE has said it plans to launch a ‘pre-5G’ testing base station in 2015, commercial use of which will be possible in 2016, following tests and adjustment. Here is what they think pre-5G means:


Thursday 18 September 2014

Update on Public Safety and Mission Critical communications

Its been a while since I wrote about Public Safety and Mission Critical communications, so here is a quick summary.


Iain Sharp have a good overview of whats happening in the standards in the LTE World Summit back in June. Embedded below is his complete presentation.



There is another slightly older presentation that I also thought was worthwhile adding here.

There is a lot of discussion centred around the use of commercial networks for mission critical communications, mainly die to cost. While this may make sense to an extent, there should be procedures put in place to give priority to public safety in case of emergency.



We are planning to run a one day training in Jan 2015 on public safety. If this is of interest to you then please get in touch with me for more details.

x-o-x-o-x-o-x-o-x-o-x-o-x
After the post someone brought these links to my attention so I am adding them below:

Tuesday 9 September 2014

LTE Device-to-device (D2D) Use Cases

Device-to-device is a popular topic. I wrote a post, back in March on LTE-Radar (another name) which has already had 10K+ views. Another post in Jan, last year has had over 13K views. In the LTE World Summit, Thomas Henze from Deutsche Telekom AG presented some use cases of 'proximity services via LTE device broadcast'


While there are some interesting use cases in his presentation (embedded below), I am not sure that they will necessarily achieve success overnight. While it would be great to have a standardised solution for applications that rely on proximity services, the apps have already come up with their own solutions in the meantime.

Image iTunes

The dating app Tinder, for example, finds a date near where you are. It relies on GPS and I agree that some people would say that GPS consumes more power but its already available today.



Another example is "Nearby Friends" from Facebook that allows to find your friends if they are nearby, perfect for a day when you have nothing better to do.

With an App, I can be sure that my location is being shared only for one App. With a standardised solution, all my Apps have info about location that I may not necessarily want. There are pros and cons, not sure which will win here.

Anyway, the complete presentation is embedded below:



For anyone interested in going a bit more in detail about D2D, please check this excellent article by Dr. Alastair Bryon, titled "Opportunities and threats from LTE Device-to-Device (D2D) communication"

Do let me know what you think about the use cases.

Sunday 24 August 2014

New LTE-A UE Category 9 and 10 in Rel-11

Its been a while since we saw any new UE categories coming but then I noticed some new categories came earlier this year for Release-11. The latest 3TPP TS 36.306 have these new Category 9 and Category 10 as follows.
For those who are aware of the categories of the UE's being used in practice may be aware that the most common ones have been 'Category 3' with 100Mbps max in DL and 50Mbps max in UL. The new 'Cat. 4' devices are becoming more common as more manufacturers start bringing these devices to the market. They support 150Mbps max in DL and 50Mbps max in UL. Neither of them supports Carrier Aggregation.

Having said that, a lot of Cat. 4 devices that we may use in testing actually supports carrier aggregation. The next most popular devices soon to be hitting the market is Cat. 6 UE's with 300Mbps max in DL and 50Mbps max in UL. Category 6 UE's support 2 x 20MHz CA in downlink hence you can say that they can combine 2 x Cat. 4 UE's in DL but they do not support CA in uplink hence the UL part remains the same as Cat. 4 device.

Cat. 9 and 10 are interesting case as Car. 8 was already defined earlier to meet IMT-A requirement as shown below.


To meet IMT-A requirements of peak data rates of 1Gbps in UL and DL, LTE-A had to define category 8 with 5 band CA and 8x8 MIMO to be able to provide 3Gbps max in DL and 1.5Gbps max in UL. No one sees this device becoming a reality in the short term.

The new categories will have to be defined from Cat. 9 onwards.

Cat. 9 allows 3 x Cat. 4 device CA in the downlink to have the maximum possible downlink data rates of 450Mbps but there is no CA in the uplink. As a result, the UL is still 50Mbps max. Cat. 10 allows carrier aggregation in the uplink for upto 2 bands which would result in 100Mbps max in UL.

The LG space website gives a better representation of the same information above which is shown below:



A UE category 9 transmits Rel 11 category 9 + Rel 10 category 6 + Rel 8 category 4

With Release-12 due to be finalised later in the year, we may see new UE categories being defined further.