Symbian3/PDK/Source/GUID-E7DD9CFD-F477-5D25-BC10-BEBFB1022F7E.dita
changeset 14 578be2adaf3e
parent 12 80ef3a206772
equal deleted inserted replaced
13:48780e181b38 14:578be2adaf3e
    61 </ul> <p>The SUPL WAP Push handler plug-in and SUPL SMS Trigger plug-in use
    61 </ul> <p>The SUPL WAP Push handler plug-in and SUPL SMS Trigger plug-in use
    62 the SUPL Push API to notify the SUPL Protocol Module that an SLP is starting
    62 the SUPL Push API to notify the SUPL Protocol Module that an SLP is starting
    63 a network initiated location request. </p> <fig id="GUID-BEDFACD2-D262-500C-ACF5-37679F7FA091">
    63 a network initiated location request. </p> <fig id="GUID-BEDFACD2-D262-500C-ACF5-37679F7FA091">
    64 <title>              Figure 1: SUPL Push API and Symbian plug-ins        
    64 <title>              Figure 1: SUPL Push API and Symbian plug-ins        
    65    </title>
    65    </title>
    66 <image href="GUID-398483AD-C341-5777-AD23-381A067F9180_d0e460040_href.png" placement="inline"/>
    66 <image href="GUID-398483AD-C341-5777-AD23-381A067F9180_d0e457872_href.png" placement="inline"/>
    67 </fig> <p><b>SUPL
    67 </fig> <p><b>SUPL
    68 WAP Push plug-in</b> </p> <p>The Symbian platform includes the WAP Push Framework
    68 WAP Push plug-in</b> </p> <p>The Symbian platform includes the WAP Push Framework
    69 to process WAP Push messages. If the Symbian SUPL WAP Push plug-in is installed,
    69 to process WAP Push messages. If the Symbian SUPL WAP Push plug-in is installed,
    70 the WAP Push Framework uses it to process <codeph>SUPL INIT</codeph> messages
    70 the WAP Push Framework uses it to process <codeph>SUPL INIT</codeph> messages
    71 sent by WAP Push. The plug-in calls the methods of the SUPL Push API causing
    71 sent by WAP Push. The plug-in calls the methods of the SUPL Push API causing
   102 the LBS subsystem. Figure 2 shows the SUPL Push API sender classes. Licensees
   102 the LBS subsystem. Figure 2 shows the SUPL Push API sender classes. Licensees
   103 use the API sender classes to implement their own <codeph>SUPL INIT</codeph> handler
   103 use the API sender classes to implement their own <codeph>SUPL INIT</codeph> handler
   104 (if required). </p> <fig id="GUID-47957CAE-DC5F-55C9-B157-6274D00B0990">
   104 (if required). </p> <fig id="GUID-47957CAE-DC5F-55C9-B157-6274D00B0990">
   105 <title>                 Figure 2: Class diagram of SUPL Push API sender classes
   105 <title>                 Figure 2: Class diagram of SUPL Push API sender classes
   106               </title>
   106               </title>
   107 <image href="GUID-0A24FF35-5A61-5305-812B-632F20F0395D_d0e460144_href.png" placement="inline"/>
   107 <image href="GUID-0A24FF35-5A61-5305-812B-632F20F0395D_d0e457976_href.png" placement="inline"/>
   108 </fig> <table id="GUID-01E93B41-A2AB-5251-947D-E4839A0AC71D">
   108 </fig> <table id="GUID-01E93B41-A2AB-5251-947D-E4839A0AC71D">
   109 <tgroup cols="3"><colspec colname="col0"/><colspec colname="col1"/><colspec colname="col2"/>
   109 <tgroup cols="3"><colspec colname="col0"/><colspec colname="col1"/><colspec colname="col2"/>
   110 <thead>
   110 <thead>
   111 <row>
   111 <row>
   112 <entry>Class name</entry>
   112 <entry>Class name</entry>
   176 INIT</codeph> messages. </p> <p>Figure 3 shows the SUPL Push API receiver
   176 INIT</codeph> messages. </p> <p>Figure 3 shows the SUPL Push API receiver
   177 classes. Symbian licensees do not need to use the receiver classes - they
   177 classes. Symbian licensees do not need to use the receiver classes - they
   178 are used by the Symbian reference SUPL Protocol Module. </p> <fig id="GUID-62800587-837F-5EC0-872C-AA505491E3E0">
   178 are used by the Symbian reference SUPL Protocol Module. </p> <fig id="GUID-62800587-837F-5EC0-872C-AA505491E3E0">
   179 <title>                 Figure 3: Class diagram of SUPL Push API receiver
   179 <title>                 Figure 3: Class diagram of SUPL Push API receiver
   180 classes               </title>
   180 classes               </title>
   181 <image href="GUID-120CA508-9984-54D0-B366-6D10D646FD49_d0e460374_href.png" placement="inline"/>
   181 <image href="GUID-120CA508-9984-54D0-B366-6D10D646FD49_d0e458206_href.png" placement="inline"/>
   182 </fig> <table id="GUID-1D1A1ED6-1BEC-575C-98B4-1B93F6F5D1DD">
   182 </fig> <table id="GUID-1D1A1ED6-1BEC-575C-98B4-1B93F6F5D1DD">
   183 <tgroup cols="3"><colspec colname="col0"/><colspec colname="col1"/><colspec colname="col2"/>
   183 <tgroup cols="3"><colspec colname="col0"/><colspec colname="col1"/><colspec colname="col2"/>
   184 <thead>
   184 <thead>
   185 <row>
   185 <row>
   186 <entry>Class name</entry>
   186 <entry>Class name</entry>
   222 may be another error code as decribed in the API reference documentation. </p> <p>Note
   222 may be another error code as decribed in the API reference documentation. </p> <p>Note
   223 that the SUPL Protocol Module calls <xref href="GUID-B26D8EEC-9DD0-373C-8B29-38C6AC06390C.dita#GUID-B26D8EEC-9DD0-373C-8B29-38C6AC06390C/GUID-049D2C6E-7892-3223-9AC3-B130E0AE7FCC"><apiname>CSuplPushRec::SuplInitComplete()</apiname></xref> when
   223 that the SUPL Protocol Module calls <xref href="GUID-B26D8EEC-9DD0-373C-8B29-38C6AC06390C.dita#GUID-B26D8EEC-9DD0-373C-8B29-38C6AC06390C/GUID-049D2C6E-7892-3223-9AC3-B130E0AE7FCC"><apiname>CSuplPushRec::SuplInitComplete()</apiname></xref> when
   224 the <codeph>SUPL           INIT</codeph> message is received, but this does
   224 the <codeph>SUPL           INIT</codeph> message is received, but this does
   225 not guarantee that the network initiated location request will complete successfully. </p> <fig id="GUID-AF4F52FA-F4CC-58E0-BD6F-5C74BC6B6ECD">
   225 not guarantee that the network initiated location request will complete successfully. </p> <fig id="GUID-AF4F52FA-F4CC-58E0-BD6F-5C74BC6B6ECD">
   226 <title>              Figure 4: SUPL Push API sequence diagram            </title>
   226 <title>              Figure 4: SUPL Push API sequence diagram            </title>
   227 <image href="GUID-84623607-ACCA-5E57-9001-DA56E16C1652_d0e460570_href.png" placement="inline"/>
   227 <image href="GUID-84623607-ACCA-5E57-9001-DA56E16C1652_d0e458402_href.png" placement="inline"/>
   228 </fig> </section>
   228 </fig> </section>
   229 <section id="GUID-202D83AC-6C99-5481-8074-ACFEBD426AE3"><title>References</title> <p>[1] <xref href="http://www.openmobilealliance.org" scope="external">Open Mobile Alliance</xref> Secure
   229 <section id="GUID-202D83AC-6C99-5481-8074-ACFEBD426AE3"><title>References</title> <p>[1] <xref href="http://www.openmobilealliance.org" scope="external">Open Mobile Alliance</xref> Secure
   230 User Plane Location (SUPL) Architecture OMA-AD-SUPL-V1_0-20070615-A </p> </section>
   230 User Plane Location (SUPL) Architecture OMA-AD-SUPL-V1_0-20070615-A </p> </section>
   231 </conbody><related-links>
   231 </conbody><related-links>
   232 <link href="GUID-EE07DF44-6B3B-5D9A-A794-C49863597721.dita"><linktext>SUPL    
   232 <link href="GUID-EE07DF44-6B3B-5D9A-A794-C49863597721.dita"><linktext>SUPL