Showing posts with label Public Safety Comm. Show all posts
Showing posts with label Public Safety Comm. Show all posts

Monday 27 September 2021

Maritime Communication (MARCOM) Services over 3GPP system


Maritime Communication Services over 3GPP System is one of the topics listed in the 3GPP Release-16 summary that I summarised here.

Maritime domain, one of 5G vertical domains in 3GPP, started to be considered since 2016 to enable 3GPP systems to play the role of mobile communication platform necessary for the digitalization and mobilization of the maritime domain that bring about the Fourth Industrial Revolution of the maritime businesses as well as maritime safety.

Compared to other vertical domains, the maritime domain has the radio communication environment that 3GPP hasn’t considered in detail, which means that maritime related issues and features were not in the scope of 3GPP standardization and some of existing 3GPP enabling technologies or solutions are not able to fully support the optimized performances required by the maritime domain in a way that has been guaranteed for on-land communication. In addition, on-board mobile users in a vessel would like to experience the same rich mobile communication services as they enjoy on land.

Furthermore, it is of the view that the capacity and rate for data transmission based on legacy maritime radio communication technologies are indeed not enough for e-Navigation described in IMO Strategy Implementation Plan (SIP) or Maritime Autonomous Surface Ships (MASS), which the International Maritime Organization (IMO), a United Nations specialized agency, have been working to provide to ship.

Considering that the maritime domain is one of 5G vertical domains that 3GPP take into account in order for 5G to be able to provide enhanced mobile broadband services or massive machine-type communication services etc. everywhere anytime in the world, it is desirable to study use cases and requirements for maritime communication services over 3GPP system so that 3GPP system can be a good candidate of innovative tools to help address the information gap between users on land and users at sea as well as the maritime safety and vessel traffic management etc. that IMO intends to achieve especially in 5G era.

3GPP TR 22.819, Feasibility Study on Maritime Communication Services over 3GPP system concluded in 2018 and a report is available here. The scope of the document says:

The present document aims to support the maritime communication services between users ashore and at sea or between vessels at sea over 3GPP system that are targeted to improve maritime safety, protect the maritime environment and promote the efficiency of shipping by reducing maritime casualty caused by human error, in particular, involving small ships and fishing vessels. In addition, the outcome of the technical report is expected to narrow the information gap between mobile users on land and shipboard users on vessels at sea by making it possible to provide the mobile broadband services.

The document describes use cases and potential requirements for services between shore-based users such as authorities and shipboard users in the maritime radio communication environment over 3GPP system. In addition, it deals with use cases to support Mission Critical Services between authorities on land and authorities at sea (e.g. maritime police) as well as use cases to support the interworking between 3GPP system and the existing/future maritime radio communication system for the seamless service of voice communication and data communication between users ashore and at sea or between vessels at sea.

Analysis is also made on which legacy services and requirements from the existing 3GPP system need to be included and which potential requirements need additional work for new functions to support maritime communication services over 3GPP system.

The first 3GPP Technical Specification (TS) 22.119 covering service requirements (Stage 1) is specified for the support of maritime communication (MARCOM) over 3GPP systems.

The maritime domain, one of the 5G vertical domains in 3GPP, is moving forward with the digitalisation and mobilisation of commercial as well as safety fields. Legacy 3GPP-based technologies and solutions can be beneficial to the digitalisation and mobilisation of the maritime domain though some of the legacy 3GPP enabling technologies and solutions may not be able to fully support the performances required by the maritime domain. The maritime radio environment was not originally considered by 3GPP when the technical specifications and solutions were standardised for LTE and 5G. 

However, most of the legacy mobile services and IoT services based on capabilities of EPS and 5GS specified in 3GPP specifications are applicable to maritime usage for the support of mobile broadband services, and for the support of IoT services or machine-type communication services in a vessel at sea. 

In addition, there are service scenarios and requirements specified in 3GPP specifications based on requirements of other related vertical domains (e.g. public safety domain, automotive domain, factory automation domain, and satellite industrial domain). Some requirements derived by service scenarios from these related vertical domains are applicable to the maritime domain. Thus, it is beneficial to use 3GPP enabling technologies developed to satisfy those requirements for the maritime domain in terms of the economy of scale.

