enhanced Public Warning System (ePWS) in 3GPP Release-16

I wrote about PWS 9 years back here. Since then there has been little chance to PWS until recently. According to 3GPP News:

Additional requirements for an enhanced Public Warning System (ePWS) have been agreed at the recent 3GPP TSG SA#79 meeting, as an update to Technical Specification (TS) 22.268.

3GPP Public Warning Systems were first specified in Release 8, allowing for direct warnings to be sent to mobile users on conventional User Equipment (PWS-UE), capable of displaying a text-based and language-dependent Warning Notification.

Since that time, there has been a growth in the number of mobile devices with little or no user interface - including wrist bands, sensors and cameras – many of which are not able to display Warning Notifications. The recent growth in the number of IoT devices - not used by human users – also highlights the need for an alternative to text based Warning Notifications. If those devices can be made aware of the type of incident (e.g. a fire or flood) in some other way than with a text message, then they may take preventive actions (e.g. lift go to ground floor automatically).

3GPP SA1 delegates also considered how graphical symbols or images can now be used to better disseminate Warning Notifications, specifically aimed at the following categories of users:

• Users with disabilities who have UEs supporting assistive technologies beyond text assistive technologies; and
• Users who are not fluent in the language of the Warning Notifications.

Much of the work on enhancing the Public Warning System is set out in the ePWS requirements specification: TS 22.268 (SA1). You should also keep an eye on the 3GPP protocol specifications (CT1, Stage 3 work) in Release 16, covering:

• Specifying Message Identifiers for ePWS-UE, especially IoT devices that are intended for machine type communications
• Enabling language-independent content to be included in Warning Notifications

The work on ePWS in TS 22.268 (Release 16) is expected to help manufacturers of User Equipment meet any future regulatory requirements dedicated to such products.

Related Specs:

• 3GPP TR 22.869: Feasibility study on enhancements of Public Warning System; Stage 1
• 3GPP TS 22.268: Public Warning System (PWS) requirements - Stage 1 for Public Warning System
• 3GPP TS 23.041: Technical realization of Cell Broadcast Service (CBS) - CT1 aspects of Stage 3 for Public Warning System 
• 3GPP TS 29.168: Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage 3 - CT4 aspects of Stage 3 for Public Warning System

Further reading:

• 3GPP: Towards a better Public Warning System (ePWS)
• 3G4G Blog: Public Warning System (PWS) in Release-9

Tutorial: Service Based Architecture (SBA) for 5G Core (5GC)

As a continuation of 'Control and User Plane Separation of EPC nodes (CUPS) in 3GPP Release-14', here is another tutorial on Service Base Architecture (SBA) for the 5G Core.

The slides (with video) is embedded below but there are quite a few tutorials on 5G available on 3G4G page here.

Advanced: 5G Service Based Architecture (SBA) from 3G4G

Further Reading:

• Control and User Plane Separation of EPC nodes (CUPS) in 3GPP Release-14
• 3GPP 5G Specifications
• 5G - 3G4G Webpage
• 2G, 3G, 4G & 5G Training and Tutorial Videos - 3G4G Webpage

QUIC - Possibly in 5G, 3GPP Release-16

Over the last year or so, I have heard quite a few discussions and read many articles around why QUIC is so good and why we will replace TCP with QUIC (Quick UDP Internet Connection). One such article talking about QUIC benefits says:

QUIC was initially developed by Google as an alternative transport protocol to shorten the time it takes to set up a connection. Google wanted to take benefits of the work done with SPDY, another protocol developed by Google that became the basis for the HTTP/2 standard, into a transport protocol with faster connection setup time and built-in security. HTTP/2 over TCP multiplexes and pipelines requests over one connection but a single packet loss and retransmission packet causes Head-of-Line Blocking (HOLB) for the resources that were being downloaded in parallel. QUIC overcomes the shortcomings of multiplexed streams by removing HOLB. QUIC was created with HTTP/2 as the primary application protocol and optimizes HTTP/2 semantics.

What makes QUIC interesting is that it is built on top of UDP rather than TCP. As such, the time to get a secure connection running is shorter using QUIC because packet loss in a particular stream does not affect the other streams on the connection. This results in successfully retrieving multiple objects in parallel, even when some packets are lost on a different stream. Since QUIC is implemented in the userspace compared to TCP, which is implemented in the kernel, QUIC allows developers the flexibility of improving congestion control over time, since it can be optimized and better replaced compared to kernel upgrades (for example, apps and browsers update more often than OS updates).

