|This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.|
An SI notification has the following life cycle only if the hrefattribute has an explicitly assigned value.
|The device will automatically delete the SI notification at the time specified in the si-expiresattribute. If no si-expiresattribute is provided, the notification is not automatically deleted. The user can delete SI notifications that are stored in the Inbox at any time.|
The following diagram illustrates a Service Indication notification life cycle if the hrefattribute has an explicitly assigned value.
The following steps describe the life cycle of an SI notification with an explicitly assigned hrefattribute value:
- The Push Initiator (network) instructs the Push Proxy Gateway
to push an SI, in XML format, to the device by using the Push
Access Protocol. The Push Initiator creates the SI XML file with an
appropriate text message and a URI to the new service or update.
- The Push Proxy Gateway translates the XML file into WBXML and
then sends the SI notification to the device by using the Push OTA
protocol. Usually, Short Message Service (SMS) is the transmission
- The device receives the SI notification. Depending on the
actionattribute of the file, the notification is presented
to the user or it goes directly to the Inbox. If the SI is
presented to the user, the user is given the option to start the
service immediately or postpone the SI. If the user postpones the
SI, the file goes to the Inbox. When an SI notification is sent to
the Inbox, it exists only on the device and never synchronizes back
to a mail server. SI notifications are never stored on the
Subscriber Identity Module (SIM). If multiple SIs are received
simultaneously, they are processed in the order that they are
At this point, the device also examines the notification content for the following information and takes action accordingly:
- If the newly received SI notification is newer than an
otherwise identical SI notification that is stored in the Inbox,
the stored SI is deleted.
- If the expiration date and time have passed for a newly
received SI, the SI is discarded.
- If the
actionattribute value for the received SI is set to
delete, the received SI and any other SIs stored in the
Inbox that have the same
si-idattribute value (or
si-iddoes not exist) as the received SI are deleted. If
there are no other SIs with identical
hrefattribute values, only the received SI is deleted.
- If an SI with an
actionattribute value set to
deleteis received without an
si-idattribute value, the SI is discarded.
- If the newly received SI notification is newer than an otherwise identical SI notification that is stored in the Inbox, the stored SI is deleted.
- If the user chooses to retrieve the service, the mobile
Internet browser starts and the service indicated by the URI is
retrieved (pulled) from the origin server.
- The service starts running on the device through the mobile
Internet browser. If the browser cannot process the content type of
the pulled service, it searches the registry to find the correct