6. User Agent Profile / UAProf Reference -- PushCharacteristics Component

The PushCharacteristics component of User Agent Profile / UAProf provides information about the WAP Push capabilities of the mobile device. For example, character encodings supported, character sets supported, content types / MIME types supported and maximum WAP Push message size.

The following table lists some base attributes of the PushCharacteristics component as specified in the UAProf schema. A description and some examples are provided for each base attribute. Note that a user agent profile may not include all attributes listed below.


To scroll the table, use the scroll bars on the right and bottom of the table. A full-page version is available additionally.

UAProf Attribute / Property

Description

Example

Push-Accept

The Push-Accept attribute states the MIME media types that can be placed in the message body of WAP Push messages.

<prf:Push-Accept>
  <rdf:Bag>
    <rdf:li>application/vnd.wap.multipart.mixed</rdf:li>
    <rdf:li>application/vnd.wap.multipart.related</rdf:li>
    <rdf:li>application/vnd.wap.wmlc</rdf:li>
    <rdf:li>application/vnd.wap.xhtml+xml</rdf:li>
    <rdf:li>multipart/mixed</rdf:li>
    <rdf:li>multipart/related</rdf:li>
    <rdf:li>text/plain</rdf:li>
    <rdf:li>text/vnd.wap.wml</rdf:li>
  </rdf:Bag>
</prf:Push-Accept>

Push-Accept-AppID

The Push-Accept-AppID attribute states the application IDs supported by WAP Push.

"*" means all applications are supported.

<prf:Push-Accept-AppID>
  <rdf:Bag>
    <rdf:li>x-wap-application:wml.ua</rdf:li>
    <rdf:li>*</rdf:li>
  </rdf:Bag>
</prf:Push-Accept-AppID>

Push-Accept-Charset

The Push-Accept-Charset attribute contains a list of character sets supported by WAP Push messages.

<prf:Push-Accept-Charset>
  <rdf:Bag>
    <rdf:li>US-ASCII</rdf:li>
    <rdf:li>ISO-8859-1</rdf:li>
    <rdf:li>UTF-8</rdf:li>
    <rdf:li>ISO-10646-UCS-2</rdf:li>
  </rdf:Bag>
</prf:Push-Accept-Charset>

Push-Accept-Encoding

The Push-Accept-Encoding attribute states the transfer encodings supported by WAP Push messages. The transfer encoding names can be found at IANA's website.

<prf:Push-Accept-Encoding>
  <rdf:Bag>
    <rdf:li>base64</rdf:li>
    <rdf:li>quoted-printable</rdf:li>
  </rdf:Bag>
</prf:Push-Accept-Encoding>

Push-Accept-Language

The Push-Accept-Language attribute states the language preference of the user for WAP Push messages.

The items are listed in order of preference. For example, the first list item is the most preferred language.

<prf:Push-Accept-Language>
  <rdf:Seq>
    <rdf:li>en</rdf:li>
    <rdf:li>de</rdf:li>
    <rdf:li>fr</rdf:li>
    <rdf:li>zh-TW</rdf:li>
    <rdf:li>zh-CN</rdf:li>
  </rdf:Seq>
</prf:Push-Accept-Language>

Push-MaxPushReq

The Push-MaxPushReq attribute states the maximum number of WAP Push requests that the mobile device is capable to deal with.

<prf:Push-MaxPushReq>1</prf:Push-MaxPushReq>

Push-MsgSize

The Push-MsgSize attribute states the maximum WAP Push message size (in bytes) supported by the mobile device.

<prf:Push-MsgSize>1400</prf:Push-MsgSize>


Previous Page Page 6 of 7 Next Page


Feedback Form (ExpandCollapse)

What do you think about this web page?






(Optional) Please provide us more details. For example, suppose you select option 2 above, can you tell us specifically what information is missing? You can also suggest anything that can help us improve this web page.

(Optional) Your name:

(Optional) Your email address:

Please enter again to confirm:

Due to the amount of messages we received, we may not be able to reply to all messages.

A button for going back to the top of this page