Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

Service Indication Life Cycle

Windows Mobile 6.5
4/8/2010

An SI notification has the following life cycle only if the href attribute has an explicitly assigned value.

Bb415612.note(en-us,MSDN.10).gifNote:
The device will automatically delete the SI notification at the time specified in the si-expires attribute. If no si-expires attribute 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 href attribute has an explicitly assigned value.

Bb415612.a4d106f4-0492-4006-9c5d-45b59ecb43c3(en-us,MSDN.10).gif

The following steps describe the life cycle of an SI notification with an explicitly assigned href attribute value:

  1. 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.
  2. 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 channel.
  3. The device receives the SI notification. Depending on the action attribute 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 received.
    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 action attribute 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-id attribute value (or href if si-id does not exist) as the received SI are deleted. If there are no other SIs with identical href attribute values, only the received SI is deleted.
    • If an SI with an action attribute value set to delete is received without an si-id attribute value, the SI is discarded.
  4. 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.
  5. 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 application.

Community Additions

Show:
© 2015 Microsoft