Pages

Showing posts with label KT. Show all posts
Showing posts with label KT. Show all posts

Saturday, 12 November 2016

Verizon's 5G Standard

Earlier this year I wrote a Linkedin post on how operators are setting a timetable for 5G (5G: Mine is bigger than yours) and recently Dean Bubley of Disruptive Analysis wrote a similar kind of post also on Linkedin with a bit more detail (5G: Industry Politics, Use-Cases & a Realistic Timeline)


Some of you may be unaware that the US operator Verizon has formed 'Verizon 5G Technology Forum' (V5GTF) with the intention of developing the first set of standards that can also influence the direction of 3GPP standardization and also provide an early mover advantage to itself and its partners.

The following from Light Reading news summarizes the situation well:

Verizon has posted its second round of work with its partners on a 5G specification. The first round was around the 5G radio specification; this time the work has been on the mechanics of connecting to the network. The operator has been working on the specification with Cisco Systems Inc., Ericsson AB, Intel Corp., LG Electronics Inc., Nokia Corp., Qualcomm Inc. and Samsung Corp. via the 5G Technology Forum (V5GTF) it formed late in 2015.

Sanyogita Shamsunder, director of strategy at Verizon, says that the specification is "75% to 80% there" at least for a "fixed wireless use case." Verizon is aiming for a "friendly, pre-commercial launch" of a fixed wireless pilot in 2017, Koeppe notes.

Before we go further, lets see this excellent video by R&S wherein Andreas Roessler explains what Verizon is up to:



Verizon and SKT are both trying to be the 5G leaders and trying to roll out a pre-standard 5G whenever they can. In fact Qualcomm recently released a 28 GHz modem that will be used in separate pre-standard 5G cellular trials by Verizon and Korea Telecom

Quoting from the EE times article:

The Snapdragon X50 delivers 5 Gbits/second downlinks and multiple gigabit uplinks for mobile and fixed-wireless networks. It uses a separate LTE connection as an anchor for control signals while the 28 GHz link delivers the higher data rates over distances of tens to hundreds of meters.

The X50 uses eight 100 MHz channels, a 2x2 MIMO antenna array, adaptive beamforming techniques and 64 QAM to achieve a 90 dB link budget. It works in conjunction with Qualcomm’s SDR05x mmWave transceiver and PMX50 power management chip. So far, Qualcomm is not revealing more details of modem that will sample next year and be in production before June 2018.

Verizon and Korea Telecom will use the chips in separate trials starting late next year, anticipating commercial services in 2018. The new chips mark a departure from prototypes not intended as products that Qualcomm Research announced in June.

Korea Telecom plans a mobile 5G offering at the February 2018 Winter Olympics. Verizon plans to launch in 2018 a less ambitious fixed-wireless service in the U.S. based on a specification it released in July. KT and Verizon are among a quartet of carriers that formed a group in February to share results of early 5G trials.

For its part, the 3GPP standards group is also stepping up the pace of the 5G standards efforts it officially started earlier this year. It endorsed last month a proposal to consider moving the date for finishing Phase I, an initial version of 5G anchored to LTE, from June 2018 to as early as December 2017, according to a recent Qualcomm blog.

Coming back to Verizon's 5G standard, is it good enough and compatible with 3GPP standards? The answer right now seems to be NO.


The following is from Rethink Wireless:

The issue is that Verizon’s specs include a subcarrier spacing value of 75 kHz, whereas the 3GPP has laid out guidelines that subcarrier spacing must increase by 30 kHz at a time, according to research from Signals Research Group. This means that different networks can work in synergy if required without interfering with each other.

Verizon’s 5G specs do stick to 3GPP requirements in that it includes MIMO and millimeter wave (mmWave). MmWave is a technology that both AT&T and Verizon are leading the way in – which could succeed in establishing spectrum which is licensed fairly traditionally as the core of the US’s high frequency build outs.

A Verizon-fronted group recently rejected a proposal from AT&T to push the 3GPP into finalizing an initial 5G standard for late 2017, thus returning to the original proposed time of June 2018. Verizon was supported by Samsung, ZTE, Deutsche Telecom, France Telecom, TIM and others, which were concerned the split would defocus SA and New Radio efforts and even delay those standards being finalized.

Verizon has been openly criticized in the industry, mostly by AT&T (unsurprisingly), as its hastiness may lead to fragmentation – yet it still looks likely to beat AT&T to be the first operator to deploy 5G, if only for fixed access.

Verizon probably wants the industry to believe that it was prepared for eventualities such as this – prior to the study from Signal Research Group, the operator said its pre-standard implementation will be close enough to the standard that it could easily achieve full compatibility with simple alterations. However, Signals Research Group’s president Michael Thelander has been working with the 3GPP since the 5G standard was birthed, and he begs to differ.