Georg Mayer mentioned about QUIC in a recent discussion with Telecom TV. His interview is embedded below. Jump to 5:25 for QUIC part only

Georg Mayer, 3GPP CT work on 5G from 3GPPlive on Vimeo.

Below are some good references about QUIC in case you want to study further.

• IETF QUIC Charter
• Youtube: QUIC Next generation multiplexed transport over UDP - Google
• Understanding QUIC wire protocol - Anuradha Niroshan
• HTTP/2 and QUICK protocols. Optimizing the Web stack for HTTP/2 era
• Measuring QUIC vs TCP on mobile and desktop

3GPP-VRIF workshop on Virtual Reality Ecosystem & Standards in 5G

Its been a year since I last posted about Augmented / Virtual Reality Requirements for 5G. The topic of Virtual Reality has since made good progress for 5G. There are 2 technical reports that is looking at VR specifically. They are:

• 3GPP TR 26.918: Virtual Reality (VR) media services over 3GPP
• 3GPP TR 26.929: QoE parameters and metrics relevant to the Virtual Reality user experience

The second one is work in progress though. 

Anyway, back in Dec. 3GPP and Virtual Reality Industry Forum (VRIF) held a workshop on VR Ecosystem & Standards. All the materials, including agenda is available here. The final report is not there yet but I assume that there will be a press release when the report is published.

While there are some interesting presentations, here is what I found interesting:

From presentation by Gordon Castle, Head of Strategy Development, Ericsson

From presentation by Martin Renschler, Senior Director Technology, Qualcomm

For anyone wanting to learn more about 6 degrees of freedom (6- DoF), see this Wikipedia entry. According to the Nokia presentation, Facebook’s marketing people call this “6DOF;” the engineers at MPEG call it “3DOF+.”

XR is 'cross reality', which is any hardware that combines aspects of AR, MR and VR; such as Google Tango.

From presentation by Devon Copley, Former Head of Product, Nokia Ozo VR Platform

Some good stuff in the pres.

From presentation by Youngkwon Lim, Samsung Research America; the presentation provided a link to a recent YouTube video on this presentation. I really liked it so I am embedding that here:



Finally, from presentation by Gilles Teniou, SA4 Vice chairman - Video SWG chairman, 3GPP

You can check and download all the presentations here.

Further Reading:

• 3GPP 5G Specifications

Satellites & Non-terrestrial networks (NTN) in 5G

Satellites has been an area of interest of mine for a while as some of you know that I used to work as Satellite Applications & Services Programme manager at techUK. I have written about how I see satellites complementing the mobile networks here and here.

Pic Source: The Role of Satellite in 5G - SES

Its good to see that there is some activity in 3GPP going on about satellites & Non-terrestrial networks (NTN) in 5G. While there are some obvious roles that satellites can play (see pic above), the 5G work is looking to cover a lot more topics in details.

Pic Source: Nomor - Overview 3GPP 5G Satellite Activities, Oct 2017

3GPP TR 38.913: Study on scenarios and requirements for next generation access technologies looks at 12 different scenarios, the ones relevant to this topic ate Air to ground, Light aircraft and Satellite to terrestrial.

3GPP TR 38.811: Study on New Radio (NR) to support non terrestrial networks (Release 15) covers this topic a bit more in detail. From looking at how satellites and other aerial networks work in general, it looks at the different NTN architecture options as can be seen above.

People looking to study this area in detail should probably start looking at this TR first.

3GPP also released a news item on this topic last week. It also refers to the above TR and a new one for Release 16. The following from 3GPP news:

The roles and benefits of satellites in 5G have been studied in 3GPP Release 14, leading to the specific requirement to support satellite access being captured in TS 22.261 - “Service requirements for next generation new services and markets; Stage 1”, recognizing the added value that satellite coverage brings, as part of the mix of access technologies for 5G, especially for mission critical and industrial applications where ubiquitous coverage is crucial.

