1. Qualcomm 1 CMAS E-interface parameters over 1x SMS Ravi Patwardhan, (rpatward@qualcomm.com) April 2008, Montreal, Canada

2. Qualcomm 2 Introduction FCC NPRM identifies E-interface parameters E-interface parameters are carried over-the-air between MS and BS This contribution proposes way to carry E-interface parameters over 1x Broadcast SMS defined in TIA-637 –TIA-637 defines “Service Category” and “Bearer data subparameters”

3. Qualcomm 3 Option 1 Define new “Service Category” values for CMAS Use existing “Bearer data subparameters” as much as possible, and define/modify new “Bearer data subparameters” as necessary Requires changes to TIA-637 standard, and implementation

4. Qualcomm 4 Option 2 Define new “Service Category” values for CMAS Carry all E-interface parameters as part of "User Data" subparameter –“User Data” subparameter will contain all E-interface parameters including Display text. E-interface parameters CMAE_protocol_version CMAE_identifier CMAE_alert_handling.. CMAE_Alert_Text

5. Qualcomm 5 Advantages of Option 2 No changes required to TIA-637 standard, and implementation Less overhead than option 1 –Format of “Bearer data subparameters” is TLV (Type, Length, Value). »Option 1: coding E-interface parameters have overhead of “Type” and “Length” fields for each parameter »Option 2: All CMAS parameters can have fixed coding, or can be coded as single TLV E-interface parameter format can be defined in CMAS E-interface document –Format parsed by CMAS application –Same format can be used on different transports(1x, DO etc.) –Same format can be used on GSM too. Possible to harmonize the format

6. Qualcomm 6 Recommendation Option 2 recommended –Carry all E-interface parameters as part of "User Data”