For example, satellite access is one of the 3GPP radio access networks supported over the 5G system, so it is possible to provide seamless maritime mobile services by integrating multiple access technologies including satellite access depending on the service scenarios. In addition, Vertical LAN that can replace Ethernet-based access are applicable to indoor maritime mobile services inside a vessel.

Mission Critical (MC) Services specified in 3GPP specifications are applicable to commercial and maritime safety fields. Some similarities exist between the public safety domain and the maritime domain in terms of service scenarios that are essentially the same. For example, in some situations, mobile communication services are supported in spite of disconnected networks, i.e. off-network mode, or under isolated conditions. 

However, the maritime domain also has specific situations that do not happen in other vertical domains or in the legacy ICT industrial domain. New 3GPP enabling technologies dedicated to the maritime domain can be used to address such specific situations based on requirements derived from maritime use cases. Other vertical domains may benefit from such new 3GPP enabling technologies that consider maritime domain scenarios and may need more robust technologies or solutions than those that currently exist for those vertical domains.

The following specifications are relevant for MARCOM:

  • 3GPP TS 22.119, Maritime communication services over 3GPP system
  • 3GPP TS 22.179, Mission Critical Push to Talk (MCPTT); Stage 1
  • 3GPP TS 22.280, Mission Critical (MC) services common requirements
  • 3GPP TS 22.281, Mission Critical (MC) video
  • 3GPP TS 22.282, Mission Critical (MC) data

Related Posts

Tuesday 17 August 2021

'5G RAN Release 18 for Industry Verticals' Webinar Highlights

5G PPP held a virtual workshop on RAN Release 18 for Industry Verticals on June 23rd, 2021. The workshop was organised by 3GPP Market Representation Partners (MRPs): 5G-IA, 5GAA, 5G-ACIA and PSCE.

It features a fireside chat with new 3GPP RAN TSG Chair, Wanshi Chen. In addition to this, the workshop then provides a deep dive on new requirements from verticals, spanning automotive (5GAA), manufacturing (5G-ACIA), critical communications and public safety (TCCA with PSCE), broadcasting and media (5G-MAG), satellite (ESOA), rail (UIC), maritime (IALA) and energy (EUTC).

5G-SOLUTIONS came on board as a 5G PPP project supporting verticals with the 5G-EVE and 5G-VINNI 5G network infrastructures alongside RAN specialists doing standardisation work applicable to multiple verticals.

The video of the webinar is embedded below. In addition, you will find timings of when a particular talk starts and a link to the slides (if shared/available)

Timings:

  • 0:04:21 Fireside chat with Wanshi Chen, Qualcomm and 3GPP RAN TSG Chairman
  • 0:21:00 NTN Requirements in Rel-18 by Nicolas Chuberre, Thales Alenia Space (slides)
  • 0:31:40 Multiple verticals: Andrea Di Giglio, 5G SOLUTIONS (slides)
  • 0:36:35 Media and Broadcasting: David Vargas, BBC and 5G-MAG Chair of CD-T WG, Proposals for 3GPP RAN Rel-18 (slides)
  • 0:43:19 Maritime: Hyounhee Koo, Synctechno and IALA, Maritime Requirements on 3GPP Rel 18 RAN Studies/Works Priorities (slides)
  • 0:46:12 Rail: Ingo Wendler, UIC, NR Narrowband Channel Bandwidth - Railway Use Case (slides)
  • 0:50:02 Utilities: Julian Stafford, EUTC 3GPP RAN Rel-18 Requirements (slides)
  • 0:58:35 Utilities: Erik Guttman, Samsung 5G Smart Energy Infrastructure (slides)
  • 1:05:45 Multiple verticals: Mathew Webb, Huawei and 3GPP RAN 3GPP Release 17 and Release 18 support for industry verticals (slides)
  • 1:15:19 Public Safety/Critical Communications: Tero Pesonen, TCCA Chair, joint presentation with PSCE, 3GPP MRP Mini Workshop: 3GPP Rel 18. Requirements from industry verticals (slides)
  • 1:20:15 Multiple verticals: Thierry Berisot, Novamint and 3GPP RAN, Industry Verticals and Rel-18 RAN (slides)
  • 1:32:56 Manufacturing/IIoT: Michael Bahr, Siemens and 5G-ACIA WG 1Chair and An Xueli, Huawei and 5G-ACIA WG1 Vice Chair 3GPP RAN Rel-18 for Industry Verticals (slides)
  • 1:42:20 Automotive: 5GAA Maxime Flament, CTO Input to RAN 18 Rel-18 Workshop (slides)
  • 1:53:35 Interactive Session 2
  • 2:04:36 Passive IoT for 5G-Advanced, Mathew Webb, Huawei and 3GPP RAN (slides)
  • 2:14:59 Template A for Interactive Session 2
  • 2:20:40 Critical Communications / Public Safety requirements for Release 18 
  • 2:26:00 Closing Remarks