Thelander told FierceWireless, “I believe what Verizon is doing is not hardware-upgradeable to the real specification. It’s great to be trialing, even if you define your own spec, just to kind of get out there and play around with things. That’s great and wonderful and hats off to them. But when you oversell it and call it 5G and talk about commercial services, it’s not 5G. It’s really its own spec that has nothing to do with Release 16, which is still three years away. Just because you have something that operates in millimeter wave spectrum and uses Massive MIMO and OFDM, that doesn’t make it a 5G solution.”

Back in the 3G days, NTT Docomo was the leader in standards and it didn't have enough patience to wait for 3GPP standards to complete. As a result it released its first 3G network called FOMA (Freedom of Mobile Access) based on pre-standard version of specs. This resulted in handset manufacturers having to tweak their software to cope with this version and it suffered from economy of scale. Early version of 3G phones were also not able to roam on the Docomo network. In a way, Verizon is going down the same path.

While there can be some good learning as a result of this pre-5G standard, it may be a good idea not to get too tied into it. A standard that is not compliant will not achieve the required economy of scale, either with handsets or with dongles and other hotspot devices.


Related posts:



Sunday, 25 October 2015

Updates from the 3GPP RAN 5G Workshop - Part 3

Continuing with the updates from 5G RAN workshop, part 1 and part 2 here.
Dish network wants to have a satellite based 5G network. A recent article from Light Reading shows the following:

Dish states that there are misconceptions about what satellite technology can deliver for 5G networks. Essentially Dish says that satellites will be capable of delivering two-way communications to support 5G.

A hybrid ground and space 5G network would use small satellites that each use a "spot beam" to provide a dedicated area of two-way coverage on the ground. This is different than the old model of using one satellite with a single beam to provide a one-way service like a TV broadcast over a landmass.

Dish argues that newer, smaller satellites, equipped with the latest multi-antenna arrays (MIMO) would allow for "ubiquitous connectivity through hybrid satellite and terrestrial networks," the operator writes. In this model, satellites could connect areas that it would be hard to network otherwise like mountains and lakes.

The presentation from Dish is as follows:



Alcatel-Lucent provided a whitepaper along with the presentation. The paper provides an interesting view of 5G from their point of view. Its embedded below:



The presentation from Kyocera focused on TD-LTE which I think will play a prominent role in 5G. In case of wide channels, TD-LTE can help predict the channel accurately, which is a drawback for FDD at high frequencies. Their presentation is available here.

The presentation from NEC focussed on different technologies that will play a role in 5G. Their presentation is available here.
The final presentation we will look at this time is by the South Korean operator, KT. What is interesting to see is that in the part 1 we saw in the chairman's summary that 5G will come in two phases; Rel-15 will be phase 1 and Rel-16 will be phase 2. In the summary slide in KT's presentation, it looks like they are going to consider Rel-14 as 5G. Its not at all surprising considering that Verizon has said that they want to commercialise 5G by 2017, even though 5G will not be fully specified according to 3GPP by then. Anyway, here is the presentation by KT.



Sunday, 12 July 2015

S8HR: Standardization of New VoLTE Roaming Architecture

VoLTE is a very popular topic on this blog. A basic VoLTE document from Anritsu has over 40K views and my summary from last years LTE Voice summit has over 30K views. I assume this is not just due to the complexity of this feature.

When I attended the LTE Voice summit last year, of the many solutions being proposed for roaming, 'Roaming Architecture for Voice over LTE with Local Breakout (RAVEL)' was being touted as the preferred solution, even though many vendors had reservations.

Since then, GSMA has endorsed a new VoLTE roaming architecture, S8HR, as a candidate for VoLTE roaming. Unlike previous architectures, S8HR does not require the deployment of an IMS platform in VPLMN. This is advantageous because it shortens time-to-market and provides services universally without having to depend on the capability of VPLMN.



Telecom Italia has a nice quick summary, reproduced below:

S8HR simplicity, however, is not only its strength but also its weakness, as it is the source of some serious technical issues that will have to be solved. The analysis of these issues is on the Rel13 3GPP agenda for the next months, but may overflow to Rel14. Let’s see what these issues are, more in detail:


