1. 1 | CMAS Overvview | Month 2008 Commercial Mobile Alert Service (CMAS) Potential Changes Source: Orlett W. Pearson, Alcatel-Lucent opearson@alcatel-lucent.com Ravi Patwardhan, Qualcomm Inc. ravindra@qualcomm.com

2. 2 | CMAS Overvview | Month 2008 Commercial Mobile Alert Service (CMAS) CMAS Support: 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  Where will these be defined?  IS-637 or  CMAS “E” Interface Document

3. 3 | CMAS Overvview | Month 2008 Commercial Mobile Alert Service (CMAS) CMAS Support:  Mapping Consideration  Decide which parameters are mandatory or optional  Decide on the length of each parameter  Map CMAS Parameters –Option 1: Map CMAS parameters to existing IS-637 sub-parameters and/or define new IS-637 sub-parameters – Impact: Modify IS-637 – Advantages: (1) Re-use of existing sub-parameters – Disadvantages: All CMAS parameters cannot be mapped to existing sub-parameters –Option 2: 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

4. 4 | CMAS Overvview | Month 2008 Commercial Mobile Alert Service (CMAS) CMAS Support: 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