Official page here.

The slide above nicely summarizes 3GPP RAN Verticals up to Release 17.

Related Posts

Wednesday 6 May 2020

Virve 2.0 - Finland's 4G/5G Public Safety Network

State Security Networks Group Finland (Erillisverkot) safeguards the Finnish society by offering authorities and critical operators engaged in critical infrastructure and services secure and reliable ICT services. Much like in the civilian world, communication between authorities includes transferring images and video material to an increasing degree, which results in ever-growing data transfer volumes and, subsequently, new kinds of demands for all communication networks. 


Virve is a means of ensuring communication and cooperation between authorities and other partners across organisational borders into the future. It also entails the introduction of a higher service standard, as the transfer to broadband, estimated to take place in 2022, will make it possible to transfer video material, images and data. This will mean that it will be possible to send video material in a reliable and secure way in the case of accidents, for example. The radio network Virve, based on Tetra technology, will reach the end of its lifecycle by the end of the 2020s. The current Virve network will be used simultaneously with the new Virve 2.0 network until, at least, 2025.


Erillisverkot will acquire the broadband Virve 2.0 radio access network as a service from Elisa and the core systems from Ericsson. Separate networks will ensure the continuity of critical communications and operational capability of public safety in all situations in the future.

I would assume this would be MOCN, similar to the UK deployment of ESN networks as shown here.

Virve 2.0 subcribers will use Elisa’s public radio network, which the operator is expanding to become Finland’s largest data and voice network.

About 80 million messages pass through the Virve system every week. Elisa is committed to increasing the coverage, capacity and verification of its mobile network to meet the requirements of Virve 2.0.

The new online services will provide support for critical communication between public authorities and other parties.

The addition of image, video, and other wireless broadband services alongside existing Virve services will enable a better and more up-to-date view of the day-to-day operations of authorities and other actors.

The IoT enables automatic monitoring of rescue personnel and mobile use of surveillance cameras and drones.

The Virve 2.0 radio network service will be in use from 2021 and will include the 4G and 5G technologies and the internet of things. The contract is for ten years.

Finally, a recent advert of Elisa explaining 5G to outside world



Further Study:
  • Erillisverkot: Obstacles for MCX Broadband and how to overcome them [PDF]
  • Erillisverkot: Virve Broadband Plans for the Future - Critical Communications Europe 2019 [PDF]
  • 5G-XCast Whitepaper: Rapidly Deployable Network System for Critical Communications in Remote Locations [PDF]
  • Erillisverkot: White paper - Virve 2.0 RFI Summary of responses [PDF]
  • Erillisverkot: Factsheet - What is Virve 2.0? [PDF]

Related Posts:

Thursday 21 March 2019

Update from 3GPP on LTE & 5G Mission Critical Communications


Adrian Scrase, CTO of ETSI & Head of MCC, 3GPP presented an update at BAPCO / CCE 2019 on Public Safety LTE and 5G. His presentation is embedded below.

There has been quite a progress in this area since I wrote my last post on Release-14 here.
This is the list of features that are planned for Release-16. There is also an update on Satellite communications but I will look at it separately in another post. Here are the slides:



The presentation can be directly downloaded from 3GPP website here.

Related posts:

Sunday 17 March 2019

Update on UK's Emergency Services Network (ESN) from #BAPCO2019


