SOURCE: Orlett W. Pearson, Jialin Zou

CONTACT: Orlett W. Pearson opearson@alcatel-lucent.com

DATE: September 2009

ABSTRACT: ALU proposes a method to support the low cost short multi-cast messaging for supporting CMAS in HRPD.

TITLE: Short Multi-Cast Messaging for CMAS

TSG-C SWG2

RECOMMENDATION: Discuss and Adopt

Alcatel-Lucent grant a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. Alcatel-Lucent is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution.This document has been prepared by Alcatel-Lucent to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on Alcatel-Lucent. Alcatel-Lucent specifically reserves the right to amend or modify the material contained herein and to any intellectual property of Alcatel-Lucent other than provided in the copyright statement above.

2

Commercial Mobile Alert Service - Overview

Warning Alert and Response Network (WARN) Act was passed by Congress and signed into law by President Bush on Oct. 13, 2006. WARN Act establishes a process for Commercial Mobile Service Providers (CMSPs) to voluntarily elect to transmit emergency alerts.

– A CMSP who elects to transmit emergency alerts can elect to transmit the emergency alert services “in whole or in part”.

• “all or a subset of the mobile operator’s service area and/or all or a subset of current and future mobile devices supported by the mobile operator network”

– A CMSP who elects in whole or in part NOT to transmit emergency alerts:

• Must provide notification of this decision to its existing subscribers

• Must provide notice at point-of-sale of any devices with which its commercial mobile service is included, that it will not transmit such alerts via the service it provides for the device

3

Commercial Mobile Alert Service - Overview

– A CMSP who elects in whole or in part NOT to transmit emergency alerts (cont):

•Any commercial mobile service provider that transmits emergency alerts and meets it obligations shall not be liable for:

– A CMSP electing to transmit emergency alerts may offer subscribers the capability of preventing the subscriber’s device from receiving alerts, or classes of such alerts, other than an alert issued by the President

– Any act or omission related to or any harm resulting from the transmission of, or failure to transmit, an emergency alert.

– The release to a government agency or entity, public safety, fire service, law enforcement official, emergency medical service, or emergency facility of subscriber information used in connection with delivering such an alert.

4

Commercial Mobile Alert Service - Overview

WARN Act required that the Federal Communications Commission (FCC) establish the Commercial Mobile Service Alert Advisory Committee (CMSACC) to develop and recommend technical standards and protocols for the voluntary transmission of emergency alerts by CMSPs

– CMSACC developed Commercial Mobile Alert Service (CMAS) Architecture and Requirements recommendations

Department of Homeland Security (DHS) selects Federal Emergency Management Agency (FEMA) for the Federal Alert Aggregator and Federal Alert Gateway functions (June 2008)

– FEMA announced intention to adopt (during the first quarter of 2009) an alerting protocol in line with Common Alerting Protocol (CAP) 1.1 as the standard for the Integrated Public Alert and Warnings System (July 30, 2008)

5

CMAS Standards Development Joint ATIS/TIA Standards Development

– Federal Alert Gateway to CMSP Gateway Interface (Reference Point “C”)

• ATIS WTSC-G3GSN and TIA TR-45.2 standards development

– CMAS Mobile Device Behavior Specification

• ATIS WTSC-G3GSN and TIA-TR-45.5 standards development

TIA TR-45.5 Development

– Reference Point “E” standard for CDMA

– Based on existing Broadcast SMS network capability

– TR-45.5 work on CDMA air interface

– Requires new Mobile Devices

6

CMAS Standards Development

ATIS WTSC-G3GSN Standards Development

– Reference Point “E” standard for GSM/UMTS

– Based on Cell Broadcast

– Requires new Mobile Devices

7

CMAS Reference Architecture

8

Mobile Device Functionality Monitors associated channel or channels for CMAS alerts

Maintains configuration of CMAS alert options including:

– Subscriber’s choice of CMAS alert opt-out selections

– Subscriber’s preferred language for CMAS alerts if applicable to the delivery technology

– Default language is English if CMAS alert is not being transmitted in subscriber’s preferred language

Extracts the CMAS alert content in the subscriber’s preferred language or in the default language of English, if the CMAS alert is not being transmitted in the subscriber’s preferred language

9

Mobile Device Functionality Presents the received CMAS alert content to the mobile device

user in accordance with the capabilities of the mobile device, if the CMAS alert complies with the subscriber’s opt-out selections.

– Presidential level CMAS alerts are always presented.

– Presentation of a CMAS alert will activate associated visual, audio, and mechanical (e.g., vibration) indicators per subscriber options configured on the mobile device.

Detects and suppresses presentation of duplicate CMAS alerts.

Suppresses CMAS alert visual, audio and mechanical (e.g., vibration) indicators upon subscriber’s action on the mobile device user interface (e.g., key stroke, touch screen).

10

CMAS in 1x using SMS CMAS Support:

– Mapping Consideration• Decided on mandatory or optional parameters, along with the length

of each parameter. • Map CMAS Parameters

– Map all parameters to user data SMS Sub-Parameter which contains header information and display text.

• Impact: Define Header Structure in “E” Interface Standard• Advantages: (1) Technology Independent, (2) No Standards Changes

11

CMAS support for 1x Commercial Mobile Alert Service (CMAS)

– B-SMS over 1x Paging Channel as the transport mechanism for CDMA to support Commercial Mobile Alert (CMA) Text Profile

• The Standards support PCH • The Standards support BCCH

Mapping the CMAS “E” Interface parameters to CDMA B-SMS sub-parameters were defined in a new document for CMAS.

Mapping the CMA classes, categories, and eventCodes to Broadcast Service Categories in TSB-58.

• Identify a block of codes• Create a separate table specifically for CMAS

Under Consideration:– Battery Life Improvements

• Standards Impact: Unknown/TBD

12

Motivations for Supporting CMAS over HRPD

CMAS emergency notification requires the multicast/broadcast short messaging capabilities

BCMCS may not be enabled by all the operators

Make use of the existing EVDO control channel, Multicast Access Terminal Identifier (MATI) and the Broadcast Access Terminal Identifier (BATI)

– Transmit short message data over the control channel similar to DoS

– Make use of the MATI/BATI which is already defined in existing DO standards

The solution is simple and not depending on BCMCS

– HRPD is widely deployed

– Several operators have already opted in for support in CMAS

– Boost the value of HRPD

13

Forward Link Multicast

Multicast Access Terminal Identifier (MATI) assigned to access terminals in a group

Multicast message transmission over the Control Channel

– Allow transmitting Data over Signaling (DoS) message with Multicast ATI

– Quick Synchronous Channel may be used to indicate to access terminals with common MATI whether or not a DoS message is transmitted in the next Control Channel

– Multicast ATI• One Multicast ATI per flow per group of users

• MATI assigned using a GAUPable MATI attribute