Regulatory requirements - S8HR roaming architecture needs to meet all the current regulatory requirements applicable to voice roaming, specifically:
  • Support of emergency calls - The issues in this context are several. For example, authenticated emergency calls rely on the existence if an IMS NNI between VPLMN and HPLMN (which S8HR does not provide); conversely, the unauthenticated emergency calls, although technically feasible in S8HR, are allowed only in some Countries subject to the local regulation of VPLMN. Also, for a non-UE-detectable IMS Emergency call, the P-CSCF in the HPLMN needs to be capable of deciding the subsequent action (e.g. translate the dialed number and progress the call or reject it with the indication to set up an emergency call instead), taking the VPLMN ID into account. A configuration of local emergency numbers per Mobile Country Code on P-CSCF may thus be needed.
  • ­Support of Lawful Interception (LI) & data retention for inbound roamers in VPLMN -  S8HR offers no solution to the case where interception is required in the VPLMN for inbound roamers. 3GPP is required to define a solution that fulfill such vital regulatory requirement, as done today in circuit switched networks. Of course VPLMN and HPLMN can agree in their bilateral roaming agreement to disable confidentiality protection to support inbound roamer LI but is this practice really viable from a regulatory point of view?
Voice call continuity – The issue is that when the inbound roamers lose the LTE coverage to enter into  a 2G/3G CS area, the Single Radio Voice Call Continuity (SRVCC) should be performed involving the HPLMN in a totally different way than current specification (i.e. without any IMS NNI being deployed).
Coexistence of LBO and S8HR roaming architectures will have to be studied since an operator may need to support both LBO and S8HR VoLTE roaming architecture options for roaming with different operators, on the basis of bilateral agreement and depending on the capability.
Other issues relate to the capability of the home based S-CSCF and TAS (Telephony Application Server) to be made aware about the VPLMN identity for charging purposes and to enable the TAS to subsequently perform communication barring supplementary services. Also, where the roaming user calls a geo-local number (e.g. short code, or premium numbers), the IMS entities in HPLMN must do number resolution to correctly route the call.
From preliminary discussions held at Working Group level in SA2 (architecture) and SA3 (security) in April, it was felt useful to create a new 3GPP Technical Report to perform comprehensive technical analysis on the subject. Thus it is expected that the discussions will continue in the next months until the end of 2015 and will overheat Release 13 agenda due to their commercial and “political” nature. Stay tuned to monitor the progress of the subject or contact the authors for further information!
NTT Docomo also did some trials back in February and got some brilliant results:

In the trials, DOCOMO and KT achieved the world's first high-definition voice and video call with full end-to-end quality of service. Also, DOCOMO and Verizon achieved the world's first transoceanic high-definition VoLTE roaming calls. DOCOMO has existing commercial 3G and 4G roaming relations with Verizon Wireless and KT.
The calls were made on an IP eXchange (IPX) and network equipment to replicate commercial networks. With only two months of preparation, which also proved the technology's feasibility of speedy commercialization, the quality of VoLTE roaming calls using S8HR architecture over both short and long distances was proven to be better than that of existing 3G voice roaming services.


In fact, NTT Docomo has already said based on the survery from GSMA's Network 2020 programme that 80% of the network operators want this to be supported by the standards and 46% of the operators already have a plan to support this.


The architecture has the following technical characteristics:
(1) Bearers for IMS services are established on the S8 reference point, just as LTE data roaming.
(2) All IMS nodes are located at Home Public Land Mobile Network (HPLMN), and all signaling and media traffic for the VoLTE roaming service go through HPLMN.
(3) IMS transactions are performed directly between the terminal and P-CSCF at HPLMN. Accordingly, Visited Public Land Mobile Network (VPLMN) and interconnect networks (IPX/GRX) are not service-aware at the IMS level. The services can only be differentiated by APN or QoS levels.

These three technical features make it possible to provide all IMS services by HPLMN only and to minimize functional addition to VPLMN. As a result, S8HR shortens the time-to-market for VoLTE roaming services.

Figure 2 shows the attach procedure for S8HR VoLTE roaming. From Steps 1 to 3, there is no significant difference from the LTE data roaming attach procedure. In Step 4, HSS sends an update location answer message to MME. In order for the MME to select the PGW in HPLMN (Step 5), the MME must set the information element VPLMN Dynamic Address “Allowed,” which is included in the subscribed data, to “Not Allowed.” In Step 6, the bearer for SIP signaling is created between SGW and PGW with QCI=5. MME sends an attach accept message to the terminal with an IMS Voice over PS Session Support Indication information element, which indicates that VoLTE is supported. The information element is set on the basis of the MME’s internal configuration specifying whether there is a VoLTE roaming agreement to use S8HR. If no agreement exists between two PLMNs, the information element will not be set.

The complete article from the NTT Docomo technical journal is embedded



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.

Tuesday, 22 October 2013

Korea Telecom ‘Route Decision System’ for midnight buses

Interesting presentation from Korea Telecom in LTE Asia 2013 about how they use Big Data to decide the night bus routes. Here are two pics which are self explanatory


We will soon start seeing operators using the data being collected from users and this can also be a nice little earner for them.