I have discussed about the UK's Emergency Services Network (ESN) multiple times but I manged to hear about the progress first hand this week. Bryan Clark, ESN Programme Director, Home Office gave a keynote address at BAPCO on Day 2 and the title of his presentation was "2019: The year vision becomes reality"

British APCO or BAPCO Annual Conference and Exhibition 2019 was going to be a big launchpad for the ESN network. The ESN LinkedIn post said "Representatives from ESN and EE will be on hand to discuss coverage and ESN Assure. See an installation of the ESN Gateway solution within a police car, plus a live demonstration showing how ESN coverage can be extended from a vehicle into a building. We’ll also have a ‘Motorola Zone’ where you can watch demos of Kodiak and the ESN self-service portal – and a large touchscreen demo of the Samsung ESN Galaxy"


Bryan started by cracking a joke about people referring to 'ESN' as 'ES When' programme because it has been delayed multiple times. He said straight in the beginning that he going to talk about what the ESN programme is doing now and what comes next.

He started with this short video, embedded below but detailed info available on this LinkedIn post

x

So here is a short summary of the talk:
  • There are roughly 350,000 customers of this service
  • There are 137 separate organizations that will take advantage of this new this new technology. 
  • There are couple of vehicles in the display area (pic on the top and video below) and roughly 50,000 vehicles that need to have a kit
  • Over 100 aircraft need to have an air network access that currently isn't there. 
  • There are nearly 30 direct suppliers to the program and that doesn't include the whole supply chain through each of those suppliers.
  • Looking at the coverage, there is a commitment to providing a signal along half a million (0.5 million) kilometers of roads in England, Scotland & Wales. It extends 12 nautical miles out to sea and 10,000 feet in the air right across England, Scotland & Wales.
  • In London alone there are over 400 kilometres of tunnels that were actually almost finished cabling out.
  • 300 masts are being built as part of the ESN programme to extend services into remote areas.
  • EE has extended their network by adding 700 additional masts. 
  • Thousands of special locations will need to have effective access to ESN network
  • ESN is a large programme so it's hardly surprising that it's very late. It's Bryan's job over the past 10 months to work out how to get it back on track. 
  • People are going through quite a detailed review of where ESN has got to in terms of next steps. 
  • The programme now has a very clear and approved plan to complete the technical element of the work, most of it should be done by late summer next year.
  • One of the first products, Assure, is a way of testing the effectiveness of the network in the field. 
  • A demonstration of Push-To-Talk (PTT) on a 4G network will be demoed within 3 weeks.
  • This is the first generation end-to-end solution
  • Emergency services is critical national infrastructure so any new solution can only replace the legacy once we are absolutely confident that we've got an effective replacement
  • Even though the technical piece is quite challenging, when you compare it to the business change that follows, the technical part looks pretty simple. 
  • To ensure that everything works effectively operationally, plans are in place but more detailed plans are going to follow in the coming three to four months.
  • Individual components are already being tested in the field
  • Programme deployment should start by the end of 2019 in terms of having basically completed laying the core components and a clear plan will be in place for how to test in an operational context. 
  • The ESN programme is not only responsible for the replacement solution but also for operations to date based on the Airwave contract with Motorola currently
  • The number one priority is to provide critical voice communications of sufficient quality that people can rely on in the field and enable them to move away from the TETRA technology that served them so well. So we aren't going anywhere until we've got rock solid critical voice communications. It's our number one priority, simply because people's lives depend on it.
The following are various videos from the ESN demo area. The Gateway device (which is a mobile small cell) is supplied by Parallel Wireless*.



In case you missed BAPCO, Ken Rehbehn, a very well known Industry Analyst who works as a Principal Analyst at Critical Communications Insights and is also Montgomery County Firefighter/EMT, shared his observations and reflections from conference. Very grateful for his interview which is embedded below



Further Reading:




Related posts:

*Full Disclosure: I work for Parallel Wireless as a Senior Director in Strategic Marketing. This blog is maintained in my personal capacity and expresses my own views, not the views of my employer or anyone else. Anyone who knows me well would know this.

Tuesday 5 December 2017

Summary of 3GPP Release-14 Work Items


With all focus on 5G (Release-15), looks like Rel-14 has been feeling a bit neglected. There are some important updates though as it lays foundation for other services.

3GPP used to maintain Release Descriptions here for all different releases but have stopped doing that since 2014. For Release-14, a new document "3GPP TR 21.914: Release 14 Description; Summary of Rel-14 Work Items" is now available here.

An executive summary from the document:

Release 14 focusses on the following items:
  • Improving the Mission Critical aspects, in particular with the introduction of Video and Data services
  • Introducing the Vehicle-to-Everything (V2X) aspects, in particular the Vehicle-to-Vehicle (V2)
  • Improving the Cellular Internet of Things (CIoT) aspects, with 2G, 3G and 4G support of Machine-Type of Communications (MTC)
  • Improving the radio interface, in particular by enhancing the aspects related to coordination with WLAN and unlicensed spectrum
  • A set of uncorrelated improvements, e.g. on Voice over LTE (VoLTE), IMS, Location reporting.


The continuation of this document provides an exhaustive view of all the items specified by 3GPP in Release 14.

I have blogged about the Mission Critical Communications here. 3GPP has also done a webinar on this topic which can be viewed here. I like this slide below that summarizes features in different releases.

Then there are quite a few new features and enhancements for V2X. I have blogged about sidelink and its proposed extensions here.

From the document:

The Work Item on “Architecture enhancements for LTE support of V2X services (V2XARC)”, driven by SA WG2, specifies the V2X architectures, functional entities involved for V2X communication, interfaces, provisioned parameters and procedures in TS 23.285.
Figure above depicts an overall architecture for V2X communication. V2X Control Function is the logical function defined for network related actions required for V2X and performs authorization and provisioning of necessary parameters for V2X communication to the UE via V3 interface.

A UE can send V2X messages over PC5 interface by using network scheduled operation mode (i.e. centralized scheduling) and UE autonomous resources selection mode (i.e. distributed scheduling) when the UE is "served by E-UTRAN" while a UE can send V2X messages over PC5 interface only by using UE autonomous resources selection mode when the UE is "not served by E-UTRAN". 

Both IP based and non-IP based V2X messages over PC5 are supported. For IP based V2X messages over PC5, only IPv6 is used. PPPP (ProSe Per-Packet Priority) reflecting priority and latency for V2X message is applied to schedule the transmission of V2X message over PC5.

A UE can send V2X messages over LTE-Uu interface destined to a locally relevant V2X Application Server, and the V2X Application Server delivers the V2X messages to the UE(s) in a target area using unicast delivery and/or MBMS (Multimedia Broadcast/Multicast Service) delivery.

Both IP based and non-IP based V2X messages are supported for V2X communication over LTE-Uu. In order to transmit non-IP based V2X messages over LTE-Uu, the UE encapsulates the V2X messages in IP packets.

For latency improvements for MBMS, localized MBMS can be considered for localized routing of V2X messages destined to UEs.

For V2X communication over LTE-Uu interface, the V2X messages can be delivered via Non-GBR bearer (i.e. an IP transmission path with no reserved bitrate resources) as well as GBR bearer (i.e. an IP transmission path with reserved (guaranteed) bitrate resources). In order to meet the latency requirement for V2X message delivery, the following standardized QCI (QoS Class Identifier) values defined in TS 23.203 can be used:
  • QCI 3 (GBR bearer) and QCI 79 (Non-GBR bearer) can be used for the unicast delivery of V2X messages.
  • QCI 75 (GBR bearer) is only used for the delivery of V2X messages over MBMS bearers. 


There are updates to cellular IoT (CIot) which I have blogged about here.