Satellites refer to Spaceborne vehicles in Low Earth Orbits (LEO), Medium Earth Orbits (MEO), Geostationary Earth Orbit (GEO) or in Highly Elliptical Orbits (HEO).

Beyond satellites, Non-terrestrial networks (NTN) refer to networks, or segments of networks, using an airborne or spaceborne vehicle for transmission. Airborne vehicles refer to High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) - including tethered UAS, Lighter than Air UAS and Heavier than Air UAS - all operating at altitude; typically between 8 and 50 km, quasi-stationary.

These Non-terrestrial networks feature in TSG RAN’s TR 38.811 “Study on NR to support non-terrestrial networks”. They will:

• Help foster the 5G service roll out in un-served or underserved areas to upgrade the performance of terrestrial networks
• Reinforce service reliability by providing service continuity for user equipment or for moving platforms (e.g. passenger vehicles-aircraft, ships, high speed trains, buses)
• Increase service availability everywhere; especially for critical communications, future railway/maritime/aeronautical communications
• Enable 5G network scalability through the provision of efficient multicast/broadcast resources for data delivery towards the network edges or even directly to the user equipment

The objective of TR 38.811 is to study channel models, to define the deployment scenarios as well as the related system parameters and to identify and assess potential key impact areas on the NR. In a second phase, solutions for the identified key impacts on RAN protocols/architecture will be evaluated and defined.

A second study item, the “Study on using Satellite Access in 5G” is being addressed in Working Group SA1.  It shall lead to the delivery of the corresponding Technical Report TR 22.822 as part of Release 16.

This study will identify use cases for the provision of services when considering the integration of 5G satellite-based access components in the 5G system. When addressing the integration of (a) satellite component(s), use cases will identify new potential requirements for 5G systems addressing:

• The associated identification of existing / planned services and the corresponding modified or new requirements
• The associated identification of new services and the corresponding requirements
• The requirements on set-up / configuration / maintenance of the features of UE’s when using satellite components related features as well for other components from the 5G system
• Regulatory requirements when moving to (or from) satellite from (or to) terrestrial networks

Related Posts:

• An Introduction to Non-Terrestrial Networks (NTN)
• Connectivity on Planes
• Connectivity Technology Blog: TIP has launched 'Non-Terrestrial Connectivity Solutions' Group
• 3G4G Small Cells Blog: Flying Small Cells are here...

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

3GPP held a 5G Workshop in Phoenix last week. 550 delegates and over 70 presentations contributed to the discussion, which covered the full range of requirements that will feed TSG RAN work items for the next five years. I will eventually look at all the presentations and highlight the ones that I find interesting as a part of this blog. Due to the vast number of presentations, I will split them into a few blog posts.

Lets start with the chairman summary. The chair highlighted three high level use cases that 5G needs to address (This has been highlighted in many presentations, see here for example):

• Enhanced Mobile Broadbandare 
• Massive Machine Type Communications
• Ultra-reliable and Low Latency Communications

As can be seen in the picture above, 3GPP is planning to split the 5G work into two phases. Phase 1 (Rel-15) will look at a subset of requirements that are important for the commercial needs of the day. Phase 2 (Rel-16) will look at more features, use cases, detailed requirements, etc.

Here is the chair summary of the workshop:

The presentation (RWS-150002) from Motorola/Lenovo highlighted the need to handle different spectrum. For sub-6GHz, the existing air interface could work with slight modifications. For spectrum between 6GHz and 30GHz, again a similar air interface like 4G may be good enough but for above 30GHz, there is a need for new one die to phase noise.

The presentation by CATT or China Academy of Telecommunication Technology (RWS-150003) is quite interesting and is embedded below. They also propose Pattern Division Multiple Access (PDMA).

Orange (RWS-150004) has definitely put a thought into what good 5G would be. Their presentation is embedded below too:

The presentation from Huawei (RWS-150006) introduced the concept of Unified Air Interface, UAI.



They presentation also explains the concept of Adaptive Frame structures and RAN slicing very well. For those who may be wondering, uMTC stands for ultra-reliable MTC and mMTC stands for massive MTC. RAN slicing enables the RAN to be partitioned such that a certain amount of carriers are always dedicated to a certain services independently of other services. This ensures that the service in the slice is always served reliably.

The final presentation is the vision and priorities by 5GPPP as follows: