We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byPaige Chase
Modified over 2 years ago
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 1 Hannu Hietalahti Kevin Holley Stephen Hayes Brian Daly PWS Public Warning System IETF #79, 7 – 12 Dec, 2010, Beijing, China
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 2 Contents Cell Broadcast Service Overview Current status of PWS PWS Service requirements Cell Broadcast Service PWS Technical overview Use case Details Extensibility Message Identifiers Regional Standards CMAS architecture and call flow example Summary
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 3 Current status of Public Warning System PWS comprises public alert services in 3GPP Earthquake and Tsunami Warning System ETWS (Rel-8) Commercial Mobile Alert System CMAS (Rel-9) EU-Alert requirements are being studied (Rel-11) Global service Warning categories must be defined globally Detection of the warning categories must be global for roaming users Applicable in 3GPP systems over GSM, UTRAN and LTE radio Specification references Stage 1 in 3GPP TS (Requirements) Stage 2 in 3GPP TS (CBS, Message Identifier coding) Stage 3 in 3GPP TS , , , , , (Radio interface)
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 4 Service requirements (from 3GPP TS ) Broadcast Warning Notifications to multiple users simultaneously Geographical notification area is specified by the Warning Notification Provider Roaming subscribers must be supported Concurrent broadcast of multiple Warning Notifications with no acknowledgement required PWS capable terminals in idle mode shall be able to receive broadcast warnings User may opt-out from certain alert categories Warning Notifications languages are determined by regulatory requirements Warning Notifications are processed by PWS on a first in, first out basis, subject to regulatory requirements Reception and presentation of Warning Notifications to the user shall not pre- empt an active voice or data session. Current implementation requirement is up to 90 7-bit characters Typical contents of the warning: Event Description Area Affected Recommended Action Expiration Time (with time zone) Sending Agency
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 5 Cell Broadcast Service (CBS) CBS is defined in 3GPP TS CBS can cover different services that are independent of each other PWS uses CBS in GSM and UTRAN In LTE the messages are encoded according to CBS rules, but distribution at the radio interface is LTE specific Unacknowledged broadcast to all CBS-capable mobiles within a particular region defined geographical areas known as cell broadcast areas may comprise of one or more cells, up to the entire network CBS messages may originate from a number of Cell Broadcast Entities (CBEs) through an operators Cell Broadcast centre (CBC) CBS messages are sent from the CBC to the cells, in accordance with the CBS's coverage requirements Maximum capacity ranges from GSM 93 7-bit characters to LTE 316 characters Message segmentation is possible (15 – 64 segments) A CBS message is identified by a message identifier and serial number Can be used by the mobile to screen which messages are received Also to identify and ignore re broadcasts of already received messages 3GPP manages the message identifiers CBS messages may be broadcast cyclically by the cell at a frequency and for a duration agreed between the operator and the information provider
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 6 Technical overview, use case (Figure from 3GPP TS ) Key points: Interface provided to Government authority to submit alert messages Government authority is responsible for interface to and authentication of alert originators Security against fake alarms, operator must authenticate alert issuer at interface C Support for all terminals in the affected geographical area, including roaming users and terminals sourced from other countries Distribution mechanisms at radio interface differ between GSM, UTRAN, LTE but are all based on broadcast mechanisms
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 7 Technical overview, details Radio procedures for broadcasting in 3GPP radio access technologies Common paging or SysInfo change or CBS Distribution area Geographical selectivity is based on network topology Alert codes are globally defined Detection of alert categories is not restricted to physical distribution channel at radio interface but part of PWS service Paging to wake up the terminal to listen to broadcast information Mutual authentication to avoid MiM and playback attacks Data coding scheme is critical for compatibility and mobility Message Identifier corresponds with alert category Message Identifiers to be received can be pre-configured on USIM or by the user Language code Default 7-bit coding with several language specific extensions or 16-bit UCS2 coding for other languages Sequencing to distinguish between different messages
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 8 PWS extensibility Message identifier ranges are assigned for different broadcast use cases MI 0 – 999 are defined by GSMA for Flash messages, weather reports, traffic reports, date & time, etc MI are defined by 3GPP for specific services, among them PWS MI values 1100 – 18FF are reserved for PWS use More than 2000 code points not assigned yet ME application configures the reception of the MIs related with the service Reception of any MI can be configured on USIM by the HPLMN operator Legacy terminal processing of unforeseen data is normatively specified and thus predictable alert category, character set, broken sequence, etc. All alert categories shall be globally unique National or regional exceptions cannot change the meaning of alert code Japanese Tsunami alert code cannot be re-used for avalanche warning in Switzerland CMAS Presidential Level Alert code point can be re-used for EU-Alert 1 Additions to existing codes are possible National extensions must be defined globally
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 9 Message Identifiers (3GPP TS ) DecimalHexMeaning 0 – – 03E7Allocated by GSMA (see GSMA PRD SE.15 )... … ETWS CBS Message Identifier for earthquake warning message ETWS CBS Message Identifier for tsunami warning message ETWS CBS Message Identifier for earthquake and tsunami combined warning message ETWS CBS Message Identifier for test message. Normal UE silently discards this message. Test UE may may display its contents ETWS CBS Message Identifier for messages related to other emergency types – ETWS CBS Message Identifier for future extension.... … Intended for standardization in future versions of this document. These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message CMAS CBS Message Identifier for Presidential Level Alerts. Not settable by MMI CMAS CBS Message Identifier for Extreme Alerts with Severity of Extreme, Urgency of Immediate, and Certainty of Observed. Settable by MMI as per CMAS subscriber opt-out requirements... … F-112FCMAS CBS Message Identifier for future extension – 18FFCBS Message Identifier for future PWS use. These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message – – 9FFFIntended for standardization in future versions of this document. These values shall not be transmitted by networks that are compliant to this version of this document. If a Message Identifier from this range is in the "search list", the ME shall attempt to receive this CBS message.... …
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 10 Regional Standards ETWS, CMAS, EU-Alert ETWS requirements are defined by Japanese requlator, but not normatively referenced from 3GPP specifications 3GPP TS captures the 3GPP system requirements for ETWS CMAS is defined under FCC CFR 47 Part 10 Rules in the U.S. CMAS Standards developed by ATIS and TIA: J-STD-100, J-STD-101, ATIS , ATIS , ATIS , ATIS EU-Alert requirements are specified in ETSI ETS
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 11 CMAS architecture 11 E-UTRAN UTRAN GERAN Public authority Network Operator Access specific broadcast procedures
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 12 CMAS Call Flow Example CMSP Gateway in the operator network receives the CMAS alert from the government entity The alert is passed to the operators cell broadcast centre (CBC) which identifies the cell site(s) to broadcast the alert The alert is broadcast using 3GPP PWS
© 3GPP 2009 Mobile World Congress, Barcelona, 19 th February 2009© 3GPP GPP PWS presentation 13 Summary PWS was designed by 3GPP as a global solution for issuing public warnings over 3GPP mobile systems PWS is designed to allow extendable set of national and regional specific alerts while maintaining global uniqueness PWS is a service for alerting and updating the user of emergency situations in a timely, secure, and geographically selective manner PWS architecture provides interface towards public authorities who generate and authorize the warnings uses common PWS broadcast and message coding capabilities uses radio specific cell broadcast procedures in GSM, UMTS and LTE is extendable in future 3GPP enhancements
Chapter 20 Power Management for 4G Mobile Broadband Wireless Access Networks Maruti Gupta, Ali T. Koc, Rath Vannithamby Intel Labs, Intel Corporation.
16 August 2010© Crown Copyright (2010)1 Module 2.8 Assurance Continuity and Composition.
MUSE Policy Control Framework in FMC Govinda Rajan
Performance Evaluation HR Training Sessions May , 2013.
All Rights Reserved © Alcatel-Lucent 2009 BSNL FIXED IN Service Descriptions.
Mobile Communications: Long Term Evolution Part 1 Motivation for LTE Evolution of the standards Requirements and targets Competing standards Frequency.
Indiana Standard Operating Procedures Development Establishing Standard Operating Procedures to Achieve Statewide Interoperability 1 Indiana.
2 Welcome To Defect Management Training Objective: The objective of this course is to learn about standards that emphasize a best practice approach for.
10 th Anniversary Many-to-One: Managing Multiple APEX Applications Scott Spendolini, Sumner Technologies.
Wireless Systems: Where are we heading?. 2 Outline Some definitions Current situation Near Future 4G: what we really want What are the obstacles Higher.
1 Introducing the Specifications of the MEF An Overview of MEF 6.1, 10.2, Carrier Ethernet Definitions and Attributes 2011 December.
Presented to By. 2Normative references ISO 9000:2005, Quality management systems Fundamentals and vocabulary ISO 19011:2002, Guidelines for quality and/or.
The Smart Card Platform Gaby Lenhart Project leader ETSI Technical Committee Smart Card Platform (TB SCP)
©Silberschatz, Korth and Sudarshan8.1Database System Concepts, 5 th Ed, slide version 5.0, August Chapter 8: Application Design and Development.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 10 Architectural Design.
Evolution road of 3GPP-LTE Huawei Technology Co., LTD DOCUMENT #:GSC13-PLEN-41 FOR:Presentation SOURCE:Huawei Technologies Co., Ltd AGENDA ITEM:Plenary;
Fostering worldwide interoperabilityGeneva, July 2009 ATIS Emergency Communications (EC) Standards Development Global Standards Collaboration (GSC)
D-Plus Miscellaneous DMAS Enhancements Enhancements For iSeries 400 DMAS from Copyright I/O International, 2005, 2007, 2008, 2009, 2010 Skip Intro.
ITU-T ITU-T technical results in IMT-2000 Studies: Mobile Network Evolution Greg Jones, ITU-T June, 2002, Lisbon.
Chapter 7 – Design and Implementation 1Chapter 7 Design and implementation Note: These are a modified version of Ch 7 slides available from the authors.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 29Slide 1 Chapter 29 Configuration Management.
Dec 2005 UMT Portfolio Manager Builder User Training.
PrevNext | Slide 1 Michigan Electronic Grants System MEGS MEGS Overview and Updates for DLEG Adult Education.
1 Computer Networks: A Systems Approach, 5e Larry L. Peterson and Bruce S. Davie Chapter 9 Applications Copyright © 2010, Elsevier Inc. All rights Reserved.
1 Introducing the Specifications of the MEF An Overview of MEF 6.1, 6.1.1, 10.2, Carrier Ethernet Definitions and Attributes 2012 March.
Sales Order Cycle Review Report Insert Date. Source: 2 Table of Contents Executive Summary 3 Objective, Scope & Procedures Performed4.
Zeichen setzen für die Zukunft Committing to the future Market Launch Documentation Testo Saveris 21CFR11 Software July 2009.
Overview of ETSIs Technical Groups - The ETSI Approach David Boswarthick Technical Officer TC M2M © ETSI All rights reserved.
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: Multi-Radio-Paging Title: Multi-Radio Paging Study Group Request Date Submitted: March,
OCTOBER 14, SLIDE 1 Copyright © 2010 International Swaps and Derivatives Association, Inc. FpML 5.0 Overview ® ISDA is a registered trademark of.
© 2016 SlidePlayer.com Inc. All rights reserved.