There are some other interesting topic that are enhanced as part of Release14. Here are some of them:
  • S8 Home Routing Architecture for VoLTE
    • Robust Call Setup for VoLTE subscriber in LTE
    • Enhancements to Domain Selection between VoLTE and CDMA CS
    • MBMS improvements
    • eMBMS enhancements for LTE
    • IMS related items
    • Evolution to and Interworking with eCall in IMS
    • Password-based service activation for IMS Multimedia Telephony service
    • Multimedia Priority Service Modifications
    • Enhancements to Multi-stream Multiparty Conferencing Media Handling
    • Enhancement for TV service
    • Improved Streaming QoE Reporting in 3GPP (IQoE)
    • Quality of Experience (QoE) Measurement Collection for streaming services in UTRAN
    • Development of super-wideband and fullband P.835
    • Enhancements to User Location Reporting Support
    • Enhancing Location Capabilities for Indoor and Outdoor Emergency Communications
    • Further Indoor Positioning Enhancements for UTRA and LTE
    • Improvements of awareness of user location change
    • Terminating Access Domain Selection (T-ADS) supporting WLAN Access
    • Enhanced LTE-WLAN Aggregation (LWA)
    • Enhanced LTE WLAN Radio Level Integration with IPsec Tunnel (eLWIP)
    • Positioning Enhancements for GERAN
    • New GPRS algorithms for EASE
    • RRC optimization for UMTS
    • Multi-Carrier Enhancements for UMTS
    • DTX/DRX enhancements in CELL_FACH
    • LTE radio improvements
    • Enhancements on Full-Dimension (FD) MIMO for LTE
    • Downlink Multiuser Superposition Transmission for LTE
    • Performance enhancements for high speed scenario in LTE
    • Control and User Plane Separation (CUPS) of EPC nodes
    • Paging Policy Enhancements and Procedure
    • Shared Subscription Data Update
    • Service Domain Centralization
    • Control of Applications when Third party Servers encounter difficulties
    • PS Data Off Services
    • Enhancement to Flexible Mobile Service Steering 
    • Sponsored data connectivity improvements
    • Group based enhancements in the network capability exposure functions
    • Improved operator control using new UE configuration parameters
    • Charging and OAM stand alone improvements
    • Rel-14 Charging
    • ...

    Further Reading:


    Tuesday 27 June 2017

    Mission Critical Services update from 3GPP - June 2017


    3GPP has published an overview of what has been achieved so far in the Mission Critical and also provides an outlook of what can be expected in the near future. A more detailed paper summarizing the use cases and functional aspects of Rel-13, Rel-14 and upcoming Rel-15 will be published later this year.

    Mission Critical Services – Detailed List of Rel-13, Rel-14 and Rel-15 Functionalities

    Rel-13 MCPTT (completed 2016)
    • User authentication and service authorization
    • Configuration
    • Affiliation and de-affiliation
    • Group calls on-network and off-network (within one system or multiple systems, pre-arranged or chat model, late entry, broadcast group calls, emergency group calls, imminent peril group calls, emergency alerts)
    • Private calls on-network and off-network (automatic or manual commencement modes, emergency private calls)
    • MCPTT security
    • Encryption (media and control signalling)
    • Simultaneous sessions for call
    • Dynamic group management (group regrouping)
    • Floor control in on-network (within one system or across systems) and in off-network
    • Pre-established sessions
    • Resource management (unicast, multicast, modification, shared priority)
    • Multicast/Unicast bearer control, MBMS (Multimedia Broadcast/Multicast Service) bearers
    • Location configuration, reporting and triggering
    • Use of UE-to-network relays
    Rel-14 MC Services (completed 2017)
    MC Services Common Functionalities:
    • User authentication and service authorization
    • Service configuration
    • Affiliation and de-affiliation
    • Extended Location Features
    • (Dynamic) Group Management
    • Identity management
    • MC Security framework
    • Encryption (media and control signalling)
    MCPTT Enhancements:
    • First-to-answer call setup (with and without floor control)
    • Floor control for audio cut-in enabled group
    • Updating the selected MC Service user profile for an MC Service
    • Ambient listening call
    • MCPTT private call-back request
    • Remote change of selected group
    MCVideo, Common Functions plus:
    • Group Call (including emergency group calls, imminent peril group calls, emergency alerts)
    • Private Call (off-network)
    • Transmission Control
    MCData, Common Functions plus:
    • Short Data Service (SDS)
    • File Distribution (FD) (on-network)
    • Transmission and Reception Control
    • Handling of Disposition Notifications
    • Communication Release
    Rel-15 MC Services (in progress)

    MC Services Common Functionalities Enhancements:
    • Enhanced MCPTT group call setup procedure with MBMS bearer
    • Enhanced Location management, information and triggers
    • Interconnection between 3GPP defined MC systems
    • Interworking with legacy systems

    MCPTT Enhancements:
    • Remotely initiated MCPTT call
    • Enhanced handling of MCPTT Emergency Alerts
    • Enhanced Broadcast group call
    • Updating pre-selected MC Service user profile
    • Temporary group call - user regroup
    • Functional alias identity for user and equipment
    • Multiple simultaneous users
    MCVideo Additions:
    • Video push
    • Video pull
    • Private call (on-network)
    • Broadcast Group Call
    • Ambient Viewing Call
    • Capability information sharing
    • Simultaneous Sessions
    • Use of MBMS transmission
    • Emergency and imminent peril private communications
    • Primary and Partner MC system interactions for MCVideo communications
    • Remote video parameters control capabilities

    MCData Additions:
    • MCData specific Location
    • Enhanced Status
    • Accessing list of deferred communications
    • Usage of MBMS
    • Emergency Alert
    • Data streaming
    • File Distribution (FD) (off-network)
    • IP connectivity

    Release-14 features will be available by end of September 2017 and many Release-15 features, that is being hurried due to 5G will be available by June 2018.

    For more details, follow the links below:



    Sunday 12 March 2017

    High Power / Performance User Equipment (#HPUE)

    3GPP refers to HPUE as High Power UE while the US operator Sprint prefers to use the term High Performance UE.

    HPUE was initially defined for US Public Safety Band 14 (700MHz). The intention was that this high power UEs can increase the coverage range from 4km to 8km. This would mean larger coverage areas and less number of cells.

    While the commercial UE's (class 3) transmit at +23dBm (max 200mW), the Public Safety people intend to use class 1 UE transmitting +31 dBm (max 1.25W). It was felt that this feature could be beneficial for some TDD bands that do not have to worry about backward compatibility. One such band, pushed by Sprint was TDD Band 41 (2500MHz). As this band is for the commercial UE's, instead of class 1, class 2 power at +26dBm (max 400mW) was proposed.

    3GPP TS 36.886 provides the following justification:

    Currently, 3GPP has defined only Power Class UE 3 as the type of UE supported for TDD LTE band 41 operations. This definition was based on aligning TDD LTE Band 41 UE power classes with prior work in 3GPP related to other bands. However, it should be mentioned that 3GPP UE Power Class 3 definition (i.e. 23dBm) was mainly driven to ensure backward compatibility with prior technologies (i.e. GSM/UMTS) [2] so that network deployment topologies remain similar. Furthermore, maintaining the same power class UE definition (i.e. Class 3) as previous technologies would maintaining compliance with various national regulatory rulings, particularly in terms of SAR, for FDD LTE duplexing mode. 

    However, TDD LTE band 41 does not have any 3GPP legacy technologies associated with it, hence the backward compatibility consideration is not applicable in its case. Also, since band 41 is defined as a TDD LTE band, it is less susceptible to SAR levels that FDD LTE bands due to SAR definition. Therefore, defining a new UE power class with higher than 23dBm Tx power for TDD LTE Band 41 operations would not compromise any of 3GPP foundational work, while improving UE and network performance. It should also be mentioned that 3GPP has done similar work on other bands (i.e. band 14) when defining a higher power class UE, hence the concept presented in this document is a continuation of that process.

    The present document carries out a feasibility analysis for defining a UE Power class 2 (i.e. 26dBm) for operation on TDD LTE band 41. The document analyses current and future technological advancements in the area of UE RF front-end components and architectures that enable such definition while maintaining 3GPP specification and other regulatory bodies' requirements. It should be emphasized that this proposal only relates to single carrier UL operations on TDD band 41 (i.e. TM-1/2 modes) without affecting current 3GPP definition for UL carrier aggregation on band 41.

    As you can see from the tweet above, Sprint CEO is quite pleased with the HPUE. 

    SourceDiana Goovaerts

    Iain Gillott, iGR points out that HPUE applies to Sprint’s 2.5 GHz TDD network and associated spectrum, and the company claims up to 30 percent increase in cell cover from the new technology.  It should be noted that HPUE is a 3GPP standard that applies to the 2.5 GHz TDD band (Band 41) and is also to be used by China Mobile and Softbank.  HPUE was developed as part of the Global TDD LTE Initiative (GTI) which includes Qualcomm Technologies, Samsung, ZTE, Broadcom, MediaTek, Skyworks Solutions, Alcatel, Motorola, LG and Qorvo... The cool part: the improvement in coverage comes from simply improving the device uplink power.  So Sprint, China Mobile and Softbank will not have to visit their cell sites to make changes; they just need 2.5 GHz TDD devices with HPUE to get the benefit.


    Milan Milanović recently wrote about Sprint’s Gigabit Class LTE network goes live in New Orleans. One of the questions I had was why is the uplink so rubbish as compared to downlink. He kindly pointed out to me that this is TDD config 2
    If you are wondering what is TDD Config 2, see the pic below
    Source: ShareTechNote

    Sprint expects HPUE to appear in postpaid devices starting in 2017, including new devices from Samsung, LG, HTC, and Moto. It’s expected that all of Sprint’s new devices will have HPUE support within the next two years.

    I think it would be interesting to see how this impacts when there are a lot more users and devices. I am quite sure there will be more requests for HPUE in further TDD bands.

    Related Links:

    Sunday 16 October 2016

    Inside 3GPP Release-13 - Whitepaper by 5G Americas


    The following is from the 5G Americas press release:

    The summary offers insight to the future of wireless broadband and how new requirements and technological goals will be achieved. The report updates Release 13 (Rel-13) features that are now completed at 3GPP and were not available at the time of the publication of a detailed 5G Americas report, Mobile Broadband Evolution Towards 5G: 3GPP Release 12 & Release 13 and Beyond in June 2015.
    The 3GPP standards have many innovations remaining for LTE to create a foundation for 5G.  Rel-12, which was finalized in December 2014, contains a vast array of features for both LTE and HSPA+ that bring greater efficiency for networks and devices, as well as enable new applications and services. Many of the Rel-12 features were extended into Rel-13.  Rel-13, functionally frozen in December 2015 and completed in March 2016, continues to build on these technical capabilities while adding many robust new features.
    Jim Seymour, Principal Engineer, Mobility CTO Group, Cisco and co-leader of the 5G Americas report explained, “3GPP Release 13 is just a peek behind the curtain for the unveiling of future innovations for LTE that will parallel the technical work at 3GPP on 5G. Both LTE and 5G will work together to form our connected future.”
    The numerous features in the Rel-13 standards include the following for LTE-Advanced:
    • Active Antenna Systems (AAS), including beamforming, Multi-Input Multi-Output (MIMO) and Self-Organizing Network (SON) aspects
    • Enhanced signaling to support inter-site Coordinated Multi-Point Transmission and Reception (CoMP)
    • Carrier Aggregation (CA) enhancements to support up to 32 component carriers
    • Dual Connectivity (DC) enhancements to better support multi-vendor deployments with improved traffic steering
    • Improvements in Radio Access Network (RAN) sharing
    • Enhancements to Machine Type Communication (MTC)
    • Enhanced Proximity Services (ProSe)
    Some of the standards work in Rel-13 related to spectrum efficiency include:                                                                                                                       
    • Licensed Assisted Access for LTE (LAA) in which LTE can be deployed in unlicensed spectrum
    • LTE Wireless Local Area Network (WLAN) Aggregation (LWA) where Wi-Fi can now be supported by a radio bearer and aggregated with an LTE radio bearer
    • Narrowband IoT (NB-IoT) where lower power wider coverage LTE carriers have been designed to support IoT applications
    • Downlink (DL) Multi-User Superposition Transmission (MUST) which is a new concept for transmitting more than one data layer to multiple users without time, frequency or spatial separation
    “The vision for 5G is being clarified in each step of the 3GPP standards. To understand those steps, 5G Americas provides reports on the developments in this succinct, understandable format,” said Vicki Livingston, Head of Communications for the association.

    The whitepaper as follows:



    Related posts: