OMA InternetLocationProtocol

Internal Location Protocol
Approved Version 2.0.1 5 Dec 2012
Open Mobile Alliance OMA-TS-ILP-V2_0_1-20121205-A
2012 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
[OMA-Template-Spec-20120101-I]
OMA-TS-ILP-V2_0_1-20121205-A
Page 2 (295)
Use of this document is subject to all of the terms and conditions of the Use Agreement located at http://www.openmobilealliance.org/UseAgreement.html. Unless this document is clearly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance specification, and is subject to revision or removal without notice. You may use this document or any part of the document for internal or educational purposes only, provided you do not modify, edit or take out of context the information in this document in any manner. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document. Each Open Mobile Alliance member has agreed to use reasonable endeavors to inform the Open Mobile Alliance in a timely manner of Essential IPR as it becomes aware that the Essential IPR is related to the prepared or published specification. However, the members do not have an obligation to conduct IPR searches. The declared Essential IPR is publicly available to members and non-members of the Open Mobile Alliance and may be found on the OMA IPR Declarations list at http://www.openmobilealliance.org/ipr.html. The Open Mobile Alliance has not conducted an independent IPR review of this document and the information contained herein, and makes no representations or warranties regarding third party IPR, including without limitation patents, copyrights or trade secret rights. This document may contain inventions for which you must obtain licenses from third parties before making, using or selling the inventions. Defined terms above are set forth in the schedule to the Open Mobile Alliance Application Form. NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER OR ITS AFFILIATES REGARDING ANY OF THE IPRS REPRESENTED ON THE OMA IPR DECLARATIONS LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY, COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR NOT SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL. THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS. 2012 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. Under the terms set forth above.
OMA-TS-ILP-V2_0_1-20121205-A
Page 3 (295)
Contents
1. 2. SCOPE .............................................................................................................................................................................. 12 REFERENCES ................................................................................................................................................................ 13 2.1 NORMATIVE REFERENCES ........................................................................................................................................ 13 3. TERMINOLOGY AND CONVENTIONS .................................................................................................................... 15 3.1 CONVENTIONS ........................................................................................................................................................... 15 3.2 DEFINITIONS.............................................................................................................................................................. 15 3.3 ABBREVIATIONS ........................................................................................................................................................ 15 4. INTRODUCTION ........................................................................................................................................................... 17 DETAILED FLOWS IMMEDIATE SERVICE ........................................................................................................ 18 5.1 NETWORK INITIATED PROXY MODE ..................................................................................................................... 18 5.1.1 Non-Roaming Successful Case .......................................................................................................................... 19 5.1.2 Roaming with V-SLP Positioning Successful Case ........................................................................................... 21 5.1.3 Roaming with H-SLP Positioning Successful Case ........................................................................................... 24 5.1.4 Non-Roaming Successful Case, Notification/Verification based on current location ....................................... 28 5.1.5 Roaming with V-SLP Positioning Successful Case, Notification/Verification based on current location......... 30 5.1.6 Roaming with H-SLP Positioning Successful Case, Notification/Verification based on current location......... 34 5.2 NETWORK INITIATED NON-PROXY MODE ............................................................................................................ 36 5.2.1 Non-Roaming Successful Case .......................................................................................................................... 37 5.2.2 Roaming with V-SPC Positioning Successful Case ........................................................................................... 39 5.2.3 Roaming with H-SPC Positioning Successful Case ........................................................................................... 42 5.2.4 Non-Roaming Successful Case, Notification/Verification based on current location ....................................... 46 5.2.5 Roaming with V-SPC Positioning Successful Case, Notification/Verification based on current location ........ 48 5.2.6 Roaming with H-SPC Positioning Successful Case, Notification/Verification based on current location ........ 52 5.3 EXCEPTION PROCEDURES......................................................................................................................................... 56 5.3.1 SET Does Not Allow Positioning for Non Roaming ......................................................................................... 56 5.3.2 SET Does Not Allow Positioning for Roaming with V-SLP ............................................................................. 57 5.3.3 SET Does Not Allow Positioning for Roaming with H-SLP ............................................................................. 59 5.3.4 SUPL Protocol Error .......................................................................................................................................... 59 5.3.5 Timer expiration................................................................................................................................................. 60 5.4 SET INITIATED PROXY MODE ................................................................................................................................ 60 5.4.1 Non-Roaming Successful Case .......................................................................................................................... 60 5.4.2 Roaming with V-SLP Positioning Successful Case ........................................................................................... 62 5.4.3 Roaming with H-SLP Positioning Successful Case ........................................................................................... 65 5.4.4 SET-Initiated Location Request of another SET ................................................................................................ 68 5.4.5 Location Request of Transfer Location to Third Party ...................................................................................... 68 5.5 SET INITIATED NON-PROXY MODE ....................................................................................................................... 68 5.5.1 Non-Roaming Successful Case .......................................................................................................................... 69 5.5.2 Roaming with V-SPC Positioning Successful Case ........................................................................................... 71 5.5.3 Roaming with H-SPC Positioning Successful Case ........................................................................................... 73 5.5.4 SET-Initiated Location Request of another SET ................................................................................................ 76 5.5.5 Location Request of Transfer Location to Third Party ...................................................................................... 76 5.6 EXCEPTION PROCEDURES......................................................................................................................................... 76 5.6.1 SET Authorization Failure ................................................................................................................................. 76 5.6.2 SUPL Protocol Error .......................................................................................................................................... 76 5.6.3 Timer expiration................................................................................................................................................. 76 5.7 EMERGENCY SERVICES LOCATION REQUEST PROXY MODE ............................................................................... 76 5.7.1 Non-Roaming Successful Case .......................................................................................................................... 77 5.7.2 Roaming with V-SLP Positioning Successful Case ........................................................................................... 79 5.8 EMERGENCY SERVICES LOCATION REQUEST NON-PROXY MODE ...................................................................... 81 5.8.1 Non-Roaming Successful Case .......................................................................................................................... 82 5.8.2 Roaming Successful Case with V-SPC Positioning ........................................................................................... 84 6. DETAILED FLOWS - TRIGGERED SERVICES: PERIODIC TRIGGERS ........................................................... 88 5.
OMA-TS-ILP-V2_0_1-20121205-A
Page 4 (295)
6.1 NETWORK INITIATED PROXY MODE ...................................................................................................................... 88 6.1.1 Non-Roaming Successful Case .......................................................................................................................... 89 6.1.2 Roaming with V-SLP Positioning Successful Case ........................................................................................... 93 6.1.3 Roaming with H-SLP Positioning Successful Case ........................................................................................... 99 6.2 NETWORK INITIATED NON-PROXY MODE ........................................................................................................... 105 6.2.1 Non-Roaming Successful Case ........................................................................................................................ 105 6.2.2 Roaming with V-SPC Positioning Successful Case ......................................................................................... 109 6.2.3 Roaming with H-SPC Positioning Successful Case ......................................................................................... 115 6.3 EXCEPTION PROCEDURES....................................................................................................................................... 121 6.3.1 SET does not allow Triggered Position ........................................................................................................... 121 6.3.2 Network cancels the triggered location request ............................................................................................... 121 6.3.3 SET cancels the triggered location request ...................................................................................................... 122 6.4 SET INITIATED PROXY MODE .............................................................................................................................. 123 6.4.1 Non-Roaming Successful Case ........................................................................................................................ 123 6.4.2 Roaming with V-SLP Positioning Successful Case ......................................................................................... 125 6.4.3 Roaming with H-SLP Positioning Successful Case ......................................................................................... 128 6.5 SET INITIATED NON-PROXY MODE ..................................................................................................................... 131 6.5.1 Non-Roaming Successful Case ........................................................................................................................ 132 6.5.2 Roaming with V-SPC Positioning Successful Case ......................................................................................... 134 6.5.3 Roaming with H-SPC Positioning Successful Case ......................................................................................... 137 6.6 SET INITIATED PERIODIC LOCATION REQUEST WITH TRANSFER TO 3RD PARTY PROXY MODE ...................... 140 6.6.1 Non-Roaming Successful Case ........................................................................................................................ 141 6.6.2 Roaming with V-SLP Positioning Successful Case ......................................................................................... 145 6.6.3 Roaming with H-SLP Positioning Successful Case ......................................................................................... 150 6.7 SET INITIATED PERIODIC LOCATION REQUEST WITH TRANSFER TO 3RD PARTY NON-PROXY MODE ............. 155 6.7.1 Non-Roaming Successful Case ........................................................................................................................ 155 6.7.2 Roaming with V-SPC Positioning Successful Case ......................................................................................... 158 6.7.3 Roaming with H-SPC Positioning Successful Case ......................................................................................... 163 6.8 RETRIEVAL OF HISTORICAL POSITIONS AND/OR ENHANCED CELL SECTOR MEASUREMENTS .......................... 168 6.8.1 Retrieval of Historical Position Results non-roaming successful case ......................................................... 168 6.8.2 Retrieval of Historical Position Results roaming successful case ................................................................. 170 6.9 V-SLP TO V-SLP HANDOVER ................................................................................................................................ 171 6.10 V-SPC TO V-SPC HANDOVER ................................................................................................................................ 171 7. DETAILED FLOWS - TRIGGERED SERVICES: AREA EVENT TRIGGERS................................................... 172 7.1 NETWORK INITIATED PROXY MODE .................................................................................................................... 172 7.1.1 Non-Roaming Successful Case ........................................................................................................................ 173 7.1.2 Roaming with V-SLP Positioning Successful Case ......................................................................................... 176 7.1.3 Roaming with H-SLP Positioning Successful Case ......................................................................................... 180 7.2 NETWORK INITIATED NON-PROXY MODE ........................................................................................................... 184 7.2.1 Non-Roaming Successful Case ........................................................................................................................ 185 7.2.2 Roaming with V-SPC Positioning Successful Case ......................................................................................... 188 7.2.3 Roaming with H-SPC Positioning Successful Case ......................................................................................... 191 7.3 SET INITIATED PROXY MODE .............................................................................................................................. 195 7.3.1 Non-Roaming Successful Case ........................................................................................................................ 196 7.3.2 Roaming with V-SLP Positioning Successful Case ......................................................................................... 198 7.3.3 Roaming with H-SLP Positioning Successful Case ......................................................................................... 202 7.4 SET INITIATED NON-PROXY MODE ..................................................................................................................... 204 7.4.1 Non-Roaming Successful Case ........................................................................................................................ 205 7.4.2 Roaming with V-SPC Positioning Successful Case ......................................................................................... 207 7.4.3 Roaming with H-SPC Positioning Successful Case ......................................................................................... 210 7.5 NETWORK/SET CAPABILITIES CHANGE FOR AREA EVENT TRIGGERED SCENARIOS.......................................... 213 8. DETAILED FLOWS SLC/SPC HEARTBEAT ....................................................................................................... 214 8.1 SUCCESSFUL PALIVE EXCHANGE ......................................................................................................................... 214 8.2 PALIVE ERROR HANDLING................................................................................................................................... 214 9. SECURITY CONSIDERATIONS ............................................................................................................................... 216 9.1 SLC-SPC SECURITY ............................................................................................................................................... 216
OMA-TS-ILP-V2_0_1-20121205-A
Page 5 (295)
9.2 NON-PROXY MODE MUTUAL AUTHENTICATION KEY REFRESH MECHANISM .................................................... 216 9.2.1 Mutual Authentication Key Refresh Mechanism for non roaming .................................................................. 216 9.2.2 Mutual Authentication Key Refresh Mechanism for roaming with V-SLP ..................................................... 217 9.2.3 Mutual Authentication Key Refresh Mechanism for roaming with H-SLP ..................................................... 218 10. PROTOCOLS AND INTERFACES ........................................................................................................................ 219 10.1 TCP/IP .................................................................................................................................................................... 219 10.2 LLP........................................................................................................................................................................... 219 10.2.1 Positioning Control .......................................................................................................................................... 219 10.2.2 Positioning Data ............................................................................................................................................... 220 11. ILP MESSAGE DEFINITIONS (NORMATIVE) .................................................................................................. 221 11.1 COMMON PART ....................................................................................................................................................... 221 11.2 MESSAGE SPECIFIC PART ....................................................................................................................................... 221 11.2.1 PREQ ............................................................................................................................................................... 222 11.2.2 PRES ................................................................................................................................................................ 223 11.2.3 PRPT ................................................................................................................................................................ 224 11.2.4 PLREQ ............................................................................................................................................................. 224 11.2.5 PLRES ............................................................................................................................................................. 224 11.2.6 PINIT ............................................................................................................................................................... 225 11.2.7 PAUTH ............................................................................................................................................................ 226 11.2.8 PALIVE ........................................................................................................................................................... 227 11.2.9 PEND ............................................................................................................................................................... 227 11.2.10 PMESS ......................................................................................................................................................... 227 12. PARAMETER DEFINITIONS (NORMATIVE) .................................................................................................... 229 12.1 VERSION .................................................................................................................................................................. 229 12.2 SESSION ID2 ............................................................................................................................................................ 229 12.2.1 SLC Session ID ................................................................................................................................................ 230 12.2.2 SET Session ID ................................................................................................................................................ 230 12.2.3 SPC Session ID ................................................................................................................................................ 231 12.3 POSITIONING METHOD ........................................................................................................................................... 231 12.4 SLP MODE............................................................................................................................................................... 232 12.5 LOCATION ID .......................................................................................................................................................... 233 12.5.1 GSM Cell Info ................................................................................................................................................. 233 12.5.2 WCDMA/TD-SCDMA Cell Info ..................................................................................................................... 234 12.5.3 LTE Cell Info ................................................................................................................................................... 236 12.5.4 CDMA Cell Info .............................................................................................................................................. 237 12.5.5 HRPD Cell Info ............................................................................................................................................... 238 12.5.6 UMB Cell Info ................................................................................................................................................. 238 12.5.7 WLAN AP Info ................................................................................................................................................ 239 12.5.8 WiMAX BS Info .............................................................................................................................................. 240 12.6 POSITION ................................................................................................................................................................. 242 12.7 TRIGGER PARAMS ................................................................................................................................................... 243 12.8 SPC_SET_KEY ....................................................................................................................................................... 243 12.9 SPC-TID ................................................................................................................................................................. 243 12.10 SPC_SET_KEY_LIFETIME ................................................................................................................................. 243 12.11 QOP ..................................................................................................................................................................... 244 12.12 SPC STATUS CODE.............................................................................................................................................. 244 12.13 NUMBER OF FIX................................................................................................................................................... 244 12.14 SET CAPABILITIES.............................................................................................................................................. 245 12.15 REQUESTED ASSISTANCE DATA ......................................................................................................................... 248 12.16 POSITIONING PAYLOAD ...................................................................................................................................... 253 12.17 MULTIPLE LOCATION IDS .................................................................................................................................. 254 12.18 VELOCITY ............................................................................................................................................................ 254 12.19 UTRAN GPS REFERENCE TIME RESULT .......................................................................................................... 255 12.20 UTRAN GANSS REFERENCE TIME RESULT .................................................................................................... 256 12.21 UTRAN GPS REFERENCE TIME ASSISTANCE................................................................................................... 257 12.22 UTRAN GANSS REFERENCE TIME ASSISTANCE ............................................................................................. 258
OMA-TS-ILP-V2_0_1-20121205-A
Page 6 (295)
12.23 GNSS POSITIONING TECHNOLOGY.................................................................................................................... 259 12.24 APPROVED POSITIONING METHODS .................................................................................................................. 259 12.25 SUPPORTED POSITIONING METHODS ................................................................................................................. 261 12.26 PREFERRED POSITIONING METHOD................................................................................................................... 262 12.27 STATUS CODE ...................................................................................................................................................... 263 13. ASN.1 ENCODING OF ILP MESSAGES (NORMATIVE) .................................................................................. 265 13.1 COMMON PART ....................................................................................................................................................... 265 13.2 MESSAGE SPECIFIC PART ....................................................................................................................................... 266 13.2.1 PREQ ............................................................................................................................................................... 266 13.2.2 PRES ................................................................................................................................................................ 267 13.2.3 PRPT ................................................................................................................................................................ 267 13.2.4 PLREQ ............................................................................................................................................................. 267 13.2.5 PLRES ............................................................................................................................................................. 268 13.2.6 PINIT ............................................................................................................................................................... 268 13.2.7 PAUTH ............................................................................................................................................................ 271 13.2.8 PALIVE ........................................................................................................................................................... 271 13.2.9 PEND ............................................................................................................................................................... 271 13.2.10 PMESS ......................................................................................................................................................... 272 13.3 COMMON ELEMENTS .............................................................................................................................................. 272 APPENDIX A. CHANGE HISTORY (INFORMATIVE) ............................................................................................ 286 A.1 APPROVED VERSION HISTORY ............................................................................................................................... 286 A.1.1 Draft/Candidate Version 2.0.1 History ............................................................................................................ 286 APPENDIX B. STATIC CONFORMANCE REQUIREMENTS (NORMATIVE) ................................................... 287 B.1 SCR FOR SLC ......................................................................................................................................................... 287 B.1.1 SLC Procedures ............................................................................................................................................... 287 B.1.2 ILP Protocol Interface ...................................................................................................................................... 287 B.1.3 ILP Messages ................................................................................................................................................... 287 B.1.4 Support of Parameters for Optional Functions ................................................................................................. 287 B.2 SCR FOR SPC.......................................................................................................................................................... 289 B.2.1 SPC Procedures................................................................................................................................................ 289 B.2.2 ILP Protocol Interface ...................................................................................................................................... 289 B.2.3 ILP Messages ................................................................................................................................................... 289 B.2.4 Support of Parameters for Optional Functions ................................................................................................. 289 APPENDIX C. TIMER TABLES ................................................................................................................................... 292 C.1 ILP TIMERS ............................................................................................................................................................. 292 C.2 ULP TIMERS ........................................................................................................................................................... 293
Figures
Figure 1: Network Initiated Non-Roaming Successful Case Proxy Mode ....................................................................... 19 Figure 2: Network Initiated Roaming Successful Case Proxy mode with V-SLP positioning ....................................... 22 Figure 3: Network Initiated Roaming Successful case Proxy mode with H-SLP positioning ........................................ 25 Figure 4: Notification/Verification based on current location, Network Initiated Non-Roaming Successful Case Proxy Mode ...................................................................................................................................................................... 28 Figure 5: Notification/Verification based on current location, Network Initiated Roaming Successful Case Proxy mode with V-SLP positioning ......................................................................................................................................... 31 Figure 6: Notification/Verification based on current location, Network Initiated Roaming Successful case Proxy mode with H-SLP positioning ......................................................................................................................................... 34 Figure 7: Network Initiated Non-Roaming Successful Case Non-Proxy mode ............................................................... 37
OMA-TS-ILP-V2_0_1-20121205-A
Page 7 (295)
Figure 8: Network Initiated Roaming Successful Case Non-Proxy-mode with V-SPC positioning .............................. 40 Figure 9: Network Initiated Roaming Successful Case Non-Proxy-mode with H-SPC .................................................. 43 Figure 10: Notification/Verification based on current location, Network Initiated Non-Roaming Successful Case Non-Proxy mode .............................................................................................................................................................. 46 Figure 11: Notification/Verification based on current location, Network Initiated Roaming Successful Case NonProxy-mode with V-SPC positioning.............................................................................................................................. 49 Figure 12: Notification/Verification based on current location, Network Initiated Roaming Successful Case NonProxy-mode with H-SPC positioning ............................................................................................................................. 53 Figure 13: Network Initiated SET User Rejects Positioning for Non-Roaming. ................................................................ 56 Figure 14: Network Initiated SET User Denies Positioning for Roaming with V-SLP ..................................................... 58 Figure 15: SET-Initiated Non-Roaming Successful Case Proxy mode ............................................................................ 60 Figure 16: SET-Initiated Roaming Successful Case Proxy mode with V-SLP positioning ............................................ 63 Figure 17: SET-Initiated Roaming Successful Case Proxy mode with H-SLP positioning ............................................ 66 Figure 18: SET-Initiated Non-Roaming Successful Case Non-Proxy mode .................................................................... 69 Figure 19: SET-Initiated Roaming Successful Case Non-Proxy mode with V-SPC positioning .................................... 71 Figure 20: SET-Initiated Roaming Successful Case Non-Proxy mode with H-SPC positioning ................................... 74 Figure 21: Network Initiated Emergency Services Non-Roaming Successful Case Proxy Mode .................................. 77 Figure 22: Network Initiated Emergency Services Roaming Successful Case Proxy Mode with V-SLP positioning .. 79 Figure 23: Network Initiated Non-Roaming Successful Case Non-Proxy mode ............................................................. 82 Figure 24: Network Initiated Roaming Successful Case Non-Proxy-mode with V-SPC positioning ............................ 85 Figure 25: Network Initiated Periodic Trigger Service Non-Roaming Successful Case Proxy Mode (Part I) ............. 89 Figure 26: Network Initiated Periodic Trigger Service Non-Roaming Successful Case Proxy Mode (Part II) ........... 90 Figure 27: Network Initiated Periodic Trigger Service Roaming Successful Case Proxy with V-SLP positioning (Part I) ........................................................................................................................................................................................ 94 Figure 28: Network Initiated Periodic Trigger Service Roaming Successful Case Proxy with V-SLP positioning (Part II) ....................................................................................................................................................................................... 95 Figure 29: Network Initiated Periodic Trigger Service Roaming Successful Case Proxy with H-SLP positioning (Part I) ............................................................................................................................................................................ 100 Figure 30: Network Initiated Periodic Trigger Service Roaming Successful Case Proxy with H-SLP positioning (Part II) ........................................................................................................................................................................... 101 Figure 31: Network Initiated Periodic Trigger Service Non-Roaming Successful Case Non-Proxy Mode (Part I) ... 105 Figure 32: Network Initiated Periodic Trigger Service Non-Roaming Successful Case Non-Proxy Mode (Part II) . 106 Figure 33: Network Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning (Part I) ............................................................................................................................................................................ 110 Figure 34: Network Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning (Part II) ........................................................................................................................................................................... 111
OMA-TS-ILP-V2_0_1-20121205-A
Page 8 (295)
Figure 35: Network Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning (Part I) ............................................................................................................................................................................ 116 Figure 36: Network Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning (Part II) ........................................................................................................................................................................... 117 Figure 37: Network Initiated Triggered location, Network cancels the triggered location request ............................... 121 Figure 38: Network Initiated Triggered location, SET cancels the triggered location request ...................................... 122 Figure 39: SET Initiated Periodic Trigger Service Non-Roaming Successful Case Proxy Mode ................................ 123 Figure 40: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with V-SLP positioning .......... 126 Figure 41: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with H-SLP positioning .......... 129 Figure 42: SET Initiated Periodic Trigger Service Non-Roaming Successful Case Non-Proxy Mode........................ 132 Figure 43: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning .. 135 Figure 44: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning . 138 Figure 45: SET Periodic Trigger Service Non-Roaming Successful Case Proxy Mode (Part I) .................................. 141 Figure 46: SET Periodic Trigger Service Non-Roaming Successful Case Proxy Mode (Part II) ................................ 142 Figure 47: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with V-SLP positioning (Part I) ......................................................................................................................................................................................... 145 Figure 48: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with V-SLP positioning (Part II) ......................................................................................................................................................................................... 146 Figure 49: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with H-SLP positioning (Part I) ......................................................................................................................................................................................... 150 Figure 50: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with H-SLP positioning (Part II) ......................................................................................................................................................................................... 151 Figure 51: SET Initiated Periodic Trigger Service Non-Roaming Successful Case Non-Proxy Mode (Part I) .......... 155 Figure 52: SET Initiated Periodic Trigger Service Non-Roaming Successful Case Non-Proxy Mode (Part II) ........ 156 Figure 53: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning (Part I) ............................................................................................................................................................................ 159 Figure 54: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning (Part II) ........................................................................................................................................................................... 160 Figure 55: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning (Part I) ............................................................................................................................................................................ 164 Figure 56: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning (Part II) ........................................................................................................................................................................... 165 Figure 57: Retrieval of historical positions and/or enhanced cell/sector measurements non-roaming ....................... 169 Figure 58: Retrieval of historical positions and/or enhanced cell/sector measurements roaming ............................... 170 Figure 59: Network Initiated Area Event Trigger Service Non-Roaming Successful Case Proxy Mode.................... 173 Figure 60: Network Initiated Area Event Trigger Service Roaming Successful Case Proxy with V-SLP positioning ......................................................................................................................................................................................... 177
OMA-TS-ILP-V2_0_1-20121205-A
Page 9 (295)
Figure 61: Network Initiated Area Event Trigger Service Roaming Successful Case Proxy with H-SLP positioning ......................................................................................................................................................................................... 181 Figure 62: Network Initiated Area Event Trigger Service Non-Roaming Successful Case Non-Proxy Mode ........... 185 Figure 63: Network Initiated Area Event Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning ...................................................................................................................................................................... 188 Figure 64: Network Initiated Area Event Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning ...................................................................................................................................................................... 192 Figure 65: SET Initiated Area Event Trigger Service Non-Roaming Successful Case Proxy Mode ........................... 196 Figure 66: SET Initiated Area Event Trigger Service Roaming Successful Case Proxy with V-SLP positioning ..... 199 Figure 67: SET Initiated Area Event Trigger Service Roaming Successful Case Proxy with H-SLP positioning ..... 202 Figure 68: SET Initiated Area Event Trigger Service Non-Roaming Successful Case Non-Proxy Mode .................. 205 Figure 69: SET Initiated Area Event Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning ......................................................................................................................................................................................... 208 Figure 70: SET Initiated Area Event Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning ......................................................................................................................................................................................... 211 Figure 71: Successsful PALIVE exchange ........................................................................................................................... 214 Figure 72: PALIVE Error handling ..................................................................................................................................... 214 Figure 73: Mutual authentication key refresh mechanism for non roaming.................................................................... 216 Figure 74: Mutual authentication key refresh mechanism for roaming with V-SLP ...................................................... 217
Tables
Table 1: Llp Positioning Control .......................................................................................................................................... 219 Table 2: Llp Positioning Data ............................................................................................................................................... 220 Table 3: Common Part .......................................................................................................................................................... 221 Table 4: PREQ Message ........................................................................................................................................................ 223 Table 5: PRES Message ......................................................................................................................................................... 223 Table 6: PRPT Message ........................................................................................................................................................ 224 Table 7: PLREQ Message ..................................................................................................................................................... 224 Table 8: PLRES Message ...................................................................................................................................................... 224 Table 9: PINIT Message ........................................................................................................................................................ 226 Table 10: PAUTH Message ................................................................................................................................................... 227 Table 11: PALIVE Message .................................................................................................................................................. 227 Table 12: PEND Message ...................................................................................................................................................... 227 Table 13: PMESS Message.................................................................................................................................................... 228 Table 14: Version Parameter ................................................................................................................................................ 229
OMA-TS-ILP-V2_0_1-20121205-A
Page 10 (295)
Table 15: Session ID2 Parameter ......................................................................................................................................... 230 Table 16: SLC Session ID Parameter ................................................................................................................................... 230 Table 17: SET Session ID Parameter ................................................................................................................................... 231 Table 18: SPC Session ID Parameter ................................................................................................................................... 231 Table 19: Positioning Method Parameter ............................................................................................................................ 232 Table 20: SLP Mode Parameter ........................................................................................................................................... 233 Table 21: Location ID Parameter ......................................................................................................................................... 233 Table 22: GSM Cell Info Parameter .................................................................................................................................... 234 Table 23: WCDMA/TD-SCDMA Cell Info Parameter ...................................................................................................... 236 Table 24: LTE Cell Info ........................................................................................................................................................ 237 Table 25: CDMA Cell Info .................................................................................................................................................... 238 Table 26: HRPD Cell Info ..................................................................................................................................................... 238 Table 27: UMB Cell Info ....................................................................................................................................................... 239 Table 28: WLAN AP Info ..................................................................................................................................................... 239 Table 29: WiMAX BS Info .................................................................................................................................................... 241 Table 30: Position Parameter ............................................................................................................................................... 242 Table 31: Trigger Parameter ................................................................................................................................................ 243 Table 32: SPC_SET_Key Parameter ................................................................................................................................... 243 Table 33: SPC-TID Parameter ............................................................................................................................................. 243 Table 34: SPC_SET_Key_lifetime Parameter .................................................................................................................... 244 Table 35: QoP Parameter ...................................................................................................................................................... 244 Table 36: Status Code Parameter ......................................................................................................................................... 244 Table 37: Number of Fix Parameter .................................................................................................................................... 244 Table 38: SET Capabilities Parameter ................................................................................................................................ 248 Table 39: Requested Assistance Data Parameter ................................................................................................................ 253 Table 40: Positioning Payload Parameter ........................................................................................................................... 253 Table 41: Multiple Location ID Parameter ......................................................................................................................... 254 Table 42: Velocity Parameter ............................................................................................................................................... 255 Table 43: UTRAN GPS Reference Time Result .................................................................................................................. 256 Table 44: UTRAN GANSS Reference Time Result ............................................................................................................ 257 Table 45: UTRAN GPS Reference Time Assistance ........................................................................................................... 258 Table 46: UTRAN GANSS Reference Time Assistance ..................................................................................................... 259
OMA-TS-ILP-V2_0_1-20121205-A
Page 11 (295)
Table 47: GNSS Positioning Technology ............................................................................................................................. 259 Table 48: Approved Positioning Methods ........................................................................................................................... 261 Table 49: Supported Positioning Methods........................................................................................................................... 262 Table 50: Preferred Positioning Method ............................................................................................................................. 263 Table 51: Status Code Parameter ......................................................................................................................................... 264 Table 52: SLC Timer Values ................................................................................................................................................ 292 Table 53: SPC Timer Values ................................................................................................................................................. 293 Table 54: SET Timer Values ................................................................................................................................................. 294 Table 55: SLP Timer Values ................................................................................................................................................. 295 Table 56 RLP Timer Values ................................................................................................................................................. 295
OMA-TS-ILP-V2_0_1-20121205-A
Page 12 (295)
1. Scope
This document describes the Internal Location Protocol (ILP) for SUPL 2.0. ILP is a protocol-level instantiation of the Llp reference point described in [SUPLAD2]. The protocol is used between the SLC (SUPL Location Center) and a SPC (SUPL Positioning Center). For more details about SUPL Requirements refer to [SUPLRD2]. For more details about SUPL architecture and call-flows, refer to [SUPLAD2] and [SUPL2 ULP TS].
OMA-TS-ILP-V2_0_1-20121205-A
Page 13 (295)
2. References
2.1 Normative References
3GPP TS 49.031 Base Station System Application Part LCS Extension (BSSAP -LE) URL: http://www.3gpp.org [3GPP GAD] [3GPP 36.213] [3GPP 36.321] 3GPP TS 23.032, Universal Geographical Area Description (GAD), URL: http://www.3GPP.org 3GPP TS 36.213, Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures URL:http://www.3GPP.org/ 3GPP TS 36.321, Evolved Universal Terrestrial Radio Access (E -UTRA) Medium Access Control (MAC) protocol specification URL:http://www.3GPP.org/ 3GPP TS 36.331 Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification URL:http://www.3gpp.org/ 3GPP TS 25.331, Radio Resource Control (RRC) Protocol Specification, URL: http://www.3GPP.org/ 3GPP TS 44.031, Location Services (LCS); Mobile Station (MS) Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP), URL: http://www.3GPP.org/ 3GPP TS 36.355 Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP) URL:http://www.3gpp.org/ 3GPP2 C.S0024-A Version 3.0, September 2006; cdma2000 High Rate Packet Data Air Interface Specification, URL:http://www.3GPP.org/ 3GPP2 C.S0084-006 Version 2.0, August 2007, Connection Control Plane for Ultra Mobile Broadband (UMB) Air Interface Specification, URL:http://www.3gpp2.org/ [ASN.1] ITU-T Recommendation X.680: Information technology Abstract Syntax Notation One (ASN.1): Specification of basic notation, URL: http://www.itu.int/ITU-T/ [IEEE 802.16-2004] IEEE Std 802.16-2004, IEEE Standard for Local and metropolitan area networks, Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems, IEEE, 01-Oct-2004 URL:http://www.ieee802.org/16/published.html [IEEE 802.16e-2005] IEEE Std 802.16e-2005 and IEEE Std 80216-2004/Cor1-2005, IEEE Standard for Local and metropolitan area networks, Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems, Amendment 2: Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands, And Corrigendum 1, IEEE, 28-Feb-2006 URL:http://www.ieee802.org/16/published.html [OMAOPS] [PER] OMA Organization and Process, Version 1.6, Open Mobile Alliance, URL: http://www.openmobilealliance.org/ ITU-T Recommendation X.691: Information technology ASN.1 encoding rules: Specification of Packed Encoding Rules (PER), URL: http://www.itu.int/ITU-T/ [3GPP 49.031]
[3GPP LTE]
[3GPP RRC] [3GPP RRLP]
[3GPP LPP]
[3GPP2 HRPD]
[3GPP2 UMB]
OMA-TS-ILP-V2_0_1-20121205-A
Page 14 (295)
[RFC 2119] [RFC 3825]
Key words for use in RFCs to Indicate Requirement Levels, S. Brad ner, March 1997, URL: http://www.ietf.org/rfc/rfc2119.txt Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information, J. Polk, J. Schnizlein, M. Linsner, July 2004, URL:http://www.ietf.org/rfc/rfc3825.txt Secure User Plane Location Architecture, Versiion 2.0, Open Mobile Alliance, OMA-AD-SUPL-V2_0, URL: http//www.openmobilealliance.org/ Secure User Plane Location Requirements, Version 2.0, Open Mobile Alliance, OMA-RD-SUPL-V2_0, URL: http//www.openmobilealliance.org/ UserPlane Location Protocol, Version 2.0, Open Mobile Alliance, OMA-TS-ULP-V2, URL: http//www.openmobilealliance.org/ Mobile Station Land Station Compatibility Specification (AMPS), September 1989 URL:http://www.tiaonline.org/standards/
[SUPLAD2] [SUPLRD2] [SUPL2 ULP TS] [TIA-553]
[TIA-801]
C.S0022, Position Determination Service for cdma2000 Spread Spectrum Systems, URL: http://www.3gpp2.org/Public_html/specs/
[TLS]
Transport Layer Security (TLS) Version 1.1, IETF RFC 4346, April 2006 URL:http://www.ietf.org/rfc/rfc4346.txt
[X.694]
ITU-T Recommendation X.694: Information technology ASN.1 encoding rules: Mapping W3C XML schema definitions into ASN.1, URL:http://www.itu.int/ITU-T/studygroups/com17/languages/X694.pdf 3GPP TS 25.225 Physical Layer Measurements (TDD) URL:http://www.3gpp.org/
[3GPP 25.225]
OMA-TS-ILP-V2_0_1-20121205-A
Page 15 (295)
3. Terminology and Conventions

3.1 Conventions
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in [RFC 2119]. All sections and appendixes, except Scope and Introduction, are normative, unless they are explicitly indicated t o be informative.
3.2
Definitions
The Location ID defines the current serving cell, current serving WLAN AP or current serving WiMAX BS information of the SET. Major Versions are likely to contain major feature additions; MAY contain incompatibilities with previous specification revisions; and though unlikely, could change, drop, or replace standard or existing interfaces. Initial releases are 1_0. [OMAOPS] Minor versions are likely to contain minor feature additions, be compatible with the preceding Major Version. Minor specification revision include existing interfaces, although it MAY provide evolving interfaces. The initial minor release for any major release is 0, i.e. 1_0 [OMAOPS] The Multiple Location IDs parameter may contain current non-serving cell, current non-serving WLAN AP or current non-sercing WiMAX BS information for the SET and/or historic serving or non-serving cell, WLAN AP or WiMAX BS information for the SET. A set of attributes associated with a request for the geographic position of SET. Theattributes include the required horizontal accuracy, vertical accuracy, max location age, and response time of the SET position. Service Indicators are intended to be compatible with the Major_Minor release they relate to but add bug fixes. No new functions will be added through the release of Service Indicators. [OMAOPS] For positioning not associated with an emergency services call, SUPL Roaming occurs when a SET leaves the service area of its H-SLP. See [SUPL2 ULP TS] for a more detailed description.
Location ID Major Version
Minor Version
Multiple Location IDs
Quality of Position Service Indicator SUPL Roaming
3.3
A-GNSS A-GPS AP BS CI FQDN GANSS
Abbreviations
Assisted GNSS Assisted GPS Access Point (WLAN) Base Station (WiMAX) Cell Identity (3GPP) Fully Qualified Domain Name Galileo and Additional Navigation Satellite Systems GLObalnaya Navigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) Global Navigation Satellite System Global Positioning System Location Area Code (3GPP) Location ID Long Term Evolution Mobile Country Code (3GPP) Mobile Network Code (3GPP)
GLONASS GNSS GPS LAC Lid LTE MCC MNC
OMA-TS-ILP-V2_0_1-20121205-A
Page 16 (295)
NID OMA QoP QZSS RNC SBAS SET SID SLC SLP SM SMS SPC TCP TD-SCDMA ULP UMB WAP WCDMA WLAN
Network ID (C.S0022-A V1.0 ) Open Mobile Alliance Quality of Position Quasi-Zenith Satellite System Radio Network Controller Satellite Based Augmentation System SUPL Enabled Terminal System ID (C.S0022-A V1.0 ) SUPL Location Center SUPL Location Platform Short Message Short Message Service SUPL Positioning Center Transmission Control Protocol Time Division-Synchronous Code Division Multiple Access Userplane Location Protocol Ultra Mobile Broadband Wireless Application Protocol Wideband Code Division Multiple Access Wireless Local Area Network
OMA-TS-ILP-V2_0_1-20121205-A
Page 17 (295)
4. Introduction
This specification describes the ILP protocol, a protocol-level instantiation of the Llp reference point. The Llp reference point has been introduced into SUPL 2.0 to allow operators the use of an open interface (Llp) between the SLC and the SPC. Whether or not Llp is present in a particular implementation is optional. The presence (or absence) of Llp in a particular implementation is transparent to SUPL. The presence of Llp in an implementation does not in itself imply that SLC and SPC are deployed as physically separate network elements. The target audiences for this specification are developers, systems or network engineers developing or deploying SUPL.
OMA-TS-ILP-V2_0_1-20121205-A
Page 18 (295)
5. Detailed Flows Immediate Service

The flows in this section are those in which an immediate position is required. Set up and release of connections: Before sending any ULP messages the SET SHALL take needed actions such that a TLS connection exists to the SLP/SLC. This can be achieved by establishing a new connection, resume a connection or reuse an existing TLS connection. This includes establishment or utilization of various data connectivity resources that depends on the terminal in which the SET resides and the type of access network. Data connectivity below IP-level is out of scope of this document. The detailed flows in this section describe when a TLS connection no longer is needed. The TLS connection shall then be released unless another SUPL session is using the TLS connection.
5.1
Network Initiated Proxy Mode
This section describes Network Initiated Proxy mode scenarios. The Roaming cases are described with an R-SLC in the flow descriptions but the R-SLC can be omitted in the flow descriptions having the H-SLP interacting directly with SUPL Agent. In the Non-Roaming flow descriptions an R-SLC can be inserted between SUPL Agent and H-SLP.
OMA-TS-ILP-V2_0_1-20121205-A
Page 19 (295)
5.1.1
Non-Roaming Successful Case

H-SLC H-SPC Target SET
SUPL Agent
A B
MLP SLIR(ms-id, client-id, eqop)

SET Lookup, Routing Info
C LT1 D E F
PREQ(session-id2, QoP) PRES(session-id2) SUPL INIT(session-id, posmethod, SLP mode)
ST2
PT1 SUPL POS INIT(session-id, lid, SET capabilities, ver) PINIT(session-id2, lid, SET capabilities) PLREQ(session-id2, lid) PLRES(session-id2, posresult) PT2 SUPL POS
PMESS(session-id2, RRLP/RRC/TIA-801) SUPL POS(session-id, RRLP/RRC/TIA-801/LPP)
Data Connection Setup
G H I J
UT2
SUPL POS(session-id, RRLP/RRC/TIA-801/LPP) PMESS(session-id2, RRLP/RRC/TIA-801)
L M N MLP SLIA(posresult)
PEND(session-id2, position) SUPL END(session-id)
UT3
Figure 1: Network Initiated Non-Roaming Successful Case Proxy Mode NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP SLIR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the client-id. If a previously computed position which meets the requested QoP is available at the H-SLC and no notification or verification is required, the H-SLC SHALL directly proceed to step N. If notification and verification or notification only is required, the H-SLC SHALL proceed to step E after having performed the SET Lookup and Routing Info procedures of step B. B. The H-SLC verifies that the target SET is currently not SUPL Roaming. The H-SLC MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope.
OMA-TS-ILP-V2_0_1-20121205-A
Page 20 (295)
C. The H-SLC requests service from the H-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. D. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. E. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLP SHALL set notification mode to notification based on current location and SHALL NOT include the notification element in the SUPL INIT message; otherwise, the H-SLP SHALL set the notification mode indicator to normal notification and if notification or verification to the target subscriber is needed, the H-SLP SHALL also include the notification element in the SUPL INIT message.Before the SUPL INIT message is sent the H-SLC also computes and stores a hash of the message. If in step A the H-SLC decided to use a previously computed position, the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message carrying the results of the verification process (access granted, or access denied). If no explicit verification is required (notification only) the SET SHALL respond with a SUPL END message. The H-SLC SHALL then directly proceed to step N. NOTE 4: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step F and use the procedures described in step G to establish a secure connection to the H-SLC. F. The SET analyses the received SUPL INIT. If found to be non authentic SET takes no further actions. Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection.
G. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SET SHALL send the SUPL POS INIT message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. The H-SLC SHALL check that the hash of SUPL INIT matches the one it has computed for this particular session. H. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id and SET capabilities. The HSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step D, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL then determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step C. If required for the posmethod the H-SPC SHALL use the supported positioning protocol (e.g. RRLP, RRC, TIA-801 or LPP) from the PINIT message. If a position received from or calculated based on information received in the PINIT message is available that meets the required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session. I. If the H-SPC cannot translate the lid received in step H into a position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the HSPC can perform the translation from lid into a position itself.
OMA-TS-ILP-V2_0_1-20121205-A
Page 21 (295)
J.
This step is conditional and only occurs if step I was performed. The H-SLC reports the position result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the position meets the required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session.
K. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SLP (SET-Based). L. Once the position calculation is complete the H-SPC sends a PEND message to the H-SLC. M. The H-SLC sends a SUPL END message to the SET informing it that no further positioning procedure will be started and that the location session is finished. The SET SHALL release the secure connection to the H-SLC and release all resources related to this session. N. The H-SLC sends the position estimate back to the SUPL Agent in an MLP SLIA message and the H-SLP SHALL release all resources related to this session.
5.1.2
Roaming with V-SLP Positioning Successful Case
SUPL Roaming where the V-SLP is involved in the positioning calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 22 (295)
SUPL Agent
R-SLC
V-SLC
V-SPC
H-SLC
Target SET
A B C D

Routing Info
RLP SRLIR(ms-id, client-id, eqop)
E F LT1 G H
RLP SSRLIR(SUPL START) PREQ(session-id2, QoP) ST3 PRES(session-id2) RLP SSRLIA(SUPL RESPONSE)
I PT1 ST2
SUPL INIT(session-id, posmethod, SLP mode)
J RT1 K L M N O
ST1
RLP SSRP(SUPL POS INIT) PINIT(session-id2, lid, SET capabilities) PT2 PLRES(session-id2, posresult) SUPL POS
PMESS(session-id2, RRLP/RRC/TIA-801/LPP)
SUPL POS INIT(session-id, lid, SET capabilities, ver) UT2
PLREQ(session-id2, lid)
RLP SSRP(SUPL POS) RLP SSRP(SUPL POS) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)
SUPL POS SUPL POS
Q R S T U MLP SLIA(posresult)
PEND(session-id2, position) RLP SSRP(SUPL END) SUPL END(session-id) RLP SRLIA(posresult) UT3
Figure 2: Network Initiated Roaming Successful Case Proxy mode with V-SLP positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP SLIR message to the R-SLC, with which SUPL Agent is associated. The R-SLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. B. The R-SLC determines the H-SLC based on the received msid. NOTE 2: The specifics for determining the H-SLC are considered outside scope of SUPL. However, there are various environment dependent mechanisms.
OMA-TS-ILP-V2_0_1-20121205-A
Page 23 (295)
C. The R-SLC then forwards the location request to the H-SLC of the target subscriber, using RLP protocol. Based on the received ms-id the H-SLC SHALL apply subscriber privacy against the client-id. If a previously computed position which meets the requested QoP is available at the H-SLC and no notification or verification is required, the H-SLC SHALL directly proceed to step U. If notification and verification or notification only is required, the HSLC SHALL proceed to step I after having performed step D. D. The H-SLC verifies that the target SET is currently SUPL Roaming. In addition the H-SLC MAY also verify that the target SET supports SUPL. NOTE 3: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope E. The H-SLC sends an RLP SSRLIR to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. Mandatory parameters in SUPL START that are not known to the H-SLC (lid and SET capabilities) shall be populated with arbitrary values by the H-SLC and be ignored by V-SLC. The SET part of the session-id will not be included in this message by the H-SLC to distinguish this scenario from a SET Initiated scenario. F. The V-SLC requests service from the V-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved.
G. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. H. The V-SLC acknowledges that it is ready to initiate a SUPL positioning procedure with an RLP SSRLIA back to the H-SLC. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step C indicates that notification or verification to the target subscriber is needed, the H-SLC SHALL also include the Notification element in the SUPL INIT message. Before the SUPL INIT message is sent the H-SLC also computes and stores a hash of the message. If in step C the H-SLC decided to use a previously computed position the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message to the H SLC carrying the results of the verification process (access granted, or access denied). If no verification is required (notification only) the SET SHALL respond with a SUPL END message to the H-SLC. The H-SLP SHALL then directly proceed to step U. NOTE 5: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step J and use the procedures described in step K to establish a secure connection to the H-SLC. J. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action. Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection.. I.
K. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using the H-SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLC. The SET SHALL send the SUPL POS INIT message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally
OMA-TS-ILP-V2_0_1-20121205-A
Page 24 (295)
provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. L. The H-SLC SHALL check that the hash of SUPL INIT matches the one it has computed for this particular session. The H-SLC then tunnels the SUPL POS INIT message to the V-SLC using RLP. M. The V-SLC sends a PINIT message to the V-SPC including session-id2, location id and SET capabilities. The VSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the V-SPC in step G, or a different posmethod of the V-SLCs choosing, as long as it is one supported by the V -SPC. Based on the PINIT message including the SET capabilities, the V-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the V-SLC, the V-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the V-SPC shall choose any posmethod in line with the SET capabilities which was approved by the V-SLC in step F. If required for the posmethod the V-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the PINIT message. If an initial position calculated based on information received in the PINIT message is available that meets the required QoP, the V-SPC MAY directly proceed to step Q and not engage in a SUPL POS session. N. If the V-SPC cannot translate the lid received in step M into an initial position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into an initial position itself. O. This step is conditional and only occurs if step N was performed. The V-SLC reports an initial position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the initial position meets the required QoP, the V-SPC MAY directly proceed to step Q and not engage in a SUPL POS session. P. The SET and the V-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SPC and the V-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SLC and the H-SLC using SUPL POS over RLP tunnel messages. The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages. The flow sequence PMESS RLP SSRP(SUPL POS) SUPL POS SUPL POS RLP SSRP(SUPL POS) PMESS is conceptually shown in dotted lines. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). Q. Once the position calculation is complete, the V-SPC sends a PEND message to the V-SLC. R. The V-SLC sends a SUPL END message to the H-SLC over RLP. S. The H-SLC sends the SUPL END message to the SET informing it that no further positioning procedure will be started and that the location session is finished. The SET SHALL release the secure connection to the H-SLC and release all resources related to this session.
T. The H-SLC sends the position estimate back to the R-SLC using an RLP SRLIA message. The H-SLC SHALL release all resources related to this session. U. The R-SLC sends the position estimate back to the SUPL Agent using an MLP SLIA message.
5.1.3
Roaming with H-SLP Positioning Successful Case
SUPL Roaming where the H-SLP is involved in the positioning calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 25 (295)
SUPL Agent
R-SLC
V-SLC
H-SLC
H-SPC
Target SET
A B C D

Routing Info

E F G ST2 LT1
PT1
I J RT1 RLP SRLIR(msid, lid) ST4 K L RLP SRLIA(ms-id, posresult)
SUPL POS INIT(session-id, lid, SET capabilities, ver)
UT2
PINIT(session-id2, lid, SET capabilities) SUPL POS

PMESS(session-id2, RRLP/RRC/TIA-801/LPP) SUPL POS(session-id, RRLP/RRC/TIA-801)
SUPL POS(session-id, RRLP/RRC/TIA-801) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)
N O P Q MLP SLIA(posresult) RLP SRLIA(posresult)
UT3
Figure 3: Network Initiated Roaming Successful case Proxy mode with H-SLP positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP SLIR message to the R-SLC, with which the SUPL Agent is associated. The RSLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. B. The R-SLC determines the H-SLC based on the received msid. NOTE 2: The specifics for determining the H-SLC are considered outside scope of SUPL. However, there are various environment dependent mechanisms. C. The R-SLC then forwards the location request to the H-SLC of the target subscriber, using RLP protocol. Based on the received ms-id the H-SLC SHALL apply subscriber privacy against the client-id. If a previously computed position which meets the requested QoP is available at the H-SLC and no notification or verification is required, the
OMA-TS-ILP-V2_0_1-20121205-A
Page 26 (295)
H-SLC SHALL directly proceed to step Q. If notification and verification or notification only is required, the H-SLP SHALL proceed to step G after having performed step D. D. The H-SLC verifies that the target SET is currently SUPL Roaming. In addition the H-SLC MAY also verify that the target SET supports SUPL. NOTE 3: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms. NOTE 4: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 5: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. E. The H-SLC requests service from the H-SPC for the SUPL session by sending a PREQ message containing the session-id2 and the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. F. The H-SPC confirms its readiness for a SUPL session with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES.
G. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step indicates that notification or verification to the target subscriber is needed, the H-SLC SHALL also include the Notification element in the SUPL INIT message. Before the SUPL INIT message is sent the H-SLC also computes and stores a hash of the message. If in step C the H-SLC decided to use a previously computed position the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message to the H SLC carrying the results of the verification process (access granted, or access denied). If no verification is required (notification only) the SET SHALL respond with a SUPL END message to the H-SLC. The H-SLC SHALL then directly proceed to step Q. NOTE 6: Before sending the SUPL END message the SET shall follow the data connection setup procedure of step H and use the procedures described in step I to establish a secure connection to the H-SLC. H. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. I. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using the H-SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SET SHALL send the SUPL POS INIT message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid) and a hash of the received SUPL INIT message (ver). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. The H-SLC SHALL check that the hash of SUPL INIT matches the one it has computed for this particular session. If an initial position calculated based on information received in the SUPL POS INIT message is available which meets the requested QoP, the H-SLC MAY directly proceed to step O and send a PEND message to the H-SPC. The Otherwise the H-SLC decides that the H-SPC will provide assistance/position calculation and the H-SLC sends an RLP SRLIR request to the V-SLC to determine an initial position for further exchange of SUPL POS messages between SET and H-SPC. The RLP request contains at least the msid and the Location ID (lid). Optionally the HSLC MAY forward NMR provided by the SET to the V-SLC.
J.
OMA-TS-ILP-V2_0_1-20121205-A
Page 27 (295)
K. The V-SLC returns a RLP SRLIA message. The RLP SRLIA message contains at least the position result (e.g., initial position for A-GPS positioning). L. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id, SET capabilities and position estimate (i.e. initial position received from the V-SLC in the previous step). The H-SLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step F, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. If the computed position meets the requested QoP, the H-SPC MAY directly move to step N and not engage in a SUPL POS session. M. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step E. If required for the posmethod, the H-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the PINIT message. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET based). N. Once the position calculation is complete the H-SPC sends a PEND message to the H-SLC. O. The H-SLC sends a SUPL END message to the SET informing it that no further positioning procedure will be started and that the location session is finished. The SET SHALL release the secure connection to the H-SLC and release all resources related to this session. P. The H-SLC forwards the location estimate to the R-SLC if the position estimate is allowed by the privacy settings of the target subscriber. The H-SLC SHALL release all resources related to this session. Q. The R-SLC sends the position estimate back to the SUPL Agent using the MLP SLIA message.
OMA-TS-ILP-V2_0_1-20121205-A
Page 28 (295)
5.1.4
Non-Roaming Successful Case, Notification/Verification based on current location

SUPL Agent H-SLC H-SPC Target SET
A B

C LT1 D E F
PREQ(session-id2, QoP) PRES(session-id2) SUPL INIT(session-id, posmethod, SLP mode, ...)
ST2
PT1 SUPL POS INIT(session-id, lid, SET capabilities, ver) PINIT(session-id2, lid, SET capabilities) PLREQ(session-id2, lid) PLRES(session-id2, posresult) PT2 SUPL POS
PMESS(session-id2, RRLP/RRC/TIA-801/LPP) SUPL POS(session-id, RRLP/RRC/TIA-801)
G H I J
UT2
SUPL POS(session-id, RRLP/RRC/TIA-801) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)
L M N O P MLP SLIA(posresult) ST5
PEND(session-id2, position) SUPL NOTIFY(session-id, notification) SUPL NOTIFY RESPONSE(session-id, notification-response) SUPL END(session-id)
UT3
UT5
Figure 4: Notification/Verification based on current location, Network Initiated Non-Roaming Successful Case Proxy Mode NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP SLIR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the client-id. If a previously computed position which meets the requested QoP is available at the H-SLC and, based on that position, no notification or verification is required, the H-SLC SHALL directly proceed to step P. If, based on that position, notification and verification or notification only is required, the H-SLC SHALL proceed to step B. B. The H-SLC verifies that the target terminal is currently not SUPL Roaming. The H-SLC may also verify that the target terminal supports SUPL. NOTE 2: The specifics for determining if the SET is roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms.
OMA-TS-ILP-V2_0_1-20121205-A
Page 29 (295)
C. The H-SLC requests service from the H-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. D. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. E. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, proxy/non-proxy mode indicator and the intended positioning method. As in this case the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLP SHALL include the Notification Mode element in the SUPL INIT to indicate notification based on current location and SHALL NOT include the notification element in the SUPL INIT message. Before the SUPL INIT message is sent the H-SLC also computes and stores a hash of the message. If in step A the H-SLC decided to use a previously computed position, the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message carrying the results of the verification process (access granted, or access denied). If no explicit verification is required (notification only) the SET SHALL respond with a SUPL END message. The H-SLC SHALL then directly proceed to step P. NOTE 3: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step F. F. The SET analyses the received SUPL INIT. If found to be non authentic, the SET takes no further action. Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection.
G. The SET will evaluate the Notification rules and follow the appropriate actions. The SET checks the notification mode indicator and determines that in this case the notification is performed based on the location of the SET. The SET also checks the proxy/non-proxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using H-SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, IS-801). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if it is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. The H-SLC SHALL check that the hash of SUPL INIT matches the one it has computed for this particular session H. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id and SET capabilities. The HSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step D, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL then determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step C. If required for the posmethod the H-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the PINIT message. If a position received from or calculated based on information received in the PINIT message is available that meets the required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session. I. If the H-SPC cannot translate the lid received in step H into a position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the HSPC can perform the translation from lid into a position itself. This step is conditional and only occurs if step I was performed. The H-SLC reports the position result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the position meets the required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session.
J.
OMA-TS-ILP-V2_0_1-20121205-A
Page 30 (295)
K. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SLP (SET-Based). L. Once the position calculation is complete, the H-SPC sends a PEND message to the H-SLC M. The H-SLP applies subscriber privacy against the SET position estimate determined in Step K. If, based on this position, notification and verification or notification only is required, the H-SLP SHALL send a SUPL NOTIFY message to the SET. The SUPL NOTIFY message contains the notification element. If, based on this position, no notification or verification is required, the H-SLP SHALL directly proceed to Step O.
N. The SET SHALL send a SUPL NOTIFY RESPONSE message to the H-SLC. If notification and verification was required in step M then this will contain the containing the notification response from the user.
O. Once the position calculation is complete the H-SLC sends the SUPL END message to the SET informing it that no further positioning procedure will be started and that the location session is finished. The SET SHALL release the secure connection to the H-SLC and release all resources related to this session.
P. The H-SLC sends the position estimate back to the SUPL Agent in an MLP SLIA message and the H-SLP SHALL release all resources related to this session.
5.1.5
Roaming with V-SLP Positioning Successful Case, Notification/Verification based on current location
SUPL Roaming where the V-SLP is involved in the positioning calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 31 (295)
SUPL Agent
R-SLC
V-SLC
V-SPC
H-SLC
Target SET
A B C D

Routing Info
E F LT1 G H
I PT1 ST2
SUPL INIT(session-id, posmethod, SLP mode, ...)

J RT1 K L M N O
ST1
SUPL POS SUPL POS
Q R S T U V W
PEND(session-id2, position) RLP SSRP(SUPL END) SUPL NOTIFY(session-id, notification) ST5 SUPL NOTIFY RESPONSE(session-id, notification-response) SUPL END(session-id) RLP SRLIA(posresult) MLP SLIA(posresult) UT3
UT5
Figure 5: Notification/Verification based on current location, Network Initiated Roaming Successful Case Proxy mode with V-SLP positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP SLIR message to the R-SLC, with which SUPL Agent is associated. The R-SLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requested, based on the client-id received.
OMA-TS-ILP-V2_0_1-20121205-A
Page 32 (295)
B. The R-SLC determines the H-SLC based on the received msid. If the R-SLC determines that the SUPL Agent is not authorized for this request, Step W will be returned with the applicable MLP return code. NOTE 2: The specifics for determining the H-SLP are considered outside scope of SUPL. However, there are various environment dependent mechanisms. C. The R-SLC then forwards the location request to the H-SLC of the target subscriber, using RLP protocol. If a previously computed position which meets the requested QoP is available at the H-SLC and, based on that position, no notification or verification is required, the H-SLC SHALL directly proceed to step V. If, based on that position, notification and verification or notification only is required, the H-SLC SHALL proceed to step I after having performed the SET Lookup and Routing Info procedures of step D. D. Based on the received ms-id the H-SLC SHALL apply subscriber privacy against the client-id. The H-SLC verifies that the target SET is currently SUPL Roaming. In addition the H-SLC MAY also verify that the target SET supports SUPL. NOTE 3: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. E. The H-SLC sends an RLP SSRLIR to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. Mandatory parameters in SUPL START that are not known to H-SLC (lid and SET capabilities) shall be populated with arbitrary values by H-SLC and be ignored by V-SLC. F. The V-SLC requests service from the V-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved.
G. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. H. The V-SLC acknowledges that it is ready to initiate a SUPL positioning procedure with an RLP SSRLIA back to the H-SLC. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, proxy/non-proxy mode indicator and the intended positioning method. As in this case the result of the privacy check in Step D indicates that subscriber privacy check based on current location is required, the H-SLC SHALL include the Notification Mode element in the SUPL INIT message to indicate notification based on current location and SHALL NOT include the notification element in the SUPL INIT message..This step MAY be performed immediately after step D. Before the SUPL INIT message is sent the H-SLC also computes and stores a hash of the message. If in step C the H-SLC decided to use a previously computed position the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message to the H SLC carrying the results of the verification process (access granted, or access denied). If no verification is required (notification only) the SET SHALL respond with a SUPL END message to the H-SLC. The H-SLC SHALL then directly proceed to step V. NOTE 4: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step J. Step I MAY be performed immediately after step D, however, the H-SLC SHALL not proceed with step L before step H has returned. J. The SET analyses the received SUPL INIT. If found to be non authentic, the SET takes no further action. Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. I.
K. The SET will evaluate the Notification rules and follow the appropriate actions. The SET checks the notification mode indicator and determines that in this case the notification is performed based on the location of the SET. The SET also checks the proxy/non-proxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In
OMA-TS-ILP-V2_0_1-20121205-A
Page 33 (295)
this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using the H- SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY optionally provide its position or network timing information, if these are available and supported by both SET and H-SLP. The SET MAY optionally set the Requested Assistance Data element in the SUPL POS INIT. L. The H-SLC SHALL check that the hash of SUPL INIT matches the one it has computed for this particular session. The H-SLC then tunnels the SUPL POS INIT message over RLP to the V-SLC. M. The V-SLC sends a PINIT message to the V-SPC including session-id2, location id and SET capabilities. The VSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the V-SPC in step G, or a different posmethod of the V-SLCs choosing, as long as it is one supported by the V -SPC. Based on the PINIT message including the SET capabilities, the V-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the V-SLC, the V-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the V-SPC shall choose any posmethod in line with the SET capabilities which was approved by the V-SLC in step F. If required for the posmethod the V-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the PINIT message. If an initial position calculated based on information received in the PINIT message is available that meets the required QoP, the V-SPC MAY directly proceed to step Q and not engage in a SUPL POS session. N. If the V-SPC cannot translate the lid received in step M into an initial position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into an initial position itself. O. This step is conditional and only occurs if step N was performed. The V-SLC reports an initial position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the initial position meets the required QoP, the V-SPC MAY directly proceed to step Q and not engage in a SUPL POS session. P. The SET and the V-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SPC and the V-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SLC and the H-SLC using SUPL POS over RLP tunnel messages. The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages. The flow sequence PMESS RLP SSRP(SUPL POS) SUPL POS SUPL POS RLP SSRP(SUPL POS) PMESS is conceptually shown in dotted lines.. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). Q. Once the position calculation is complete, the V-SPC sends a PEND message to the V-SLC. R. Once the position calculation is complete the V-SLC sends the SUPL END message tunnelled over RLP to the HSLC. The V-SLP SHALL release all resources related to this session. S. The H-SLC applies subscriber privacy against the SET position estimate obtained in Step L. If, based on this position, notification and verification or notification only is required, the H-SLP SHALL send a SUPL NOTIFY message to the SET. The SUPL NOTIFY message contains notification element. If, based on this position, no notification and verification is required, the H-SLP SHALL directly proceed to Step U
T. The SET SHALL send a SUPL NOTIFY RESPONSE message to the H-SLC. If notification and verification was required in step S then this will contain the notification response from the user. U. The H-SLC sends the SUPL END to the SET informing it that no further positioning procedure will be started and that the location session is finished. The SET SHALL release the secure connection to the H-SLC and release all resources related to this session.
OMA-TS-ILP-V2_0_1-20121205-A
Page 34 (295)
V. The H-SLC sends the position estimate back to the R-SLP in an RLP SRLIA message. The H-SLP SHALL release all resources related to this session. W. The R-SLC sends the position estimate back to the SUPL Agent in an MLP SLIA message.
5.1.6
Roaming with H-SLP Positioning Successful Case, Notification/Verification based on current location
SUPL Roaming where the H-SLP is involved in the positioning calculation.
SUPL Agent
R-SLC
V-SLC
H-SLC
H-SPC
Target SET
A B C D

Routing Info

E F G ST2 LT1
PREQ(session-id2, QoP) PRES(session-id2) SUPL INIT(session-id, posmethod, SLP mode, ...)
PT1
I J RT1 RLP SRLIR(msid, lid) ST4 K L RLP SRLIA(ms-id, posresult)
SUPL POS INIT(session-id, lid, SET capabilities, ver)
UT2

PMESS(session-id2, RRLP/RRC/TIA-801) SUPL POS(session-id, RRLP/RRC/TIA-801/LPP)
SUPL POS(session-id, RRLP/RRC/TIA-801/LPP) PMESS(session-id2, RRLP/RRC/TIA-801)
N O P Q R S MLP SLIA(posresult) RLP SRLIA(posresult) ST5
PEND(session-id2, position) SUPL NOTIFY(session-id, notification) SUPL NOTIFY RESPONSE(session-id, notification-response) SUPL END(session-id)
UT3
UT5
Figure 6: Notification/Verification based on current location, Network Initiated Roaming Successful case Proxy mode with H-SLP positioning NOTE 1: See Appendix C for timer descriptions.
OMA-TS-ILP-V2_0_1-20121205-A
Page 35 (295)
A. The SUPL Agent issues an MLP SLIR message to the R-SLC, with which the SUPL Agent is associated. The RSLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requested, based on the client-id received. B. The R-SLC determines the H-SLC based on the received msid. If the R-SLC determines that the SUPL Agent is not authorized for this request, Step S will be returned with the applicable MLP return code. NOTE 2: The specifics for determining the H-SLC are considered outside scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. C. The R-SLC then forwards the location request to the H-SLC of the target subscriber, using RLP protocol. If a previously computed position which meets the requested QoP is available at the H-SLC and, based on that position, no notification or verification is required, the H-SLC SHALL directly proceed to step R. If, based on that position, notification and verification or notification only is required, the H-SLC SHALL proceed to step G after having performed the SET Lookup and Routing Info procedures of step D. D. Based on the received ms-id the H-SLC SHALL apply subscriber privacy against the client-id. The H-SLC verifies that the target SET is currently SUPL Roaming. In addition the H-SLC MAY also verify that the target SET supports SUPL. NOTE 3: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms. E. The H-SLC requests service from the H-SPC for the SUPL session by sending a PREQ message containing the session-id2 and the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. F. The H-SPC confirms its readiness for a SUPL session with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES.
G. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, proxy/non-proxy mode indicator and the intended positioning method. As in this case the result of the privacy check in Step D indicates that subscriber privacy check based on current location is required, the H-SLC SHALL include the Notification Mode element in the SUPL INIT message to indicate notification based on current location and SHALL NOT include the notification element in the SUPL INIT message. Before the SUPL INIT message is sent the H-SLC also computes and stores a hash of the message. If in step C the H-SLC decided to use a previously computed position the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message to the H SLC carrying the results of the verification process (access granted, or access denied). If no verification is required (notification only) the SET SHALL respond with a SUPL END message to the H-SLC. The H-SLC SHALL then directly proceed to step R. NOTE 4: Before sending the SUPL END message the SET shall follow the data connection setup procedure of step H. H. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. I. The SET will evaluate the Notification rules and follow the appropriate actions. The SET checks the notification mode indicator and determines that in this case the notification is performed based on the location of the SET. The SET also checks the proxy/non-proxy mode indicator to determine if the H-SLC uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using the H-SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SUPL POS INIT MAY contain a hash of the received SUPL INIT message (ver). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-
OMA-TS-ILP-V2_0_1-20121205-A
Page 36 (295)
Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if these are available and supported by both SET and H-SLP. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. J. The H-SLC SHALL check that the hash of SUPL INIT matches the one it has computed for this particular session. If an initial position calculated based on information received in the SUPL POS INIT message is available which meets the requested QoP, the H-SLC MAY directly proceed to step O and send a PEND message to the H-SPC. Otherwise the H-SLC decides that the H-SPC will provide assistance/position calculation and the H-SLC sends a RLP SRLIR request to the V-SLC to determine an initial position. The RLP request contains at least the msid and the Location ID (lid). Optionally the H-SLC MAY forward NMR provided by the SET to the V-SLC.
K. The V-SLC returns a RLP SRLIA message. The RLP SRLIA message contains the position result. If the computed position meets the requested QoP, the H-SLC MAY proceed directly to step O and send a PEND message to the HSPC. L. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id, SET capabilities and position estimate (i.e. initial position received from the V-SLC in the previous step). The H-SLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step F, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. If the computed position meets the requested QoP, the H-SPC MAY directly move to step N and not engage in a SUPL POS session. M. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step E. If required for the posmethod, the H-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the PINIT message. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET based). N. Once the position calculation is complete the H-SPC sends a PEND message to the H-SLC. O. The H-SLC applies subscriber privacy against the SET position estimate determined in Step M. If, based on this position, notification and verification or notification only is required, the H-SLC SHALL send a SUPL NOTIFY message to the SET. The SUPL NOTIFY message contains notification element. If, based on this position, no notification and verification is required, the H-SLC SHALL directly proceed to Step Q. P. The SET SHALL send a SUPL NOTIFY RESPONSE message to the H-SLC. If notification and verification was required in step O then this will contain the notification response from the user. Q. Once the position calculation is complete the H-SLC sends the SUPL END message to the SET informing it that no further positioning procedure will be started and that the location session is finished. The SET SHALL release the secure connection to the H-SLC and release all resources related to this session. R. The H-SLC forwards the location estimate to R-SLC if the position estimate is allowed by the privacy settings of the target subscriber. The H-SLP SHALL release all resources related to this session. S. The R-SLC sends the position estimate back to the SUPL Agent in an MLP SLIA message.
5.2
Network Initiated Non-Proxy Mode
This section describes Network Initiated Non-Proxy mode scenarios.

OMA-TS-ILP-V2_0_1-20121205-A
Page 37 (295)
5.2.1

A B

C LT1 D E F ST2 G H
PT1 SUPL AUTH REQ(session-id, ver) PAUTH(session-id2, SPC_SET_Key, SPC-TID) UT4
I J K L M
SUPL AUTH RESP(session-id, SPC_SET_Key, SPC-TID) SUPL POS INIT(session-id, lid, SET capabilities) PLREQ(session-id2, lid) PLRES(session-id2, posresult) PT2 SUPL POS(session id, RRLP/RRC/TIA-801/LPP)
SUPL POS SUPL POS
UT2
N O P MLP SLIA(posresult) PEND(session-id2, posresult)
SUPL END(session-id)
UT3
Figure 7: Network Initiated Non-Roaming Successful Case Non-Proxy mode NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP SLIR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the client-id. If a previously computed position which meets the requested QoP is available at the H-SLC and no notification or verification is required, the H-SLC SHALL directly proceed to step P. If notification and verification or notification only is required, the H-SLC SHALL proceed to step E after having performed the SET Lookup and Routing Info procedures of step B. B. The H-SLC verifies that the target SET is currently not SUPL Roaming. The H-SLC MAY also verify that the target SET supports SUPL.
OMA-TS-ILP-V2_0_1-20121205-A
Page 38 (295)
NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLC requests service from the H-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. D. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. E. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, address of the H-SPC, proxy/non-proxy mode indicator and the intended positioning method. The protection level indicates the level of protection for the SUPL INIT message. If the result of the privacy check in Step A indicates that notification or verification to the target subscriber is needed, the H-SLC shall also include Notification element in the SUPL INIT message. If in step A the H-SLC decided to use a previously computed position, the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message carrying the results of the verification process (access granted, or access denied). If no explicit verification is required (notification only) the SET SHALL respond with a SUPL END message. The H-SLC SHALL then directly proceed to step P. Note: before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step F to establish a secure connection to the H-SLC. F. The SET analyses the received SUPL INIT. If found to be non authentic SET takes no further actions. Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection.
G. The SET uses the address provisioned by the Home Network to establish a secure connection to the H-SLC. The SET then checks the proxy/non-proxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case non-proxy mode is used and the SET SHALL send a SUPL AUTH REQ message to the H-SLC. The SUPL AUTH REQ message SHALL contain session-id and a hash of the received SUPL INIT message (ver). H. The H-SLC creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication. The H-SLC forwards SPC_SET_Key and SPC-TID to the H-SPC using a PAUTH message which also includes the session id. I. J. The H-SLC returns a SUPL AUTH RESP message to the SET. The SUPL AUTH RESP message SHALL contain the session-id, SPC_SET_Key and SPC-TID. The SET will evaluate the Notification rules and follow the appropriate actions. The SET establishes a secure connection to the H-SPC according to the address received in step E. The SET and H-SPC perform mutual authentication and the SET sends a SUPL POS INIT message to start a positioning session with the H-SPC. The SET SHALL send the SUPL POS INIT message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SETAssisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. The SET SHALL also release the connection to the H-SLC . If an initial position calculated based on information received in the SUPL POS INIT message is available which meets the requested QoP, the H-SPC MAY directly proceed to step N and no SUPL POS positioning session takes place.
K. If the H-SPC cannot translate the lid received in step J into an initial position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the location ID.
OMA-TS-ILP-V2_0_1-20121205-A
Page 39 (295)
This step is optional and not required if the H-SPC can perform the translation from lid into an initial position itself. L. This step is conditional and only occurs if step K was performed. The H-SLC reports the initial position result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the initial position meets the required QoP, the H-SPC MAY directly proceed to step N and not engage in a SUPL POS session. M. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step C, the H-SPC SHALL only choose an approved method. If required for the posmethod the H-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL POS INIT message. The SET and the H-SPC exchange several successive positioning procedure messages (a SUPL POS message exchange is shown conceptually in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SETAssisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). N. Once the position calculation is complete, the H-SPC sends the SUPL END message to the SET informing it that no further positioning procedure will be started and that the SUPL session is finished. The SET SHALL release the secure connection to the H-SPC and release all resources related to this session. O. The H-SPC sends the position estimate to the H-SLC using a PEND message. This also indicates the end of the SUPL session. The H-SPC SHALL release all resources related to this session. P. The H-SLC sends the position estimate back to the SUPL Agent in an MLP SLIA message. The HSLC SHALL release all resources related to this session.
5.2.2
Roaming with V-SPC Positioning Successful Case
SET Roaming where the V-SPC is involved in the positioning calculation
OMA-TS-ILP-V2_0_1-20121205-A
Page 40 (295)
SUPL Agent
R-SLC
H-SLC
V-SLC
V-SPC
Target SET
A B C D E F G H I

Routing Info

RLP SSRLIR(SUPL START) PREQ(session-id2, QoP) LT1 ST3 RLP SSRLIA(SUPL RESPONSE) SUPL INIT(session-id, posmethod, SLP mode) PRES(session-id2)
J ST2 K L M N O P Q RT1 ST2
PT1 SUPL AUTH REQ(session-id, ver)
RLP SSRP(SUPL AUTH RESP) PAUTH(session-id2, SPC_SET_Key, SPC-TID) SUPL AUTH RESP(session-id, SPC_SET_Key, SPC-TID) UT4
SUPL POS INIT(session-id, lid, SET capabilities) PT2 PLRES(session-id2, posresult) PLREQ(session-id2, lid)
UT2
SUPL POS(session id, RRLP/RRC/TIA-801/LPP)

SUPL POS
SUPL POS
S T U V W MLP SLIA(posresult) RLP SSRP(SUPL END) RLP SRLIA(posresult) PEND(session-id2, posresult)
UT3
Figure 8: Network Initiated Roaming Successful Case Non-Proxy-mode with V-SPC positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP SLIR message to the R-SLC, with which SUPL Agent is associated. The R-SLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. B. The R-SLC determines the H-SLC based on the received msid. If the R-SLC determines that the SUPL Agent is not authorized for this request, Step W will be returned with the applicable MLP return code. NOTE 2: The specifics for determining the H-SLC are considered outside scope of SUPL. However, there are various environment dependent mechanisms.
OMA-TS-ILP-V2_0_1-20121205-A
Page 41 (295)
C. The R-SLC then forwards the location request to the H-SLC of the target subscriber, using RLP protocol. Based on the received ms-id the H-SLC SHALL apply subscriber privacy against the client-id. If a previously computed position which meets the requested QoP is available at the H-SLC and no notification or verification is required, the H-SLC SHALL directly proceed to step V. If notification and verification or notification only is required, the HSLC SHALL proceed to step I after having performed step D. D. The H-SLC verifies that the target SET is currently SUPL Roaming. In addition the H-SLC MAY also verify that the target SET supports SUPL. NOTE 3: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. E. The H-SLC allocates a session-id for the SUPL session and decides that the V-SPC will provide assistance data or perform the position calculation. The H-SLC sends an RLP SSRLIR to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. Mandatory parameters in SUPL START that are not known to the H-SLC (lid and SET capabilities) shall be populated with arbitrary values by the H-SLC and be ignored by the V-SLC. The SET part of the session-id will not be included in this message by the H-SLC to distinguish this scenario from a SET Initiated scenario. F. The V-SLC requests service from the V-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved.
G. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. H. The V-SLC acknowledges that V-SPC is ready to initiate a SUPL positioning procedure with an RLP SSRLIA back to the H-SLC. The message includes at least session-id, posmethod and the address of the V-SPC. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, address of the V-SPC, proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step C indicates that notification or verification to the target subscriber is needed, the H-SLC SHALL also include the Notification element in the SUPL INIT message. If in step C the H-SLP decided to use a previously computed position, the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message to the H SLC carrying the results of the verification process (access granted, or access denied). If no verification is required (notification only) the SET SHALL respond with a SUPL END message to the H-SLC. The H-SLC SHALL then directly proceed to step V. NOTE 5: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step J to establish a secure connection to the H-SLC. J. The SET analyses the received SUPL INIT. If found to be non authentic SET takes no further action. Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. I.
K. The SET uses the address provisioned by the Home Network to establish a connection to the H-SLC. The SET then checks the proxy/non-proxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case non-proxy mode is used and the SET SHALL send a SUPL AUTH REQ message to the H-SLC. The SUPL AUTH REQ message SHALL contain session-id and a hash of the received SUPL INIT message (ver). L. The H-SLP creates SPC_SET_Key and SPC-TID to be used for mutual V-SPC/SET authentication. The H-SLC forwards SPC_SET_KEY and SPC_TID to the V-SLC through an RLP SSRP message. M. The V-SLC forwards SPC_SET_Key and SPC-TID to the V-SPC using the PAUTH message.
OMA-TS-ILP-V2_0_1-20121205-A
Page 42 (295)
N. The H-SLC returns a SUPL AUTH RESP to the SET. The SUPL AUTH RESP message SHALL contain the session-id, SPC_SET_Key and SPC-TID. O. The SET will evaluate the Notification rules and follow the appropriate actions. The SET establishes a secure connection to the V-SPC according to the address received in step I. The SET and V-SPC perform mutual authentication and the SET sends a SUPL POS INIT message to start a SUPL positioning session with the V-SPC. The SET SHALL send the SUPL POS INIT message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. The SET SHALL also release the connection to the H-SLC. If an initial position calculated based on information received in the SUPL POS INIT message is available which meets the requested QoP, the V-SPC MAY directly proceed to step S and no SUPL POS positioning session takes place.. P. If the V-SPC cannot translate the lid received in step O into an initial position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into an initial position itself. Q. This step is conditional and only occurs if step P was performed. The V-SLC reports the initial position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the initial position meets the required QoP, the V-SPC MAY directly proceed to step S and not engage in a SUPL POS session. R. Based on the SUPL POS INIT message including posmethod(s) supported by the SET, the V-SPC SHALL determine the posmethod. If the V-SLC included its approved positioning methods in step F, the V-SPC SHALL only choose an approved method. If required for the posmethod, the V-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL POS INIT message. The SET and the V-SPC exchange several successive positioning procedure messages (a SUPL POS message exchange is shown conceptually in dotted lines). The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). S. Once the position calculation is complete the V-SPC sends a SUPL END message to the SET informing it that no further positioning procedure will be started and that the positioning session is finished. The SET SHALL release all resources related to this session.
T. The V-SPC informs the V-SLC using a PEND message that the positioning procedure is completed and returns the position result. The V-SPC SHALL release all resources related to this session. U. The V-SLC sends a RLP SSRP to the H-SLC carrying the position result. The V-SLC SHALL release all resources related to this session. V. The H-SLC sends the position estimate back to the R-SLC using the RLP SRLIA message. The H-SLC SHALL release all resources related to this session. W. The R-SLC sends the position estimate back to the SUPL Agent using the MLP SLIA message.
5.2.3
Roaming with H-SPC Positioning Successful Case
SUPL Roaming where the H-SPC is involved in the positioning calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 43 (295)
SUPL Agent
R-SLC
V-SLC
H-SLC
H-SPC
Target SET
A B C D

Routing Info

E F G LT1
H ST2 I
PT1 SUPL AUTH REQ(session-id, ver) PAUTH(session-id2, SPC_SET_Key, SPC-TID)
J K
SUPL AUTH RESP(session-id, SPC_SET_Key, SPC-TID)
UT4
L M N
SUPL POS INIT(session-id, lid, SET capabilities) PLREQ(session-id2, ms-id, lid) RT1 RLP SRLIR(msid, lid) ST4 UT2
O P
RLP SRLIA(ms-id, posresult) PLRES(session-id2, posresult) SUPL POS(session id, RRLP/RRC/TIA-801/LPP)

SUPL POS
SUPL POS
R S T U MLP SLIA(posresult) RLP SRLIA(posresult) PEND(session-id2, posresult)
UT3
Figure 9: Network Initiated Roaming Successful Case Non-Proxy-mode with H-SPC NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP SLIR message to the R-SLC, with which the SUPL Agent is associated. The RSLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. B. The R-SLC determines the H-SLC based on the received msid. If the R-SLC determines that the SUPL Agent is not authorized for this request, Step U will be returned with the applicable MLP return code.
OMA-TS-ILP-V2_0_1-20121205-A
Page 44 (295)
NOTE 2: The specifics for determining the H-SLC are considered outside scope of SUPL. However, there are various environment dependent mechanisms. C. The R-SLC then forwards the location request to the H-SLC of the target subscriber, using RLP protocol. Based on the received ms-id the H-SLC SHALL apply subscriber privacy against the client-id. If a previously computed position which meets the requested QoP is available at the H-SLC and no notification or verification is required, the H-SLC SHALL directly proceed to step T. If notification and verification or notification only is required, the H-SLC SHALL proceed to step G after having performed step D. D. The H-SLC verifies that the target SET is currently SUPL Roaming. In addition the H-SLC MAY also verify that the target SET supports SUPL. NOTE 3: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms. NOTE 4: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 5: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. E. The H-SLC requests service from the H-SPC for the SUPL session by sending a PREQ message containing the session-id2 and the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. F. The H-SPC confirms its readiness for a SUPL session with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES.
G. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, address of the H-SPC, proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step C indicates that notification or verification to the target subscriber is needed, the H-SLC SHALL also include the Notification element in the SUPL INIT message. If in step C the H-SLC decided to use a previously computed position the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message to the H SLC carrying the results of the verification process (access granted, or access denied). If no verification is required (notification only) the SET SHALL respond with a SUPL END message to the H-SLC. The H-SLC SHALL then directly proceed to step T. NOTE 6: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step H to establish a secure connection to the H-SLC. H. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action. Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. I. The SET uses the address provisioned by the Home Network to establish a secure connection to the H-SLC. The SET then checks the proxy/non-proxy mode indicator to determine if the H-SLC uses proxy or non-proxy mode. In this case non-proxy mode is used and the SET SHALL send a SUPL AUTH REQ message to the H-SLC. The SUPL AUTH REQ message SHALL contain session-id and a hash of the received SUPL INIT message (ver). The H-SLC creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication. The H-SLC forwards SPC_SET_Key and SPC-TID to the H-SPC using a PAUTH message.
J.
K. The H-SLC sends a SUPL AUTH RESP message to the SET. The SUPL AUTH RESP message SHALL contain the session-id, SPC_SET_Key and SPC-TID. L. The SET will evaluate the Notification rules and follow the appropriate actions. The SET establishes a secure connection to the H-SPC according to the address received in step G. The SET and H-SPC perform mutual authentication and the SET then sends a SUPL POS INIT message to start a positioning session with the H-SPC. The SET SHALL send the SUPL POS INIT message even if the SET supported positioning technologies do not
OMA-TS-ILP-V2_0_1-20121205-A
Page 45 (295)
include the intended positioning method indicated in the SUPL INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific data for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If an initial position calculated based on information received in the SUPL POS INIT message is available which meets the requested QoP, the H-SPC MAY directly proceed to step R. The SET SHALL also release the connection to the H-SLC. M. The H-SPC sends a PLREQ message to the H-SLC informing it that that the target SET has established the session and including the lid and optionally the NMR specific data for the radio technology being used (e.g., for GSM: TA, RXLEV). N. The H-SLC sends an RLP SRLIR request to the V-SLC to determine an initial position for further exchange of SUPL POS messages between SET and H-SPC. The RLP request contains at least the msid and the Location ID (lid). Optionally the H-SLC MAY forward NMR provided by the SET to the V-SLC. O. The V-SLC returns a RLP SRLIA message to the H-SLC. The RLP SRLIA message contains at least the position result. P. The H-SLC informs the H-SPC of the initial position in a PLRES message. If the computed position meets the requested QoP, the H-SPC MAY directly move to step R and not engage in a SUPL POS session. Q. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step E, the H-SPC SHALL only choose an approved method. If required for the posmethod the H-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL POS INIT message. The SET and the H-SPC exchange several successive positioning procedure messages (a SUPL POS message exchange is shown conceptually in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). R. Once the position calculation is complete the H-SPC sends SUPL END message to the SET informing it that no further positioning procedure will be started and that the positioning session is finished. The SET SHALL release all resources related to this session. S. The H-SPC informs the H-SLC in a PEND message that the positioning procedure is completed and includes the position estimate result. The H-SPC SHALL release all resources related to this session.
T. The H-SLC sends the position estimate back to the R-SLC using the RLP SRLIA message. The H-SLC SHALL release all resources related to this session. U. The R-SLC sends the position estimate back to the SUPL Agent using the MLP SLIA message.
OMA-TS-ILP-V2_0_1-20121205-A
Page 46 (295)
5.2.4
Non-Roaming Successful Case, Notification/Verification based on current location

SUPL Agent
A B

C LT1 D E F ST2 G H
PREQ(session-id2, QoP) PRES(session-id2) SUPL INIT(session-id, posmethod, SLP mode, H-SPC address, notification mode, ...)
UT4
I J K L M
SUPL POS SUPL POS
UT2
N O P Q R S T MLP SLIA(posresult) ST5 PEND(session-id2, posresult)
SUPL REPORT(session-id, position)
UT3
SUPL REPORT(session-id, position) SUPL NOTIFY(session-id, notification) SUPL NOTIFY RESPONSE(session-id, notification-response) SUPL END(session-id) UT5 UT6
Figure 10: Notification/Verification based on current location, Network Initiated Non-Roaming Successful Case Non-Proxy mode NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP SLIR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on
OMA-TS-ILP-V2_0_1-20121205-A
Page 47 (295)
the client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the client-id. If a previously computed position which meets the requested QoP is available at the H-SLC and, based on that position, no notification or verification is required, the H-SLC SHALL directly proceed to step T. If, based on that position, notification and verification or notification only is required, the H-SLC SHALL proceed to step B. B. The H-SLC verifies that the target SET is currently not SUPL Roaming. The H-SLC MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms. C. The H-SLC requests service from the H-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. If notification or verification based on current location is required, the H-SLC SHALL include the notification mode parameter. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. D. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. E. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, address of the H-SPC, proxy/non-proxy mode indicator and the intended positioning method. As in this case the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLC SHALL include the Notification Mode element in the SUPL INIT message to indicate notification based on current location and SHALL NOT include the notification element in the SUPL INIT message. If in step A, the H-SLC decided to use a previously computer position, the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message carrying the results of the verification process (access granted or access denied). If no explicit verification is required (notification only) the SET SHALL respond with a SUPL END message. The H-SLC SHALL then directly proceed to step T. NOTE 3: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step F. F. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action. Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection.
G. The SET uses the address provisioned by the Home Network to establish a secure connection to the H-SLC. The SET then checks the proxy/non-proxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case non-proxy mode is used and the SET SHALL send a SUPL AUTH REQ message to the H-SLC. The SUPL AUTH REQ message SHALL contain session-id and a hash of the received SUPL INIT message (ver). H. The H-SLC creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication. The H-SLC forwards SPC_SET_Key and SPC-TID to the H-SPC using a PAUTH message which also includes the session id. I. J. The H-SLC returns a SUPL AUTH RESP message to the SET. The SUPL AUTH RESP message SHALL contain the session-id, SPC_SET_Key and SPC-TID. The SET will evaluate the Notification rules and follow the appropriate actions. The SET checks the notification mode indicator and determines that in this case the notification is performed based on the location of the SET. The SET establishes a secure connection to the H-SPC according to the address received in step E. The SET and H-SPC perform mutual authentication and the SET sends a SUPL POS INIT message to start a positioning session with the H-SPC. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if these are available and supported by both SET and H-SPC. The SET MAY set the Requested Assistance Data element in the
OMA-TS-ILP-V2_0_1-20121205-A
Page 48 (295)
SUPL POS INIT. The SET SHALL also release the IP connection to the H-SLC and release all resources related to this session. If an initial position calculated based on information received in the SUPL POS INIT message is available which meets the requested QoP, the H-SPC MAY directly proceed to step N and no SUPL POS positioning session takes place. K. If the H-SPC cannot translate the lid received in step J into an initial position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the H-SPC can perform the translation from lid into an initial position itself. L. This step is conditional and only occurs if step K was performed. The H-SLC reports the initial position result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the initial position meets the required QoP, the H-SPC MAY directly proceed to step N and not engage in a SUPL POS session. M. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step C, the H-SPC SHALL only choose an approved method. If required for the posmethod the H-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL POS INIT message The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). N. As in this case in step C the H-SLC indicated that notification or verification is required based on the position of the SET, the H-SPC sends the calculated position to the SET in a SUPL REPORT message. O. The H-SPC sends a PEND message to the H-SLC indicating the end of the SUPL session. The H-SPC SHALL release all resources related to this session P. As in this case in step E the H-SLC indicated that notification or verification is based on the position of the SET, the SET sends the calculated position to the H-SLC in a SUPL REPORT message. Q. The H-SLC applies subscriber privacy against the SET position estimate. If, based on this position, notification and verification or notification only is required, the H-SLP SHALL send a SUPL NOTIFY message to the SET. The SUPL NOTIFY message contains the notification element. If, based on this position, no notification and verification is required, the H-SLP SHALL directly proceed to Step S. R. The SET SHALL then send an SUPL NOTIFY RESPONSE message to the H-SLC. If notification and verification was required in Step Q then this will contain the notification response from the user. S. Once the position calculation is complete the H-SLC sends the SUPL END message to the SET informing it that no further positioning procedure will be started and that the SUPL session is finished. The SET SHALL release the secure connection to the H-SLC and release all resources related to this session.
T. The H-SLC sends the position estimate back to the SUPL Agent in an MLP SLIA message and H-SLC can release all resources related to this session. The H-SLC SHALL release all resources related to this session.
5.2.5
Roaming with V-SPC Positioning Successful Case, Notification/Verification based on current location
SET Roaming where the V-SPC is involved in the positioning calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 49 (295)
SUPL Agent
R-SLC
H-SLC
V-SLC
V-SPC
Target SET
A B C D E F G H I

Routing Info

RLP SSRLIR(SUPL START) PREQ(session-id2, notification mode, QoP) LT1 ST3 RLP SSRLIA(SUPL RESPONSE) SUPL INIT(session-id, V-SPC address, posmethod, SLP mode, ...) PRES(session-id2)
PT1 SUPL AUTH REQ(session-id, ver) ST2 RT1 RLP SSRP(SUPL AUTH RESP) PAUTH(session-id2, SPC_SET_Key, SPC-TID) SUPL AUTH RESP(session-id, SPC_SET_Key, SPC-TID)
K L M N O P Q
UT4
UT2

SUPL POS
SUPL POS
S T U V W X Y Z MLP SLIA(posresult) RLP SRLIA(posresult) ST5
SUPL REPORT(session-id, position) PEND(session-id2, posresult) SUPL REPORT(session-id, position) SUPL NOTIFY(session-id, notification) SUPL NOTIFY RESPONSE(session-id, notification-response) SUPL END(session-id)
UT3
UT6
UT5
Figure 11: Notification/Verification based on current location, Network Initiated Roaming Successful Case NonProxy-mode with V-SPC positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP SLIR message to the R-SLC, with which SUPL Agent is associated. The R-SLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received.
OMA-TS-ILP-V2_0_1-20121205-A
Page 50 (295)
B. The R-SLC determines the H-SLC based on the received msid. If the R-SLC determines that the SUPL Agent is not authorized for this request, Step Z will be returned with the applicable MLP return code. NOTE 2: The specifics for determining the H-SLC are considered outside scope of SUPL. However, there are various environment dependent mechanisms. C. The R-SLC then forwards the location request to the H-SLC of the target subscriber, using RLP protocol. If a previously computed position which meets the requested QoP is available at the H-SLC and, based on that position, no notification or verification is required, the H-SLC SHALL directly proceed to step Y. If, based on that position, notification and verification or notification only is required, the H-SLP SHALL proceed to step I after having performed the SET Lookup and Routing Info procedures of step D. Based on the received ms-id the H-SLC SHALL apply subscriber privacy against the client-id. D. The H-SLC verifies that the target SET is currently SUPL Roaming. In addition the H-SLP MAY also verify that the target SET supports SUPL. NOTE 3: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms. E. The H-SLC allocates a session-id for the SUPL session and decides that the V-SLP will provide assistance data or perform the position calculation. The H-SLC sends an RLP SSRLIR to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. Mandatory parameters in SUPL START that are not known to H-SLP (lid and SET capabilities) shall be populated with arbitrary values by H-SLC and be ignored by V-SLC. If the result of the privacy check in Step C indicates that notification and verification is required based on the actual location of the target SET user, the H-SLC will inform the V-SLC accordingly. F. The V-SLC requests service from the V-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. As in this case, notification or verification based on current location is required, the H-SLC SHALL include the notification mode parameter. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved.
G. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. H. The V-SLC acknowledges that V-SPC is ready to engage in a SUPL positioning procedure with an RLP SSRLIA back to the H-SLC. The message includes the address of the V-SPC. I. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, address of the V-SPC, proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step D indicates that subscriber privacy check based on current location is required, the H-SLP SHALL include the Notification Mode element in the SUPL INIT message to indicate notification based on current location and SHALL NOT include the notification element in the SUPL INIT message.
If in step C the H-SLP decided to use a previously computed position the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message to the H SLP carrying the results of the verification process (access granted, or access denied). If no verification is required (notification only) the SET SHALL respond with a SUPL END message to the H-SLC. The H-SLC SHALL then directly proceed to step Y. NOTE 4: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step J. J. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action. Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection.
K. The SET uses the address provisioned by the Home Network to establish a connection to the H-SLC. The SET then checks the proxy/non-proxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case
OMA-TS-ILP-V2_0_1-20121205-A
Page 51 (295)
non-proxy mode is used and the SET SHALL send a SUPL AUTH REQ message to the H-SLC. The SUPL AUTH REQ message SHALL contain session-id and a hash of the received SUPL INIT message (ver). L. The H-SLC creates SPC_SET_Key and SPC-TID to be used for mutual V-SPC/SET authentication. The H-SLC forwards SPC_SET_Key and SPC-TID to the V-SLC through an RLP SSRP message. M. The V-SLC forwards SPC_SET_Key and SPC-TID to the V-SPC using the PAUTH message. N. The H-SLC returns a SUPL AUTH RESP to the SET. The SUPL AUTH RESP message SHALL contain the session-id, SPC_SET_Key and SPC-TID. O. The SET will evaluate the Notification rules and follow the appropriate actions. The SET checks the notification mode indicator and determines that in this case the notification is performed based on the location of the SET. The SET establishes a secure connection to the V-SPC according to the address received in step I. The SET and V-SPC perform mutual authentication and the SET sends a SUPL POS INIT message to start a SUPL positioning session with the V-SPC. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if these are available and supported by both SET and V-SPC. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. The SET SHALL also release the connection to the H-SLC. If an initial position calculated based on information received in the SUPL POS INIT message is available which meets the requested QoP, the V-SPC MAY directly proceed to step S and no SUPL POS positioning session takes place. P. If the V-SPC cannot translate the lid received in step O into an initial position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into an initial position itself. Q. This step is conditional and only occurs if step P was performed. The V-SLC reports the initial position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the initial position meets the required QoP, the V-SPC MAY directly proceed to step S and not engage in a SUPL POS session. R. Based on the SUPL POS INIT message including posmethod(s) supported by the SET, the V-SPC SHALL determine the posmethod. If the V-SLC included its approved positioning methods in step F, the V-SPC SHALL only choose an approved method. If required for the posmethod, the V-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL POS INIT message. The SET and the V-SPC exchange several successive positioning procedure messages. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). S. As in this case in step F the V-SLC indicated that notification or verification is required based on the position of the SET, the V-SPC sends the calculated position to the SET in a SUPL REPORT message.
T. The V-SPC informs the V-SLC using a PEND message that the positioning procedure is completed and returns the position result. The V-SPC SHALL release all resources related to this session. U. As in this case in step I the H-SLC indicated that notification or verification is based on the position of the SET, the SET sends the calculated position to the H-SLC in a SUPL REPORT message. V. The H-SLC applies subscriber privacy against the SET position estimate. If, based on this position, notification and verification or notification only is required, the H-SLP SHALL send a SUPL NOTIFY message to the SET. The SUPL NOTIFY message contains notification element. If, based on this position, no notification and verification is required, the H-SLC SHALL directly proceed to Step X. W. The SET SHALL then send an SUPL NOTIFY RESPONSE message to the H-SLP. If notification and verification was required in Step V then this will contain the notification response from the user. X. Once the position calculation is complete the H-SLC sends a SUPL END message to the SET informing it that no further positioning procedure will be started and that the positioning session is finished. The SET SHALL release all resources related to this session.
OMA-TS-ILP-V2_0_1-20121205-A
Page 52 (295)
Y. The H-SLC sends the position estimate back to the R-SLC in an RLP SRLIA message. The H-SLP SHALL release all resources related to this session. Z. The R-SLC sends the position estimate back to the SUPL Agent in an MLP SLIA message.
5.2.6
Roaming with H-SPC Positioning Successful Case, Notification/Verification based on current location
SUPL Roaming where the H-SPC is involved in the positioning calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 53 (295)
SUPL Agent
R-SLC
V-SLC
H-SLC
H-SPC
Target SET
A B C D

Routing Info

E F G LT1
PREQ(session-id2, notification mode, QoP) PRES(session-id2) SUPL INIT(session-id, posmethod, SLP mode, H-SPC address ...)
H ST2 I
J K
SUPL AUTH RESP(session-id, SPC_SET_Key, SPC-TID)
UT4
L M N
SUPL POS INIT(session-id, lid, SET capabilities) PLREQ(session-id2, ms-id, lid) RT1 RLP SRLIR(msid, lid) ST4 UT2
O P
RLP SRLIA(ms-id, posresult) PLRES(session-id2, posresult) SUPL POS(session id, RRLP/RRC/TIA-801/LPP)

SUPL POS
SUPL POS
R S T U V W X Y RLP SRLIA(posresult) MLP SLIA(posresult) ST5
SUPL REPORT(session-id, position) PEND(session-id2, posresult) SUPL REPORT(session-id, position) SUPL NOTIFY(session-id, notification) SUPL NOTIFY RESPONSE(session-id, notification-response) SUPL END(session-id)
UT3
UT6
UT5
Figure 12: Notification/Verification based on current location, Network Initiated Roaming Successful Case NonProxy-mode with H-SPC positioning NOTE 1: See Appendix C for timer descriptions.
OMA-TS-ILP-V2_0_1-20121205-A
Page 54 (295)
A. The SUPL Agent issues an MLP SLIR message to the R-SLC, with which SUPL Agent is associated. The R-SLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. B. The R-SLC determines the H-SLC based on the received msid. If the R-SLC determines that the SUPL Agent is not authorized for this request, Step Y will be returned with the applicable MLP return code. NOTE 2: The specifics for determining the H-SLC are considered outside scope of SUPL. However, there are various environment dependent mechanisms. C. The R-SLC then forwards the location request to the H-SLC of the target subscriber, using RLP protocol. If a previously computed position which meets the requested QoP is available at the H-SLC and, based on that position, no notification or verification is required, the H-SLC SHALL directly proceed to step X. If, based on that position, notification and verification or notification only is required, the H-SLC SHALL proceed to step G after having performed the SET Lookup and Routing Info procedures of step D. D. Based on the received ms-id the H-SLC SHALL apply subscriber privacy against the client-id. The H-SLC verifies that the target SET is currently SUPL Roaming. In addition the H-SLC MAY also verify that the target SET supports SUPL. NOTE 3: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms. NOTE 4: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. E. The H-SLC requests service from the H-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. If notification or verification based on current location is required, the H-SLC SHALL include the notification mode parameter. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. F. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES.
G. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, address of the H-SPC, proxy/non-proxy mode indicator and the intended positioning method. As in this case the result of the privacy check in Step D indicates that subscriber privacy check based on current location is required, the H-SLC SHALL include the Notification Mode element in the SUPL INIT message to indicate notification based on current location and SHALL NOT include the notification element in the SUPL INIT message . If in step C the H-SLC decided to use a previously computed position the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message to the H SLC carrying the results of the verification process (access granted, or access denied). If no verification is required (notification only) the SET SHALL respond with a SUPL END message to the H-SLC. The H-SLC SHALL then directly proceed to step X. NOTE 5: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step H. H. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action. Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. I. The SET uses the address provisioned by the Home Network to establish a secure connection to the H-SLC. The SET then checks the proxy/non-proxy mode indicator to determine if the H-SLC uses proxy or non-proxy mode. In this case non-proxy mode is used and the SET SHALL send a SUPL AUTH REQ message to the H-SLC. The SUPL AUTH REQ message SHALL contain session-id and a hash of the received SUPL INIT message (ver).
OMA-TS-ILP-V2_0_1-20121205-A
Page 55 (295)
J.
The H-SLC creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication. The H-SLC forwards SPC_SET_Key and SPC-TID to the H-SPC using a PAUTH message.
K. The H-SLC returns a SUPL AUTH RESP message to the SET. The SUPL AUTH RESP message SHALL contain the session-id, SPC_SET_Key and SPC-TID. L. The SET will evaluate the Notification rules and follow the appropriate actions. The SET checks the notification mode indicator and determines that in this case the notification is performed based on the location of the SET. The SET establishes a secure connection to the H-SPC according to the address received in step G. The SET and H-SPC perform mutual authentication and the SET then sends a SUPL POS INIT message to start a positioning session with the H-SPC. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific data for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if these are available and supported by both SET and H-SPC. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If an initial position calculated based on information received in the SUPL POS INIT message is available which meets the requested QoP, the H-SPC MAY directly proceed to step R. The SET SHALL also release the connection to the H-SLC. M. The H-SPC sends a PLREQ message to the H-SLC informing it that that the target SET has established the session and including the lid and optionally the NMR specific data for the radio technology being used (e.g., for GSM: TA, RXLEV). N. The H-SLC sends a RLP SRLIR request to the V-SLC to determine an initial position for further exchange of SUPL POS messages between SET and H-SPC. The RLP request contains at least the msid and the Location ID (lid). Optionally the H-SLC MAY forward NMR provided by the SET to the V-SLC. O. The V-SLP returns a RLP SRLIA message. The RLP SRLIA message contains the position result. P. The H-SLC informs the H-SPC of the initial position in a PLRES message. If the computed position meets the requested QoP, the H-SPC MAY directly move to step R and not engage in a SUPL POS session. Q. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step E, the H-SPC SHALL only choose an approved method. If required for the posmethod the H-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL POS INIT message. The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). R. As in this case in step E the H-SLC indicated that notification or verification is required based on the position of the SET, the H-SPC sends the calculated position to the SET in a SUPL REPORT message. S. The H-SPC informs the H-SLC in a PEND message that the positioning procedure is completed and includes the position estimate result. The H-SPC SHALL release all resources related to this session.
T. As in this case in step G the H-SLC indicated that notification or verification is based on the position of the SET, the SET sends the calculated position to the H-SLC in a SUPL REPORT message. U. The H-SLC applies subscriber privacy against the SET position estimate. If, based on this position, notification and verification or notification only is required, the H-SLC SHALL send a SUPL NOTIFY message to the SET. The SUPL NOTIFY message contains notification element. If, based on this position, no notification and verification is required, the H-SLC SHALL directly proceed to Step W. V. The SET SHALL then send an SUPL NOTIFY RESPONSE message to the H-SLC. If notification and verification was required in step U then this will contain the notification response from the user. W. Once the position calculation is complete the H-SLC sends SUPL END message to the SET informing it that no further positioning procedure will be started and that the positioning session is finished. The SET SHALL release all resources related to this session.
OMA-TS-ILP-V2_0_1-20121205-A
Page 56 (295)
X. The H-SLC sends the position estimate back to the R-SLP in an RLP SRLIA message. The H-SLC SHALL release all resources related to this session. Y. The R-SLP sends the position estimate back to the SUPL Agent in an MLP SLIA message.
5.3
5.3.1
Exception Procedures
SET Does Not Allow Positioning for Non Roaming
This section describes the exception procedures for Network Initiated Immediate scenarios.
After receiving a SUPL INIT message the SET executes the notification/verification procedure. In this scenario, the subscriber rejects the location request. The flow shown in Figure 13 applies to both proxy and non-proxy mode.
SUPL Agent
H-SLC
H-SPC
Target SET
MLP SLIR(ms-id, client-id, eqop) A B

PREQ(session-id2, QoP) C LT1 D PRES(session-id2)
ST2
PT1
G H I MLP SLIA(posresult)
SUPL END(session-id, status code = consentDeniedByUser, ver) PEND(session-id2)
Figure 13: Network Initiated SET User Rejects Positioning for Non-Roaming. NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP SLIR message to the H-SLP, with which the SUPL Agent is associated. The H-SLP SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLP SHALL apply subscriber privacy against the client-id. B. The H-SLP verifies that the target SET is currently not SUPL Roaming. The H-SLP may also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or if the SET supports SUPL is considered out of scope for SUPL (there are various environment dependent mechanisms). C. The H-SLC requests service from the H-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved.
OMA-TS-ILP-V2_0_1-20121205-A
Page 57 (295)
D. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. E. The H-SLP initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, proxy/non-proxy mode indicator and the intended positioning method. The SUPL INIT MAY contain the protection level, the desired QoP and the address of the H-SLP. The protection level indicates the level of protection for the SUPL INIT message. In this case the result of the privacy check in Step A indicated that notification or verification to the target subscriber is required, and the H-SLP therefore includes the Notification element in the SUPL INIT message F. The SET analyses the received SUPL INIT. If found to be non authentic, the SET takes no further action. Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection.
G. The SET evaluates the notification rules and alerts the subscriber of the position request. In this case the user rejects the location request, either by explicit action or implicitly by not responding to the notification. The SET returns a SUPL END message to the H-SLC containing the session-id, a hash of the received SUPL INIT message (ver) and the status code consentDeniedByUser. H. The H-SLC sends a PEND message to the H-SPC to terminate the SUPL session. I. The H-SLC sends the position response, containing the ms-id, client-id, and the appropriate error-code back to the SUPL Agent using an MLP SLIA message.
5.3.2
SET Does Not Allow Positioning for Roaming with V-SLP
After receiving a SUPL INIT message the SET executes the notification/verification procedure. In this scenario, the subscriber rejects the location request. The flow shown in Figure 14 applies to both proxy and non-proxy mode for roaming with V-SLP.
OMA-TS-ILP-V2_0_1-20121205-A
Page 58 (295)
SUPL Agent
R-SLC
V-SLC
V-SPC
H-SLC
Target SET
MLP SLIR(ms-id, client-id, eqop) A B C

Routing Info
E F LT1 G H
J RT1 K L M N MLP SLIA(posresult) O
ST1
PT1
ST2
RLP SSRP(SUPL END) PEND(session-id2) RLP SRLIA(posresult)
SUPL END(session-id, status code = consentDeniedByUser, ver)
Figure 14: Network Initiated SET User Denies Positioning for Roaming with V-SLP NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP SLIR message to the R-SLC, with which SUPL Agent is associated. The R-SLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. B. The R-SLC determines the H-SLC based on the received msid. If the R-SLP determines that the SUPL Agent is not authorized for this request, Step L will be returned with the applicable MLP return code. NOTE 2: The specifics for determining the H-SLC are considered outside scope of SUPL (there are various environment dependent mechanisms). C. The R-SLC forwards the location request to the H-SLC of the target subscriber, using the RLP protocol. Based on the received ms-id the H-SLC SHALL apply subscriber privacy against the client-id. If a previously computed position which meets the requested QoP is available at the H-SLC, the H-SLC SHALL proceed to step I after having performed the step D. D. The H-SLC verifies that the target SET is currently SUPL Roaming. In addition the H-SLC MAY also verify that the target SET supports SUPL. NOTE 3: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms.
OMA-TS-ILP-V2_0_1-20121205-A
Page 59 (295)
NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope E. The H-SLC sends an RLP SSRLIR to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. Mandatory parameters in SUPL START that are not known to the H-SLC (lid and SET capabilities) shall be populated with arbitrary values by the H-SLC and be ignored by V-SLC. The SET part of the session-id will not be included in this message by the H-SLC to distinguish this scenario from a SET Initiated scenario. F. The V-SLC requests service from the V-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved.
G. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. H. The V-SLC acknowledges that it is ready to initiate a SUPL positioning procedure with an RLP SSRLIA back to the H-SLC. I. The H-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, proxy/non-proxy mode indicator and the intended positioning method. In this case the result of the privacy check in Step D indicated that notification or verification to the target subscriber is needed and the H-SLC therefore includes the Notification element in the SUPL INIT message. Before the SUPL INIT message is sent the H-SLC also computes and stores a hash of the message. If in step C the H-SLC decided to use a previously computed position the SUPL INIT message SHALL indicate this in a no position posmethod parameter value. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection.
J.
K. The SET evaluates the notification rules and alerts the subscriber of the position request. In this case the user rejects the location request, either by explicit action or implicitly by not responding to the notification, and the SET returns a SUPL END message to the H-SLC containing the session-id, a hash of the received SUPL INIT message (ver) and the status code consentDeniedByUser L. The H-SLC SHALL check that the hash of SUPL INIT matches the one it has computed for this particular session. The H-SLC then tunnels the SUPL END message to the V-SLC using RLP. M. The V-SLC sends a PEND message to the V-SPC to terminate the SUPL session. N. The H-SLC sends an RLP SRLIA message to the R-SLC indicating the error condition user rejected location request. The H-SLC SHALL release all resources related to this session. O. The H-SLC sends the position response, containing the ms-id, client-id, and the appropriate error-code back to the SUPL Agent using an MLP SLIA message.
5.3.3 5.3.4
SET Does Not Allow Positioning for Roaming with H-SLP SUPL Protocol Error
This scenario is identical to the non-roaming scenario (see section 5.3.1)
When a SUPL protocol error occurs and as a result the SUPL session is terminated, a PEND message is used by the SLC or SPC to notify its counterpart (i.e. SPC or SLC) about the end of the SUPL session.
OMA-TS-ILP-V2_0_1-20121205-A
Page 60 (295)
5.3.5
Timer expiration
Timer expirations are defined in Appendix C.
5.4
5.4.1
SET Initiated Proxy mode

This section describes the SET Initiated Proxy mode scenarios.
B C
Routing Info
SUPL START(session-id, lid, SET capabilities)
UT1 D E F PREQ(session-id2, SET capabilities, lid) LT1 PRES(session-id2) SUPL RESPONSE(session-id, posmethod)
ST1 G H I J
PT1 SUPL POS INIT(session-id, lid, SET capabilities) PINIT(session-id2, lid, SET capabilities) PLREQ(session-id2, lid) PLRES(session-id2, posresult) PT2 SUPL POS
PMESS(session-id2, RRLP/RRC/TIA-801)
UT2
K
PMESS(session-id2, RRLP/RRC/TIA-801)
SUPL POS(session-id, RRLP/RRC/TIA-801/LPP) SUPL POS(session-id, RRLP/RRC/TIA-801/LPP)
L M
UT3
Figure 15: SET-Initiated Non-Roaming Successful Case Proxy mode NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for position from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL START message to start a positioning session with the H-SLP. The SUPL START message contains session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). If a previously computed position which meets any requested QoP is available at the H-SLC the H 2012 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
OMA-TS-ILP-V2_0_1-20121205-A
Page 61 (295)
SLC SHALL directly proceed to step M and send the position to the SET in the SUPL END message (step N is not executed in this case).. C. The H-SLC verifies that the target SET is currently not SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms. D. The H-SLC inspects the SUPL START message and determines if the SET is allowed to directly access the H-SPC. The H-SLC requests service from the H-SPC for a SUPL session by sending a PREQ message containing the session-id2, lid, posmethod and optionally the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. It MAY also contain a position based on information received in the PREQ message. This position does not need to meet the QoP. F. Consistent with the SUPL START message including posmethod(s) supported by the SET, the HSLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL START message. The H-SLC SHALL respond with the SUPL RESPONSE to the SET. The SUPL RESPONSE contains the session-id but no H-SLC address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL RESPONSE also contains the posmethod. The SUPL RESPONSE MAY contain location information, not meeting the QoP, but giving an initial approximation of the position. If a coarse position computed based on information received in the SUPL START message meets the requested QoP, the H-SLC MAY directly proceed to step M and terminate the session with the H-SPC using a PEND message.
G. After the SET receives the SUPL RESPONSE from the H-SLC, the SET sends a SUPL POS INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted AGPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. H. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id and SET capabilities. The H-SLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step E, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H-SPC. Based on the PINIT message including posmethod(s) supported by the SET (as part of the SET capabilities)the SET capabilities, the H-SPC SHALL then determine the posmethod. If a posmethod has been included in the PINIT by the HSLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line withthat meets the SET capabilities andwhich was approved by the H-SLC in step D. If a coarse position calculated based on information received in the PINIT message is available that meets any required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session. I. If the H-SPC cannot translate the lid received in step H into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the H-SPC can perform the translation from lid into a coarse position itself.
OMA-TS-ILP-V2_0_1-20121205-A
Page 62 (295)
J.
This step is conditional and only occurs if step I was performed. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session.
K. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SETAssisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). L. Once the position calculation is complete the H-SPC sends a PEND message to the H-SLC. M. The H-SLC sends the SUPL END message to the SET informing it that no further positioning procedure will be started and that the location session is finished. Depending on positioning method and used positioning protocol the H-SLP MAY add the determined position to the SUPL END message. The SET SHALL release the secure connection to the H-SLC and release all resources related to this session.
5.4.2
SET Roaming where the V-SLP is involved in the positioning calculation. A policy of a single SET to H-SLP SUPL session is maintained by encapsulating the messages between the SET and V-SLP through the use of the RLP protocol.
OMA-TS-ILP-V2_0_1-20121205-A
Page 63 (295)
V-SLC
V-SPC
H-SLC
Target SET
B C RLP SSRLIR(SUPL START) PREQ(session-id2, SET capabilities, lid) LT1 F G ST3 PRES(session-id2) RLP SSRLIA(SUPL RESPONSE)
Routing Info
D E
UT1
SUPL RESPONSE(session-id, posmethod) H PT1 ST1 SUPL POS INIT(session-id, lid, SET capabilities) RLP SSRP(SUPL POS INIT) PINIT(session-id2, lid, SET capabilities) PLREQ(session-id2, lid) PT2 PLRES(session-id2, posresult) SUPL POS
ST1 I J K L M
UT2
SUPL POS SUPL POS
O P Q
PEND(session-id2, position) RLP SSRP(SUPL END) SUPL END(session-id) UT3
Figure 16: SET-Initiated Roaming Successful Case Proxy mode with V-SLP positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for position from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL START message to start a positioning session with the H-SLC. The SUPL START message contains session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). If a previously computed position which meets any requested QoP is available at the H-SLC the HSLC SHALL directly proceed to step Q and send the position to the SET in the SUPL END message (step Q of this flow will then not be executed). C. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms.
OMA-TS-ILP-V2_0_1-20121205-A
Page 64 (295)
D. The H-SLC decides that the assistance data/position calculation is done by the V-SLP and sends a RLP SSRLIR tunnelling the SUPL START message to the V-SLC. E. The V-SLC requests service from the V-SPC for a SUPL session by sending a PREQ message containing the session-id2, lid, the SET capabilities and optionally the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. F. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. It MAY also contain a position based on information received in the PREQ message. This position does not need to meet the QoP.
G. Consistent with the SUPL START message including posmethod(s) supported by the SET, the VSLC MAY determine the posmethod. If the V-SPC included a list of supported posmethods in step F, the chosen posmethod SHALL be on this list. If required for the posmethod, the V-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL START message. The V-SLC responds with a SUPL RESPONSE tunnelled over RLP back to the H-SLC that it is capable of supporting this request. The SUPL RESPONSE contains at least the sessionid and posmethod. The SUPL RESPONSE MAY contain location information, not meeting the QoP, but giving an initial approximation of the position. If a coarse position calculated based on information received in the RLP SSRLIR (SUPL START) message meets any requested QoP, the VSLC SHALL send a RLP SSRLIA (SUPL END) message as opposed to RLP SSRLIA (SUPL RESPONSE) including the position estimate to the H-SLC in which case the H-SLC SHALL then proceed to step Q and terminate the session with the H-SPC using a PEND message (step R of this flow will then not be executed). H. The H-SLC forwards the SUPL RESPONSE to the SET. The SUPL RESPONSE contains the session-id but no H-SLC address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL RESPONSE also contains the posmethod. The SUPL RESPONSE MAY contain location information, not meeting the QoP, but giving an initial approximation of the position. I. After the SET receives the SUPL RESPONSE from the H-SLC, the SET sends a SUPL POS INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted AGPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. The H-SLC forwards the SUPL POS INIT to the V-SLC over the RLP tunnel.
J.
K. The V-SLC sends a PINIT message to the V-SPC including session-id2, location id and SET capabilities. The V-SLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the V-SPC in step F, or a different posmethod of the V-SLCs choosing, as long as it is one supported by the V-SPC. Based on the PINIT message including the SET capabilities, the V-SPC SHALL then determine the posmethod. If a posmethod has been included in the PINIT by the V-SLC, the V-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the V-SPC shall choose any posmethod in line with the SET capabilities which was approved by the V-SLC in step E. If a coarse position calculated based on information received in PINIT message is available that meets the required QoP, the V-SPC MAY directly proceed to step O and not engage in a SUPL POS session. L. If the V-SPC cannot translate the lid received in step K into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step
OMA-TS-ILP-V2_0_1-20121205-A
Page 65 (295)
is optional and not required if the V-SPC can perform the translation from lid into a coarse position itself. M. This step is conditional and only occurs if step L was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the V-SPC MAY directly proceed to step K and not engage in a SUPL POS session. N. The SET and the V-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SPC and the V-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA801/LPP) is transferred between the V-SLC and the H-SLC using SUPL POS over RLP tunnel messages. The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages. The flow sequence PMESS RLP SSRP(SUPL POS) SUPL POS SUPL POS RLP SSRP(SUPL POS) PMESS is conceptually shown in dotted lines. The V-SPC calculates the position estimate based on the received positioning measurements (SETAssisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC via H-SLC (SET-Based). O. Once the position calculation is complete the V-SPC sends a PEND message to the V-SLC. P. The V-SLC then sends a SUPL END message to the SET, which is tunnelled over RLP via the HSLC. The V-SLC MAY add the determined position to the SUPL END message. The V-SLP SHALL release all resources related to this session. Q. The H-SLC forwards the SUPL END to the SET informing it that no further positioning procedure will be started and that the location session is finished. The SET SHALL release the secure connection and release all resources related to this session. The H-SLC SHALL release all resources related to this session.
5.4.3
SET Roaming where the H-SLP is involved in the positioning calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 66 (295)
V-SLC
H-SLC
H-SPC
Target SET
B C D
Routing Info
UT1
RLP SRLIR(msid, lid) ST4
E F G H
RLP SRLIA(ms-id, posresult) PREQ(session-id2, SET capabilities, posresult) LT1 PRES(session-id2) SUPL RESPONSE(session-id, posmethod) ST1 PT1 SUPL POS INIT(session-id, lid, SET capabilities)

UT2
SUPL POS(session-id, RRLP/RRC/TIA-801/LPP) SUPL POS(session-id, RRLP/RRC/TIA-801/LPP) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)
L M
UT3
Figure 17: SET-Initiated Roaming Successful Case Proxy mode with H-SLP positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for position from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL START message to start a positioning session with the H-SLC. The SUPL START message contains session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). If a previously computed position which meets any requested QoP is available at the H-SLC the HSLC SHALL directly proceed to step M and send a SUPL END message including the position to the SET and end the session (step N of this flow will then not be executed). C. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms. D. The H-SLC decides that the H-SLP will provide assistance/position calculation and the H-SLC sends a plain RLP SRLIR request to the V-SLC to determine a coarse position for further exchange of SUPL POS messages between SET and H-SLP. The RLP request contains at least the msid and the Location ID (lid).
OMA-TS-ILP-V2_0_1-20121205-A
Page 67 (295)
E. The V-SLC returns a RLP SRLIA message. The RLP SRLIA message contains at least the position result (e.g., coarse position for A-GPS positioning). If the computed position meets the requested QoP, the H-SLC MAY directly proceed directly to step M. F. The H-SLC inspects the SUPL START message and determines if the SET is allowed to directly access the H-SPC. The H-SLC requests service from the H-SPC for a SUPL session by sending a PREQ message containing the session-id2, coarse position estimate, SET capabilities and optionally the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved.
G. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. It MAY also contain a position based on information received in the PREQ message. This position does not need to meet the QoP. H. Consistent with the SUPL START message including posmethod(s) supported by the SET, the HSLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step G, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL START message. The H-SLC responds with the SUPL RESPONSE to the SET. The SUPL RESPONSE contains the session-id but no H-SPC address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL RESPONSE also contains the posmethod. The SUPL RESPONSE MAY contain location information, not meeting the QoP, but giving an initial approximation of the position. If a coarse position computed based on information received in the SUPL START message meets the requested QoP, the H-SLC MAY directly proceed to step M and terminate the session with the H-SPC using a PEND message. I. After the SET receives the SUPL RESPONSE from H-SLC, the SET sends a SUPL POS INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted AGPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id and SET capabilities. If a position computed based on information received in the PINIT message is available which meets any required QoP, the H-SPC MAY directly proceed to L and not engage in a SUPL POS session. The H-SLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step G, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H-SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL then determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step F.
J.
K. The SET and the H-SCP exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SETAssisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based).
OMA-TS-ILP-V2_0_1-20121205-A
Page 68 (295)
L. Once the position calculation is complete the H-SPC sends a PEND message to the H-SLC. M. The H-SLC sends a SUPL END message to the SET informing it that no further positioning procedure will be started and that the location session is finished. Depending on positioning method and used positioning protocol the H-SLP MAY add the determined position to the SUPL END message. The SET SHALL release the secure connection to the H-SLC and release all resources related to this session
5.4.4 5.4.5
SET-Initiated Location Request of another SET Location Request of Transfer Location to Third Party
This scenario does not involve ILP.
All scenarios to do with transfer of location to a third party are identical to the equivalent scenarios without transfer of location as far as ILP is concerned.
5.5
SET Initiated Non-Proxy mode
This section describes the SET Initiated Non-Proxy mode scenarios.
OMA-TS-ILP-V2_0_1-20121205-A
Page 69 (295)
5.5.1

A SUPL START(session-id, lid, SET capabilities)
Routing Info
D LT1 E F
PREQ(session-id2, SET capabilities, lid, SPC_SET_Key, SPC-TID) PRES(session-id2) SUPL RESPONSE(session-id, SPC address, posmethod, SPC_SET_Key, SPC-TID)
UT1
ST1 G H I J
PT1 SUPL POS INIT(session-id, lid, SET capabilities) PLREQ(session-id2, lid) PLRES(session-id2, posresult) PT2 SUPL POS(session id, RRLP/RRC/TIA-801/LPP)
SUPL POS SUPL POS
UT2
K L PEND(session-id2)
UT3
Figure 18: SET-Initiated Non-Roaming Successful Case Non-Proxy mode NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for position from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL START message to start a positioning session with the H-SLC. The SUPL START message contains session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). If a previously computed position which meets any requested QoP is available at the H-SLC the HSLC shall respond with a SUPL END message to the SET containing the position and end the SUPL session. C. The H-SLC verifies that the target SET is currently not SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms.
OMA-TS-ILP-V2_0_1-20121205-A
Page 70 (295)
D. The H-SLC will inspect the SUPL START message and determine if the SET is allowed to directly access the H-SPC. The H-SLC requests service from the H-SPC for a SUPL session by sending a PREQ message containing the session-id2, lid, SET capabilities and optionally the QoP. The H-SLC creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication and forwards them to the H-SPC in the PREQ message. The H-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the HSPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. It MAY also contain a position based on information received in the PREQ message. This position does not need to meet the QoP. F. Consistent with the SUPL START message including posmethod(s) supported by the SET, the HSLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL START message. The H-SLC SHALL respond with a SUPL RESPONSE to the SET. The SUPL RESPONSE contains the session-id, SPC_SET_Key and SPC-TID to be used by the SET for mutual H-SPC/SET authentication, and the address of the H-SPC to indicate to the SET that a new secure connection SHALL be established. The SUPL RESPONSE MAY contain location information, not meeting the QoP, but giving an initial approximation of the position. If a coarse position computed based on information received in the SUPL START message meets any requested QoP, the H-SLC MAY respond with a SUPL END message (instead of the SUPL RESPONSE) to the SET containing the position to end the SUPL session and terminate the session with the H-SPC using a PEND message. G. To initiate the actual positioning session the SET opens a new secure connection to the H-SPC using the address indicated in step F. The SET and H-SPC perform mutual authentication through the keys received in step D and step F, and the SET sends a SUPL POS INIT message. Before the new secure connection is established the existing secure connection to the H-SLC is closed. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based AGPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a coarse position calculated based on information received in the SUPL POS INIT message is available that meets any required QoP, the H-SPC MAY directly proceed to step K and not engage in a SUPL POS session. H. If the H-SPC cannot translate the lid received in step G into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the H-SPC can perform the translation from lid into a coarse position itself. I. This step is conditional and only occurs if step H was performed. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the H-SPC MAY directly proceed to step K and not engage in a SUPL POS session. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step D, the H-SPC SHALL only choose an approved method. The SET and the SPC exchange several successive positioning procedure messages (a SUPL POS message exchange is shown conceptually in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-
J.
OMA-TS-ILP-V2_0_1-20121205-A
Page 71 (295)
Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). K. Once the position calculation is complete the H-SPC SHALL send the SUPL END message to the SET informing it that no further positioning procedure will be started and that the location session is finished. Depending on positioning method and used positioning protocol the SPC MAY add the determined position to the SUPL END message. When the SUPL END is received the SET SHALL release the secure connection to the H-SPC and release all resources related to this session. The H-SPC informs the H-SLC that the positioning procedure is finished. The H-SPC SHALL release all resources related to this session. L. The H-SPC sends a PEND message to the H-SLC indicating that all resources related to this session are to be released.
5.5.2
SET Roaming where the V-SPC is involved in the positioning calculation.
H-SLC
V-SLC
V-SPC
Target SET
A SUPL START(session-id, lid, SET capabilities)
B C D E F G H I J ST3
Routing Info
RLP SSRLIR(SUPL START) PREQ(session-id2, SET capabilities, lid) LT1 PRES(session-id2) UT1 RLP SSRLIA(SUPL RESPONSE) PT1
RLP SSRP(AUTH RESP(session id, SPC_SET_Key, SPC-TID) PAUTH(session-id2, SPC_SET_Key, SPC-TID) SUPL RESPONSE(session-id, SPC address, posmethod, SPC_SET_Key, SPC-TID)
K L M
ST1
ST1 PLREQ(session-id2, lid)
SUPL POS INIT(session-id, lid, SET capabilities) PT2 PLRES(session-id2, posresult)
UT2

SUPL POS
SUPL POS
O P Q RLP SSRP(SUPL END) PEND(session-id2)
UT3
Figure 19: SET-Initiated Roaming Successful Case Non-Proxy mode with V-SPC positioning NOTE 1: See Appendix C for timer descriptions.
OMA-TS-ILP-V2_0_1-20121205-A
Page 72 (295)
A. The SUPL Agent on the SET receives a request for position from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL START message to start a positioning session with the H-SLC. The SUPL START message contains session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). If a previously computed position which meets any requested QoP is available at the H-SLC the HSLC SHALL send a SUPL END message including the position to the SET and end the session. C. The H-SLP verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. However, there are various environment dependent mechanisms. D. The H-SLC decides that the assistance data/position calculation is done by the V-SPC, allocates a sessionid and sends an RLP SSRLIR tunnelling the SUPL START message to the V-SLC. E. The V-SLC requests service from the V-SPC for a SUPL session by sending a PREQ message containing the session-id2, lid, SET capabilities and optionally the QoP. The V-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. F. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. It MAY also contain a position based on information received in the PREQ message. This position does not need to meet the QoP.
G. Consistent with the SUPL START message including posmethod(s) supported by the SET, the VSLC MAY determine the posmethod. If the V-SPC included a list of supported posmethods in step F, the chosen posmethod SHALL be on this list. If required for the posmethod, the V-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL START message. The V-SLC responds with a SUPL RESPONSE tunnelled over RLP back to the H-SLC that it is capable of supporting this request. The SUPL RESPONSE contains at least the sessionid, and the VSPC address. The SUPL RESPONSE also contains the posmethod. The SUPL RESPONSE MAY contain location information, not meeting the QoP, but giving an initial approximation of the position. If a coarse position calculated based on information received in the RLP SSRLIR (SUPL START) message meets any requested QoP, the V-SLC MAY send a RLP SSRLIA (SUPL END) message as opposed to RLP SSRLIA (SUPL RESPONSE) including the position estimate to the H-SLC in which case the H-SLC sends a SUPL END message carrying the session id and including the position estimate to the SET (as opposed to the SUPL RESPONSE message) to terminates the ULP session and terminates the session with the H-SPC using a PEND message. H. The H-SLC creates SPC_SET_Key and SPC-TID to be used for mutual V-SPC/SET authentication.The H-SLC forwards SPC_SET_Key and SPC-TID to the V-SLC through an RLP SSRP message. I. J. The V-SLC forwards SPC_SET_Key and SPC-TID to the V-SPC through a PAUTH message. The H-SLC forwards the SUPL RESPONSE to the SET. The SUPL RESPONSE contains at least session-id, posmethod, SPC_SET_Key and SPC-TID to be used by the SET for mutual V-SPC/SET authentication, and the address of the V-SPC to indicate to the SET that a new secure connection SHALL be established. The SUPL RESPONSE MAY contain location information, not meeting the QoP, but giving an initial approximation of the position.
K. To initiate the actual positioning session the SET opens a new secure connection to the V-SPC using the address indicated in step J. The SET and V-SPC perform mutual authentication through the keys received in step I and step J and the SET sends a SUPL POS INIT message. Before the new secure
OMA-TS-ILP-V2_0_1-20121205-A
Page 73 (295)
connection is established the existing secure connection to the H-SLC is closed. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based AGPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a coarse position calculated based on information received in the SUPL POS INIT message is available that meets the required QoP, the V-SPC MAY directly proceed to step O and not engage in a SUPL POS session. L. If the V-SPC cannot translate the lid received in step K into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into a coarse position itself. M. This step is conditional and only occurs if step L was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets any required QoP, the V-SPC MAY directly proceed to step K and not engage in a SUPL POS session. N. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the V-SPC SHALL determine the posmethod. If the V-SLC included its approved positioning methods in step E, the V-SPC SHALL only choose an approved method. The SET and the V-SPC exchange several successive positioning procedure messages (a SUPL POS message exchange is shown conceptually in dotted lines). The V-SPC calculates the position estimate based on the received positioning measurements (SETAssisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). O. Once the position estimate or calculation is complete, the V-SPC sends a SUPL END to the SET and depending on positioning method and positioning protocol optionally includes the position. The SET SHALL release the secure connection and release all resources related to this session. P. The V-SPC informs the V-SLC of the end of the SUPL positioning session. The V-SPC SHALL release all resources related to this session. Q. The V-SLC sends a RLP SSRP to the H-SLC to inform about the end of the SUPL session. The HSLC and V-SLC SHALL release all resources related to this session.
5.5.3
SET Roaming where the H-SPC is involved in the positioning calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 74 (295)
V-SLC
H-SLC
H-SPC
Target SET
B C D
Routing Info
RLP SRLIR(msid, lid) ST4
UT1
E F G H
RLP SRLIA(ms-id, posresult) PREQ(session-id2, SET capabilities, posresult, SPC_SET_Key, SPC-TID) PRES(session-id2) SUPL RESPONSE(session-id, H-SPC address, posmethod, SPC_SET_Key, SPC-TID) PT1
LT1
ST1 I
SUPL POS INIT(session-id, lid, SET capabilities) SUPL POS(session id, RRLP/RRC/ TIA-801/LPP)
SUPL POS SUPL POS
UT2
K L PEND(session-id2)
UT3
Figure 20: SET-Initiated Roaming Successful Case Non-Proxy mode with H-SPC positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for position from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL START message to the H-SLC to start a SUPL session with the H-SLC and to request authorization to start a SUPL positioning session with the HSPC. The SUPL START message contains session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). If a previously computed position which meets any requested QoP is available at the H-SLC the HSLC SHALL send a SUPL END message including the position to the SET and end the session. C. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL. D. The H-SLC decides that the H-SPC will provide assistance/position calculation and the H-SLC sends a plain RLP SRLIR request to the V-SLC to determine a coarse position for further exchange
OMA-TS-ILP-V2_0_1-20121205-A
Page 75 (295)
of SUPL POS messages between SET and H-SPC. The RLP request contains at least the msid and the Location ID (lid). E. The V-SLC returns a RLP SRLIA message. The RLP SRLIA message contains at least the position result (e.g., coarse position for A-GPS positioning). If the coarse position received from the V-SLC meets any requested QoP the H-SLC MAY send a SUPL END to the SET carrying the sessionid and the position result and terminate the SUPL session. F. The H-SLC will inspect the SUPL START message and determine if the SET is allowed to directly access the H-SPC. The H-SLC requests service from the H-SPC for a SUPL session by sending a PREQ message containing the session-id2, coarse position estimate, SET capabilities and optionally the QoP. The H-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. The H-SLC also creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication. SPC_SET_Key and SPC-TID are forwarded to the H-SPC in the PREQ message.
G. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. It MAY also contain a position based on information received in the PREQ message. This position does not need to meet the QoP. H. Consistent with the SUPL START message including posmethod(s) supported by the SET, the HSLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step G, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL START message. The H-SLC responds with the SUPL RESPONSE to the SET. The SUPL RESPONSE contains the session-id, SPC_SET_Key and SPC-TID to be used by the SET for mutual H-SPC/SET authentication, and the H-SPC address. The SUPL RESPONSE also contains the posmethod. The SUPL RESPONSE MAY contain location information, not meeting the QoP, but giving an initial approximation of the position. If a coarse position computed based on information received in the SUPL START message meets any requested QoP, the H-SLC MAY respond with a SUPL END message (instead of the SUPL RESPONSE) to the SET containing the position to end the SUPL session and terminate the session with the H-SPC using a PEND message. I. To initiate the actual positioning session the SET opens a new secure connection to the H-SPC using the address indicated in step H. The SET and H-SPC perform mutual authentication through the keys received in step F and step H, and the SET sends a SUPL POS INIT message. Before the new secure connection is established the existing secure connection to the H-SLC is closed. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based AGPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position computed based on information received in the PINIT message is available which meets any required QoP, the H-SPC MAY directly proceed to K and not engage in a SUPL POS session. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step F, the H-SPC SHALL only choose an approved method. The SET and the H-SPC exchange several successive positioning procedure messages (a SUPL POS message exchange is shown conceptually in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SETAssisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based).
J.
OMA-TS-ILP-V2_0_1-20121205-A
Page 76 (295)
K. Once the position calculation is complete the H-SPC sends a SUPL END message to the SET informing it that no further positioning procedure will be started and that the location session is finished. Depending on the positioning protocol used and positioning method the location estimate is optionally included in the SUPL END message. The SET SHALL release the secure connection and release all resources related to this session. The H-SPC informs the H-SLC that the positioning procedure is finished. The H-SPC SHALL release all resources related to this session. L. The H-SPC sends a PEND message to the H-SLC indicating that all resources related to this session are to be released.
5.5.4 5.5.5
SET-Initiated Location Request of another SET Location Request of Transfer Location to Third Party
This scenario does not involve ILP.
All scenarios to do with transfer of location to a third party are identical to the equivalent scenarios without transfer of location as far as ILP is concerned.
5.6
5.6.1 5.6.2
SET Authorization Failure SUPL Protocol Error
This section describes the exception procedures for SET Initiated Immediate scenarios.
This error case does not impact the Llp interface.
When a SUPL protocol error occurs and as a result the SUPL session is terminated, a PEND message is used by the SLC or SPC to notify its counterpart (i.e. SPC or SLC) about the end of the SUPL session.
5.6.3
Timer expiration
Timer expirations are defined in Appendix C.
5.7
Emergency Services Location Request Proxy Mode
This section describes the handling of Emergency Service Location Requests in Proxy Mode.
OMA-TS-ILP-V2_0_1-20121205-A
Page 77 (295)
5.7.1

SUPL Agent E-SLC E-SPC Target SET
A B
MLP ELIR(ms-id, client-id, eqop)

Non-roaming Verification, Routing Info
C LT1 D E F
PREQ(session-id2, QoP) PRES(session-id2) SUPL INIT(session-id, posmethod, SLP mode, E-SLP address)
ST2
PT1
G H I J
SUPL POS INIT(session-id, lid, SET capabilities, ver) PINIT(session-id2, lid, SET capabilities) PLREQ(session-id2, lid) PLRES(session-id2, posresult) PT2 SUPL POS
PMESS(session-id2, RRLP/RRC/TIA-801/LPP) SUPL POS(session-id, RRLP/RRC/TIA-801/LPP) SUPL POS(session-id, RRLP/RRC/TIA-801/LPP) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)
UT2
L M N MLP ELIA(posresult)
UT3
Figure 21: Network Initiated Emergency Services Non-Roaming Successful Case Proxy Mode NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP ELIR message to the E-SLC, with which SUPL Agent is associated. The MLP ELIR message may include the SET IP address and location data. The E-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. If a previously computed position which meets the requested QoP is available at the E-SLC and no notification or verification is required according to local regulatory requirements, the E-SLC SHALL directly proceed to step N. If notification and verification or notification only is required, the E-SLC SHALL proceed to step B. B. The E-SLC may use any location data and/or any SET IP address received in step A to verify that the target SET is currently not SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL (there are various environment dependent mechanisms). C. The E-SLC requests service from the E-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The E-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the E-SPC SHALL assume that all its available positioning methods have been approved.
OMA-TS-ILP-V2_0_1-20121205-A
Page 78 (295)
D. The E-SPC accepts the service request for a SUPL session from the E-SLC with a PRES message containing the session-id2. The E-SPC MAY include a preferred positioning method in the PRES. The E-SPC MAY include its supported positioning methods in the PRES message. E. The E-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, proxy/non-proxy mode indicator and the intended positioning method. The SUPL INIT message SHALL contain the E-SLP address if the E-SLP is not the H-SLP for the SET. The SUPL INIT MAY contain the desired QoP. The E-SLP SHALL also include the Notification element in the SUPL INIT message indicating location for emergency services and, according to local regulatory requirements, whether notification or verification to the target SET is or is not required. Before the SUPL INIT message is sent the E-SLC also computes and stores a hash of the message. If in step A the E-SLC decided to use a previously computed position, the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message carrying the results of the verification process (access granted, or access denied). If no explicit verification is required (notification only) the SET SHALL respond with a SUPL END message. The E-SLC SHALL then directly proceed to step N. NOTE 3: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step F and use the procedures described in step G to establish a secure connection to the E-SLC. F. The SET takes needed action preparing for establishment or resumption of a secure connection.
G. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the E-SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the E-SLC using either the provisioned H-SLP or defaulted ESLP address, if no E-SLP address was received in step E, or the E-SLP address received in step E. The SET then sends a SUPL POS INIT message to start a positioning session with the E-SLP. The SET SHALL send the SUPL POS INIT message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. H. The E-SLC sends a PINIT message to the E-SPC including session-id2, location id and SET capabilities. The E-SLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the E-SPC in step D, or a different posmethod of the E-SLCs choosing, as long as it is one supported by the E-SPC. Based on the PINIT message including the SET capabilities, the E-SPC SHALL then determine the posmethod. If a posmethod has been included in the PINIT by the E-SLC, the E-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the E-SPC shall choose any posmethod in line with the SET capabilities which was approved by the E-SLC in step C. If required for the posmethod the E-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the PINIT message. If a position received from or calculated based on information received in the PINIT message is available that meets the required QoP, the E-SPC MAY directly proceed to step L and not engage in a SUPL POS session. I. If the E-SPC cannot translate the lid received in step H into a position, the E-SPC sends a PLREQ message to the ESLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the E-SPC can perform the translation from lid into a position itself. This step is conditional and only occurs if step I was performed. The E-SLC reports the position result back to the ESPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the position meets the required QoP, the E-SPC MAY directly proceed to step L and not engage in a SUPL POS session.
J.
K. The SET and the E-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the E-SPC and the E-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the E-SLC and the SET using
OMA-TS-ILP-V2_0_1-20121205-A
Page 79 (295)
SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The E-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the E-SLP (SET-Based). L. Once the position calculation is complete the E-SPC sends a PEND message to the E-SLC including the position result. M. The E-SLC sends a SUPL END message to the SET informing it that no further positioning procedure will be started and that the location session is finished. The SET SHALL release the secure connection to the E-SLC and release all resources related to this session. N. The E-SLC sends the position estimate back to the SUPL Agent using an MLP ELIA message. The E-SLP SHALL release all resources related to this session.
5.7.2

SUPL Agent
A B RLP SSRLIR(SUPL START) PREQ(session-id2, QoP) LT1 E F ST3 PRES(session-id2) RLP SSRLIA(SUPL RESPONSE)
V-SLC
V-SPC
E-SLC
Target SET
C D
G PT1 ST2
SUPL INIT(session-id, posmethod, SLP mode, E-SLP Address) ST1

I J K L M
SUPL POS SUPL POS
O P Q R MLP ELIA(posresult)
PEND(session-id2, position) RLP SSRP(SUPL END) SUPL END(session-id) UT3
Figure 22: Network Initiated Emergency Services Roaming Successful Case Proxy Mode with V-SLP positioning
OMA-TS-ILP-V2_0_1-20121205-A
Page 80 (295)
NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP ELIR message to the E-SLC, with which SUPL Agent is associated. The MLP ELIR message may include the SET IP address and location data. The E-SLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. If a previously computed position which meets the requested QoP is available at the E-SLC and no notification or verification is required according to local regulatory requirements, the E-SLC SHALL directly proceed to step R. If notification and verification or notification only is required, the E-SLC SHALL proceed to step G after having performed step B. B. The E-SLC may use any location data and/or any SET IP address received in step A to verify that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL (there are various environment dependent mechanisms). C. The E-SLC sends an RLP SSRLIR to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. Mandatory parameters in SUPL START that are not known to the E-SLC (lid and SET capabilities) shall be populated with arbitrary values by the E-SLC and be ignored by V-SLC. The SET part of the session-id will not be included in this message by the E-SLC to distinguish this scenario from a SET Initiated scenario. D. The V-SLC requests service from the V-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. E. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. F. The V-SLC acknowledges that it is ready to initiate a SUPL positioning procedure with an RLP SSRLIA back to the E-SLC.
G. The E-SLC initiates the location session with the SET using the SUPL INIT message.The SUPL INIT message contains at least session-id, proxy/non-proxy mode indicator and the intended positioning method. The SUPL INIT SHALL contain the E-SLP address if the E-SLP is not the H-SLP for the SET. The SUPL INIT MAY contain the desired QoP. The E-SLC SHALL also include the Notification element in the SUPL INIT message indicating location for emergency services and, according to local regulatory requirements, whether notification or verification to the target SET is or is not required. Before the SUPL INIT message is sent the E-SLC also computes and stores a hash of the message. If in step A the E-SLC decided to use a previously computed position, the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message to the ESLC carrying the results of the verification process (access granted, or access denied). If no verification is required (notification only) the SET SHALL respond with a SUPL END message to the E-SLC. The E-SLP SHALL then directly proceed to step R. NOTE 3: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step H and use the procedures described in step I to establish a secure connection to the E-SLC. H. The SET takes needed action preparing for establishment or resumption of a secure connection. I. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the E-SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the E-SLC using either the H-SLP address, if no E-SLP address was received in step G, or the E-SLP address received in step G. The SET then sends a SUPL POS INIT message to start a positioning session with the E-SLC. The SET SHALL send the SUPL POS INIT message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid). The SET capabilities include the supported positioning methods
OMA-TS-ILP-V2_0_1-20121205-A
Page 81 (295)
(e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. J. The E-SLC SHALL check that the hash of SUPL INIT matches the one it has computed for this particular session. The E-SLC then tunnels the SUPL POS INIT message to the V-SLC using RLP.
K. The V-SLC sends a PINIT message to the V-SPC including session-id2, location id and SET capabilities. The VSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the V-SPC in step E, or a different posmethod of the V-SLCs choosing, as long as it is one supported by the V-SPC. Based on the PINIT message including the SET capabilities, the V-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the V-SLC, the V-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the V-SPC shall choose any posmethod in line with the SET capabilities which was approved by the V-SLC in step D. If required for the posmethod the V-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the PINIT message. If an initial position calculated based on information received in the PINIT message is available that meets the required QoP, the V-SPC MAY directly proceed to step O and not engage in a SUPL POS session. L. If the V-SPC cannot translate the lid received in step K into an initial position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into an initial position itself. M. This step is conditional and only occurs if step L was performed. The V-SLC reports an initial position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the initial position meets the required QoP, the V-SPC MAY directly proceed to step O and not engage in a SUPL POS session. N. The SET and the V-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SPC and the V-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SLC and the E-SLC using SUPL POS over RLP tunnel messages. The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the E-SLC and the SET using SUPL POS messages. The flow sequence PMESS RLP SSRP (SUPL POS) SUPL POS SUPL POS RLP SSRP(SUPL POS) PMESS is conceptually shown in dotted lines. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). O. Once the position calculation is complete, the V-SPC sends a PEND message to the V-SLC including the position result. P. The V-SLC sends a SUPL END message to the E-SLC over RLP. The SUPL END message SHALL contain the session id and the position result. Q. The E-SLC sends the SUPL END message to the SET informing it that no further positioning procedure will be started and that the location session is finished. The SET SHALL release the secure connection to the E-SLC and release all resources related to this session. R. The E-SLC sends the position estimate back to the SUPL Agent using an MLP ELIA message.
5.8
Emergency Services Location Request Non-Proxy Mode
This section describes the handling of an Emergency Services Location Request in Non-Proxy Mode.
OMA-TS-ILP-V2_0_1-20121205-A
Page 82 (295)
5.8.1
SUPL Agent
H-SLC
H-SPC
Target SET
A B

C LT1 D E F ST2 G H
PREQ(session-id2, QoP) PRES(session-id2) SUPL INIT(session-id, posmethod, SLP mode, E-SLP address)
PT1 SUPL AUTH REQ(session-id, ver) PAUTH(session-id2, SPC_SET_Key, SPC-TID) UT4
I J K L M
SUPL POS SUPL POS
UT2
N O P MLP ELIA(posresult) PEND(session-id2, posresult)
UT3
Figure 23: Network Initiated Non-Roaming Successful Case Non-Proxy mode NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP ELIR message to the E-SLC, with which SUPL Agent is associated. The MLP ELIR message may include the SET IP address and location data. The E-SLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. If a previously computed position which meets the requested QoP is available at the E-SLC and no notification or verification is required according to local regulatory requirements, the E-SLC SHALL directly proceed to step P. If notification and verification or notification only is required, the E-SLC SHALL proceed to step E after having performed the SET Lookup and Routing Info procedures of step B. B. The E-SLC may use any location data and/or any SET IP address received in step A to verify that the target SET is currently not SUPL Roaming.
OMA-TS-ILP-V2_0_1-20121205-A
Page 83 (295)
NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL (there are various environment dependent mechanisms). C. The E-SLC requests service from the E-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The E-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the E-SPC SHALL assume that all its available positioning methods have been approved. D. The E-SPC accepts the service request for a SUPL session from the E-SLC with a PRES message containing the session-id2. The E-SPC MAY include a preferred positioning method in the PRES. The E-SPC MAY include its supported positioning methods in the PRES message. E. The E-SLC initiates the location session with the SET using the SUPL INIT message. The SUPL INIT message SHALL contain session-id, address of the V-SPC, proxy/non-proxy mode indicator and the intended positioning method. The SUPL INIT SHALL also contain the E-SLP address if the E-SLP is not the H-SLP for the SET. The SUPL INIT MAY contain the desired QoP. The E-SLC SHALL also include the Notification element in the SUPL INIT message indicating location for emergency services and, according to local regulatory requirements, whether notification or verification to the target SET is or is not required. Before the SUPL INIT message is sent the E-SLC also computes and stores a hash of the message. If in step A the E-SLC decided to use a previously computed position, the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message carrying the results of the verification process (access granted, or access denied). If no explicit verification is required (notification only) the SET SHALL respond with a SUPL END message. The H-SLC SHALL then directly proceed to step P. Note: before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step F to establish a secure connection to the E-SLC. F. The SET takes needed action preparing for establishment or resumption of a secure connection.
G. The SET will evaluate the Notification rules and follow the appropriate actions. The SET SHALL establish a secure connection to the E-SLC using either the provisioned H-SLP or defaulted E-SLP address, if no E-SLP address was received in step E, or the E-SLP address received in step E. The SET also checks the proxy/non-proxy mode indicator to determine if the E-SLP uses proxy or nonproxy mode. In this case, non-proxy mode is used and the SET SHALL send a SUPL AUTH REQ to the E-SLC. The SUPL AUTH REQ SHALL contain the session-id and a hash of the received SUPL INIT message (ver). H. The E-SLC creates SPC_SET_Key and SPC-TID to be used for mutual E-SPC/SET authentication. The E-SLC forwards SPC_SET_Key and SPC-TID to the E-SPC using a PAUTH message with also includes the session-id. I. J. The E-SLC returns a SUPL AUTH RESP message to the SET. The SUPL AUTH RESP message SHALL contain the session-id, SPC_SET_Key and SPC-TID. The SET will evaluate the Notification rules and follow the appropriate actions. The SET establishes a secure connection to the E-SPC according to the address received in step E. The SET and E-SPC perform mutual authentication and the SET sends a SUPL POS INIT message to start a positioning session with the E-SPC. The SET SHALL send the SUPL POS INIT message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SETAssisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. The SET SHALL also release the IP connection to the E-SLC and release all resources related to this session. If an initial position calculated based on information received in the SUPL POS INIT message is available which meets the requested QoP, the E-SPC MAY directly proceed to step N and no SUPL POS positioning session takes place.
OMA-TS-ILP-V2_0_1-20121205-A
Page 84 (295)
K. If the E-SPC cannot translate the lid received in step J into an initial position, the E-SPC sends a PLREQ message to the E-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the E-SPC can perform the translation from lid into an initial position itself. L. This step is conditional and only occurs if step K was performed. The E-SLC reports the initial position result back to the E-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the initial position meets the required QoP, the E-SPC MAY directly proceed to step N and not engage in a SUPL POS session. M. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the E-SPC SHALL determine the posmethod. If the E-SLC included its approved positioning methods in step C, the E-SPC SHALL only choose an approved method. If required for the posmethod the E-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL POS INIT message. The SET and the E-SPC exchange several successive positioning procedure messages (a SUPL POS message exchange is shown conceptually in dotted lines). The E-SPC calculates the position estimate based on the received positioning measurements (SETAssisted) or the SET calculates the position estimate based on assistance obtained from the E-SPC (SET-Based). N. Once the position calculation is complete, the E-SPC sends the SUPL END message to the SET informing it that no further positioning procedure will be started and that the SUPL session is finished. The SET SHALL release the secure connection to the E-SPC and release all resources related to this session. O. The E-SPC sends the position estimate to the E-SLC using a PEND message. This also indicates the end of the SUPL session. The E-SPC SHALL release all resources related to this session. P. The E-SLC sends the position estimate back to the SUPL Agent using an MLP ELIA message. The E-SLC SHALL release all resources related to this session.
5.8.2
Roaming Successful Case with V-SPC Positioning
SET Roaming where the V-SPC is involved in the positioning calculation
OMA-TS-ILP-V2_0_1-20121205-A
Page 85 (295)
SUPL Agent
E-SLP
V-SLC
V-SPC
Target SET
B C D E F G
RLP SSRLIR(SUPL START) PREQ(session-id2, QoP) LT1 ST3 RLP SSRLIA(SUPL RESPONSE) SUPL INIT(session-id, posmethod, SLP mode, E-SLP address) PRES(session-id2)
PT1 SUPL AUTH REQ(session-id, ver) ST2 RLP SSRP(SUPL AUTH RESP) PAUTH(session-id2, SPC_SET_Key, SPC-TID) SUPL AUTH RESP(session-id, SPC_SET_Key, SPC-TID)
I J K L M N O
UT4
UT2

SUPL POS
SUPL POS
Q R S T RLP SSRP(SUPL END) MLP ELIA(posresult) PEND(session-id2, posresult)
UT3
Figure 24: Network Initiated Roaming Successful Case Non-Proxy-mode with V-SPC positioning NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP ELIR message to the E-SLP, with which SUPL Agent is associated. The MLP ELIR message may include the SET IP address and location data. The E-SLP SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. If a previously computed position which meets the requested QoP is available at the E-SLP and no notification or verification is required according to local regulatory requirements, the E-SLP SHALL directly proceed to step T. If notification and verification or notification only is required, the E-SLP SHALL proceed to step G after having performed the Roaming Verification and Routing Info procedures of step B. B. The E-SLP may use any location data and/or any SET IP address received in step A to verify that the target SET is currently SUPL Roaming.
OMA-TS-ILP-V2_0_1-20121205-A
Page 86 (295)
NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL (there are various environment dependent mechanisms). C. The E-SLP allocates a session-id for the SUPL session and decides that the V-SPC will provide assistance data or perform the position calculation. The E-SLP sends an RLP SSRLIR to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. Mandatory parameters in SUPL START that are not known to E-SLP (lid and SET capabilities) shall be populated with arbitrary values by E-SLP and be ignored by V-SLP. The SET part of the session-id will not be included in this message by the E-SLP to distinguish this scenario from a SET Initiated scenario. D. The V-SLC requests service from the V-SPC for a SUPL session by sending a PREQ message containing the session-id2 and the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. E. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. F. The V-SLC acknowledges that V-SPC is ready to initiate a SUPL positioning procedure with an RLP SSRLIA back to the H-SLC. The message includes at least session-id, posmethod and the address of the V-SPC.
G. The E-SLP initiates the location session with the SET using the SUPL INIT message.The SUPL INIT message SHALL contain session-id, address of the V-SPC, proxy/non-proxy mode indicator and the intended positioning method. The SUPL INIT SHALL also contain the E-SLP address if the E-SLP is not the H-SLP for the SET. The SUPL INIT MAY contain the desired QoP. The E-SLP SHALL also include Notification element in the SUPL INIT message indicating location for emergency services and, according to local regulatory requirements, whether notification or verification to the target SET is or is not required. If in step A the E-SLP decided to use a previously computed position the SUPL INIT message SHALL indicate this in a no position posmethod parameter value and the SET SHALL respond with a SUPL END message to the ESLP carrying the results of the verification process (access granted, or access denied). If no verification is required (notification only) the SET SHALL respond with a SUPL END message to the E-SLP. The E-SLP SHALL then directly proceed to step T. NOTE 3: Before sending the SUPL END message the SET SHALL perform the data connection setup procedure of step H and use the procedures described in step I to establish an IP connection to the E-SLP. H. The SET takes needed action preparing for establishment or resumption of a secure connection. I. The SET establishes a secure connection to the E-SLP using either the provisioned H-SLP or defaulted E-SLP address, if no E-SLP address was received in step G, or the E-SLP address provided in step G. The SET then checks the proxy/non-proxy mode indicator to determine if the E-SLP uses proxy or non-proxy mode. In this case nonproxy mode is used and the SET SHALL send a SUPL AUTH REQ message to the E-SLP. The SUPL AUTH REQ message SHALL contain session-id and a hash of the SUPL INIT message (ver). The E-SLP creates SPC_SET_Key and SPC-TID to be used for mutual V-SPC/SET authentication. The E-SLP forwards SPC_SET_Key and SPC-TID to the V-SLC through an RLP SSRP message.
J.
K. The V-SLC forwards SPC_SET_Key and SPC-TID to the V-SPC using the PAUTH message. L. The H-SLC returns a SUPL AUTH RESP to the SET. The SUPL AUTH RESP message SHALL contain the session-id, SPC_SET_Key and SPC-TID. M. The SET will evaluate the Notification rules and follow the appropriate actions. The SET establishes an IP connection to the V-SPC according to the address received in step G. The SET and V-SPC may perform mutual authentication and the SET sends a SUPL POS INIT message to start a SUPL positioning session with the V-SPC. The SET SHALL send the SUPL POS INIT message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported
OMA-TS-ILP-V2_0_1-20121205-A
Page 87 (295)
positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. The SET SHALL also release the IP connection to the E-SLP and release all resources related to this session. N. If the V-SPC cannot translate the lid received in step M into an initial position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into an initial position itself. O. This step is conditional and only occurs if step N was performed. The V-SLC reports the initial position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the initial position meets the required QoP, the V-SPC MAY directly proceed to step Q and not engage in a SUPL POS session. P. Based on the SUPL POS INIT message including posmethod(s) supported by the SET, the V-SPC SHALL determine the posmethod. If the V-SLC included its approved positioning methods in step D, the V-SPC SHALL only choose an approved method. If required for the posmethod, the V-SPC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL POS INIT message. The SET and the V-SPC exchange several successive positioning procedure messages (a SUPL POS message exchange is shown conceptually in dotted lines). The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). Q. Once the position calculation is complete the V-SPC sends a SUPL END message to the SET informing it that no further positioning procedure will be started and that the positioning session is finished. The SET SHALL release all resources related to this session. R. The V-SPC informs the V-SLC using a PEND message that the positioning procedure is completed and returns the position result. The V-SPC SHALL release all resources related to this session. S. The V-SLC sends a SUPL END message within an RLP SSRP message to the E-SLP carrying the position result. The V-SLC SHALL release all resources related to this session.
T. The E-SLP sends the position estimate back to the SUPL Agent in an MLP ELIA message.
OMA-TS-ILP-V2_0_1-20121205-A
Page 88 (295)
6. Detailed Flows Triggered Services: Periodic Triggers

The flows in this section are those for which periodic triggers are required. Set up and release of connections: Before sending any ULP messages the SET SHALL take needed actions such that a TLS connection exists to the SLP/SLC. This can be achieved by establishing a new connection, resume a connection or reuse an existing TLS connection. This includes establishment or utilization of various data connectivity resources that depends on the terminal in which the SET resides and the type of access network. Data connectivity below IP-level is out of scope of this document. The detailed flows in this section describes when a TLS connection no longer is needed. The TLS connection shall then be released unless another SUPL session is using the TLS connection.
6.1
Network Initiated Proxy mode
This section describes the Network Initiated Proxy mode scenarios. It is assumed that the trigger resides in the SET (see [SUPL2 ULP TS] for more details). The concept of the R-SLC applies as with Immediate Service but for the sake of simplicity has been omitted in this section.
OMA-TS-ILP-V2_0_1-20121205-A
Page 89 (295)
6.1.1

SUPL Agent
A B C D E F LT1 G H I MLP TLRA(req_id) ST2 SUPL TRIGGERED START(session-id, lid, SET capabilities, rep_capabilities, ver) PREQ(session-id2, SET capabilities, triggerparams) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, trigger_params, rep_mode)
H-SLC
H-SPC
Target SET
MLP TLRR(ms-id, client-id, qop)

SUPL INIT(session-id, trigger_type=periodic, posmethod, SLP mode)

UT1
J K L M
PINIT(session-id2, lid) PLREQ(session-id2, lid)
SUPL POS INIT(session-id, lid, SET capabilities)
UT2
PLRES(session-id2, posresult) PT2
O P Q MLP TLREP(req_id, posresult)
PRPT(session-id2, position, #fix) SUPL REPORT(session-id, position)
UT3
SET obtains and stores position(s) or enhanced cell/sector measurements autonomously
S T U V LT2 MLP TLREP(req_id, posresult)
PLRES(session-id2, posresult)
Figure 25: Network Initiated Periodic Trigger Service Non-Roaming Successful Case Proxy Mode (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 90 (295)
SUPL Agent
W X Y Z
H-SLC
H-SPC
Target SET
PINIT(session-id2, lid) PLREQ(session-id2, lid)
SUPL POS INIT(session-id, lid, SET Capabilities)
UT2
AA
BB CC DD EE FF GG HH II MLP TLREP(req_id, posresult) LT2
PRPT(session-id2, position, #fix) SUPL REPORT(session-id, position) SUPL REPORT(session-id, position) PLREQ(session-id2, lid) PLRES(session-id2, posresult)
UT3
UT8 PEND(session-id2) SUPL END(session-id)
Figure 26: Network Initiated Periodic Trigger Service Non-Roaming Successful Case Proxy Mode (Part II) NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP TLRR message to the H-SLP, with which SUPL Agent is associated. The H-SLP shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLP shall apply subscriber privacy against the clientid. The TKRR message may indicate that batch reporting or quasi-real time reporting is to be used instead if real time reporting. In the case of batch reporting, the TLRR indicates the conditions for sending batch reports to the HSLP and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates (e.g. QoP, time window). B. The H-SLP verifies that the target SET is currently not SUPL Roaming. The H-SLP MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLP initiates the periodic trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case periodic), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that notification or verification to the target subscriber is needed, the H-SLP SHALL also include the Notification element in the SUPL INIT message. Before the SUPL INIT message is sent, the H-SLP also computes and stores a hash of the message.
OMA-TS-ILP-V2_0_1-20121205-A
Page 91 (295)
D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLP using SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start a periodic triggered session with the H-SLP. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid) and reporting capabilities (rep_capabilities). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The rep_capabilities parameter indicates whether the SET is capable of batch reporting, real time reporting and/or quasi-real time reporting. The H-SLC SHALL check that the hash of SUPL INIT matches the one it has computed for this particular session. F. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved.
G. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. H. Consistent with the SET capabilities received in the SUPL TRIGGERED START message the H-SLC selects the intended positioning method to be used for the periodic triggered session. If the H-SPC included a list of supported posmethods in step G, the chosen posmethod SHALL be on this list. The H-SLC responds with a SUPL TRIGGERED RESPONSE message including session-id, posmethod and periodic trigger parameters. Consistent with the rep_capabilities of the SET, the H-SLP also indicates the reporting mode (rep_mode parameter) to be used by the SET: real time reporting, quasi-real time reporting or batch reporting. In the case of batch reporting, the SUPL TRIGGERED RESPONSE message indicates the conditions for sending batch reports to the H-SLP and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates and/or (if allowed) particular stored enhanced cell/sector measurements. In the case of quasi-real time reporting, the SUPL TRIGGERED RESPONSE message indicates whether the SET is allowed to send enhanced cell/sector measurements in lieu of or in addition to position estimates. If enhanced cell/sector positioning was selected for batch or quasi-real time reporting, the SUPL TRIGGERED RESPONSE message indicates if the SET is permitted to send stored enhanced cell/sector measurements. In this case, if batch reporting was selected, the SET MAY skip steps J to N. The H-SLP informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the periodic triggered session. The SET and the H-SLP MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR. J. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id and the Location ID (lid) and the SET capabilities parameter. The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets the required QoP, the H-SLP MAY directly proceed to step P and not engage in a SUPL POS session. I.
OMA-TS-ILP-V2_0_1-20121205-A
Page 92 (295)
K. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id and SET capabilities. The HSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step G, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities, which was approved by the H-SLC in step F. If a coarse position calculated based on information received in the PINIT message is available that meets the required QoP, the H-SPC MAY directly proceed to step O and not engage in a SUPL POS session. L. If the H-SPC cannot translate the lid received in step K into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the H-SPC can perform the translation from lid into coarse position itself. M. This step is conditional and only occurs if step L was performed. The H-SLC calculates a coarse position based on lid and reports the result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the H-SPC MAY directly proceed to step O and not engage in a SUPL POS session. N. The SET and the H-SLP exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SETAssisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). O. Once the position calculation is complete the H-SPC sends a PRPT message to the H-SLC. PRPT contains the session-id2, the position result if calculated in H-SPC and the number of the fix. P. Once the position calculation is complete the H-SLP sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the H-SLP. If the reporting mode is batch reporting, the SET stores all calculated position estimates. In SET Assisted mode the position is calculated by the H-SLP and therefore needs to be included in the message for batch reporting mode. If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not require an assistance data update from the H-SLP) steps J to P are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLP using a SUPL REPORT message containing the session-id and the position estimate. Q. This step is optional: Once the position calculation is complete and if real time or quasi-real time reporting is used, the H-SLP sends a MLP TLREP message to the SUPL Agent. The MLP TLREP message includes the req_id and the position result. If the reporting mode is set to batch reporting, this message is not used. R. This step is optional: If the SET cannot communicate with the H-SLP (e.g. no radio coverage available) and quasireal time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the H-SLP, enhanced cell/sector measurements. In the case of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the H-SLP. S. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLC. The SUPL REPORT message contains the session-id and the position result(s) including date and time information for each position result and optionally the position method used. In the case of batch reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT
OMA-TS-ILP-V2_0_1-20121205-A
Page 93 (295)
message may be chosen according to criteria received in step H. If no criteria are received in step H, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. T. This step is optional: if the SUPL REPORT message in step S contained enhanced cell/sector measurements and the H-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the H-SLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step S. U. This step is conditional and only used if step T occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results. V. The H-SLP forwards the reported and/or calculated position estimate(s) to the SUPL Agent in an MLP TLREP message. Steps J to V are repeated as applicable. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps W to CC may be performed (a repeat of steps J to P). Alternatively and if applicable step R is repeated. DD. This step is optional. When real-time reporting is used, it is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due. When batch or quasi real-time reporting is used, step DD is executed if and as soon as the following conditions apply: i. The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLC. ii. The SET is able to establish communication with the H-SLP. iii. In the case of batch reporting, the conditions for sending have arisen or the SET has obtained the last fix according to the number of fixes (in which case an incomplete batch of positions is sent). The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLC. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step H. If no criteria are received in step H, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported. EE. This step is optional: if the SUPL REPORT message in step DD contained enhanced cell/sector measurements and the H-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the HSLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step DD. FF. This step is conditional and only used if step EE occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results. GG. The H-SLP forwards the reported and/or calculated historical position estimate(s) to the SUPL Agent in an MLP TLREP message. As an option (e.g. if the SUPL Agent is not available), the H-SLP could retain the historic position fixes for later retrieval by the SUPL Agent. HH. After the last position result has been reported to the SUPL Agent in step GG or following some timeout on not receiving stored position estimates in step DD, the H-SLC informs the H-SPC about the end of the periodic triggered session by sending a PEND message. PEND contains session-id2. II. The H-SLC ends the periodic triggered session by sending a SUPL END message to the SET.
6.1.2
SUPL Roaming where the V-SLP is involved in the position calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 94 (295)
SUPL Agent
A
V-SLC
V-SPC
H-SLP
Target SET
C D E F G LT1 H I J K MLP TLRA(req_id) RLP SSRLIR(SUPL TRIGGERED START) PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) RLP SSRLIA(SUPL TRIGGERED RESPONSE) ST3 ST2

SUPL TRIGGERED START(session-id, lid, SET capabilities, rep_capabilities, ver)
UT1
SUPL TRIGGERED RESPONSE(session-id, posmethod, trigger_params, rep_mode)
L M N O P
RLP SSRP(SUPL POS INIT) PINIT(session-id2, lid, SET capabilities) PLREQ(session-id2, lid) PLRES(session-id2, posresult) PT2
UT2
PMESS(session-id2, RRLP/RRC/TIA-801/LPP) RLP SSRP(SUPL POS)
SUPL POS SUPL POS
RLP SSRP(SUPL POS) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)
R S T U
PRPT(session-id2, position, #fix) RLP SSRP(SUPL REPORT) SUPL REPORT(session-id, position) MLP TLREP(req_id, posresult)
UT3
Figure 27: Network Initiated Periodic Trigger Service Roaming Successful Case Proxy with V-SLP positioning (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 95 (295)
SUPL Agent
W X Y Z AA BB
V-SLC
V-SPC
H-SLP
Target SET
RLP SSRP(SUPL REPORT) PLREQ(session-id2, lid)
LT2
PLRES(session-id2, posresult) RLP SSRP(SUPL REPORT) MLP TLREP(req_id, posresult)
CC DD EE FF GG
UT2
SUPL POS SUPL POS
HH
II JJ KK LL
PRPT(session-id2, position, #fix) RLP SSRP(SUPL REPORT) SUPL REPORT(session-id, position) SUPL REPORT(session-id, position) RLP SSRP(SUPL REPORT)
UT3
MM NN OO PP QQ RR SS TT RLP SSRP(SUPL END) PEND(session-id2) PLREQ(session-id2, lid) LT2 PLRES(session-id2, posresult) RLP SSRP(SUPL REPORT) MLP TLREP(req_id, posresult) SUPL END(session-id) UT8
Figure 28: Network Initiated Periodic Trigger Service Roaming Successful Case Proxy with V-SLP positioning (Part II) NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP TLRR message to the H-SLP, with which SUPL Agent is associated. The H-SLP shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLP shall apply subscriber privacy against the clientid. The TLRR message may indicate that batch reporting or quasi-real time reporting is to be used instead of real time reporting.In the case of batch reporting, the TLRR indicates the conditions for sending batch reports to the HSLP and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates (e.g. QoP, time window).
OMA-TS-ILP-V2_0_1-20121205-A
Page 96 (295)
B. The H-SLP verifies that the target SET is currently SUPL Roaming. The H-SLP MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLP initiates the periodic trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case periodic), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that notification or verification to the target subscriber is needed, the H-SLP SHALL also include the Notification element in the SUPL INIT message. Before the SUPL INIT message is sent, the H-SLP also computes and stores a hash of the message. D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLP using SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start a periodic triggered session with the H-SLP. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver), and Location ID (lid) and reporting capabilities (rep_capabilities). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The rep_capabilities parameter indicates whether the SET is capable of batch reporting, real time reporting and/or quasi-real time reporting. F. Based on the received lid or other mechanisms, the H-SLP determines the V-SLP and sends an RLP SSRLIR including the SUPL TRIGGERED START message to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure.
G. The V-SLC requests service from the V-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY optionally contain the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. H. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. I. Consistent with the SET capabilities received in step F, the V-SLC determines a posmethod to be used for the periodic triggered session. If the V-SPC included a list of supported posmethods in step H, the chosen posmethod SHALL be on this list. The V-SLC indicates its readiness for a periodic triggered session by sending a SUPL TRIGGERED RESPONSE message back to the H-SLP in a RLP SSRLIA message. The H-SLP forwards the received SUPL TRIGGERED RESPONSE message to the SET including session-id, posmethod and periodic trigger parameters. Consistent with the rep_capabilities of the SET, the H-SLP also indicates the reporting mode (rep_mode parameter) to be used by the SET: real time reporting, quasi-real time reporting or batch reporting. In the case of batch reporting, the SUPL TRIGGERED RESPONSE message indicates the conditions for sending batch reports to the H-SLP and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates and/or (if allowed) particular stored enhanced cell/sector measurements. In the case of quasi-real time reporting, the SUPL TRIGGERED RESPONSE message indicates whether the SET is allowed to send enhanced cell/sector measurements in lieu of or in addition to position estimates.
J.
OMA-TS-ILP-V2_0_1-20121205-A
Page 97 (295)
If enhanced cell/sector positioning was selected for batch or quasi-real time reporting, the SUPL TRIGGERED RESPONSE message indicates if the SET is permitted to send stored enhanced cell/sector measurements. In this case, if batch reporting was selected, the SET MAY skip steps L to Q. K. The H-SLP informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the periodic triggered session. The SET and the H-SLP MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR. L. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the H-SLP to start a positioning session with the V-SLP. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If the SUPL POS INIT message contains a position that meets the required QoP, the H-SLP MAY directly proceed to step T. M. The H-SLP forwards the SUPL POS INIT message to the V-SLC using a RLP SSRP message. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets the required QoP, the V-SLC MAY directly proceed to step S and not engage in a SUPL POS session. N. The V-SLC sends a PINIT message to the V-SPC including session-id2, location id and SET capabilities. The VSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the V-SPC in step H, or a different posmethod of the V-SLCs choosing, as long as it is one supported by the V -SPC. Based on the PINIT message including the SET capabilities, the V-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the V-SLC, the V-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the V-SPC shall choose any posmethod in line with the SET capabilities, which was approved by the V-SLC in step G. If a coarse position calculated based on information received in the PINIT message is available that meets the required QoP, the V-SPC MAY directly proceed to step R and not engage in a SUPL POS session. O. If the V-SPC cannot translate the lid received in step N into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into coarse position itself. P. This step is conditional and only occurs if step O was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the V-SPC MAY directly proceed to step R and not engage in a SUPL POS session. Q. The SET and the V-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SPC and the V-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SLC and the H-SLC using SUPL POS over RLP tunnel messages. The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages. The flow sequence PMESS RLP SSRP (SUPL POS) SUPL POS SUPL POS RLP SSRP(SUPL POS) PMESS is conceptually shown in dotted lines. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). R. Once the position calculation is complete, the V-SPC sends a PRPT message to the V-SLC. PRPT contains the session-id2, the position result if calculated in V-SPC and the number of the fix. S. Once the position calculation is complete, the V-SLC sends a SUPL REPORT message including the position to the H-SLP in an RLP tunnel using an SSRP message.
OMA-TS-ILP-V2_0_1-20121205-A
Page 98 (295)
T. Once the position calculation is complete the H-SLP sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the H-SLP. If the reporting mode is batch reporting, the SET stores all calculated position estimates. In SET Assisted mode the position is calculated by the V-SLP and therefore needs to be included in the message for batch reporting mode. If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not require an assistance data update from the H-SLP) steps L to T are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLP using a SUPL REPORT message containing the session-id and the position estimate. U. This step is optional: once the position calculation is complete and if real time or quasi-real time reporting is used, the H-SLP forwards the received position estimate from the V-SLC in an MLP TLREP message to the SUPL Agent. The MLP TLREP message includes the req_id and the position result. If the reporting mode is set to batch reporting, this message is not used. V. This step is optional: if the SET cannot communicate with the H-SLP (e.g. no radio coverage available) quasi-real time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the HSLP, enhanced cell/sector measurements. In the case of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the H-SLP. W. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLP. The SUPL REPORT message contains the session-id and the position result(s) including data and time information for each position result and optionally the position method used. In the case of batch reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step J. If no criteria are received in step J, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. X. This step is optional: if in step W the SET sent enhanced cell/sector measurements, the H-SLP needs to engage the help of the V-SLP to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLP sends the received enhanced cell/sector measurements in a SUPL REPORT message to the V-SLC using an SSRP message over RLP tunnel. Y. This step is optional: if the SUPL REPORT message in step X contained enhanced cell/sector measurements and the V-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the V-SLC sends a PLREQ message to the V-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step X. Z. This step is conditional and only used if step Y occurred: the V-SPC returns the calculated position estimates to the V-SLC in a PLRES message. PLRES contains session-id2 and the position results. AA. This step is optional: if in step X the V-SLC received enhanced cell/sector measurements, the results of the translation into position estimate need to be returned to the H-SLP. To this end a SUPL REPORT message is sent to the H-SLP. The SUPL REPORT message is carried within an SSRP message over RLP tunnel. BB. The H-SLP forwards the reported and/or calculated position estimate(s) to the SUPL Agent in an MLP TLREP message. Steps L to BB are repeated as applicable. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps CC to KK may be performed (a repeat of steps L to T). Alternatively and if applicable step V is repeated. LL. This step is optional. When real-time reporting is used, it is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due. When batch or quasi real-time reporting is used, step LL is executed if and as soon as the following conditions apply:
OMA-TS-ILP-V2_0_1-20121205-A
Page 99 (295)
i. ii.
The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLP. The SET is able to establish communication with the H-SLP.
iii. In the case of batch reporting, the conditions for sending have arisen or the SET has obtained the last fix according to the number of fixes (in which case an incomplete batch of positions is sent). The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLP. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step J. If no criteria are received in step J, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported. MM. This step is optional: if in step LL the SET sent enhanced cell/sector measurements, the H-SLP needs to engage the help of the V-SLP to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLP sends the received enhanced cell/sector measurements in a SUPL REPORT message to the VSLC using an SSRP message over RLP tunnel. NN. This step is optional: if the SUPL REPORT message in step MM contained enhanced cell/sector measurements and the V-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the VSLC sends a PLREQ message to the V-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step MM. OO. This step is conditional and only used if step NN occurred: the V-SPC returns the calculated position estimates to the V-SLC in a PLRES message. PLRES contains session-id2 and the position results. PP. This step is optional: if in step MM the V-SLC received enhanced cell/sector measurements, the results of the translation into position estimate need to be returned to the H-SLP. To this end a SUPL REPORT message is sent to the H-SLP. The SUPL REPORT message is carried within an SSRP message over RLP tunnel. QQ. The H-SLP forwards the reported and/or calculated historical position estimate(s) to the SUPL Agent in an MLP TLREP message. As an option (e.g. if the SUPL Agent is not available), the H-SLP could retain the historic position fixes for later retrieval by the SUPL Agent. RR. After the last position result has been reported to the SUPL Agent in step QQ, or following some timeout on not receiving stored position estimates in step LL, the H-SLP ends the periodic triggered session by sending a SUPL END message to the SET. SS. The H-SLP informs the V-SLC about the end of the periodic triggered session by sending a SUPL END message using an RLP SSRP tunnel message. TT. The V-SLC ends the periodic triggered session with the V-SPC by sending a PEND message. PEND contains the session-id2.
6.1.3
SUPL Roaming where the H-SLP is involved in the position calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 100 (295)
SUPL Agent
A B C D E
V-SLP
H-SLC
H-SPC
Target SET

ST2
SUPL TRIGGERED START(session-id, lid, SET capabilities, rep_capabilities, ver) UT1 PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, trigger_params, rep_mode)
F G H I MLP TLRA(req_id)
LT1
J K L M
RLP SRLIR(msid, lid) RLP SRLIA(ms-id, posresult)
ST4 PINIT(session-id2, lid, SET capabilities)

UT2
O P Q MLP TLREP(req_id, posresult)
UT3
Figure 29: Network Initiated Periodic Trigger Service Roaming Successful Case Proxy with H-SLP positioning (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 101 (295)
SUPL Agent
S T U V
V-SLC
RLP SRLIR(msid, lid)
H-SLC
H-SPC
Target SET
RLP SRLIA(ms-id, posresult) MLP TLREP(req_id, posresult)
ST4
W X Y Z

PMESS(session-id2, RRLP/RRC/TIA-801/LPP) SUPL POS(session-id, RRLP/RRC/TIA-801/LPP)
UT2
AA
SUPL POS(session-id, RRLP/RRC/TIA-801/LPP) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)
BB CC DD EE FF GG HH II JJ RLP SSRP(SUPL END) RLP SRLIR(msid, lid) RLP SRLIA(ms-id, posresult) MLP TLREP(req_id, posresult)
PRPT(session-id2, position, #fix) SUPL REPORT(session-id, position) SUPL REPORT(session-id, position)
UT3
ST4 UT8
PEND(session-id2)
Figure 30: Network Initiated Periodic Trigger Service Roaming Successful Case Proxy with H-SLP positioning (Part II) NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP TLRR message to the H-SLP, with which SUPL Agent is associated. The H-SLP shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLP shall apply subscriber privacy against the clientid. The TLRR message may indicate that batch reporting or quasi-real time reporting is to be used instead of real time reporting.In the case of batch reporting, the TLRR indicates the conditions for sending batch reports to the HSLP and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates (e.g. QoP, time window). B. The H-SLP verifies that the target SET is currently SUPL Roaming. The H-SLP MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope.
OMA-TS-ILP-V2_0_1-20121205-A
Page 102 (295)
C. The H-SLP initiates the periodic trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case periodic), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that notification or verification to the target subscriber is needed, the H-SLP SHALL also include the Notification element in the SUPL INIT message. Before the SUPL INIT message is sent, the H-SLP also computes and stores a hash of the message. D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLP using SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start a periodic triggered session with the H-SLP. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver), and Location ID (lid) and reporting capabilities (rep_capabilities). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The rep_capabilities parameter indicates whether the SET is capable of batch reporting, real-time reporting and/or quasi-real time reporting. F. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved.
G. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. H. Consistent with the SET capabilities received in step E. the H-SLC determines a posmethod to be used for the periodic triggered session. If the H-SPC included a list of supported posmethods in step G, the chosen posmethod SHALL be on this list. The H-SLC indicates its readiness for a periodic triggered session by sending a SUPL TRIGGERED RESPONSE message back to the SET. The SUPL TRIGGERED RESPONSE message to the SET includes at a minimum the session-id, posmethod and periodic trigger parameters. Consistent with the rep_capabilities of the SET, the H-SLC also indicates the reporting mode (rep_mode parameter) to be used by the SET: real time reporting, quasi-real time reporting or batch reporting. In the case of batch reporting, the SUPL TRIGGERED RESPONSE message indicates the conditions for sending batch reports to the H-SLC and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates and/or (if allowed) particular stored enhanced cell/sector measurements. In the case of quasi-real time reporting, the SUPL TRIGGERED RESPONSE message indicates whether the SET is allowed to send enhanced cell/sector measurements in lieu of or in addition to position estimates. If enhanced cell/sector positioning was selected for batch or quasi-real time reporting, the SUPL TRIGGERED RESPONSE message indicates if the SET is permitted to send stored enhanced cell/sector measurements. In this case, if batch reporting was selected, the SET MAY skip steps J to N. The H-SLC informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the periodic triggered session. The SET and the H-SLP MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR. J. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the H-SLC to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. I.
OMA-TS-ILP-V2_0_1-20121205-A
Page 103 (295)
If the SUPL POS INIT message contains a position that meets the required QoP, the H-SLC MAY directly proceed to step P and not engage in a SUPL POS session. K. To obtain a coarse position based on lid received in step J, the H-SLC sends an RLP SRLIR message to the V-SLP. L. The V-SLP translates the received lid into a position estimate and returns the result to the H-SLC in an RLP SRLIA message. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets the required QoP, the H-SLC MAY directly proceed to step P and not engage in a SUPL POS session. M. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id, SET capabilities and position estimate (i.e. coarse position received from the V-SLC in the previous step). The H-SLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step G, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities, which was approved by the H-SLC in step F. N. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). O. Once the position calculation is complete, the H-SPC sends a PRPT message to the H-SLC. PRPT contains the session-id2, the position result if calculated in H-SPC and the number of the fix. P. Once the position calculation is complete the H-SLP sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the H-SLP. If the reporting mode is batch reporting, the SET stores all calculated position estimates. In SET Assisted mode the position is calculated by the H-SLP and therefore needs to be included in the message for batch reporting mode. If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not require an assistance data update from the H-SLP) steps J to P are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLP using a SUPL REPORT message containing the session-id and the position estimate. Q. This step is optional: once the position calculation is complete and if real time or quasi-real time reporting is used the H-SLP sends the calculated position estimate to the SUPL Agent in an MLP TLREP message to the SUPL Agent. The MLP TLREP message includes the req_id and the position result. If the reporting mode is set to batch reporting, this message is not used. R. This step is optional: if the SET cannot communicate with the H-SLP (e.g. no radio coverage available) and quasireal time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the H-SLP, enhanced cell/sector measurements. In the case of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the H-SLP. S. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLC. The SUPL REPORT message contains the session-id and the position result(s) including
OMA-TS-ILP-V2_0_1-20121205-A
Page 104 (295)
data and time information for each position result and optionally the position method used. In the case of batch reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step J. If no criteria are received in step J, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. T. This step is optional: if in step S the SET sent enhanced cell/sector measurements, the H-SLC needs to engage the help of the V-SLP to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLC sends an RLP SRLIR message to the V-SLP. U. This step is optional and only takes place if step T has occurred: The V-SLP translates the received enhanced cell/sector measurements into position estimates and returns the results to the H-SLC in an RLP SRLIA message. V. The H-SLC forwards the reported and/or calculated position estimate(s) to the SUPL Agent in an MLP TLREP message. Steps J to V are repeated as applicable. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps W to CC may be performed (a repeat of steps J to P). Alternatively and if applicable step R is repeated. DD. This step is optional. When real-time reporting is used, it is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due. When batch or quasi real-time reporting is used, step DD is executed if and as soon as the following conditions apply: i. ii. iii. The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLC. The SET is able to establish communication with the H-SLP. In the case of batch reporting, the conditions for sending have arisen or the SET has obtained the last fix according to the number of fixes (in which case an incomplete batch of positions is sent).
The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLC. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step J. If no criteria are received in step J, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported. EE. This step is optional: if in step DD the SET sent enhanced cell/sector measurements, the H-SLC needs to engage the help of the V-SLP to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLC sends an RLP SRLIR message to the V-SLP. FF. This step is optional and only takes place if step EE has occurred: after receiving the enhanced cell/sector measurements the V-SLP translates the received enhanced cell/sector measurements into position estimates and returns the results to the H-SLC in an RLP SRLIA message. GG. The H-SLC forwards the reported and/or calculated historical position estimate(s) to the SUPL Agent in an MLP TLREP message. As an option (e.g. if the SUPL Agent is not available), the H-SLC could retain the historic position fixes for later retrieval by the SUPL Agent. HH. After the last position result has been reported to the SUPL Agent in step GG, or following some timeout on not receiving stored position estimates in step DD, the H-SLC ends the periodic triggered session by sending a SUPL END message to the SET. II. The H-SLC informs the V-SLP about the end of the periodic triggered session by sending a SUPL END message using an SSRP message over RLP tunnel. JJ. The H-SLC informs the H-SPC about the end of the periodic triggered session in a PEND message. PEND contains session-id2.
OMA-TS-ILP-V2_0_1-20121205-A
Page 105 (295)
6.2
Network Initiated Non-Proxy mode
This section describes the Network Initiated Non-Proxy mode scenarios. It is assumed that the trigger resides in the SET. The concept of the R-SLC applies as with Immediate Service but for the sake of simplicity has been omitted in this section.
6.2.1

A B

C D E F LT1 G H I MLP TLRA(req_id) ST2

SUPL TRIGGERED START(session-id, lid, SET capabilities, rep_capabilities, ver) PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, H-SPC address, trigger_params, rep_mode, SPC_SET_Key, SPC-TID) UT1
J K L
UT2
SUPL POS(session id, RRLP/RRC/TIA-801/LPP) SUPL REPORT(session-id, position) PRPT(session-id2, position, #fix) MLP TLREP(req_id, posresult) UT3
N O P
R S T U
PLREQ(session-id2, lid) LT2 MLP TLREP(req_id, posresult)
Figure 31: Network Initiated Periodic Trigger Service Non-Roaming Successful Case Non-Proxy Mode (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 106 (295)
SUPL Agent
V W X
H-SLC
H-SPC
Target SET
UT2
SUPL POS(session id, RRLP/RRC/TIA-801/LPP) SUPL REPORT(session-id, position) PRPT(session-id2, position, #fix) SUPL REPORT(session-id, position) PLREQ(session-id2, lid) LT2 MLP TLREP(req_id, posresult) PEND(session-id2) SUPL END(session-id) PLRES(session-id2, posresult) UT8 UT3
Z AA BB CC DD EE FF GG
Figure 32: Network Initiated Periodic Trigger Service Non-Roaming Successful Case Non-Proxy Mode (Part II) NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP TLRR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the clientid. The TLRR message may indicate that batch reporting or quasi-real time reporting is to be used instead of real time reporting.In the case of batch reporting, the TLRR indicates the conditions for sending batch reports to the HSLC and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates (e.g. QoP, time window). B. The H-SLC verifies that the target SET is currently not SUPL Roaming. The H-SLC MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLC initiates the periodic trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case periodic), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLP SHALL set notification mode to notification based on current location and SHALL NOT include the notification element in the SUPL INIT message; otherwise, the HSLP SHALL set the notification mode indicator to normal notification and if notification or verification to the target subscriber is needed, the H-SLP SHALL also include the notification element in the SUPL INIT message.Before the SUPL INIT message is sent, the H-SLC also computes and stores a hash of the message.
OMA-TS-ILP-V2_0_1-20121205-A
Page 107 (295)
D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, non-proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using the H-SLC address which has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start a periodic triggered session with the H-SLP. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver), and Location ID (lid) and reporting capabilities (rep_capabilities). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The rep_capabilities parameter indicates whether the SET is capable of batch reporting, real-time reporting and/or quasi-real time reporting. F. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The H-SLC generates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication and forwards both to the H-SPC in the PREQ message. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved.
G. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. H. Consistent with the SET capabilities received in the SUPL TRIGGERED START message the H-SLC selects a positioning method to be used for the periodic triggered session. This posmethod may either be the posmethod recommended by the H-SPC in step G, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H-SPC. The H-SLC responds with a SUPL TRIGGERED RESPONSE message including sessionid, posmethod, H-SPC address, periodic trigger parameters, SPC_SET_Key and SPC-TID. Consistent with the rep_capabilities of the SET, the H-SLC also indicates the reporting mode (rep_mode parameter) to be used by the SET: real time reporting, quasi-real time reporting or batch reporting. In the case of batch reporting, the SUPL TRIGGERED RESPONSE message indicates the conditions for sending batch reports to the H-SLC and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates and/or (if allowed) particular stored enhanced cell/sector measurements. In the case of quasi-real time reporting, the SUPL TRIGGERED RESONSE message indicates whether the SET is allowed to send enhanced cell/sector measurements in lieu of or in addition to position estimates. If enhanced cell/sector positioning was selected for batch or quasi-real time reporting, the SUPL TRIGGERED RESPONSE message indicates if the SET is permitted to send stored enhanced cell/sector measurements. In this case, if batch reporting was selected, the SET MAY skip steps J to N. The H-SLC informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the periodic triggered session. The SET and the H-SLC MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR. J. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SPC. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets the required QoP, the H-SPC MAY directly proceed to step N and not engage in a SUPL POS session. I.
OMA-TS-ILP-V2_0_1-20121205-A
Page 108 (295)
K. If the H-SPC cannot translate the lid received in step J into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the HSPC can perform the translation from lid into coarse position itself. L. This step is conditional and only occurs if step K was performed. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the H-SPC MAY directly proceed to step N and not engage in a SUPL POS session. M. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step F, the H-SPC SHALL only choose an approved method. The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). N. Once the position calculation is complete the H-SPC sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the H-SPC. If the reporting mode is batch reporting, the SET stores all calculated position estimates. In SET Assisted mode the position is calculated by the H-SPC and therefore needs to be included in the message for batch reporting mode. O. This step is optional: Once the position calculation is complete and if real time or quasi-real time reporting is used the H-SPC sends the position estimate in a PRPT message to the H-SLC. PRPT contains the session-id2, the position result and the number of the fix. This message is optional and only used if the position was calculated by the H-SPC i.e. in SET Assisted mode. If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not require an assistance data update from the H-SLP) steps J to O are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLC using a SUPL REPORT message containing the session-id and the position estimate. P. This step is optional: once the position calculation is complete and if real time or quasi-real time reporting is used, the H-SLC sends a MLP TLREP message to the SUPL Agent. The MLP TLREP message includes the req_id and the position result. If the reporting mode is set to batch reporting, this message is not used. Q. This step is optional: If the SET cannot communicate with the H-SLP (e.g. no radio coverage available) and quasireal time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the H-SLP, enhanced cell/sector measurements. In the case of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the H-SLP. R. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLC. The SUPL REPORT message contains the session-id and the position result(s) including date and time information for each position result and optionally the position method used. In the case of batch reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step H. If no criteria are received in step H, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. S. This step is optional: if the SUPL REPORT message in step R contained enhanced cell/sector measurements and the H-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the H-SLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step R.
T. This step is conditional and only used if step S occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results.
OMA-TS-ILP-V2_0_1-20121205-A
Page 109 (295)
U. The H-SLP forwards the reported and/or calculated position estimate(s) to the SUPL Agent in an MLP TLREP message. Steps J to U are repeated as applicable. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps V to AA may be performed (a repeat of steps J to O). Alternatively and if applicable step Q is repeated. BB. This step is optional. When real-time reporting is used, it is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due. When batch or quasi real-time reporting is used, step BB is executed if and as soon as the following conditions apply: i. ii. iii. The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLC. The SET is able to establish communication with the H-SLP In the case of batch reporting, the conditions for sending have arisen or the SET has obtained the last fix according to the number of fixes (in which case an incomplete batch of positions is sent ).
The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLC. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step H. If no criteria are received in step H, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported. CC. This step is optional: if the SUPL REPORT message in step BB contained enhanced cell/sector measurements and the H-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the HSLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step BB. DD. This step is conditional and only used if step CC occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results. EE. The H-SLC forwards the reported and/or calculated historical position estimate(s) to the SUPL Agent in an MLP TLREP message. As an option (e.g. if the SUPL Agent is not available), the H-SLC could retain the historic position fixes for later retrieval by the SUPL Agent. FF. After the last position result has been reported to the SUPL Agent in step EE the H-SLC informs the H-SPC about the end of the periodic triggered session by sending a PEND message. PEND contains the session-id2. GG. The H-SLC ends the periodic triggered session by sending a SUPL END message to the SET. Please note that if the last position was calculated in step Y and step BB was not performed, the SUPL END message is sent from the HSPC to the SET (as opposed to from the H-SLC to the SET).
6.2.2
SUPL Roaming where the V-SPC is involved in the position calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 110 (295)
SUPL Agent
A B C D E F G H I J K
H-SLC
V-SLC
V-SPC
Target SET


ST2
SUPL TRIGGERED START(session-id, lid, SET capabilities, rep_capabilities, ver) RLP SSRLIR(SUPL TRIGGERED START, SPC_SET_Key, SPC-TID) UT1 ST3 LT1 PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2) RLP SSRLIA(SUPL TRIGGERED RESPONSE) SUPL TRIGGERED RESPONSE(session-id, posmethod, V-SPC address, trigger_params, rep_mode, SPC_SET_Key, SPC-TID)
MLP TLRA(req_id)
L M N O P Q R S
UT2
SUPL POS SUPL REPORT(session-id, position) PRPT(session-id2, position, #fix) RLP SSRP(SUPL REPORT) MLP TLREP(req_id, posresult) UT3
U V W X Y Z
RLP SSRP(SUPL REPORT) PLREQ(session-id2, lid) LT2
RLP SSRP(SUPL REPORT) MLP TLREP(req_id, posresult)
Figure 33: Network Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 111 (295)
SUPL Agent
AA BB CC DD EE FF GG HH II JJ KK LL MM NN OO PP
H-SLC
V-SLC
V-SPC
Target SET
UT2
SUPL POS SUPL REPORT(session-id, position) PRPT(session-id2, position, #fix) RLP SSRP(SUPL REPORT) SUPL REPORT(session-id, position) RLP SSRP(SUPL REPORT) PLREQ(session-id2, lid) LT2 PLRES(session-id2, posresult) UT8 UT3
RLP SSRP(SUPL REPORT) MLP TLREP(req_id, posresult) RLP SSRP(SUPL END) PEND(session-id2) SUPL END(session-id)
Figure 34: Network Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning (Part II) NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP TLRR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the clientid. The TLRR message may indicate that batch reporting or quasi-real time reporting is to be used instead of real time reporting.In the case of batch reporting, the TLRR indicates the conditions for sending batch reports to the HSLP and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates (e.g. QoP, time window). B. The H-SLC verifies that the target SET is currently SUPL Roaming. The H-SLC MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLC initiates the periodic trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case periodic), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLP SHALL set notification mode to notification based on
OMA-TS-ILP-V2_0_1-20121205-A
Page 112 (295)
current location and SHALL NOT include the notification element in the SUPL INIT message; otherwise, the HSLP SHALL set the notification mode indicator to normal notification and if notification or verification to the target subscriber is needed, the H-SLP SHALL also include the notification element in the SUPL INIT message.Before the SUPL INIT message is sent, the H-SLC also computes and stores a hash of the message. D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLC uses proxy or non-proxy mode. In this case, non-proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using the H-SLC address which has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start a periodic triggered session with the H-SLP. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver), Location ID (lid) and reporting capabilities (rep_capabilities). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The rep_capabilities parameter indicates whether the SET is capable of batch reporting, real-time reporting and/or quasi-real time reporting. F. Based on the received lid or other mechanisms, the H-SLC determines the V-SLC and sends an RLP SSRLIR including the SUPL TRIGGERED START message to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. The H-SLC also generates SPC_SET_Key and SPC-TID to be used for VSPC/SET mutual authentication and includes both in the RLP SSRLIR message.
G. The V-SLC requests service from the V-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The V-SLC also forwards SPC_SET_Key and SPC-TID received in step F to the V-SPC in the PREQ message. The PREQ MAY also optionally contain the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. H. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. I. Consistent with the SET capabilities received in step E, the V-SLC determines a posmethod to be used for the periodic triggered session. This posmethod may either be the posmethod recommended by the V-SPC in step H, or a different posmethod of the V-SLCs choosing, as long as it is one supported by the V -SPC. The V-SLC indicates its readiness for a periodic triggered session by sending a SUPL TRIGGERED RESPONSE message back to the HSLC in an RLP SSRLIA message. The H-SLC forwards the received SUPL TRIGGERED RESPONSE message to the SET including session-id, posmethod, V-SPC address, periodic trigger parameters, SPC_SET_Key and SPC-TID. Consistent with the rep_capabilities of the SET, the H-SLC also indicates the reporting mode (rep_mode parameter) to be used by the SET: real time reporting, quasi-real time reporting or batch reporting. In the case of batch reporting, the SUPL TRIGGERED RESPONSE message indicates the conditions for sending batch reports to the H-SLC and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates and/or (if allowed) particular stored enhanced cell/sector measurements. In the case of quasi-real time reporting, the SUPL TRIGGERED RESONSE message indicates whether the SET is allowed to send enhanced cell/sector measurements in lieu of or in addition to position estimates. If enhanced cell/sector positioning was selected for batch or quasi-real time reporting, the SUPL TRIGGERED RESPONSE message indicates if the SET is permitted to send stored enhanced cell/sector measurements. In this case, if batch reporting was selected, the SET MAY skip steps L to P.
J.
K. The H-SLC informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the periodic triggered session. The SET and the H-SLC MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR.
OMA-TS-ILP-V2_0_1-20121205-A
Page 113 (295)
L. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the V-SPC to start a positioning session with the V-SPC. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets the required QoP, the V-SPC MAY directly proceed to step P and not engage in a SUPL POS session. M. If the V-SPC cannot translate the lid received in step L into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the VSPC can perform the translation from lid into coarse position itself. N. This step is conditional and only occurs if step M was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the V-SPC MAY directly proceed to step P and not engage in a SUPL POS session. O. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the V-SPC SHALL determine the posmethod. If the V-SLC included its approved positioning methods in step G, the V-SPC SHALL only choose an approved method. The SET and the V-SPC exchange several successive positioning procedure messages. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). P. Once the position calculation is complete the V-SPC sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the V-SLP. If the reporting mode is batch reporting, the SET stores all calculated position estimates. In SET Assisted mode the position is calculated by the V-SPC and therefore needs to be included in the message for batch reporting mode. Q. This step is optional: once the position calculation is complete and real time or quasi-real time reporting is used, the V-SPC sends the position estimate in a PRPT message to the V-SLC. PRPT contains the session-id2, the position result and the number of the fix. This message is optional and only used if the position was calculated by the V-SPC i.e. in SET Assisted mode. R. This step is conditional and is only used after step Q occurred. The V-SLC sends the position estimate to the H-SLC in a SUPL REPORT message. The SUPL REPORT message includes at a minimum the session-id and the position estimate. The SUPL REPORT message is carried within an RLP SSRP message. If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not require an assistance data update from the V-SLP) steps L to R are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLC using a SUPL REPORT message containing the session-id and the position estimate. S. This step is optional: if real time or quasi-real time reporting is used, the H-SLC forwards the position estimate received in an MLP TLREP message to the SUPL Agent. The MLP TLREP message includes the req_id and the position result. If the reporting mode is set to batch reporting, this message is not needed.
T. This step is optional: If the SET cannot communicate with the V-SLP (e.g. no radio coverage available) and quasireal time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the H-SLP, enhanced cell/sector measurements. In the case, of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the V-SLP. U. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP/V-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLC. The SUPL REPORT message contains the session-id and the position result(s)
OMA-TS-ILP-V2_0_1-20121205-A
Page 114 (295)
including date and time information for each position result and optionally the position method used. In the case of batch reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step J. If no criteria are received in step J, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. V. This step is optional: if the H-SLC received stored enhanced cell/sector measurements in the SUPL REPORT message in step U, the V-SLP may need to be involved to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLC sends a SUPL REPORT message to the V-SLC using an SSRP message over RLP tunnel. W. This step is optional: if the SUPL REPORT message in step V contained enhanced cell/sector measurements and the V-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the V-SLC sends a PLREQ message to the V-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step V. X. This step is conditional and only used if step W occurred: the V-SPC returns the calculated position estimates to the V-SLC in a PLRES message. PLRES contains session-id2 and the position results. Y. This step is conditional and takes place after step V and optionally steps W and X. A SUPL REPORT message containing position estimates calculated from enhanced cell/sector measurements received in step V is sent from the V-SLC to the H-SLC using an SSRP message over RLP tunnel. Z. The H-SLC forwards the reported and/or calculated position estimate(s) to the SUPL Agent in an MLP TLREP message. Steps L to Z are repeated as applicable. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps AA to GG may be performed (a repeat of steps L to R). Alternatively and if applicable step T is repeated. HH. This step is optional. When real-time reporting is used, it is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due. When batch or quasi real-time reporting is used, step HH is executed if and as soon as the following conditions apply: i. ii. iii. The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLC. The SET is able to establish communication with the H-SLP. In the case of batch reporting, the conditions for sending have arisen or the SET has obtained the last fix according to the number of fixes (in which case an incomplete batch of positions is sent)..
The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLC. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step J. If no criteria are received in step J, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported. II. This step is optional: if the H-SLC received stored enhanced cell/sector measurements in the SUPL REPORT message in step HH, the V-SLP may need to be involved to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLC sends a SUPL REPORT message to the V-SLC using an SSRP message over RLP tunnel. JJ. This step is optional: if the SUPL REPORT message in step HH contained enhanced cell/sector measurements and the V-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the VSLC sends a PLREQ message to the V-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step HH. KK. This step is conditional and only used if step JJ occurred: the V-SPC returns the calculated position estimates to the V-SLC in a PLRES message. PLRES contains session-id2 and the position results.
OMA-TS-ILP-V2_0_1-20121205-A
Page 115 (295)
LL. This step is conditional and takes place after step II and optionally steps JJ and KK. A SUPL REPORT message containing position estimates calculated from enhanced cell/sector measurements received in step II is sent from the V-SLC to the H-SLC using an SSRP message over RLP tunnel. MM. The H-SLC forwards the reported and/or calculated historical position estimate(s) to the SUPL Agent in an MLP TLREP message. As an option (e.g. if the SUPL Agent is not available), the H-SLC could retain the historic position fixes for later retrieval by the SUPL Agent. NN. After the last position result has been reported to the SUPL Agent in step MM, the H-SLC informs the V-SLC about the end of the periodic triggered session through an SUPL END message carried within an SSRP message over RLP tunnel. OO. The V-SLC informs the V-SPC about the end of the periodic triggered session in a PEND the session-id2. eighbo. PEND contains
PP. The H-SLC ends the periodic triggered session with the SET by sending a SUPL END message. The SUPL END message includes at least the session-id. Please note that if the last position was calculated in step DD and step HH was not performed, the SUPL END message is sent from the V-SPC to the SET (as opposed to from the H-SLC to the SET).
6.2.3

SUPL Roaming where the H-SPC is involved in the position calculation.
OMA-TS-ILP-V2_0_1-20121205-A
Page 116 (295)
SUPL Agent
A B C D E F G H I
V-SLC
H-SLC
H-SPC
Target SET
SUPL INIT(session-id, trigger_type=periodic, posmethod, SLP mode) ST2

LT1
SUPL TRIGGERED START(session-id, lid, SET capabilities, rep_capabilities, ver) PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2)
MLP TLRA(req_id)
SUPL TRIGGERED RESPONSE(session-id, posmethod, H-SPC address, trigger_params, rep_mode, SPC_SET_Key, SPC-TID)
J K L M N O P Q R
PLREQ(session-id2, lid) ST4 RLP SRLIA(ms-id, posresult) PLRES(session-id2, posresult) RLP SRLIR(msid, lid)
UT2 PT2
SUPL POS(session id, RRLP/RRC/TIA-801/ LPP)
SUPL REPORT(session-id, position) MLP TLREP(req_id, posresult) PRPT(session-id2, position, #fix)
UT3
T U V W X Y
RLP SRLIR(msid, lid) RLP SRLIA(ms-id, posresult) PLREQ(session-id2, lid) LT2 PLRES(session-id2, posresult)
MLP TLREP(req_id, posresult)
Figure 35: Network Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 117 (295)
SUPL Agent
Z AA BB CC DD EE FF GG HH II JJ KK LL MM NN OO PP
V-SLC
H-SLC
H-SPC
Target SET
UT2
PT2
SUPL REPORT(session-id, position) PRPT(session-id2, position, #fix) SUPL REPORT(session-id, position)
UT3
RLP SRLIA(ms-id, posresult) PLREQ(session-id2, lid) LT2 MLP TLREP(req_id, posresult) RLP SSRP(SUPL END) PEND(session-id2) SUPL END(session-id) PLRES(session-id2, posresult) UT8
Figure 36: Network Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning (Part II) NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP TLRR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the clientid. The TLRR message may indicate that batch reporting or quasi-real time reporting is to be used instead of real time reporting.In the case of batch reporting, the TLRR indicates the conditions for sending batch reports to the HSLP and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates (e.g. QoP, time window). B. The H-SLC verifies that the target SET is currently SUPL Roaming. The H-SLC MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLC may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLC initiates the periodic trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case periodic), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLP SHALL set notification mode to notification based on
OMA-TS-ILP-V2_0_1-20121205-A
Page 118 (295)
current location and SHALL NOT include the notification element in the SUPL INIT message; otherwise, the HSLP SHALL set the notification mode indicator to normal notification and if notification or verification to the target subscriber is needed, the H-SLP SHALL also include the notification element in the SUPL INIT message.Before the SUPL INIT message is sent, the H-SLC also computes and stores a hash of the message. D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, non-proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using the H-SLC address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start a periodic triggered session with the H-SLC. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver), Location ID (lid) and reporting capabilities (rep_capabilities). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The rep_capabilities parameter indicates whether the SET is capable of batch reporting, real-time reporting and/or quasi-real time reporting. F. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The H-SLC generates SPC_SET_Key and SPC-TID for mutual H-SPC/SET authentication and forwards both to the H-SPC in the PREQ message. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved.
G. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. H. Consistent with the SET capabilities received in step E, the H-SLC determines a posmethod to be used for the periodic triggered session. This posmethod may either be the posmethod recommended by the H-SPC in step G, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. The H-SLC indicates its readiness for a periodic triggered session by sending a SUPL TRIGGERED RESPONSE message back to the SET. The SUPL TRIGGERED RESPONSE message to the SET includes at a minimum the session-id, posmethod, HSPC address, periodic trigger parameters, SPC_SET_Key and SPC-TID. Consistent with the rep_capabilities of the SET, the H-SLC also indicates the reporting mode (rep_mode parameter) to be used by the SET: real time reporting, quasi-real time reporting or batch reporting. In the case of batch reporting, the SUPL TRIGGERED RESPONSE message indicates the conditions for sending batch reports to the H-SLC and any criteria, when the conditions for sending arise, for including or excluding particular stored position estimates and/or (if allowed) particular stored enhanced cell/sector measurements. In the case of quasi-real time reporting, the SUPL TRIGGERED RESONSE message indicates whether the SET is allowed to send enhanced cell/sector measurements in lieu of or in addition to position estimates. If enhanced cell/sector positioning was selected for batch or quasi-real time reporting, the SUPL TRIGGERED RESPONSE message indicates if the SET is permitted to send stored enhanced cell/sector measurements. In this case, if batch reporting was selected, the SET MAY skip steps J to P. The H-SLC informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the periodic triggered session. The SET and the H-SLC MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR. J. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the H-SPC to start a positioning session with the H-SPC. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data I.
OMA-TS-ILP-V2_0_1-20121205-A
Page 119 (295)
element in the SUPL POS INIT. If the SUPL POS INIT message contains a position that meets the required QoP, the H-SPC MAY directly proceed to step P. K. To translate the lid received in step J into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. L. To obtain a coarse position the H-SLC sends an RLP SRLIR message to the V-SLP. M. The V-SLP translates the received lid into a position estimate and returns the result to the H-SLC in an RLP SRLIA message. For real-time or quasi-real time reporting, if the returned position meets the required QoP, the H-SLC MAY directly proceed to step R and not engage in a SUPL POS session. For batch reporting, if the returned position meets the required QoP, the H-SLC MAY send the position result through internal communication to the H-SPC (step N) and the H-SPC will forward the position result to the SET using a SUPL REPORT message (step P) without engaging in a SUPL POS session (step O). N. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the sessionid2 and the posresult. If the coarse position meets the required QoP, the H-SPC SHALL directly proceed to step P and not engage in a SUPL POS session. O. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step F, the H-SPC SHALL only choose an approved method. The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). P. Once the position calculation is complete the H-SPC sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the H-SLP. If the reporting mode is batch reporting, the SET stores all calculated position estimates. In SET Assisted mode the position is calculated by the H-SPC and therefore needs to be included in the message for batch reporting mode. Q. This step is optional: once the position calculation is complete and if real time or quasi-real time reporting is used, the H-SPC sends the position estimate in a PRPT message to the H-SLC. PRPT contains the session-id2, the position result and the number of the fix. This message is optional and only used if the position was calculated by the H-SPC i.e. in SET Assisted mode. If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not require an assistance data update from the H-SLP) steps J to Q are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLC using a SUPL REPORT message containing the session-id and the position estimate. R. This step is optional: if real time or quasi-real time reporting is used, the H-SLC forwards the calculated position estimate to the SUPL Agent in an MLP TLREP message. The MLP TLREP message includes the req_id and the position result. If the reporting mode is set to batch reporting, this message is not needed. S. This step is optional: If the SET cannot communicate with the H-SLP (e.g. no radio coverage available) and quasireal time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the H-SLP, enhanced cell/sector measurements. In the case, of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the H-SLP.
T. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLC. The SUPL REPORT message contains the session-id and the position result(s) including date and time information for each position result and optionally the position method used. In the case of batch
OMA-TS-ILP-V2_0_1-20121205-A
Page 120 (295)
reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step H. If no criteria are received in step H, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. U. This step is optional: if the H-SLC received stored enhanced cell/sector measurements in the SUPL REPORT message in step T, the V-SLP may need to be involved to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLC sends an RLP SRLIR message to the V-SLC. V. This step is conditional and takes place only if step U occurred. The V-SLC sends the position result calculated based on the enhanced cell/sector measurements received in step U to the H-SLC. W. This step is optional and only takes place if after the translation into a position estimate in steps U and V the H-SPC is required to calculate the position estimate. In this case the H-SLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step T. X. This step is conditional and only used if step W occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results. Y. The H-SLC forwards the reported and/or calculated position estimate(s) to the SUPL Agent in an MLP TLREP message. Steps J to Y are repeated as applicable. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps Z to FF may be performed (a repeat of steps J to Q). Alternatively and if applicable step S is repeated. HH. This step is optional. When real-time reporting is used, it is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due. When batch or quasi real-time reporting is used, step HH is executed if and as soon as the following conditions apply: i. ii. iii. The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLC. The SET is able to establish communication with the H-SLP. In the case of batch reporting, the conditions for sending have arisen or the SET has obtained the last fix according to the number of fixes (in which case an incomplete batch of positions is sent).
The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLC. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step H. If no criteria are received in step H, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported. II. This step is optional: if the H-SLC received stored enhanced cell/sector measurements in the SUPL REPORT message in step HH, the V-SLP may need to be involved to translate the enhanced cell/sector measurements into actual position estimates To this end the H-SLC sends an RLP SRLIR message to the V-SLC. JJ. This step is conditional and takes place only if step II occurred. The V-SLC sends the position result calculated based on the enhanced cell/sector measurements received in step II to the H-SLC. KK. This step is optional and only takes place if after the translation into a position estimate in steps II and JJ the H-SPC is required to calculate the position estimate. In this case the H-SLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step HH. LL. This step is conditional and only used if step KK occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results. MM. The H-SLC forwards the reported and/or calculated historical position estimate(s) to the SUPL Agent in an MLP TLREP message. As an option (e.g. if the SUPL Agent is not available), the H-SLC could retain the historic position fixes for later retrieval by the SUPL Agent.
OMA-TS-ILP-V2_0_1-20121205-A
Page 121 (295)
NN. When the last position result was reported to the SUPL Agent in step OO, the H-SLC closes the periodic triggered session with the V-SLC by sending a SUPL END message encapsulated in an SSRP message over RLP tunnel. OO. The H-SLC informs the H-SPC about the end of the periodic triggered session by sending a PEND message. PEND contains the session-id2. PP. The H-SLC ends the periodic triggered session with the SET by sending a SUPL END message. The SUPL END message includes at least the session-id. Please note that if the last position was calculated in step EE and step HH was not performed, the SUPL END message is sent from the H-SPC to the SET (as opposed to from the H-SLC to the SET).
6.3
6.3.1 6.3.2
SET does not allow Triggered Position Network cancels the triggered location request
V-SLP H-SLC H-SPC Target SET
This section describes the exception procedures for triggered scenarios.
This error case does not impact the Llp interface.
SUPL Agent
Triggered Location service in progress
B C D E F G
MLP TLRSR(ms-id, client-id, qop) RLP SSRP(SUPL TRIGGERED STOP) SUPL TRIGGERED STOP(session-id) SUPL END(session-id) PEND(session-id2, Status Code) MLP TLRSA(req_id)
ST6
Figure 37: Network Initiated Triggered location, Network cancels the triggered location request NOTE 1: See Appendix C for timer descriptions. A. The triggered location procedure is in progress. B. The SUPL Agent sends a MLP TLRSR message to cancel the ongoing triggered session. NOTE 2: The MLP TLRSR in this flow is only used to illustrate a possible triggered session cancellation initiated by the SUPL Agent. The triggered session could also be cancelled by the H-SLC i.e. without the SUPL Agents involvement.
OMA-TS-ILP-V2_0_1-20121205-A
Page 122 (295)
C. This step is optional. For roaming with V-SLP scenarios where the V-SLP is involved, an RLP SSRP message carrying the SUPL TRIGGERED STOP message is sent by the H-SLC to the V-SLP to notify the V-SLP that the triggered session has been cancelled and that all resource allocated to this session are to be released. D. The H-SLP sends a SUPL TRIGGERED STOP message with the session-id to the target SET to request cancellation of the triggered session. E. The target SET acknowledges that it has cancelled the positioning procedure with the SUPL END message back to the H-SLP. F. The H-SLC cancels the triggered session with the H-SPC by sending a PEND message including the appropriate Status Code.
G. The H-SLC confirms cancellation of the triggered SUPL session by sending a MLP TLRSA message to the SUPL Agent.
6.3.3
SET cancels the triggered location request

V-SLP H-SLC H-SPC Target SET
SUPL Agent
Triggered Location service in progress
B RLP SSRP(SUPL TRIGGERED STOP) C D E F MLP TLRSA(req_id)
SUPL TRIGGERED STOP(session-id)
UT7 SUPL END(session-id) PEND(session-id2, Status Code)
Figure 38: Network Initiated Triggered location, SET cancels the triggered location request NOTE 1: See Appendix C for timer descriptions. A. The triggered location procedure is in progress. B. The SET sends a SUPL TRIGGERED STOP message including the session-id to the H-SLC to request cancellation of the triggered session. C. This step is optional. For roaming with V-SLP scenarios where the V-SLP is involved, an RLP SSRP message carrying the SUPL TRIGGERED STOP message is sent by the H-SLC to the V-SLP to notify the V-SLP that the triggered session has been cancelled and that all resource allocated to this session are to be released. D. The H-SLC sends a SUPL END message to the SET. The SET SHALL release the secure connection and release all resources related to this session. E. The H-SLC cancels the triggered session with the H-SPC by sending a PEND message including the appropriate Status Code.
OMA-TS-ILP-V2_0_1-20121205-A
Page 123 (295)
F.
The H-SLC sends an MLP TLRSA message to the SUPL Agent to inform the SUPL Agent that the triggered session has been cancelled.
6.4
6.4.1

This section describes the SET Initiated Proxy mode scenarios. It is assumed that the trigger resides in the SET.
A B C D E F
Routing Info
SUPL TRIGGERED START(session-id, trigger_type=periodic, lid, SET capabilities, trigger_params) UT1
LT1
PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod)
G H I J
SUPL POS INIT(session-id, lid, SET capabilities) PINIT(session-id2, lid, SET capabilities) PLREQ(session-id2, lid) PLRES(session-id2, posresult) PT2
UT2
L M
PRPT(session-id2, position, #fix)
UT3 SUPL REPORT(session-id, position) position fix #1
N O P Q
UT2
S T U V
PRPT(session-id2, position, #fix)
UT3 SUPL REPORT(session-id, position) SUPL END(session-id) position fix #n
PEND(session-id2)
Figure 39: SET Initiated Periodic Trigger Service Non-Roaming Successful Case Proxy Mode
OMA-TS-ILP-V2_0_1-20121205-A
Page 124 (295)
NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for a periodic triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case periodic), Location ID (lid) and periodic trigger parameters. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently not SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. F. Consistent with the SUPL TRIGGERED START message including the SET capabilities of the SET, the H-SLP MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLP SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC SHALL respond with a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE contains the session-id but no H-SLC address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL TRIGGERED RESPONSE also contains the posmethod. The SET and the H-SLC MAY release the secure connection.
G. When the periodic trigger in the SET indicates that a position fix has to be calculated the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the H-SLC MAY directly proceed to step M and not engage in a SUPL POS session. H. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id and SET capabilities. The HSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step E, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H-SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step D. If a coarse position calculated based on information received in the SUPL POS INIT message is available that meets the required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session.
OMA-TS-ILP-V2_0_1-20121205-A
Page 125 (295)
I.
If the H-SPC cannot translate the lid received in step H into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the H-SPC can perform the translation from lid into coarse position itself. This step is conditional and only occurs if step I was performed. The H-SLC calculates a coarse position based on lid and reports the result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session.
J.
K. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). L. Once the position calculation is complete the H-SPC sends a PRPT message to the H-SLC. PRPT contains the session-id2, the position result if calculated in H-SPC and the number of the fix. M. Once the position calculation is complete the H-SLC sends a SUPL REPORT message to the SET. The SUPL REPORT message includes the position result if the position estimate is calculated in the H-SPC and therefore needs to be sent to the SET. The SET MAY release the secure connection to the H-SLC. NOTE 3: steps G to M are optional and not performed for A-GPS SET Based mode in the case where no GPS assistance data is required from the network. In this case the SET autonomously calculates a position fix based on the currently available GPS assistance data stored in the SET. Steps G to M are repeated if so required for calculating any of the remaining position estimates of the periodic triggered session. The last position estimate which as shown in this case requires the execution of steps G to M, is shown in steps N to T. U. After the last position result has been calculated, the SET ends the periodic triggered session by sending a SUPL END message to the H-SLC. V. The H-SLC ends the periodic triggered session with the H-SPC by sending a PEND message. PEND contains the session-id2. NOTE 4: Note that for A-GPS SET Based mode where the SET calculates the position estimate based on GPS assistance data available in the SET, steps G to M are performed whenever new GPS assistance data is required by the SET.
6.4.2
OMA-TS-ILP-V2_0_1-20121205-A
Page 126 (295)
V-SLC
V-SPC
H-SLP
Target SET
A B C D E F G H RLP SSRLIR(SUPL TRIGGERED START) PREQ(session-id2, lid, SET capabilities, triggerparams) LT1 PRES(session-id2) RLP SSRLIA(SUPL TRIGGERED RESPONSE) ST3
Routing Info
I J K L M
SUPL TRIGGERED RESPONSE(session-id, posmethod)
SUPL POS INIT(session-id, lid, SET capabilities) UT2
PMESS(session-id2, RRLP/RRC/TIA-801/LPP) RLP SSRP(SUPL POS) RLP SSRP(SUPL POS) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)
SUPL POS SUPL POS
O P Q
PRPT(session-id2, position, #fix) RLP SSRP(SUPL REPORT) SUPL REPORT(session-id, position)
UT3 position fix #1
R S T U V
UT2
SUPL POS SUPL POS
X Y Z AA BB CC
PRPT(session-id2, position, #fix) RLP SSRP(SUPL REPORT) SUPL REPORT(session-id, position) SUPL END(session-id) RLP SSRP(SUPL END) PEND(session-id2)
UT3 position fix #n
Figure 40: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with V-SLP positioning NOTE 1: See Appendix C for timer descriptions.
OMA-TS-ILP-V2_0_1-20121205-A
Page 127 (295)
A. The SUPL Agent on the SET receives a request for a periodic triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLP and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case periodic), Location ID (lid) and periodic trigger parameters. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLP verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. Based on the received lid or other method, the H-SLC determines the V-SLP and sends an SSRLIR SUPL TRIGGERED START message over RLP tunnel to the V-SLC. E. The V-SLC requests service from the V-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY optionally contain the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. F. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES.
G. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the VSLC MAY determine the posmethod. If the V-SPC included a list of supported posmethods in step F, the chosen posmethod SHALL be on this list. If required for the posmethod, the V-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The V-SLC responds with a SUPL TRIGGERED RESPONSE tunnelled over RLP in a SSRLIA message back to the H-SLP that it is capable of supporting this request. The SUPL TRIGGERED RESPONSE contains at least the sessionid and posmethod. H. The H-SLP forwards the SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE contains the session-id but no H-SLP address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL TRIGGERED RESPONSE also contains the posmethod. The SET and the H-SLP MAY release the secure connection. I. When the periodic trigger in the SET indicates that a position fix has to be calculated the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If the SUPL POS INIT message contains a position that meets any required QoP, the H-SLP MAY directly proceed to step Q. The H-SLP forwards the SUPL POS INIT message to the V-SLC over the RLP tunnel in an SSRP message. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the V-SLC MAY directly proceed to step P and not engage in a SUPL POS session.
J.
K. The V-SLC sends a PINIT message to the V-SPC including session-id2, location id and SET capabilities. The VSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the V-SPC in step F, or a different posmethod of the V-SLCs choosing, as long as it is one supported by the V -SPC.
OMA-TS-ILP-V2_0_1-20121205-A
Page 128 (295)
Based on the PINIT message including the SET capabilities, the V-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the V-SLC, the V-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the V-SPC shall choose any posmethod in line with the SET capabilities which was approved by the V-SLC in step E. If a coarse position calculated based on information received in the PINIT message is available that meets the required QoP, the V-SPC MAY directly proceed to step O and not engage in a SUPL POS session. L. If the V-SPC cannot translate the lid received in step K into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into coarse position itself. M. This step is conditional and only occurs if step L was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the V-SPC MAY directly proceed to step O and not engage in a SUPL POS session. N. The SET and the V-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SPC and the V-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SLC and the H-SLC using SUPL POS over RLP tunnel messages. The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages. The flow sequence PMESS RLP SSRP(SUPL POS) SUPL POS SUPL POS RLP SSRP(SUPL POS) PMESS is conceptually shown in dotted lines. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). O. Once the position calculation is complete, the V-SPC sends a PRPT message to the V-SLC. PRPT contains the session-id2, the position result if calculated in V-SPC and the number of the fix. P. Once the position calculation is complete, the V-SLC sends a SUPL REPORT message in an RLP tunnel using an SSRP message to the H-SLP. Q. The H-SLP forwards the SUPL REPORT message to the SET. The SUPL REPORT message includes the position result if the position estimate is calculated in the V-SPC and therefore needs to be sent to the SET. The SET and the H-SLP MAY release the secure connection. NOTE 3: steps I to Q are optional and not performed for A-GPS SET Based in the case where no GPS assistance data is required from the network. In this case the SET autonomously calculates a position fix based on the currently available GPS assistance data stored in the SET. Steps I to Q are repeated if so required for calculating any of the remaining position estimates of the periodic triggered session. The last position estimate which as shown in this case requires the execution of steps I to Q, is shown in steps R to Z. AA. After the last position result has been calculated, the SET ends the periodic triggered session by sending a SUPL END message to the H-SLP. BB. The H-SLP informs the V-SLC about the end of the periodic triggered session by sending a SUPL END message using an RLP SSRP tunnel message to the V-SLC. CC. The V-SLC ends the periodic triggered session with the V-SPC by sending a PEND message. PEND contains the session-id2. NOTE 4: Note that for A-GPS SET Based mode where the SET calculates the position estimate based on GPS assistance data available in the SET, steps I to Q are performed whenever new GPS assistance data is required by the SET.
6.4.3

OMA-TS-ILP-V2_0_1-20121205-A
Page 129 (295)
V-SLP
H-SLC
H-SPC
Target SET
A B C
SUPL TRIGGERED START(session-id, trigger_type=periodic, lid, SET capabilities, trigger_params)

Routing Info
UT1 D LT1 E F PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod)
G H I J
RLP SRLIR(msid, lid) ST4 RLP SRLIA(ms-id, posresult)
UT2 PINIT(session-id2, lid, SET capabilities)
L M
UT3 position fix #1
N O P Q
S T U V W RLP SSRP(SUPL END)
PRPT(session-id2, position, #fix) SUPL REPORT(session-id, position) SUPL END(session-id)
UT3 position fix #n
PEND(session-id2)
Figure 41: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with H-SLP positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for a periodic triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection.
OMA-TS-ILP-V2_0_1-20121205-A
Page 130 (295)
B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case periodic), Location ID (lid) and periodic trigger parameters. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. F. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the HSLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC sends a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE contains the sessionid but no H-SLP address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL TRIGGERED RESPONSE also contains the posmethod. The SET and the H-SLC MAY release the secure connection.
G. When the periodic trigger in the SET indicates that a position fix has to be calculated the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLC. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If the SUPL POS INIT message contains a position that meets any required QoP, the H-SLC MAY directly proceed to step M. H. To obtain a coarse position based on lid received in step G, the H-SLC sends an RLP SRLIR message to the V-SLP. I. The V-SLP translates the received lid into a position estimate and returns the result to the H-SLC in an RLP SRLIA message. If the position estimate meets any required QoP, the H-SLC MAY directly proceed to step M and not engage in a SUPL POS session. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id and SET capabilities. The HSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step E, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H-SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step D.
J.
K. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The
OMA-TS-ILP-V2_0_1-20121205-A
Page 131 (295)
positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). L. Once the position calculation is complete, the H-SPC sends a PRPT message to the H-SLC. PRPT contains the session-id2, the position result if calculated in the H-SPC and the number of the fix. M. Once the position calculation is complete, the H-SLC sends a SUPL REPORT message to the SET. The SUPL REPORT message includes the position result if the position estimate is calculated in the H-SLP and therefore needs to be sent to the SET. The SET MAY release the secure connection to the H-SLC. NOTE 3: steps G to M are optional and not performed for A-GPS SET Based in the case where no GPS assistance data is required from the network. In this case the SET autonomously calculates a position fix based on the currently available GPS assistance data stored in the SET. Steps G to M are repeated if so required for calculating any of the remaining position estimates of the periodic triggered session. The last position estimate which as shown in this case requires the execution of steps G to M, is shown in steps N to T. U. After the last position result has been calculated, the SET ends the periodic triggered session by sending a SUPL END message to the H-SLC. V. The H-SLC informs the V-SLP about the end of the periodic triggered session by sending a SUPL END message using an RLP SSRP tunnel message to the V-SLP. W. The H-SLC ends the periodic triggered session with the H-SPC by sending a PEND message. PEND contains the session-id2. NOTE 4: Note that for A-GPS SET Based mode where the SET calculates the position estimate based on GPS assistance data available in the SET, steps G to M are performed whenever new GPS assistance data is required by the SET.
6.5
This section describes the SET Initiated Non-Proxy mode scenarios. It is assumed that the trigger resides in the SET.
OMA-TS-ILP-V2_0_1-20121205-A
Page 132 (295)
6.5.1

A B C D E F
Routing Info
LT1
PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, H-SPC address, SPC_SET_Key, SPC-TID)
G H I PLREQ(session-id2, lid)
PLRES(session-id2, posresult) PT2 UT2 SUPL POS(session id, RRLP/RRC/TIA-801/LPP) PRPT(session-id2, position, #fix) UT3 SUPL REPORT(session-id, position) position fix #1
K L
M N O PLREQ(session-id2, lid)
UT2
P PRPT(session-id2, position, #fix)
SUPL POS(session id, RRLP/RRC/TIA-801/LPP) UT3 SUPL REPORT(session-id, position) SUPL END(session-id) PEND(session-id2) position fix #n
Q R S T
Figure 42: SET Initiated Periodic Trigger Service Non-Roaming Successful Case Non-Proxy Mode NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for a periodic triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the
OMA-TS-ILP-V2_0_1-20121205-A
Page 133 (295)
H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case periodic), Location ID (lid) and periodic trigger parameters. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently not SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The H-SLC also creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication. SPC_SET_Key and SPC-TID are forwarded to the H-SPC. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. F. Consistent with the SUPL TRIGGERED START message including the SET capabilities of the SET, the H-SLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC SHALL respond with a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE message contains session-id, posmethod, H-SPC address and SPC_SET_Key and SPC-TID to be used for mutual HSPC/SET authentication. The SET and the H-SLC MAY release the secure connection.
G. When the periodic trigger in the SET indicates that a position fix has to be calculated the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SPC. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the H-SPC MAY directly proceed to step K and not engage in a SUPL POS session. H. If the H-SPC cannot translate the lid received in step G into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the H-SPC can perform the translation from lid into coarse position itself. I. This step is conditional and only occurs if step H was performed. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the H-SPC MAY directly proceed to step K and not engage in a SUPL POS session. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step D, the H-SPC SHALL only choose an approved method. The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance data obtained from the H-SPC (SET-Based).
J.
K. The H-SPC may optionally inform the H-SLC about the position fix or assistance data delivery process performed in step J. To this end the H-SPC sends a PRPT message to the H-SLC. PRPT contains at least session-id2.
OMA-TS-ILP-V2_0_1-20121205-A
Page 134 (295)
L. Once the position calculation is complete the H-SPC sends a SUPL REPORT message to the SET. The SUPL REPORT message includes the position result if the position estimate is calculated in the H-SPC and therefore needs to be sent to the SET. The SET MAY release the secure connection to the H-SPC. NOTE 3: steps G to L are optional and not performed for A-GPS SET Based in the case where no GPS assistance data is required from the network. In this case the SET autonomously calculates a position fix based on the currently available GPS assistance data stored in the SET. Steps G to L are repeated if so required for calculating any of the remaining position estimates of the periodic triggered session. The last position estimate which as shown in this case requires the execution of steps G to L, is shown in steps M to R. S. After the last position result has been calculated, the SET ends the periodic triggered session by sending a SUPL END message to the H-SPC.
T. The H-SPC informs the H-SLC through a PEND message that the periodic triggered session has ended. PEND contains session-id2. NOTE 4: Note that for A-GPS SET Based mode where the SET calculates the position estimate based on GPS assistance data available in the SET, steps G to L are performed whenever new GPS assistance data is required by the SET.
6.5.2
OMA-TS-ILP-V2_0_1-20121205-A
Page 135 (295)
H-SLC
V-SLC
V-SPC
Target SET
A B C D E F G H ST3
Routing Info
RLP SSRLIR(SUPL TRIGGERED START, SPC_SET_Key, SPC-TID) PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2)
LT1
RLP SSRLIA(SUPL TRIGGERED RESPONSE) SUPL TRIGGERED RESPONSE(session-id, posmethod, V-SPC address, SPC_SET_Key, SPC-TID)
I J K
SUPL POS INIT(session-id, lid, SET capabilities) PLREQ(session-id2, lid) PLRES(session-id2, posresult) PT2 UT2
M N
UT3 position fix #1
O P Q
S T
UT3 position fix #n
SUPL END(session-id) U V W RLP SSRP(SUPL END) PEND(session-id2)
Figure 43: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for a periodic triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the
OMA-TS-ILP-V2_0_1-20121205-A
Page 136 (295)
H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case periodic), Location ID (lid) and periodic trigger parameters. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. Based on the received lid or other mechanisms, the H-SLC determines the V-SLP and sends an RLP SSRLIR including a SUPL TRIGGERED START message to the V-SLC to inform the V-SLP that a periodic triggered session is in the progress of being initiated. The H-SLC also creates SPC_SET_Key and SPC-TID to be used for mutual V-SPC/SET authentication and sends it to the V-SLC as part of the RLP SSRLIR message. E. The V-SLC requests service from the V-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY also optionally contain the QoP. PREQ also contains SPC_SET_Key and SPC-TID for mutual V-SPC/SET authentication. The VSLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. F. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES.
G. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the VSLC MAY determine the posmethod. If the V-SPC included a list of supported posmethods in step F, the chosen posmethod SHALL be on this list. If required for the posmethod, the V-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The V-SLC responds with a SUPL TRIGGERED RESPONSE tunnelled over RLP in a SSRLIA message back to the H-SLC that it is capable of supporting this request. The SUPL TRIGGERED RESPONSE contains at least the sessionid, posmethod and the V-SPC address. H. The H-SLC sends a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE message contains session-id, posmethod, V-SPC address and SPC_SET_Key and SPC-TID. The SET and the HSLC MAY release the secure connection. I. When the periodic trigger in the SET indicates that a position fix has to be calculated the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the V-SPC. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the V-SPC MAY directly proceed to step M and not engage in a SUPL POS session. If the V-SPC cannot translate the lid received in step I into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the VSPC can perform the translation from lid into coarse position itself.
J.
K. This step is conditional and only occurs if step J was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the V-SPC MAY directly proceed to step M and not engage in a SUPL POS session. L. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the V-SPC SHALL determine the posmethod. If the V-SLC included its approved positioning methods in step E, the V-SPC SHALL only choose
OMA-TS-ILP-V2_0_1-20121205-A
Page 137 (295)
an approved method. The SET and the V-SPC exchange several successive positioning procedure messages. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance data obtained from the V-SPC (SET-Based). M. The V-SPC may optionally inform the V-SPC about the position fix or assistance data delivery process performed in step L. To this end the V-SPC sends a PRPT message to the V-SLC. PRPT contains at least session-id2. N. Once the position calculation is complete, the V-SPC sends a SUPL REPORT message to the SET. The SUPL REPORT message includes the position result if the position estimate is calculated in the V-SPC and therefore needs to be sent to the SET. The SET and the V-SPC MAY release the secure connection. NOTE 3: steps I to N are optional and not performed for A-GPS SET Based in the case where no GPS assistance data is required from the network. In this case the SET autonomously calculates a position fix based on the currently available GPS assistance data stored in the SET. Steps I to N are repeated if so required for calculating any of the remaining position estimates of the periodic triggered session. The last position estimate which as shown in this case requires the execution of steps I to N, is shown in steps O to T. U. After the last position result has been calculated, the SET ends the periodic triggered session by sending a SUPL END message to the V-SPC. V. The V-SPC informs the V-SLC through a PEND message that the periodic triggered session has ended. PEND contains session-id2. W. The V-SLC informs the H-SLC about the end of the periodic triggered session by sending a SUPL END message using an RLP SSRP tunnel message to the H-SLC. NOTE 4: Note that for A-GPS SET Based mode where the SET calculates the position estimate based on GPS assistance data available in the SET, steps I to N are performed whenever new GPS assistance data is required by the SET.
6.5.3

OMA-TS-ILP-V2_0_1-20121205-A
Page 138 (295)
V-SLC
H-SLC
H-SPC
Target SET
A B C D LT1 E F
SUPL TRIGGERED START(session-id, trigger_type=periodic, lid, SET capabilities, trigger_params)

Routing Info
UT1
PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, H-SPC Address, SPC_SET_Key, SPC-TID)
G H I J K L M N
RLP SRLIR(msid, lid) PLREQ(session-id2, lid) ST4 RLP SRLIA(ms-id, posresult) PLRES(session-id2, posresult)
PT2
UT2
UT3 position fix #1
O P Q R S T U V W X Y
PT2
UT2
PRPT(session-id2, position, #fix) SUPL REPORT(session-id, position) SUPL END(session-id) PEND(session-id2) RLP SSRP(SUPL END)
UT3 position fix #n
Figure 44: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for a periodic triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in
OMA-TS-ILP-V2_0_1-20121205-A
Page 139 (295)
this case periodic), Location ID (lid) and periodic trigger parameters. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The H-SLC also creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication. SPC_SET_Key and SPC-TID are forwarded to the H-SPC. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. F. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the HSLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC sends a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE message contains session-id, posmethod, H-SPC address and SPC_SET_Key and SPC-TID for mutual H-SPC/SET authentication. The SET and the H-SLC MAY release the secure connection.
G. When the periodic trigger in the SET indicates that a position fix has to be calculated the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SPC. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If the SUPL POS INIT message contains a position that meets any required QoP, the H-SPC MAY directly proceed to step M. H. The H-SPC sends a PLREQ message to the H-SLC to request translation of the received lid into a coarse position. The PLREQ message contains the session-id2 and the lid. I. J. To obtain a coarse position the H-SLC sends an RLP SRLIR message to the V-SLP. The V-SLC translates the received lid into a position estimate and returns the result to the H-SLC in an RLP SRLIA message.
K. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the sessionid2 and the posresult. If the coarse position meets any required QoP, the H-SPC MAY directly proceed to step M and not engage in a SUPL POS session. L. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step D, the H-SPC SHALL only choose an approved method. The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance data obtained from the H-SPC (SET-Based). M. The H-SPC may optionally inform the H-SPC about the position fix or assistance data delivery process performed in step L. To this end the H-SPC sends a PRPT message to the H-SLC. PRPT contains at least session-id2.
OMA-TS-ILP-V2_0_1-20121205-A
Page 140 (295)
N. Once the position calculation is complete, the H-SPC sends a SUPL REPORT message to the SET. The SUPL REPORT message includes the position result if the position estimate is calculated in the H-SPC and therefore needs to be sent to the SET. The SET and the H-SPC MAY release the secure connection. NOTE 3: steps G to N are optional and not performed for A-GPS SET Based in the case where no GPS assistance data is required from the network. In this case the SET autonomously calculates a position fix based on the currently available GPS assistance data stored in the SET. Steps G to N are repeated if so required for calculating any of the remaining position estimates of the periodic triggered session. The last position estimate which as shown in this case requires the execution of steps G to N, is shown in steps O to V. W. After the last position result has been calculated, the SET ends the periodic triggered session by sending a SUPL END message to the H-SPC. X. The H-SPC informs the H-SLC through a PEND message that the periodic triggered session has ended. PEND contains session-id2. Y. The H-SLC informs the V-SLC about the end of the periodic triggered session by sending a SUPL END message using an RLP SSRP tunnel message to the V-SLC. NOTE 4: Note that for A-GPS SET Based mode where the SET calculates the position estimate based on GPS assistance data available in the SET, steps G to N are performed whenever new GPS assistance data is required by the SET.
6.6
SET Initiated Periodic Location Request with Transfer to 3rd Party Proxy mode
This section describes the flows for SET Initiated Periodic Location Requests with transfer of the position results to a 3 rd party.
OMA-TS-ILP-V2_0_1-20121205-A
Page 141 (295)
6.6.1

H-SLC
A B C D LT1 E F
Routing Info
H-SPC
Target SET
SUPL TRIGGERED START(session-id, lid, SET capabilities, rep_capabilities, 3rd party id)
PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, trigger_params, rep_mode)
UT1
G H I J PINIT(session-id2, lid) PLREQ(session-id2, lid)
UT2
L M N

Location Delivery
UT3
P Q R S LT2 PLREQ(session-id2, lid)
Location Delivery
Figure 45: SET Periodic Trigger Service Non-Roaming Successful Case Proxy Mode (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 142 (295)
H-SLC
H-SPC
Target SET
T U V W PINIT(session-id2, lid) PLREQ(session-id2, lid)
UT2
Y Z AA BB CC DD EE FF LT2
PRPT(session-id2, position, #fix) SUPL REPORT(session-id, position) SUPL REPORT(session-id, position) PLREQ(session-id2, lid) PLRES(session-id2, posresult)
UT3
Location Delivery
PEND(session-id2) SUPL END(session-id)
Figure 46: SET Periodic Trigger Service Non-Roaming Successful Case Proxy Mode (Part II) NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for a periodic triggered service with transfer to a 3 rd party from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case periodic), Location ID (lid), periodic trigger parameters and Third Party ID. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently not SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES.
OMA-TS-ILP-V2_0_1-20121205-A
Page 143 (295)
F.
Consistent with the SUPL TRIGGERED START message including the SET capabilities of the SET, the H-SPC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLP SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC SHALL respond with a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE contains the session-id but no H-SLC address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL TRIGGERED RESPONSE also contains the posmethod. The SET and the H-SLC MAY release the secure connection.
G. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id and the Location ID (lid) and the SET capabilities parameter. The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the H-SLC MAY directly proceed to step M and not engage in a SUPL POS session. H. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id and SET capabilities. The HSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step E, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step D. If a coarse position calculated based on information received in the PINIT message is available that meets the required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session. I. If the H-SPC cannot translate the lid received in step H into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the H-SPC can perform the translation from lid into coarse position itself. This step is conditional and only occurs if step I was performed. The H-SLC calculates a coarse position based on lid and reports the result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session.
J.
K. The SET and the H-SLP exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SETAssisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). L. Once the position calculation is complete the H-SPC sends a PRPT message to the H-SLC. PRPT contains the session-id2, the position result if calculated in H-SPC and the number of the fix. M. The H-SLC sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the H-SLP. If the reporting mode is batch reporting, the SET stores all calculated position estimates. In SET Assisted mode the position is calculated by the H-SLP and therefore needs to be included in the message for batch reporting mode. If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not require an assistance data update from the H-SLP) steps G to H are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLP using a SUPL REPORT message containing the session-id and the position estimate.
OMA-TS-ILP-V2_0_1-20121205-A
Page 144 (295)
N. This step is optional: Once the position calculation is complete and if real time or quasi-real time reporting is used, the H-SLC delivers the position estimate(s) to the 3rd party. If the reporting mode is set to batch reporting, this message is not used. O. This step is optional: If the SET cannot communicate with the H-SLP (e.g. no radio coverage available) and quasireal time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the H-SLP, enhanced cell/sector measurements. In the case of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the H-SLP. P. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLC. The SUPL REPORT message contains the session-id and the position result(s) including date and time information for each position result and optionally the position method used. In the case of batch reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step F. If no criteria are received in step F, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. Q. This step is optional: if the SUPL REPORT message in step P contained enhanced cell/sector measurements and the H-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the H-SLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step P. R. This step is conditional and only used if step Q occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results. S. The H-SLC delivers the position estimate(s) to the 3rd party. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps T to Z may be performed (a repeat of steps G to M). Alternatively and if applicable step O is repeated. AA. This step is optional and is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due, and at any time up until step EE, if and as soon as all the following conditions apply: i. Batch reporting or quasi-real time reporting is used. ii. The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLC. iii. The SET is able to establish communication with the H-SLP iv. In the case of batch reporting, the conditions for sending have arisen (e.g. the conditions define sending after the last position estimate is obtained). The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLC. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step F. If no criteria are received in step F, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported. BB. This step is optional: if the SUPL REPORT message in step AA contained enhanced cell/sector measurements and the H-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the HSLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step AA. CC. This step is conditional and only used if step BB occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results.
OMA-TS-ILP-V2_0_1-20121205-A
Page 145 (295)
DD. The H-SLC delivers the reported and/or calculated historical position estimate(s) to the 3d party. EE. After the last position result has been reported to the 3 rd party in step DD or following some timeout on not receiving stored position estimates in step AA, the H-SLC informs the H-SPC about the end of the periodic triggered session by sending a PEND message. PEND contains session-id2. FF. The H-SLC ends the periodic triggered session by sending a SUPL END message to the SET.
6.6.2

Target SET
V-SLC
V-SPC
H-SLP
A B C D E LT1 F G H RLP SSRLIR(SUPL TRIGGERED START) PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) RLP SSRLIA(SUPL TRIGGERED RESPONSE) ST3
SUPL TRIGGERED START(session-id, lid, SET capabilities, rep_capabilities, 3rd party id)
Routing Info
UT1
SUPL TRIGGERED RESPONSE(session-id, posmethod, trigger_params, rep_mode)
I J K L M
UT2
SUPL POS SUPL POS
O P Q R
PRPT(session-id2, position, #fix) RLP SSRP(SUPL REPORT) SUPL REPORT(session-id, position)

Location Delivery
UT3
Figure 47: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with V-SLP positioning (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 146 (295)
V-SLC
V-SPC
H-SLP
Target SET
T U V W X Y PLREQ(session-id2, lid) LT2
RLP SSRP(SUPL REPORT)
PLRES(session-id2, posresult) RLP SSRP(SUPL REPORT)

Location Delivery
Z AA BB CC DD
UT2
SUPL POS SUPL POS
EE
FF GG HH II
PRPT(session-id2, position, #fix) RLP SSRP(SUPL REPORT) SUPL REPORT(session-id, position) SUPL REPORT(session-id, position) RLP SSRP(SUPL REPORT)
UT3
JJ KK LL MM NN OO PP QQ RLP SSRP(SUPL END) PEND(session-id2) PLREQ(session-id2, lid) LT2 PLRES(session-id2, posresult) RLP SSRP(SUPL REPORT)
Location Delivery
Figure 48: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with V-SLP positioning (Part II) NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for a periodic triggered service with transfer to a 3 rd party from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLP and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case periodic), Location ID (lid), periodic trigger parameters and Third Party ID. The SET capabilities include
OMA-TS-ILP-V2_0_1-20121205-A
Page 147 (295)
the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLP verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. Based on the received lid or other method, the H-SLC determines the V-SLP and sends an SSRLIR SUPL TRIGGERED START message over RLP tunnel to the V-SLC. E. The V-SLC requests service from the V-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY optionally contain the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. F. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES.
G. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the VSLC MAY determine the posmethod. If the V-SPC included a list of supported posmethods in step F, the chosen posmethod SHALL be on this list. If required for the posmethod, the V-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The V-SLC responds with a SUPL TRIGGERED RESPONSE tunnelled over RLP in a SSRLIA message back to the H-SLP that it is capable of supporting this request. The SUPL TRIGGERED RESPONSE contains at least the sessionid and posmethod. H. The H-SLP forwards the SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE contains the session-id but no H-SLP address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL TRIGGERED RESPONSE also contains the posmethod. The SET and the H-SLP MAY release the secure connection. I. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the H-SLP to start a positioning session with the V-SLP. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If the SUPL POS INIT message contains a position that meets any required QoP, the H-SLP MAY directly proceed to step Q. The H-SLP forwards the SUPL POS INIT message to the V-SLC using a RLP SSRP message. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the V-SLC MAY directly proceed to step P and not engage in a SUPL POS session.
J.
K. The V-SLC sends a PINIT message to the V-SPC including session-id2, location id and SET capabilities. The VSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the V-SPC in step F, or a different posmethod of the V-SLCs choosing, as long as it is one supported by the V -SPC. Based on the PINIT message including the SET capabilities, the V-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the V-SLC, the V-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the V-SPC shall choose any posmethod in line with the SET capabilities which was approved by the V-SLC in step E. If a coarse position calculated based on information received in the PINIT message is available that meets the required QoP, the V-SPC MAY directly proceed to step O and not engage in a SUPL POS session.
OMA-TS-ILP-V2_0_1-20121205-A
Page 148 (295)
L. If the V-SPC cannot translate the lid received in step K into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into coarse position itself. M. This step is conditional and only occurs if step L was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets any required QoP, the V-SPC MAY directly proceed to step O and not engage in a SUPL POS session. N. The SET and the V-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SPC and the V-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SLC and the H-SLC using SUPL POS over RLP tunnel messages. The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages. The flow sequence PMESS RLP SSRP(SUPL POS) SUPL POS SUPL POS RLP SSRP(SUPL POS) PMESS is conceptually shown in dotted lines. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). O. Once the position calculation is complete, the V-SPC sends a PRPT message to the V-SLC. PRPT contains the session-id2, the position result if calculated in V-SPC and the number of the fix. P. Once the position calculation is complete, the V-SLC sends a SUPL REPORT message to the H-SLP in an RLP tunnel using an SSRP message. Q. The H-SLC sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the H-SLP. If the reporting mode is batch reporting, the SET stores all calculated position estimates. In SET Assisted mode the position is calculated by the H-SLP and therefore needs to be included in the message for batch reporting mode. If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not require an assistance data update from the H-SLP) steps I to Q are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLC using a SUPL REPORT message containing the session-id and the position estimate. R. This step is optional: once the position calculation is complete and if real time or quasi-real time reporting is used, the H-SLP delivers the received position estimate to the 3 rd party. If the reporting mode is set to batch reporting, this message is not used. S. This step is optional: if the SET cannot communicate with the H-SLP (e.g. no radio coverage available) and quasireal time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the H-SLP, enhanced cell/sector measurements. In the case of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the H-SLP.
T. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLP. The SUPL REPORT message contains the session-id and the position result(s) including data and time information for each position result and optionally the position method used. In the case of batch reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step H. If no criteria are received in step H, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. U. This step is optional: if in step T the SET sent enhanced cell/sector measurements, the H-SLP needs to engage the help of the V-SLP to translate the enhanced cell/sector measurements into actual position estimates. To this end the
OMA-TS-ILP-V2_0_1-20121205-A
Page 149 (295)
H-SLP sends the received enhanced cell/sector measurements in a SUPL REPORT message to the V-SLC using an SSRP message over RLP tunnel. V. This step is optional: if the SUPL REPORT message in step U contained enhanced cell/sector measurements and the V-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the V-SLC sends a PLREQ message to the V-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step U. W. This step is conditional and only used if step V occurred: the V-SPC returns the calculated position estimates to the V-SLC in a PLRES message. PLRES contains session-id2 and the position results. X. This step is optional: if in step U the V-SLC received enhanced cell/sector measurements, the results of the translation into position estimate need to be returned to the H-SLP. To this end a SUPL REPORT message is sent to the H-SLP. The SUPL REPORT message is carried within an SSRP message over RLP tunnel. Y. The H-SLC delivers the reported and/or calculated position estimate(s) to the 3rd party. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps Z to HH may be performed (a repeat of steps I to Q). Alternatively and if applicable step S is repeated. II. This step is optional and is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due, and at any time up until step OO, if and as soon as all of the following conditions apply: i. ii. Batch reporting or quasi-real time reporting is used. The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLP.
iii. The SET is able to establish communication with the H-SLP. iv. In the case of batch reporting, the conditions for sending have arisen (e.g. the conditions define sending after the last position estimate is obtained). The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLP. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step H. If no criteria are received in step H, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported. JJ. This step is optional: if in step II the SET sent enhanced cell/sector measurements, the H-SLP needs to engage the help of the V-SLP to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLP sends the received enhanced cell/sector measurements in a SUPL REPORT message to the V-SLC using an SSRP message over RLP tunnel. KK. This step is optional: if the SUPL REPORT message in step JJ contained enhanced cell/sector measurements and the V-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the V-SLC sends a PLREQ message to the V-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step JJ. LL. This step is conditional and only used if step KK occurred: the V-SPC returns the calculated position estimates to the V-SLC in a PLRES message. PLRES contains session-id2 and the position results. MM. This step is optional: if in step JJ the V-SLC received enhanced cell/sector measurements, the results of the translation into position estimate need to be returned to the H-SLP. To this end a SUPL REPORT message is sent to the H-SLP. The SUPL REPORT message is carried within an SSRP message over RLP tunnel. NN. The H-SLC delivers the reported and/or calculated historical position estimate(s) to the 3 rd party.
OMA-TS-ILP-V2_0_1-20121205-A
Page 150 (295)
OO. After the last position result has been reported to the 3 rd party in step NN, or following some timeout on not receiving stored position estimates in step II, the H-SLC ends the periodic triggered session by sending a SUPL END message to the SET. PP. The H-SLC informs the V-SLC about the end of the periodic triggered session by sending a SUPL END message using an RLP SSRP tunnel message. QQ. The V-SLC ends the periodic triggered session with the V-SPC by sending a PEND message. PEND contains the session-id2.
6.6.3
V-SLP
H-SLC
H-SPC
Target SET
A B C
Routing Info
SUPL TRIGGERED START(session-id, lid, SET capabilities, rep_capabilities, Third party id)
UT1 D E F PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, trigger_params, rep_mode)
LT1
G H I J RLP SRLIR(msid, lid) RLP SRLIA(ms-id, posresult)

UT2
L M N

Location Delivery
UT3
Figure 49: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with H-SLP positioning (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 151 (295)
V-SLC
P Q R S RLP SRLIR(msid, lid)
H-SLC
H-SPC
Target SET
RLP SRLIA(ms-id, posresult)
ST4
Location Delivery
T U V W RLP SRLIR(msid, lid) RLP SRLIA(ms-id, posresult)

UT2
Y Z AA BB CC DD EE FF GG RLP SSRP(SUPL END) RLP SRLIR(msid, lid) RLP SRLIA(ms-id, posresult)
PRPT(session-id2, position, #fix) SUPL REPORT(session-id, position) SUPL REPORT(session-id, position)
UT3
ST4
Location Delivery
PEND(session-id2)
Figure 50: SET Initiated Periodic Trigger Service Roaming Successful Case Proxy with H-SLP positioning (Part II) NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for a periodic triggered service with transfer to a 3 rd party from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case periodic), Location ID (lid), periodic trigger parameters and Third Party ID. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms.
OMA-TS-ILP-V2_0_1-20121205-A
Page 152 (295)
D. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. F. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the HSLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC sends a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE contains the sessionid but no H-SLP address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL TRIGGERED RESPONSE also contains the posmethod. The SET and the H-SLC MAY release the secure connection.
G. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the H-SLC to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If the SUPL POS INIT message contains a position that meets any required QoP, the H-SLC MAY directly proceed to step M and not engage in a SUPL POS session. H. To obtain a coarse position based on lid received in step G, the H-SLC sends an RLP SRLIR message to the V-SLP. I. The V-SLP translates the received lid into a position estimate and returns the result to the H-SLC in an RLP SRLIA message. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the H-SLC MAY directly proceed to step M and not engage in a SUPL POS session. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id, SET capabilities and position estimate (i.e. coarse position received from the V-SLC in the previous step). The H-SLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step E, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step D.
J.
K. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). L. Once the position calculation is complete, the H-SPC sends a PRPT message to the H-SLC. PRPT contains the session-id2, the position result if calculated in H-SPC and the number of the fix. M. The H-SLC sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the H-SLC. If the reporting mode is batch reporting, the SET stores
OMA-TS-ILP-V2_0_1-20121205-A
Page 153 (295)
all calculated position estimates. In SET Assisted mode the position is calculated by the H-SLP and therefore needs to be included in the message for batch reporting mode. If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not require an assistance data update from the H-SLP) steps G to M are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLP using a SUPL REPORT message containing the session-id and the position estimate. N. This step is optional: once the position calculation is complete and if real time or quasi-real time reporting is used the H-SLC delivers the calculated position estimate to the 3rd party. If the reporting mode is set to batch reporting, this message is not used. O. This step is optional: if the SET cannot communicate with the H-SLP (e.g. no radio coverage available) and quasireal time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the H-SLP, enhanced cell/sector measurements. In the case of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the H-SLP. P. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLC. The SUPL REPORT message contains the session-id and the position result(s) including data and time information for each position result and optionally the position method used. In the case of batch reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step F. If no criteria are received in step F, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. Q. This step is optional: if in step P the SET sent enhanced cell/sector measurements, the H-SLC needs to engage the help of the V-SLP to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLC sends an RLP SRLIR message to the V-SLP. R. This step is optional and only takes place if step Q has occurred: The V-SLP translates the received enhanced cell/sector measurements into position estimates and returns the results to the H-SLC in an RLP SRLIA message. S. The H-SLC delivers the reported and/or calculated position estimate(s) to the 3rd party. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps T to Z may be performed (a repeat of steps G to M). Alternatively and if applicable step O is repeated. AA. This step is optional and is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due, and at any time up until step EE, if and as soon as all of the following conditions apply: i. ii. iii. iv. Batch reporting or quasi-real time reporting is used. The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLC. The SET is able to establish communication with the H-SLP. In the case of batch reporting, the conditions for sending have arisen (e.g. the conditions define sending after the last position estimate is obtained).
The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLC. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step F. If no criteria are received in step F, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported.
OMA-TS-ILP-V2_0_1-20121205-A
Page 154 (295)
BB. This step is optional: if in step AA the SET sent enhanced cell/sector measurements, the H-SLC needs to engage the help of the V-SLP to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLC sends an RLP SRLIR message to the V-SLP. CC. This step is optional and only takes place if step BB has occurred: after receiving the enhanced cell/sector measurements the V-SLP translates the received enhanced cell/sector measurements into position estimates and returns the results to the H-SLC in an RLP SRLIA message. DD. The H-SLC delivers the reported and/or calculated historical position estimate(s) to the 3 rd party. EE. After the last position result has been reported to the 3 rd party in step DD, or following some timeout on not receiving stored position estimates in step AA, the H-SLC ends the periodic triggered session by sending a SUPL END message to the SET. FF. The H-SLC informs the V-SLP about the end of the periodic triggered session by sending a SUPL END message using an SSRP message over RLP tunnel. GG. The H-SLC informs the H-SPC about the end of the periodic triggered session in a PEND message. PEND contains session-id2.
OMA-TS-ILP-V2_0_1-20121205-A
Page 155 (295)
6.7
6.7.1
SET Initiated Periodic Location Request with Transfer to 3rd Party Non-Proxy mode
A B C D LT1 E F
Routing Info
SUPL TRIGGERED START(session-id, lid, SET capabilities, rep_capabilities, Third Party id)
PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, H-SPC address, trigger_params, rep_mode, SPC_SET_Key, SPC-TID) UT1
UT2
SUPL POS(session id, RRLP/RRC/TIA-801/LPP) SUPL REPORT(session-id, position) PRPT(session-id2, position, #fix)
Location Delivery
UT3
K L M
O P Q R PLREQ(session-id2, lid) LT2
Location Delivery
Figure 51: SET Initiated Periodic Trigger Service Non-Roaming Successful Case Non-Proxy Mode (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 156 (295)
H-SLC
H-SPC
Target SET
S T U PLREQ(session-id2, lid)
SUPL POS(session id, RRLP/RRC/TIA-801/LPP) SUPL REPORT(session-id, position) PRPT(session-id2, position, #fix) SUPL REPORT(session-id, position) PLREQ(session-id2, lid) LT2 PLRES(session-id2, posresult) UT3
W X Y Z AA BB CC DD
Location Delivery
PEND(session-id2) SUPL END(session-id)
Figure 52: SET Initiated Periodic Trigger Service Non-Roaming Successful Case Non-Proxy Mode (Part II) NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for a periodic triggered service with transfer to a 3 rd party from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case periodic), Location ID (lid), periodic trigger parameters and Third Party ID. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently not SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid The H-SLC also creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication. SPC_SET_Key and SPC-TID are forwarded to the H-SPC. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. F. Consistent with the SUPL TRIGGERED START message including the SET capabilities of the SET, the H-SLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen
OMA-TS-ILP-V2_0_1-20121205-A
Page 157 (295)
posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC SHALL respond with a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE message contains session-id, posmethod, H-SPC address and SPC_SET_Key and SPC-TID for mutual H-SPC/SET authentication. The SET and the H-SLC MAY release the secure connection. G. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SPC. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the H-SPC MAY directly proceed to step K and not engage in a SUPL POS session. H. If the H-SPC cannot translate the lid received in step G into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the H-SPC can perform the translation from lid into coarse position itself. I. This step is conditional and only occurs if step H was performed. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets any required QoP, the H-SPC MAY directly proceed to step K and not engage in a SUPL POS session. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step D, the H-SPC SHALL only choose an approved method. The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based).
J.
K. Once the position calculation is complete the H-SPC sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the H-SPC. If the reporting mode is batch reporting, the SET stores all calculated position estimates. In SET Assisted mode the position is calculated by the H-SPC and therefore needs to be included in the message for batch reporting mode. L. This step is optional: Once the position calculation is complete and if real time or quasi-real time reporting is used the H-SPC sends the position estimate in a PRPT message to the H-SLC. PRPT contains the session-id2, the position result and the number of the fix. This message is optional and only used if the position was calculated by the H-SPC i.e. in SET Assisted mode. If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not require an assistance data update from the H-SLP) steps G to L are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLC using a SUPL REPORT message containing the session-id and the position estimate. M. This step is optional: once the position calculation is complete and if real time or quasi-real time reporting is used, the H-SLC delivers the position estimate to the 3rd party. If the reporting mode is set to batch reporting, this message is not used. N. This step is optional: If the SET cannot communicate with the H-SLP (e.g. no radio coverage available) and quasireal time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the H-SLP, enhanced cell/sector measurements. In the case of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the H-SLP. O. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position
OMA-TS-ILP-V2_0_1-20121205-A
Page 158 (295)
estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLC. The SUPL REPORT message contains the session-id and the position result(s) including date and time information for each position result and optionally the position method used. In the case of batch reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step F. If no criteria are received in step F, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. P. This step is optional: if the SUPL REPORT message in step O contained enhanced cell/sector measurements and the H-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the H-SLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step O. Q. This step is conditional and only used if step P occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results. R. The H-SLC delivers the reported and/or calculated position estimate(s) to the 3rd party. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps S to X may be performed (a repeat of steps G to L). Alternatively and if applicable step N is repeated. Y. This step is optional and is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due, and at any time up until step CC, if and as soon as all the following conditions apply: i. ii. iii. iv. Batch reporting or quasi-real time reporting is used. The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLC. The SET is able to establish communication with the H-SLP In the case of batch reporting, the conditions for sending have arisen (e.g. the conditions define sending after the last position estimate is obtained).
The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLC. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step F. If no criteria are received in step F, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported. Z. This step is optional: if the SUPL REPORT message in step Y contained enhanced cell/sector measurements and the H-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the H-SLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step Y. AA. This step is conditional and only used if step Z occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results. BB. The H-SLC delivers the reported and/or calculated historical position estimate(s) to the 3rd party. CC. After the last position result has been reported to the 3 rd party in step BB the H-SLC informs the H-SPC about the end of the periodic triggered session by sending a PEND message. PEND contains the session-id2. DD. The H-SLC ends the periodic triggered session by sending a SUPL END message to the SET. Please note that if the last position was calculated in step V and step Y was not performed, the SUPL END message is sent from the HSPC to the SET (as opposed to from the H-SLC to the SET).
6.7.2

OMA-TS-ILP-V2_0_1-20121205-A
Page 159 (295)
H-SLC
V-SLC
V-SPC
Target SET
A B C D E F G H ST3
Routing Info
RLP SSRLIR(SUPL TRIGGERED START, SPC_SET_Key, SPC-TID) UT1 LT1 PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2) RLP SSRLIA(SUPL TRIGGERED RESPONSE) SUPL TRIGGERED RESPONSE(session-id, posmethod, V-SPC address, trigger_params, rep_mode, SPC_SET_Key, SPC-TID)
I J K L M N O P
UT2
SUPL POS SUPL REPORT(session-id, position) PRPT(session-id2, position, #fix) RLP SSRP(SUPL REPORT)
Location Delivery
UT3
R S T U V W
RLP SSRP(SUPL REPORT) PLREQ(session-id2, lid) LT2

Location Delivery
Figure 53: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 160 (295)
H-SLC
V-SLC
V-SPC
Target SET
UT2
X Y Z AA
SUPL POS SUPL REPORT(session-id, position) PRPT(session-id2, position, #fix) RLP SSRP(SUPL REPORT) SUPL REPORT(session-id, position) RLP SSRP(SUPL REPORT) PLREQ(session-id2, lid) LT2 PLRES(session-id2, posresult) UT3
BB CC DD EE FF GG HH II JJ KK LL MM

Location Delivery
RLP SSRP(SUPL END) PEND(session-id2) SUPL END(session-id)
Figure 54: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning (Part II) NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for a periodic triggered service with transfer to a 3 rd party from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case periodic), Location ID (lid), periodic trigger parameters and Third Party ID. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. Based on the received lid or other mechanisms, the H-SLC determines the V-SLP and sends an RLP SSRLIR including a SUPL TRIGGERED START message to the V-SLC to inform the V-SLP that a periodic triggered session is in the progress of being initiated. The H-SLC also creates SPC_SET_Key and SPC-TID to be used for mutual V-SPC/SET authentication and sends it as part of the RLP SSRLIR message to the V-SLC. E. The V-SLC requests service from the V-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY also optionally
OMA-TS-ILP-V2_0_1-20121205-A
Page 161 (295)
contain the QoP. The PREQ message also contains SPC_SET_Key and SPC-TID for mutual V-SPC/SET authentication. The V-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. F. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES.
G. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the VSLC MAY determine the posmethod. If the V-SPC included a list of supported posmethods in step F, the chosen posmethod SHALL be on this list. If required for the posmethod, the V-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The V-SLC responds with a SUPL TRIGGERED RESPONSE tunnelled over RLP in a SSRLIA message back to the H-SLC that it is capable of supporting this request. The SUPL TRIGGERED RESPONSE contains at least the sessionid, posmethod and the V-SPC address. H. The H-SLC sends a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE message contains session-id, posmethod, V-SPC address, and SPC_SET_Key and SPC-TID for mutual V-SPC/SET authentication. The SET and the H-SLC MAY release the secure connection. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the V-SPC to start a positioning session with the V-SPC. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the V-SPC MAY directly proceed to step M and not engage in a SUPL POS session. If the V-SPC cannot translate the lid received in step I into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the VSPC can perform the translation from lid into coarse position itself.
I.
J.
K. This step is conditional and only occurs if step J was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets any required QoP, the V-SPC MAY directly proceed to step M and not engage in a SUPL POS session. L. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the V-SPC SHALL determine the posmethod. If the V-SLC included its approved positioning methods in step E, the V-SPC SHALL only choose an approved method. The SET and the V-SPC exchange several successive positioning procedure messages. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). M. Once the position calculation is complete the V-SPC sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the V-SPC. If the reporting mode is batch reporting, the SET stores all calculated position estimates. In SET Assisted mode the position is calculated by the V-SPC and therefore needs to be included in the message for batch reporting mode. N. This step is optional: once the position calculation is complete and real time or quasi-real time reporting is used, the V-SPC sends the position estimate in a PRPT message to the V-SLC. PRPT contains the session-id2, the position result and the number of the fix. This message is optional and only used if the position was calculated by the V-SPC i.e. in SET Assisted mode. O. This step is conditional and is only used after step N occurred. The V-SLC sends the position estimate to the H-SLC in a SUPL REPORT message. The SUPL REPORT message includes at a minimum the session-id and the position estimate. The SUPL REPORT message is carried within an RLP SSRP message.
OMA-TS-ILP-V2_0_1-20121205-A
Page 162 (295)
If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not require an assistance data update from the H-SLP) steps I to N are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLC using a SUPL REPORT message containing the session-id and the position estimate. P. This step is optional: if real time or quasi-real time reporting is used, the H-SLC delivers the position estimate received to the 3rd party. If the reporting mode is set to batch reporting, this message is not needed. Q. This step is optional: If the SET cannot communicate with the V-SLP (e.g. no radio coverage available) and quasireal time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the H-SLP, enhanced cell/sector measurements. In the case, of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the V-SLP. R. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP/V-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLC. The SUPL REPORT message contains the session-id and the position result(s) including date and time information for each position result and optionally the position method used. In the case of batch reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step H. If no criteria are received in step H, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. S. This step is optional: if the H-SLC received stored enhanced cell/sector measurements in the SUPL REPORT message in step R, the V-SLP may need to be involved to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLC sends a SUPL REPORT message to the V-SLC using an SSRP message over RLP tunnel.
T. This step is optional: if the SUPL REPORT message in step S contained enhanced cell/sector measurements and the V-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the V-SLC sends a PLREQ message to the V-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step S. U. This step is conditional and only used if step T occurred: the V-SPC returns the calculated position estimates to the V-SLC in a PLRES message. PLRES contains session-id2 and the position results. V. This step is conditional and takes place after step S and optionally steps T and U. A SUPL REPORT message containing position estimates calculated from enhanced cell/sector measurements received in step S is sent from the V-SLC to the H-SLC using an SSRP message over RLP tunnel. W. The H-SLC delivers the reported and/or calculated position estimate(s) to the 3 rd party. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps X to DD may be performed (a repeat of steps I to N). Alternatively and if applicable step Q is repeated. EE. This step is optional and is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due, and at any time up until step KK, if and as soon as all the following conditions apply: i. Batch reporting or quasi-real time reporting is used. ii. The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLC. iii. The SET is able to establish communication with the H-SLP. iv. In the case of batch reporting, the conditions for sending have arisen (e.g. the conditions define sending after the last position estimate is obtained).
OMA-TS-ILP-V2_0_1-20121205-A
Page 163 (295)
The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLC. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step H. If no criteria are received in step H, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported. FF. This step is optional: if the H-SLC received stored enhanced cell/sector measurements in the SUPL REPORT message in step EE, the V-SLP may need to be involved to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLC sends a SUPL REPORT message to the V-SLC using an SSRP message over RLP tunnel. GG. This step is optional: if the SUPL REPORT message in step EE contained enhanced cell/sector measurements and the V-SPC is required to translate the received enhanced cell/sector measurements into position estimates, the VSLC sends a PLREQ message to the V-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step EE. HH. This step is conditional and only used if step GG occurred: the V-SPC returns the calculated position estimates to the V-SLC in a PLRES message. PLRES contains session-id2 and the position results. II. This step is conditional and takes place after step FF and optionally steps GG and HH. A SUPL REPORT message containing position estimates calculated from enhanced cell/sector measurements received in step FF is sent from the V-SLC to the H-SLC using an SSRP message over RLP tunnel. JJ. The H-SLC delivers the reported and/or calculated historical position estimate(s) to the 3rd party. KK. After the last position result has been reported to the 3 rd party in step JJ, the H-SLC informs the V-SLC about the end of the periodic triggered session through an SUPL END message carried within an SSRP message over RLP tunnel. LL. The V-SLC informs the V-SPC about the end of the periodic triggered session in a PEND the session-id2. eighbo. PEND contains
MM. The H-SLC ends the periodic triggered session with the SET by sending a SUPL END message. The SUPL END message includes at least the session-id. Please note that if the last position was calculated in step AA and step EE was not performed, the SUPL END message is sent from the V-SPC to the SET (as opposed to from the H-SLC to the SET).
6.7.3

OMA-TS-ILP-V2_0_1-20121205-A
Page 164 (295)
V-SLC
H-SLC
H-SPC
Target SET
A B C D E F
Routing Info
LT1
PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2)
UT1
SUPL TRIGGERED RESPONSE(session-id, posmethod, H-SPC address, trigger_params, rep_mode, SPC_SET_Key, SPC-TID)
G H I J K L M N O
PT2
UT2
SUPL REPORT(session-id, position) PRPT(session-id2, position, #fix)

Location Delivery
UT3
Q R S T U V
RLP SRLIR(msid, lid) RLP SRLIA(ms-id, posresult) PLREQ(session-id2, lid) LT2 PLRES(session-id2, posresult)
Location Delivery
Figure 55: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning (Part I)
OMA-TS-ILP-V2_0_1-20121205-A
Page 165 (295)
V-SLC
H-SLC
H-SPC
Target SET
UT2
W X Y Z AA BB CC DD EE FF GG HH II JJ KK LL MM
PT2
SUPL REPORT(session-id, position) PRPT(session-id2, position, #fix) SUPL REPORT(session-id, position)
UT3
RLP SRLIA(ms-id, posresult) PLREQ(session-id2, lid) LT2

Location Delivery
RLP SSRP(SUPL END) PEND(session-id2) SUPL END(session-id)
Figure 56: SET Initiated Periodic Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning (Part II) NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for a periodic triggered service with transfer to a 3 rd party from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case periodic), Location ID (lid), periodic trigger parameters and Third Party ID. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. The H-SLC requests service from the H-SPC for a periodic triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The H-SLC also creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication. SPC_SET_Key and SPC-TID are forwarded to the H-SPC in the PREQ message. The PREQ MAY also optionally contain the QoP. The H-SLC MAY
OMA-TS-ILP-V2_0_1-20121205-A
Page 166 (295)
include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. F. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the HSLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC sends a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE message contains session-id, posmethod, H-SPC address and SPC_SET_Key and SPC-TID for mutual H-SPC/SET authentication. The SET and the H-SLC MAY release the secure connection.
G. When the periodic trigger in the SET indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the H-SPC to start a positioning session with the H-SPC. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If the SUPL POS INIT message contains a position that meets any required QoP, the H-SPC MAY directly proceed to step M. H. To translate the lid received in step G into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. I. J. To obtain a coarse position the H-SLC sends an RLP SRLIR message to the V-SLP. The V-SLP translates the received lid into a position estimate and returns the result to the H-SLC in an RLP SRLIA message. For real-time or quasi-real time reporting, if the returned position meets the required QoP, the H-SLC SHALL directly proceed to step N and not engage in a SUPL POS session. For batch reporting, if the returned position meets any required QoP, the H-SLC MAY send the position result through internal communication to the H-SPC (step K) and the H-SPC will forward the position result to the SET using a SUPL REPORT message (step M) without engaging in a SUPL POS session (step L).
K. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the sessionid2 and the posresult. If the coarse position meets any required QoP, the H-SPC MAY directly proceed to step M and not engage in a SUPL POS session. L. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step D, the H-SPC SHALL only choose an approved method. The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). M. Once the position calculation is complete the H-SPC sends the SUPL REPORT message to the SET informing it that the positioning procedure is completed. The SET MAY release the secure connection to the H-SLP. If the reporting mode is batch reporting, the SET stores all calculated position estimates. In SET Assisted mode the position is calculated by the H-SPC and therefore needs to be included in the message for batch reporting mode. N. This step is optional: once the position calculation is complete and if real time or quasi-real time reporting is used, the H-SPC sends the position estimate in a PRPT message to the H-SLC. PRPT contains the session-id2, the position result and the number of the fix. This message is optional and only used if the position was calculated by the H-SPC i.e. in SET Assisted mode. If a SET Based positioning method was chosen which allows the SET to autonomously calculate a position estimate (e.g. autonomous GPS or A-GPS SET Based mode where the SET has current GPS assistance data and does not
OMA-TS-ILP-V2_0_1-20121205-A
Page 167 (295)
require an assistance data update from the H-SLP) steps G to N are not performed. Instead, the SET autonomously calculates the position estimate and for real time or quasi-real time reporting sends the calculated position estimate to the H-SLC using a SUPL REPORT message containing the session-id and the position estimate. O. This step is optional: if real time or quasi-real time reporting is used, the H-SLC delivers the calculated position estimate to the 3rd party. If the reporting mode is set to batch reporting, this message is not needed. P. This step is optional: If the SET cannot communicate with the H-SLP (e.g. no radio coverage available) and quasireal time reporting is used or if batch reporting is used, the SET MAY if supported perform SET Based position fixes (autonomous GPS or SET Based A-GPS where the SET has current assistance data) and/or, if allowed by the H-SLP, enhanced cell/sector measurements. In the case, of batch reporting, and if explicitly allowed by the H-SLP, enhanced cell/sector measurements are permitted even when the SET can communicate with the H-SLP. Q. This step is optional and is executed if batch reporting is used and if any of the conditions for sending batch reports have occurred. It is also executed, once the SET is able to re-establish communication with the H-SLP, if quasi-real time reporting is used if one or more previous reports have been missed. The SET sends the stored position estimates and/or, if allowed, the stored enhanced cell/sector measurements in an unsolicited SUPL REPORT message to the H-SLC. The SUPL REPORT message contains the session-id and the position result(s) including date and time information for each position result and optionally the position method used. In the case of batch reporting, the stored position estimates and/or enhanced cell/sector measurements included in the SUPL REPORT message may be chosen according to criteria received in step F. If no criteria are received in step F, the SET shall include all stored position estimates and/or enhanced cell/sector measurements not previously reported. R. This step is optional: if the H-SLC received stored enhanced cell/sector measurements in the SUPL REPORT message in step Q, the V-SLP may need to be involved to translate the enhanced cell/sector measurements into actual position estimates. To this end the H-SLC sends an RLP SRLIR message to the V-SLC. S. This step is conditional and takes place only if step R occurred. The V-SLC sends the position result calculated based on the enhanced cell/sector measurements received in step R to the H-SLC.
T. This step is optional and only takes place if after the translation into a position estimate in steps R and S the H-SPC is required to calculate the position estimate. In this case the H-SLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step Q. U. This step is conditional and only used if step T occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results. V. The H-SLC delivers the reported and/or calculated position estimate(s) to the 3 rd party. When the last position estimate needs to be calculated i.e. the end of the periodic triggered session has been reached, steps W to DD may be performed (a repeat of steps G to N). Alternatively and if applicable step P is repeated. EE. This step is optional and is executed after the last position estimate or, if allowed, last set of enhanced cell/sector measurements has been obtained or was due, and at any time up until step KK, if and as soon as all the following conditions apply: i. ii. iii. iv. Batch reporting or quasi-real time reporting is used. The SET has stored historic location reports and/or stored historic enhanced cell/sector measurements that have not yet been sent to the H-SLC. The SET is able to establish communication with the H-SLP. In the case of batch reporting, the conditions for sending have arisen (e.g. the conditions define sending after the last position estimate is obtained).
The SUPL REPORT message is used to send all or a subset of stored position fixes and/or stored enhanced cell/sector measurements not previously reported to the H-SLC. In the case of batch reporting, the stored position estimates and/or stored enhanced cell/sector measurements included in the SUPL REPORT message may be chosen
OMA-TS-ILP-V2_0_1-20121205-A
Page 168 (295)
according to criteria received in step F. If no criteria are received in step F, the SET shall include all stored position estimates and/or stored enhanced cell/sector measurements not previously reported. FF. This step is optional: if the H-SLC received stored enhanced cell/sector measurements in the SUPL REPORT message in step EE, the V-SLP may need to be involved to translate the enhanced cell/sector measurements into actual position estimates To this end the H-SLC sends an RLP SRLIR message to the V-SLC. GG. This step is conditional and takes place only if step FF occurred. The V-SLC sends the position result calculated based on the enhanced cell/sector measurements received in step FF to the H-SLC. HH. This step is optional and only takes place if after the translation into a position estimate in steps FF and GG the HSPC is required to calculate the position estimate. In this case the H-SLC sends a PLREQ message to the H-SPC. The PLREQ message contains the session-id2 and the enhanced cell/sector measurements received in step EE. II. This step is conditional and only used if step HH occurred: the H-SPC returns the calculated position estimates to the H-SLC in a PLRES message. PLRES contains session-id2 and the position results. JJ. The H-SLC delivers the reported and/or calculated historical position estimate(s) to the 3rd party. KK. When the last position result was reported to the 3 rd party in step JJ, the H-SLC closes the periodic triggered session with the V-SLC by sending a SUPL END message encapsulated in an SSRP message over RLP tunnel. LL. The H-SLC informs the H-SPC about the end of the periodic triggered session by sending a PEND message. PEND contains the session-id2. MM. The H-SLC ends the periodic triggered session with the SET by sending a SUPL END message. The SUPL END message includes at least the session-id. Please note that if the last position was calculated in step BB and step EE was not performed, the SUPL END message is sent from the H-SPC to the SET (as opposed to from the H-SLC to the SET).
6.8
Retrieval of Historical Positions and/or Enhanced Cell Sector Measurements
This section describes the retrieval of stored historical positions and/or enhanced cell/sector measurements. Please note that the concept of non-proxy mode does not apply since the SET is not involved in a positioning session i.e. does not directly communicate with the SPC.
6.8.1
Retrieval of Historical Position Results non-roaming successful case
The following flow defines the retrieval of historical position results from the SET for non-roaming. In the context of retrieval of historical position and/or enhanced cell/sector measurements non-roaming means that enhanced cell/sector measurements which the SET reports were taken while the SET was not SUPL Roaming.
OMA-TS-ILP-V2_0_1-20121205-A
Page 169 (295)
SUPL Agent
H-SLC
H-SPC
Target SET
MLP HLIR(ms-id, client-id, hist-params) A SUPL INIT(session-id, posmethod=historical data retrieval, SLP mode, historic reporting) B C D E LT2 F MLP HLIA(posresults) G PLRES(session-id2, posresults) PLREQ(session-id2, lids)
ST5
SUPL REPORT(session-id, positions/enhanced cell/sector measurements, ver)
Figure 57: Retrieval of historical positions and/or enhanced cell/sector measurements non-roaming NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP HLIR message to the H-SLC, with which SUPL Agent is associated. The H-SLC SHALL authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLC SHALL apply subscriber privacy against the client-id. The hist-params parameter in the HLIR message defines criteria to be applied by the SET when selecting historical position to be reported to the SUPL Agent (e.g. time window, QoP, positioning method, etc.). The H-SLC initiates the retrieval of historical positions with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, posmethod, SLP mode, supported network measurements and criteria for selecting stored historical position estimates and/or stored enhanced cell/sector measurements (historic reporting). Historical data retrieval is indicated by posmethod: historical data retrieval. If the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLP SHALL set notification mode to notification based on current location and SHALL NOT include the notification element in the SUPL INIT message; otherwise, the H-SLP SHALL set the notification mode indicator to normal notification and if notification or verification to the target subscriber is needed, the H-SLP SHALL also include the notification element in the SUPL INIT message.Before the SUPL INIT message is sent, the H-SLC also computes and stores a hash of the message. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. The SET will evaluate the Notification rules and follow the appropriate actions. The SET then establishes a secure connection to the H-SLC using an H-SLP address that has been provisioned by the Home Network to the SET. The SET selects historical position estimates and/or historic enhanced cell/sector measurements based on the criteria received in step B and sends the positions and/or enhanced cell/sector measurements in a SUPL REPORT message to the H-SLC. The SUPL REPORT message contains session-id, a hash of the received SUPL INIT message (ver) and positions and/or enhanced cell/sector measurements. After sending the SUPL REPORT message, the SET SHALL release all resources related to this session. This step is optional: if the H-SLC cannot convert received historical enhanced cell/sector measurements into position estimates, it sends the measurements in a PLREQ message to the H-SPC for conversion. This step is optional and only takes place if step E has taken place: the H-SPC sends the converted position estimates back to the H-SLC in a PLRES message. The H-SLC reports the historical position estimates to the SUPL Agent in an MLP HLIA message.
B.
C. D.
E. F. G.
OMA-TS-ILP-V2_0_1-20121205-A
Page 170 (295)
6.8.2
Retrieval of Historical Position Results roaming successful case
The following flow defines the retrieval of historical position results from the SET for roaming. In the context of retrieval of historical position and/or enhanced cell/sector measurements roaming means that enhanced cell/sector measurements reported by the SET were taken while the SET was SUPL Roaming.
SUPL Agent
V-SPC
V-SLC
H-SLP
Target SET
MLP HLIR(ms-id, client-id, hist-params) A B C D E F G H MLP HLIA(posresults) I LT2 PLRES(msid, posresults) RLP-SRLIA(msid, posresults) RLP-SRLIR(msid, lids) PLREQ(session-id2, lids) ST4 SUPL INIT(session-id, posmethod=historical data retrieval, SLP mode, historic reporting) ST5
SUPL REPORT(session-id, positions/enhanced cell/sector measurements, ver)
Figure 58: Retrieval of historical positions and/or enhanced cell/sector measurements roaming NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent issues an MLP HLIR message to the H-SLP, with which SUPL Agent is associated. The H-SLP shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLP shall apply subscriber privacy against the client-id. The hist-params parameter in the HLIR message defines criteria to be applied by the SET when selecting historical position to be reported to the SUPL Agent (e.g. time window, QoP, positioning method, etc.). B. The H-SLP initiates the retrieval of historical positions with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, posmethod, SLP mode, supported network measurements and criteria for selecting stored historical position estimates and/or stored enhanced cell/sector measurements (historic reporting). Historical data retrieval is indicated by posmethod: historical data retrieval. If the result of the privacy check in Step A indicates that notification or verification to the target subscriber is needed, the H-SLP SHALL also include the Notification element in the SUPL INIT message. Before the SUPL INIT message is sent, the H-SLP also computes and stores a hash of the message. C. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. D. The SET will evaluate the Notification rules and follow the appropriate actions. The SET then establishes a secure connection to the H-SLP using a H-SLP address that has been provisioned by the Home Network to the SET. The SET selects historical position estimates and/or historic enhanced cell/sector measurements based on the criteria received in step B and sends the positions and/or enhanced cell/sector measurements in a SUPL REPORT message to the H-SLP. The SUPL REPORT message contains session-id, a hash of the received SUPL INIT message (ver) and positions and/or enhanced cell/sector measurements. E. If in step D the H-SLP received enhanced cell/sector measurements, the H-SLP converts them into position estimates. However, enhanced cell/sector measurements taken while the SET was SUPL Roaming, cannot to be
OMA-TS-ILP-V2_0_1-20121205-A
Page 171 (295)
converted into position estimates by the H-SLP. These measurements are instead forwarded to the respective V-SLC in an RLP-SRLIR message. F. This step is optional: if the V-SLC cannot convert received historical enhanced cell/sector measurements into position estimates, it sends the measurements in a PLREQ message to the V-SPC for conversion.
G. This step is optional and only takes place if step F has taken place: the V-SPC sends the converted position estimates back to the V-SLC in a PLRES message. H. The V-SLC returns the results to the H-SLP in an RLP-SRLIA message. I. The H-SLP reports the historical position estimates to the SUPL Agent in an MLP HLIA message.
6.9
V-SLP to V-SLP Handover
The V-SLP to V-SLP handover which is defined in [SUPL 2 ULP TS] sections 5.1.11,and 5.2.12 does not have implications for ILP since the mechanism for determining of whether or not a SET is SUPL Roaming within a particular SLPs SUPL coverage is out of scope of SUPL.
6.10 V-SPC to V-SPC Handover

The V-SPC to V-SPC handover which is defined in [SUPL 2 ULP TS] sections 5.1.11 and 5.2.13 does not have implications for ILP since the mechanism for determining of whether or not a SET is SUPL Roaming within a particular SLPs SUPL coverage is out of scope of SUPL.
OMA-TS-ILP-V2_0_1-20121205-A
Page 172 (295)
7. Detailed Flows Triggered Services: Area Event Triggers

The flows in this section are those in which area event triggers are used. Set up and release of connections: Before sending any ULP messages the SET SHALL take needed actions such that a TLS connection exists to the SLP/SLC. This can be achieved by establishing a new connection, resume a connection or reuse an existing TLS connection. This includes establishment or utilization of various data connectivity resources that depends on the terminal in which the SET resides and the type of access network. Data connectivity below IP-level is out of scope of this document. The detailed flows in this section describes when a TLS connection no longer is needed. The TLS connection shall then be released unless another SUPL session is using the TLS connection.
7.1
Network Initiated Proxy mode
This section describes the flows for Network Initiated area event triggered services for proxy mode. The trigger thereby resides in the SET and the SET makes the decision if an area event occurred based on continuously repeated position determinations.
OMA-TS-ILP-V2_0_1-20121205-A
Page 173 (295)
7.1.1

SUPL Agent
A B C D E F LT1 G H I MLP TLRA(req_id) ST2 SUPL TRIGGERED START(session-id, lid, SET capabilities, ver) PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, trigger_params)
H-SLC
H-SPC
Target SET

SUPL INIT(session-id, trigger_type=area event, posmethod, SLP mode)

UT1
J K L M
UT2
O P Q
UT3
Check for area event
R S MLP TLREP(req_id)
SUPL REPORT(session-id)
T U
SUPL END(session-id) PEND(session-id2)
Figure 59: Network Initiated Area Event Trigger Service Non-Roaming Successful Case Proxy Mode NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP TLRR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the clientid.
OMA-TS-ILP-V2_0_1-20121205-A
Page 174 (295)
B. The H-SLC verifies that the target SET is currently not SUPL Roaming. The H-SLC MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLC initiates the area event trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case area event), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLP SHALL set notification mode to notification based on current location and SHALL NOT include the notification element in the SUPL INIT message; otherwise, the HSLP SHALL set the notification mode indicator to normal notification and if notification or verification to the target subscriber is needed, the H-SLP SHALL also include the notification element in the SUPL INIT message.Before the SUPL INIT message is sent, the H-SLC also computes and stores a hash of the message. D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start an area event triggered session with the H-SLC. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SETAssisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). F. The H-SLC requests service from the H-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved.
G. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. H. Consistent with the SET capabilities received in the SUPL TRIGGERED START message the H-SLC selects a positioning method to be used for the area event triggered session. If the H-SPC included a list of supported posmethods in step G, the chosen posmethod SHALL be on this list. The H-SLC responds with a SUPL TRIGGERED RESPONSE message including session-id, posmethod and area event trigger parameters. The SUPL TRIGGERED RESPONSE message may contain the area ids of the specified area for the area event triggered session. The H-SLC informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the area event triggered session. The SET and the H-SLC MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR. J. If the area ids are downloaded in step H, the SET SHALL compare the current area id to the downloaded area ids. When the area event trigger mechanism in the SET or the comparison of the current area id to the downloaded area ids indicates that a position fix is to be executed, the SET takes appropriate action establishing or resuming a secure I.
OMA-TS-ILP-V2_0_1-20121205-A
Page 175 (295)
connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets the required QoP, the H-SLC MAY directly proceed to step P and not engage in a SUPL POS session. K. The H-SLC sends a PINIT message to the H-SPC. The H-SLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step G, or a different posmethod of the HSLCs choosing, as long as it is one supported by the H -SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the HSLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step F. If a coarse position calculated based on information received in the PINIT message is available that meets the required QoP, the H-SPC MAY directly proceed to step O and not engage in a SUPL POS session. L. If the H-SPC cannot translate the lid received in step K into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the H-SPC can perform the translation from lid into coarse position itself. M. This step is conditional and only occurs if step L was performed. The H-SLC calculates a coarse position based on lid and reports the result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the H-SPC MAY directly proceed to step O and not engage in a SUPL POS session. N. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). O. Once the position calculation is complete the H-SPC sends a PRPT message to the H-SLC. PRPT contains the session-id2, the position result if calculated in H-SPC and the number of the fix. P. Once the position calculation is complete the H-SLC sends a SUPL REPORT message to the SET. The SET MAY release the secure connection to the H-SLC. The SUPL REPORT message includes the position result if the position estimate is calculated in the H-SLP and therefore needs to be sent to the SET. Q. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met. If no area event is triggered, the SET SHALL return to step J. If an area event is triggered, the SET SHALL proceed to step R. R. The SET sends a SUPL REPORT message including the session id and the position estimate to the H-SLC unless the Location estimate parameter is set to false in which case no position estimate is included. S. The H-SLC sends an MLP TLREP message to the SUPL Agent which may include the position result.
If the SUPL Agent has requested several reports and more reports are to be sent, the SET repeats steps J to S or steps J to Q depending on whether or not the area event condition has been met. Note that in this case, step R occurs only after the minimum time between reports has elapsed. T. When the last report has been sent the H-SLC ends the area event triggered session by sending a SUPL END message to the SET.
OMA-TS-ILP-V2_0_1-20121205-A
Page 176 (295)
U. The H-SLC informs the H-SPC about the end of the triggered session by sending a PEND message. PEND contains the session-id2. The flow described in Figure 59 is applicable to all positioning methods, however, individual steps within the flows are optional: Step N is not performed for cell-id based positioning methods. Steps K, L and M may or may not be performed for cell-id based positioning methods.
In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the H-SLP is required to calculate a position estimate. Interaction with the H-SLP is only required for GPS assistance data update in which case steps J to P are performed.
7.1.2
OMA-TS-ILP-V2_0_1-20121205-A
Page 177 (295)
SUPL Agent
A
V-SLC
V-SPC
H-SLP
Target SET
C D ST2

E F G LT1 H I J K MLP TLRA(req_id) RLP SSRLIA(SUPL TRIGGERED RESPONSE) RLP SSRLIR(SUPL TRIGGERED START) PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) ST3
SUPL TRIGGERED START(session-id, lid, SET capabilities, ver)
UT1
SUPL TRIGGERED RESPONSE(session-id, posmethod, trigger_params)
RLP SSRP(SUPL POS INIT)
M N O P
PMESS(session-id2, RRLP/RRC/TIA-801/LPP) RLP SSRP(SUPL POS) SUPL POS SUPL POS
UT2 PINIT(session-id2, lid, SET capabilities) PLREQ(session-id2, lid) PLRES(session-id2, posresult) PT2
Q
RLP SSRP(SUPL POS)
PRPT(session-id2, position) R S T U RLP SSRP(SUPL REPORT) SUPL REPORT(session-id, position)
UT3
V W MLP TLREP(req_id)
X Y Z
RLP SSRP(SUPL END) PEND(session-id2)
Figure 60: Network Initiated Area Event Trigger Service Roaming Successful Case Proxy with V-SLP positioning NOTE 1: See Appendix C for timer descriptions.
OMA-TS-ILP-V2_0_1-20121205-A
Page 178 (295)
A. SUPL Agent issues an MLP TLRR message to the H-SLP, with which SUPL Agent is associated. The H-SLP shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLP shall apply subscriber privacy against the clientid. B. The H-SLP verifies that the target SET is currently SUPL Roaming. The H-SLP MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLP initiates the area event trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case area event), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that notification or verification to the target subscriber is needed, the H-SLP SHALL also include the Notification element in the SUPL INIT message. Before the SUPL INIT message is sent, the H-SLP also computes and stores a hash of the message. D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLP using SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start an area event triggered session with the H-SLP. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SETAssisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). F. Based on the received lid or other mechanisms, the H-SLP determines the V-SLP and sends an RLP SSRLIR including the SUPL TRIGGERED START message to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. The area event trigger parameters such as area information requested by SUPL Agent for the area event triggered session MAY be included in this message by the H-SLP.
G. The V-SLC requests service from the V-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY optionally contain the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. H. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. I. Consistent with the SET capabilities received in step F, the V-SLC determines a posmethod to be used for the area event triggered session. If the V-SPC included a list of supported posmethods in step H, the chosen posmethod SHALL be on this list. The V-SLC indicates its readiness for an area event triggered session by sending a SUPL TRIGGERED RESPONSE message back to the H-SLP in a RLP SSRLIA message. The V-SLC MAY include area ids corresponding to the area for the area event trigger session in the SUPL TRIGGERED RESPONSE message. The H-SLP forwards the received SUPL TRIGGERED RESPONSE message to the SET including session-id, posmethod and area event trigger parameters. The SUPL TRIGGERED RESPONSE message may contain the area ids of the specified area for the area event triggered session.
J.
OMA-TS-ILP-V2_0_1-20121205-A
Page 179 (295)
K. The H-SLP informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the area event triggered session. The SET and the H-SLP MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR. L. If the area ids are downloaded in step J, the SET SHALL compare the current area id to the downloaded area ids. When the area event trigger in the SET or the comparison of the current area id to the downloaded area ids indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the H-SLP to start a positioning session with the VSLP. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position is received in the SUPL POS INIT message that meets the required QoP, the H-SLP MAY directly proceed to step T and not engage in a SUPL POS session. M. The H-SLP forwards the SUPL POS INIT message to the V-SLC using a RLP SSRP message. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets the required QoP, the V-SLC MAY directly proceed to step S and not engage in a SUPL POS session. N. The V-SLC sends a PINIT message to the V-SPC including session-id2, location id and SET capabilities. The VSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the V-SPC in step G, or a different posmethod of the V-SLCs choosing, as long as it is one supported by the V -SPC. Based on the PINIT message including the SET capabilities, the V-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the V-SLC, the V-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the V-SPC shall choose any posmethod in line with the SET capabilities, which was approved by the V-SLC in step F. If a coarse position calculated based on information received in the PINIT message is available that meets the required QoP, the V-SPC MAY directly proceed to step R and not engage in a SUPL POS session. O. If the V-SPC cannot translate the lid received in step N into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into coarse position itself. P. This step is conditional and only occurs if step O was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the V-SPC MAY directly proceed to step R and not engage in a SUPL POS session. Q. The SET and the V-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SPC and the V-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SLC and the H-SLC using SUPL POS over RLP tunnel messages. The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages. The flow sequence PMESS RLP SSRP(SUPL POS) SUPL POS SUPL POS RLP SSRP(SUPL POS) PMESS is conceptually shown in dotted lines. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). R. Once the position calculation is complete, the V-SPC sends a PRPT message to the V-SLC. PRPT contains the session-id2 and the position result if calculated in V-SPC. This message is optional and only used if the position was calculated by the V-SPC i.e. in SET Assisted mode. S. Once the position calculation is complete, the V-SLC sends a SUPL REPORT message carried within an RLP SSRP message. The SUPL REPORT message includes the position estimate if the position estimate is calculated in the V-SLP and therefore needs to be sent to the SET.
OMA-TS-ILP-V2_0_1-20121205-A
Page 180 (295)
T. The H-SLP forwards the received SUPL REPORT from the V-SLC in a SUPL REPORT message to the SET. The SET MAY release the secure connection to the H-SLP. The SUPL REPORT message includes the position estimate if the position estimate is calculated in the V-SLP (or the H-SLP) and therefore needs to be sent to the SET. U. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met. If no area event is triggered, the SET SHALL return to step L. If an area event is triggered, the SET SHALL proceed to step V. V. The SET sends a SUPL REPORT message including the session id and the position estimate to the H-SLC unless the Location estimate parameter is set to false in which case no position estimate is included. W. The H-SLP sends an MLP TLREP message to the SUPL Agent which may include the position eighb.
If the SUPL Agent has requested several reports and more reports are to be sent, the SET repeats steps L to W or steps L to U depending on whether or not the area event condition has been met. Note that in this case, step V occurs only after the minimum time between reports has elapsed. X. When the last report has been sent, the H-SLP ends the area event triggered session with the V-SLP by sending a SUPL END message using an RLP SSRP tunnel message to the V-SLC. Y. The V-SLC informs the V-SPC about the end of the area event triggered session via a PEND message. PEND contains the session-id2. Z. The H-SLP ends the area event triggered session by sending a SUPL END message to the SET. The flow described in Figure 60 is applicable to all positioning methods, however, individual steps within the flows are optional: Step Q is not performed for cell-id based positioning methods. Steps N, O and P may or may not be performed for cell-id based positioning methods.
In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the H-SLP/VSLP is required to calculate a position estimate. Interaction with the H-SLP/V-SLP is only required for GPS assistance data update in which case steps L to T are performed.
7.1.3
OMA-TS-ILP-V2_0_1-20121205-A
Page 181 (295)
SUPL Agent
A
V-SLP
H-SLC
H-SPC
Target SET
SUPL INIT(session-id, trigger_type=area event, posmethod, SLP mode) C D ST2

E F G H LT1 I J K MLP TLRA(req_id)
SUPL TRIGGERED START(session-id, lid, SET capabilities, ver) RLP SSRLIR(SUPL TRIGGERED START) ST3 RLP SSRLIA(SUPL TRIGGERED RESPONSE) PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, trigger_params) UT1
L M N O
UT2
PRPT(session-id2, position) Q R S SUPL REPORT(session-id, position)
UT3
T U MLP TLREP(req_id)
RLP SSRP(SUPL END)
V W X PEND(session-id2)
Figure 61: Network Initiated Area Event Trigger Service Roaming Successful Case Proxy with H-SLP positioning NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP TLRR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the
OMA-TS-ILP-V2_0_1-20121205-A
Page 182 (295)
client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the clientid. B. The H-SLC verifies that the target SET is currently SUPL Roaming. The H-SLC MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLC initiates the area event trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case area event), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLP SHALL set notification mode to notification based on current location and SHALL NOT include the notification element in the SUPL INIT message; otherwise, the HSLP SHALL set the notification mode indicator to normal notification and if notification or verification to the target subscriber is needed, the H-SLP SHALL also include the notification element in the SUPL INIT message.Before the SUPL INIT message is sent, the H-SLC also computes and stores a hash of the message. D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using SLP address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start an area event triggered session with the H-SLP. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SETAssisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). F. Based on the received lid or other mechanisms, the H-SLC determines the V-SLP and sends an RLP SSRLIR including a SUPL TRIGGERED START to the V-SLP to inform the V-SLP that an area event triggered session is in the progress of being initiated with the H-SLP. The area event trigger parameters such as area information requested by SUPL Agent for the area event triggered session MAY be included in this message by the H-SLP.
G. The V-SLP acknowledges the RLP request received in step F with a SUPL TRIGGERED RESPONSE message which is carried inside an RLP SSRLIA message. The V-SLP MAY include area ids corresponding to the area for the area event trigger session in the SUPL TRIGGERED RESPONSE message. H. The H-SLC requests service from the H-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. I. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. Consistent with the SET capabilities received in step E, the H-SLP determines a posmethod to be used for the area event triggered session. If the H-SPC included a list of supported posmethods in step I, the chosen posmethod SHALL be on this list. The H-SLC indicates its readiness for an area event triggered session by sending a SUPL TRIGGERED RESPONSE message back to the SET. The SUPL TRIGGERED RESPONSE message to the SET
J.
OMA-TS-ILP-V2_0_1-20121205-A
Page 183 (295)
includes at a minimum the session-id, posmethod and area event trigger parameters. The SUPL TRIGGERED RESPONSE message may contain the area ids of the specified area for the area event triggered session. K. The H-SLC informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the area event triggered session. The SET and the H-SLP MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR. L. If the area ids are downloaded in step J, the SET SHALL compare the current area id to the downloaded area ids. When the area event trigger in the SET or the comparison of the current area id to the downloaded area ids indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the H-SLC to start a positioning session with the HSLP. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If the SUPL POS INIT message contains a position that meets the required QoP, the H-SLC MAY directly proceed to step R. M. To obtain a coarse position based on lid received in step L, the H-SLC sends an RLP SRLIR message to the V-SLP. N. The V-SLP translates the received lid into a position estimate and returns the result to the H-SLC in an RLP SRLIA message. If the position estimate meets the required QoP, the H-SLC MAY directly proceed to step R and not engage in a SUPL POS session. O. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id, SET capabilities and position estimate (i.e. coarse position received from the V-SLC in the previous step). The H-SLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step I, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step H. If a coarse position calculated based on information received in the PINIT message is available that meets the required QoP, the H-SPC MAY directly proceed to step Q and not engage in a SUPL POS session. P. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). Q. Once the position calculation is complete, the H-SPC sends a PRPT message to the H-SLC. PRPT contains the session-id2 and the position result if calculated in H-SPC. R. Once the position calculation is complete, the H-SLC sends a SUPL REPORT message to the SET. The SUPL REPORT message includes the position estimate if the position estimate is calculated in the H-SLP and therefore needs to be sent to the SET. S. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met. If no area event is triggered, the SET SHALL return to step L. If an area event is triggered, the SET SHALL proceed to step T.
T. The SET sends a SUPL REPORT message including the session id and the position estimate to the H-SLC unless the Location estimate parameter is set to false in which case no position estimate is included.
OMA-TS-ILP-V2_0_1-20121205-A
Page 184 (295)
U. The H-SLC sends an MLP TLREP message to the SUPL Agent which may include the position result. If the SUPL Agent has requested several reports and more reports are to be sent, the SET repeats steps L to U or steps L to S depending on whether or not the area event condition has been met. Note that in this case, step T occurs only after the minimum time between reports has elapsed. V. When the last report has been sent the H-SLC ends the area event triggered session with the V-SLP by sending a SUPL END message using an RLP SSRP tunnel message to the V-SLP. W. The H-SLC ends the area event triggered session with the SET via a SUPL END message. X. The H-SLC informs the H-SPC about the end of the area event triggered session via a PEND message. PEND contains session-id2. The flow described in Figure 61 is applicable to all positioning methods; however, individual steps within the flows are optional: Step P is not performed for cell-id based positioning methods. Steps M, N and O may or may not be performed for cell-id based positioning methods.
In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the H-SLP/VSLP is required to calculate a position estimate. Interaction with the H-SLP/V-SLP is only required for GPS assistance data update in which case steps L to R are performed.
7.2
Network Initiated Non-Proxy mode
This section describes the flows for Network Initiated area event triggered services for non-proxy mode. The trigger thereby resides in the SET and the SET makes the decision if an area event occurred based on continuously repeated position determinations.
OMA-TS-ILP-V2_0_1-20121205-A
Page 185 (295)
7.2.1

MLP TLRR(ms-id, client-id, qop) A B

D E
ST2
SUPL TRIGGERED START(session-id, lid, SET capabilities, ver) PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) LT1 PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, H-SPC address, trigger_params, SPC_SET_Key, SPC-TID) MLP TLRA(req_id) UT1
F G H I
J K L
UT2
M PRPT(session-id2, position)
N O P
UT3 SUPL REPORT(session-id, position)

SUPL REPORT(session-id) Q R MLP TLREP(req_id)
PEND(session-id2)
Figure 62: Network Initiated Area Event Trigger Service Non-Roaming Successful Case Non-Proxy Mode NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP TLRR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the clientid. B. The H-SLC verifies that the target SET is currently not SUPL Roaming. The H-SLC MAY also verify that the target SET supports SUPL.
OMA-TS-ILP-V2_0_1-20121205-A
Page 186 (295)
NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLC initiates the area event trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case area event), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLP SHALL set notification mode to notification based on current location and SHALL NOT include the notification element in the SUPL INIT message; otherwise, the HSLP SHALL set the notification mode indicator to normal notification and if notification or verification to the target subscriber is needed, the H-SLP SHALL also include the notification element in the SUPL INIT message.Before the SUPL INIT message is sent, the H-SLC also computes and stores a hash of the message. D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, non-proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using the H-SLP address which has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start an area event triggered session with the H-SLP. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SETAssisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). F. The H-SLC requests service from the H-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The H-SLC generates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication and forwards both to the H-SPC in the PREQ message. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved.
G. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. H. Consistent with the SET capabilities received in the SUPL TRIGGERED START message the H-SLC selects a positioning method to be used for the area event triggered session. If the H-SPC included a list of supported posmethods in step G, the chosen posmethod SHALL be on this list. The H-SLC responds with a SUPL TRIGGERED RESPONSE message including session-id, posmethod, H-SPC address, area event trigger parameters, SPC_SET_Key and SPC-TID. The SUPL TRIGGERED RESPONSE message may contain the area ids of the specified area for the area event triggered session. The H-SLC informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the area event triggered session. The SET and the H-SLC MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR. J. If the area ids are downloaded in step H, the SET SHALL compare the current area id to the downloaded area ids. When the area event trigger in the SET or the comparison of the current area id to the downloaded area ids indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure I.
OMA-TS-ILP-V2_0_1-20121205-A
Page 187 (295)
connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SPC. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets the required QoP, the H-SPC MAY directly proceed to step N and not engage in a SUPL POS session. K. If the H-SPC cannot translate the lid received in step J into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the HSPC can perform the translation from lid into coarse position itself. L. This step is conditional and only occurs if step K was performed. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the H-SPC MAY directly proceed to step N and not engage in a SUPL POS session. M. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step F, the H-SPC SHALL only choose an approved method. The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). N. The H-SPC may optionally inform the H-SLC about the position fix or assistance data delivery process performed in step M. To this end the H-SPC sends a PRPT message to the H-SLC. PRPT contains at least session-id2. O. Once the position calculation is complete the H-SPC sends a SUPL REPORT message to the SET. The SET MAY release the secure connection to the H-SPC. The SUPL REPORT message includes the position result if the position estimate is calculated in the H-SPC and therefore needs to be sent to the SET. P. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met. If no area event is triggered, the SET SHALL return to step J. If an area event is triggered, the SET SHALL proceed to step Q. Q. The SET sends a SUPL REPORT message including the session id and the position estimate to the H-SLC unless the Location estimate parameter is set to false in which case no position estimate is included. R. The H-SLC sends an MLP TLREP message to the SUPL Agent which may include the position result. If the SUPL Agent has requested several reports and more reports are to be sent, the SET repeats steps J to R or steps J to P depending on whether or not the area event condition has been met. Note that in this case, step Q occurs only after the minimum time between reports has elapsed. S. When the last report has been sent, the H-SLC informs the H-SPC about the end of the area event triggered session via a PEND message. PEND contains session-id2
T. The H-SLC ends the area event triggered session by sending a SUPL END message to the SET. The flow described in Figure 62 is applicable to all positioning methods, however, individual steps within the flows are optional: Step M is not performed for cell-id based positioning methods. Steps K and L may or may not be performed for cell-id based positioning methods.
In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the H-SLP is required to calculate a position estimate. Interaction with the H-SLP is only required for GPS assistance data update in which case steps J to O are performed.
OMA-TS-ILP-V2_0_1-20121205-A
Page 188 (295)
7.2.2
SUPL Agent
H-SLC
V-SLC
V-SPC
Target SET
MLP TLRR(ms-id, client-id, qop) A B C D E F G H I J K MLP TLRA(req_id) ST3 ST2 SUPL TRIGGERED START(session-id, lid, SET capabilities, ver) RLP SSRLIR(SUPL TRIGGERED START, SPC_SET_Key, SPC-TID) UT1 LT1 PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2) RLP SSRLIA(SUPL TRIGGERED RESPONSE) SUPL TRIGGERED RESPONSE(session-id, posmethod, V-SPC address, trigger_params, SPC_SET_Key, SPC-TID)

L M N O P Q R
UT2
SUPL POS PRPT(session-id2, position) SUPL REPORT(session-id, position)

UT3
SUPL REPORT(session-id) S T MLP TLREP(req_id)
U V W
RLP TSRLRR(SUPL END) PEND(session-id2) SUPL END(session-id)
Figure 63: Network Initiated Area Event Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP TLRR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the
OMA-TS-ILP-V2_0_1-20121205-A
Page 189 (295)
client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the clientid. B. The H-SLC verifies that the target SET is currently SUPL Roaming. The H-SLC MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLC initiates the area event trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case area event), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLP SHALL set notification mode to notification based on current location and SHALL NOT include the notification element in the SUPL INIT message; otherwise, the HSLP SHALL set the notification mode indicator to normal notification and if notification or verification to the target subscriber is needed, the H-SLP SHALL also include the notification element in the SUPL INIT message.Before the SUPL INIT message is sent, the H-SLC also computes and stores a hash of the message. D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLC uses proxy or non-proxy mode. In this case, non-proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using the H-SLC address which has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start an area event triggered session with the H-SLP. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SETAssisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). F. Based on the received lid or other mechanisms, the H-SLC determines the V-SLC and sends an RLP SSRLIR including the SUPL TRIGGERED START message to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. The H-SLC also generates SPC_SET_Key and SPC-TID to be used for VSPC/SET mutual authentication and includes both in the RLP SSRLIR message. The area event trigger parameters such as area information requested by SUPL Agent for the area event triggered session MAY be included in this message by the H-SLC.
G. The V-SLC requests service from the V-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The V-SLC also forwards SPC_SET_Key and SPC-TID to the V-SPC in the PREQ message. The PREQ MAY also optionally contain the QoP. The V-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. H. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES. I. Consistent with the SET capabilities received in step F. the V-SLC determines a posmethod to be used for the area event triggered session. If the V-SPC included a list of supported posmethods in step H, the chosen posmethod SHALL be on this list. The V-SLC indicates its readiness for an area event triggered session by sending a SUPL TRIGGERED RESPONSE message back to the H-SLC in an RLP SSRLIA message. The V-SLC MAY include
OMA-TS-ILP-V2_0_1-20121205-A
Page 190 (295)
area-ids corresponding to the area for the area event trigger session in the SUPL TRIGGERED RESPONSE message. J. The H-SLC forwards the received SUPL TRIGGERED RESPONSE message to the SET including session-id, posmethod, V-SPC address, area event trigger parameters, SPC_SET_Key and SPC-TID. The SUPL TRIGGERED RESPONSE message may contain the area ids of the specified area for the area event triggered session.
K. The H-SLC informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the area event triggered session. The SET and the H-SLC MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR. L. If the area ids are downloaded in step J, the SET SHALL compare the current area id to the downloaded area ids. When the area event trigger in the SET or the comparison of the current area id to the downloaded area ids indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the V-SPC to start a positioning session with the VSPC. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets the required QoP, the V-SPC MAY directly proceed to step P and not engage in a SUPL POS session. M. If the V-SPC cannot translate the lid received in step L into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the VSPC can perform the translation from lid into coarse position itself. N. This step is conditional and only occurs if step M was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the V-SPC MAY directly proceed to step P and not engage in a SUPL POS session. O. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the V-SPC SHALL determine the posmethod. If the V-SLC included its approved positioning methods in step G, the V-SPC SHALL only choose an approved method. The SET and the V-SPC exchange several successive positioning procedure messages. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). P. The V-SPC may optionally inform the V-SLC about the position fix or assistance data delivery process performed in step O. To this end the V-SPC sends a PRPT message to the V-SLC. PRPT contains at least session-id2. Q. Once the position calculation is complete the V-SPC sends a SUPL REPORT message to the SET. The SET MAY release the secure connection to the V-SPC. The SUPL REPORT message includes the position result if the position estimate is calculated in the V-SPC and therefore needs to be sent to the SET. R. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met. If no area event is triggered, the SET SHALL return to step L. If an area event is triggered, the SET SHALL proceed to step S. S. The SET sends a SUPL REPORT message including the session id and the position estimate to the H-SLC unless the Location estimate parameter is set to false in which case no position estimate is included.
T. The H-SLC sends an MLP TLREP message to the SUPL Agent which may include the position result. If the SUPL Agent has requested several reports and more reports are to be sent, the SET repeats steps L to T or steps L to R depending on whether or not the area event condition has been met. Note that in this case, step S occurs only after the minimum time between reports has elapsed.
OMA-TS-ILP-V2_0_1-20121205-A
Page 191 (295)
U. When the last report has been sent, the H-SLC informs the V-SLC about the end of the area event triggered session through an SUPL END message carried within an SSRP message over RLP tunnel.,. V. The V-SLC informs the V-SPC about the end of the area event triggered session via a PEND message. The PEND contains the session-id2 W. The H-SLC ends the area event triggered session by sending a SUPL END message to the SET. The flow described in Figure 63 is applicable to all positioning methods, however, individual steps within the flows are optional: Step O is not performed for cell-id based positioning methods. Steps M and N may or may not be performed for cell-id based positioning methods. In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the VSLP is required to calculate a position estimate. Interaction with the V-SLP is only required for GPS assistance data update in which case steps L to Q are performed.
7.2.3

OMA-TS-ILP-V2_0_1-20121205-A
Page 192 (295)
SUPL Agent
A B C D E F G H I J K
V-SLC
H-SLC
H-SPC
Target SET
SUPL INIT(session-id, trigger_type=area event, posmethod, SLP mode) ST2

SUPL TRIGGERED START(session-id, lid, SET capabilities, ver) RLP SSRLIR(SUPL TRIGGERED START) ST3 RLP SSRLIA(SUPL TRIGGERED RESPONSE) PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2)
LT1
MLP TLRA(req_id)
SUPL TRIGGERED RESPONSE(session-id, posmethod, H-SPC address, trigger_params, SPC_SET_Key, SPC-TID)
L M N O P Q R S T
UT2 PT2
UT3
U V MLP TLREP(req_id)
W X Y
RLP TSRLRR(SUPL END) PEND(session-id2)
Figure 64: Network Initiated Area Event Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning NOTE 1: See Appendix C for timer descriptions. A. SUPL Agent issues an MLP TLRR message to the H-SLC, with which SUPL Agent is associated. The H-SLC shall authenticate the SUPL Agent and check if the SUPL Agent is authorized for the service it requests, based on the client-id received. Further, based on the received ms-id the H-SLC shall apply subscriber privacy against the clientid.
OMA-TS-ILP-V2_0_1-20121205-A
Page 193 (295)
B. The H-SLC verifies that the target SET is currently SUPL Roaming. The H-SLC MAY also verify that the target SET supports SUPL. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL. However, there are various environment dependent mechanisms. NOTE 3: Alternatively, the H-SLP may determine whether the SET is SUPL Roaming in a later step using the location identifier (lid) received from the SET. NOTE 4: The specifics for determining if the SET supports SUPL are beyond SUPL 2.0 scope. C. The H-SLC initiates the area event trigger session with the SET using the SUPL INIT message. The SUPL INIT message contains at least session-id, trigger type indicator (in this case area event), proxy/non-proxy mode indicator and the intended positioning method. If the result of the privacy check in Step A indicates that subscriber privacy check based on current location is required, the H-SLP SHALL set notification mode to notification based on current location and SHALL NOT include the notification element in the SUPL INIT message; otherwise, the HSLP SHALL set the notification mode indicator to normal notification and if notification or verification to the target subscriber is needed, the H-SLP SHALL also include the notification element in the SUPL INIT message.Before the SUPL INIT message is sent, the H-SLC also computes and stores a hash of the message. D. The SET analyses the received SUPL INIT. If it is found to be non authentic, the SET takes no further action.Otherwise the SET takes needed action preparing for establishment or resumption of a secure connection. E. The SET will evaluate the Notification rules and follow the appropriate actions. The SET also checks the proxy/nonproxy mode indicator to determine if the H-SLP uses proxy or non-proxy mode. In this case, non-proxy mode is used, and the SET SHALL establish a secure connection to the H-SLC using the H-SLC address that has been provisioned by the Home Network to the SET. The SET then sends a SUPL TRIGGERED START message to start an area event triggered session with the H-SLC. The SET SHALL send the SUPL TRIGGERED START message even if the SET supported positioning technologies do not include the intended positioning method indicated in the SUPL INIT message. The SUPL TRIGGERED START message contains at least session-id, SET capabilities, a hash of the received SUPL INIT message (ver) and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SETAssisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). F. Based on the received lid or other mechanisms, the H-SLC determines the V-SLC and sends an RLP SSRLIR including a SUPL TRIGGERED START message to the V-SLC to inform the V-SLC that an area event triggered session is in the progress of being initiated with the H-SLP. The area event trigger parameters such as area information requested by SUPL Agent for the area event triggered session MAY be included in this message by the H-SLC.
G. The V-SLC acknowledges the RLP request received in step F with a SUPL TRIGGERED RESPONSE message which is carried inside an RLP SSRLIA message. The V-SLC MAY include area ids corresponding to the area for the area event trigger session in the SUPL TRIGGERED RESPONSE message. H. The H-SLC requests service from the H-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The H-SLC generates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication and forwards both to the H-SPC in the PREQ message. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. I. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2.The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. Consistent with the SET capabilities received in step E, the H-SLC determines a posmethod to be used for the area event triggered session. If the H-SPC included a list of supported posmethods in step I, the chosen posmethod SHALL be on this list. The H-SLC indicates its readiness for an area event triggered session by sending a SUPL TRIGGERED RESPONSE message back to the SET. The SUPL TRIGGERED RESPONSE message to the SET
J.
OMA-TS-ILP-V2_0_1-20121205-A
Page 194 (295)
includes at a minimum the session-id, posmethod, H-SPC address, area event trigger parameters, SPC_SET_Key and SPC-TID. The SUPL TRIGGERED RESPONSE message may contain the area ids of the specified area for the area event triggered session. K. The H-SLC informs the SUPL Agent in an MLP TLRA message that the triggered location response request has been accepted and also includes a req_id parameter to be used as a transaction id for the entire duration of the area event triggered session. The SET and the H-SLC MAY release the secure connection. NOTE 5: The MLP TLRA may be sent earlier at any time after the H-SLP receives the MLP TLRR. L. If the area ids are downloaded in step J, the SET SHALL compare the current area id to the downloaded area ids. When the area event trigger in the SET or the comparison of the current area id to the downloaded area ids indicates that a position fix has to be performed, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to the H-SPC to start a positioning session with the HSPC. The SUPL POS INIT message contains at least session-id and the Location ID (lid). The SET MAY provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If the SUPL POS INIT message contains a position that meets the required QoP, the H-SPC MAY directly proceed to step R. M. To translate the lid received in step L into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. N. To obtain a coarse position the H-SLC sends an RLP SRLIR message to the V-SLC. O. The V-SLC translates the received lid into a position estimate and returns the result to the H-SLC in an RLP SRLIA message. P. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the sessionid2 and the posresult. If the coarse position meets the required QoP, the H-SPC MAY directly proceed to step R and not engage in a SUPL POS session. Q. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step H, the H-SPC SHALL only choose an approved method. The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). R. The H-SPC may optionally inform the H-SLC about the position fix or assistance data delivery process performed in step Q. To this end the H-SPC sends a PRPT message to the H-SLC. PRPT contains at least session-id2 S. Once the position calculation is complete the H-SPC sends a SUPL REPORT message to the SET. The SET MAY release the secure connection to the H-SPC. The SUPL REPORT message includes the position result if the position estimate is calculated in the H-SPC and therefore needs to be sent to the SET.
T. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met. If no area event is triggered, the SET SHALL return to step L. If an area event is triggered, the SET SHALL proceed to step U. U. The SET sends a SUPL REPORT message including the session id and the position estimate to the H-SLC unless the Location estimate parameter is set to false in which case no position estimate is included. V. The H-SLC sends an MLP TLREP message to the SUPL Agent which may include the position result. If the SUPL Agent has requested several reports and more reports are to be sent, the SET repeats steps L to V or steps L to T depending on whether or not the area event condition has been met. Note that in this case, step U occurs only after the minimum time between reports has elapsed.
OMA-TS-ILP-V2_0_1-20121205-A
Page 195 (295)
W. When the last report has been sent, the H-SLC informs the V-SLC about the end of the area event triggered session by sending a SUPL END message using an RLP SSRP tunnel message to the V-SLC. X. The H-SLC informs the H-SPC about the end of the area event triggered session via a PEND message. The PEND contains the session-id2. Y. The H-SLC ends the area event triggered session by sending a SUPL END message to the SET. The flow described in Figure 64 is applicable to all positioning methods, however, individual steps within the flows are optional: Step Q is not performed for cell-id based positioning methods. In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the HSLP/V-SLP is required to calculate a position estimate. Interaction with the H-SLP/V-SLP is only required for GPS assistance data update in which case steps L to S are performed.
7.3
This section describes the flows for SET Initiated area event triggered services for proxy mode. The trigger thereby resides in the SET and the SET makes the decision if an area event occurred based on continuously repeated position determinations.
OMA-TS-ILP-V2_0_1-20121205-A
Page 196 (295)
7.3.1

A B C D E F
Routing Info
SUPL TRIGGERED START(session-id, trigger_type=area event, lid, SET capabilities, trigger_params) UT1 LT1 PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod)
G H I J
UT2
L M N
PRPT(session-id2, position) SUPL REPORT(session-id, position)
UT3
O P Q R PEND(session-id2)
position fix
Figure 65: SET Initiated Area Event Trigger Service Non-Roaming Successful Case Proxy Mode NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for an area event triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLP and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case area event), Location ID (lid) and area event trigger parameters. The SET capabilities include the supported
OMA-TS-ILP-V2_0_1-20121205-A
Page 197 (295)
positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLP verifies that the target SET is currently not SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. The H-SLC requests service from the H-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. F. Consistent with the SUPL TRIGGERED START message including the SET capabilities of the SET, the H-SLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC SHALL respond with a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE contains the session-id but no H-SLP address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL TRIGGERED RESPONSE also contains the posmethod. The SET and the H-SLC MAY release the secure connection.
G. When the area event trigger in the SET indicates that a position fix has to be calculated, the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the H-SLP MAY directly proceed to step M and not engage in a SUPL POS session. H. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id and SET capabilities. The HSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step E, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step D. If a coarse position calculated based on information received in the PINIT message is available that meets the required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session. I. If the H-SPC cannot translate the lid received in step H into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the H-SPC can perform the translation from lid into coarse position itself. This step is conditional and only occurs if step I was performed. The H-SLC calculates a coarse position based on lid and reports the result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets the required QoP, the H-SPC MAY directly proceed to step L and not engage in a SUPL POS session.
J.
OMA-TS-ILP-V2_0_1-20121205-A
Page 198 (295)
K. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). L. Once the position calculation is complete the H-SPC sends a PRPT message to the H-SLC. PRPT contains the session-id2 and the position result if calculated in the H-SPC. M. Once the position calculation is complete the H-SLC sends a SUPL REPORT message to the SET. The SET MAY release the secure connection to the H-SLC. The SUPL REPORT message includes the position result if the position estimate is calculated in the H-SPC and therefore needs to be sent to the SET. N. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met. O. If the area event was triggered the SET forwards the calculated position estimate to the internal SUPL Agent. P. If the SET decides to end the triggered session the SET proceeds to step Q. Otherwise whenever the area event trigger mechanism in the SET indicates that a new position fix has to be performed, steps G to O are repeated. Q. The SET ends the triggered session by sending a SUPL END message to the H-SLC. R. The H-SLC informs the H-SPC about the end of the triggered session by sending a PEND message. PEND contains the session-id2. The flow described in Figure 65 is applicable to all positioning methods, however, individual steps within the flows are optional: Step K is not performed for cell-id based positioning methods. Steps H, I and J may or may not be performed for cell-id based positioning methods. In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the HSLP is required to calculate a position estimate. Interaction with the H-SLP is only required for GPS assistance data update in which case steps G to M are performed.
7.3.2
OMA-TS-ILP-V2_0_1-20121205-A
Page 199 (295)
V-SLC
V-SPC
H-SLP
Target SET
A B C D E F G H RLP SSRLIR(SUPL TRIGGERED START) PREQ(session-id2, lid, SET capabilities, triggerparams) LT1 PRES(session-id2) RLP SSRLIA(SUPL TRIGGERED RESPONSE) ST3
Routing Info
SUPL TRIGGERED START(session-id, trigger_type=area event, lid, SET capabilities, trigger_params) UT1
I J K L M
SUPL TRIGGERED RESPONSE(session-id, posmethod)
PMESS(session-id2, RRLP/RRC/TIA-801/LPP) RLP SSRP(SUPL POS) RLP SSRP(SUPL POS) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)
SUPL POS SUPL POS
O P Q R
PRPT(session-id2, position) RLP SSRP(SUPL REPORT) SUPL REPORT(session-id, position)

UT3
S T U V W RLP SSRP(SUPL END) PEND(session-id2)
position fix
Figure 66: SET Initiated Area Event Trigger Service Roaming Successful Case Proxy with V-SLP positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for an area event triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLP and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in
OMA-TS-ILP-V2_0_1-20121205-A
Page 200 (295)
this case area event), Location ID (lid) and area event trigger parameters. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLP verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. Based on the received lid or other mechanisms, the H-SLP determines the V-SLC and sends an RLP SSRLIR including the SUPL TRIGGERED START message to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. The area event trigger parameters such as area information requested by SUPL Agent for the area event triggered session MAY be included in this message by the H-SLP. E. The V-SLC requests service from the V-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY optionally contain the QoP. The V-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. F. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES.
G. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the VSLP MAY determine the posmethod. If the V-SPC included a list of supported posmethods in step F, the chosen posmethod SHALL be on this list. If required for the posmethod, the V-SLP SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The V-SLC responds with a SUPL TRIGGERED RESPONSE tunnelled over RLP in a SSRLIA message back to the H-SLP that it is capable of supporting this request. The SUPL TRIGGERED RESPONSE contains at least the sessionid and posmethod. H. The H-SLP forwards the SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE contains the session-id but no H-SLP address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL TRIGGERED RESPONSE also contains the posmethod. The SET and the H-SLP MAY release the secure connection. I. When the area event trigger in the SET indicates that a position fix has to be calculated the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position is received in the SUPL POS INIT message that meets any required QoP, the H-SLP MAY directly proceed to step Q and not engage in a SUPL POS session. The H-SLP forwards the SUPL POS INIT message to the V-SLP over the RLP tunnel in an SSRP message. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the V-SLP MAY directly proceed to step P and not engage in a SUPL POS session.
J.
K. The V-SLC sends a PINIT message to the V-SPC including session-id2, location id and SET capabilities. The VSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the V-SPC in step F, or a different posmethod of the V-SLCs choosing, as long as it is one supported by the V -SPC. Based on the PINIT message including the SET capabilities, the V-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the V-SLC, the V-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the V-SPC shall choose any posmethod in line with the SET capabilities which was approved by the V-SLC in step E. If a coarse position
OMA-TS-ILP-V2_0_1-20121205-A
Page 201 (295)
calculated based on information received in the PINIT message is available that meets any required QoP, the V-SPC MAY directly proceed to step O and not engage in a SUPL POS session. L. If the V-SPC cannot translate the lid received in step K into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the V-SPC can perform the translation from lid into coarse position itself. M. This step is conditional and only occurs if step L was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets any required QoP, the V-SPC MAY directly proceed to step R and not engage in a SUPL POS session. N. The SET and the V-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SPC and the V-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the V-SLC and the H-SLC using SUPL POS over RLP tunnel messages. The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages. The flow sequence PMESS RLP SSRP(SUPL POS) SUPL POS SUPL POS RLP SSRP(SUPL POS) PMESS is conceptually shown in dotted lines. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the V-SPC (SET-Based). O. Once the position calculation is complete, the V-SPC sends a PRPT message to the V-SLC. PRPT contains the session-id2 and the position result if calculated in the V-SPC. P. Once the position calculation is complete, the V-SLC sends a SUPL REPORT message in an RLP tunnel using an SSRP message to the H-SLP. The SUPL REPORT message includes the position result if the position estimate is calculated in the V-SLP and therefore needs to be sent to the SET. Q. The H-SLP forwards the SUPL REPORT message to the SET. The SET and the H-SLP MAY release the secure connection. The SUPL REPORT message includes the position result if the position estimate is calculated in the V-SLP (or the H-SLP) and therefore needs to be sent to the SET. R. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met. S. If the area event was triggered the SET forwards the calculated position estimate to the internal SUPL Agent.
T. If the SET decides to end the triggered session the SET proceeds to step U. Otherwise whenever the area event trigger mechanism in the SET indicates that a new position fix has to be performed, steps I to S are repeated. U. The SET ends the triggered session by sending a SUPL END message to the H-SLP. V. The H-SLP informs the V-SLC about the end of the area event triggered session by sending a SUPL END message using an RLP SSRP tunnel message W. The V-SLC ends the area event triggered session with the V-SPC by sending a PEND message. PEND contains the session-id2. The flow described in Figure 66 is applicable to all positioning methods, however, individual steps within the flows are optional: Step N is not performed for cell-id based positioning methods. Steps K, L and M may or may not be performed for cell-id based positioning methods.
OMA-TS-ILP-V2_0_1-20121205-A
Page 202 (295)
In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the HSLP/V-SLP is required to calculate a position estimate. Interaction with the H-SLP/V-SLP is only required for GPS assistance data update in which case steps I to Q are performed.
7.3.3
V-SLP
H-SLC
H-SPC
Target SET
A B C D E F LT1 G H
SUPL TRIGGERED START(session-id, trigger_type=area event, lid, SET capabilities, trigger_params)

Routing Info
RLP SSRLIR(SUPL TRIGGERED START) ST3 RLP SSRLIA(SUPL TRIGGERED RESPONSE) PREQ(session-id2, lid, SET capabilities, triggerparams) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod)
UT1
I J K L
N O P
PRPT(session-id2, position) SUPL REPORT(session-id, position)
UT3
Q R
position fix
S T U RLP SSRP(SUPL END)
PEND(session-id2)
Figure 67: SET Initiated Area Event Trigger Service Roaming Successful Case Proxy with H-SLP positioning
OMA-TS-ILP-V2_0_1-20121205-A
Page 203 (295)
NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for an area event triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case area event), Location ID (lid) and area event trigger parameters. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. Based on the received lid or other mechanisms, the H-SLC determines the V-SLP and sends an RLP SSRLIR including a SUPL TRIGGERED START to the V-SLP to inform the V-SLP that an area event triggered session is in the progress of being initiated with the H-SLP. The area event trigger parameters such as area information requested by SUPL Agent for the area event triggered session MAY be included in this message by the H-SLC. E. The V-SLP acknowledges the RLP request received in step D with a SUPL TRIGGERED RESPONSE message which is carried inside an RLP SSRLIA message. F. The H-SLC requests service from the H-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved.
G. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. H. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the HSLP MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step G, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLP SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC sends a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE contains the sessionid but no H-SLP address, to indicate to the SET that a new connection SHALL NOT be established. The SUPL TRIGGERED RESPONSE also contains the posmethod. The SET and the H-SLC MAY release the secure connection. I. When the area event trigger in the SET indicates that a position fix has to be calculated the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SLP. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position is received in the SUPL POS INIT message that meets any required QoP, the H-SLC MAY directly proceed to step O and not engage in a SUPL POS session. To obtain a coarse position based on lid received in step I, the H-SLC sends an RLP SRLIR message to the V-SLP.
J.
K. The V-SLP translates the received lid into a position estimate and returns the result to the H-SLC in an RLP SRLIA message.
OMA-TS-ILP-V2_0_1-20121205-A
Page 204 (295)
If the received position meets any required QoP, the H-SLC MAY directly proceed to step O and not engage in a SUPL POS session. L. The H-SLC sends a PINIT message to the H-SPC including session-id2, location id and SET capabilities. The HSLC MAY include a posmethod in the PINIT. This posmethod may either be the posmethod recommended by the H-SPC in step G, or a different posmethod of the H-SLCs choosing, as long as it is one supported by the H -SPC. Based on the PINIT message including the SET capabilities, the H-SPC SHALL determine the posmethod. If a posmethod has been included in the PINIT by the H-SLC, the H-SPC SHALL use that posmethod, unless it does not meet the SET capabilities. If no posmethod parameter was included in the PINIT, the H-SPC shall choose any posmethod in line with the SET capabilities which was approved by the H-SLC in step F. M. The SET and the H-SPC exchange several successive positioning procedure messages. Thereby the positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SPC and the H-SLC using PMESS messages. PMESS includes the session-id2 and the positioning procedure payload (RRLP/RRC/TIA-801/LPP). The positioning procedure payload (RRLP/RRC/TIA-801/LPP) is transferred between the H-SLC and the SET using SUPL POS messages (the PMESS SUPL POS SUPL POS PMESS message exchange is conceptually shown in dotted lines). The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance obtained from the H-SPC (SET-Based). N. Once the position calculation is complete, the H-SPC sends a PRPT message to the H-SLC. PRPT contains the session-id2, the position result if calculated in the H-SPC and the number of the fix. O. Once the position calculation is complete, the H-SLC sends a SUPL REPORT message to the SET. The SUPL REPORT message includes the position result if the position estimate is calculated in the H-SLP and therefore needs to be sent to the SET. P. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met. Q. If the area event was triggered the SET forwards the calculated position estimate to the internal SUPL Agent. R. If the SET decides to end the triggered session the SET proceeds to step s. Otherwise whenever the area event trigger mechanism in the SET indicates that a new position fix has to be performed, steps I to Q are repeated. S. The SET ends the triggered session by sending a SUPL END message to the H-SLC.
T. The H-SLP informs the V-SLP about the end of the triggered session by sending a SUPL END message in an RLP SSRP tunnel message. U. The H-SLC informs the H-SPC about the end of the area event triggered session in a PEND message. PEND contains session-id2. The flow described in Figure 67 is applicable to all positioning methods, however, individual steps within the flows are optional: Step M is not performed for cell-id based positioning methods. In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the HSLP/V-SLP is required to calculate a position estimate. Interaction with the H-SLP/V-SLP is only required for GPS assistance data update in which case steps I to O are performed.
7.4
This section describes the flows for SET Initiated area event triggered services for non-proxy mode. The trigger thereby resides in the SET and the SET makes the decision if an area event occurred based on continuously repeated position determinations.
OMA-TS-ILP-V2_0_1-20121205-A
Page 205 (295)
7.4.1

A B C D E F
Routing Info
LT1
PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, H-SPC address, SPC_SET_Key, SPC-TID)
PLRES(session-id2, posresult) PT2 UT2 SUPL POS(session id, RRLP/RRC/TIA-801/LPP) PRPT(session-id2, position) SUPL REPORT(session-id, position)
K L M
UT3
N O P Q PEND(session-id2)
position fix
Figure 68: SET Initiated Area Event Trigger Service Non-Roaming Successful Case Non-Proxy Mode NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for an area event triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case area event), Location ID (lid) and area event trigger parameters. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently not SUPL Roaming.
OMA-TS-ILP-V2_0_1-20121205-A
Page 206 (295)
NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside the scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. The H-SLC requests service from the H-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The H-SLC also creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication. SPC_SET_Key and SPC-TID are forwarded to the H-SPC in the PREQ message. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved. E. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. F. Consistent with the SUPL TRIGGERED START message including the SET capabilities of the SET, the H-SLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step E, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC SHALL respond with a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE message contains session-id, posmethod, H-SPC address and SPC_SET_Key and SPC-TID to be used for mutual HSPC/SET authentication. The SET and the H-SLP MAY release the secure connection.
G. When the area event trigger in the SET indicates that a position fix has to be calculated the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SPC. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the H-SPC MAY directly proceed to step K and not engage in a SUPL POS session. H. If the H-SPC cannot translate the lid received in step G into a coarse position, the H-SPC sends a PLREQ message to the H-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the H-SPC can perform the translation from lid into coarse position itself. I. This step is conditional and only occurs if step H was performed. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets any required QoP, the H-SPC MAY directly proceed to step K and not engage in a SUPL POS session. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step D, the H-SPC SHALL only choose an approved method.The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance data obtained from the H-SPC (SET-Based).
J.
K. The H-SPC may optionally inform the H-SLC about the position fix or assistance data delivery process performed in step J. To this end the H-SPC sends a PRPT message to the H-SLC. PRPT contains at least session-id2. L. Once the position calculation is complete the H-SPC sends a SUPL REPORT message to the SET. The SET MAY release the secure connection to the H-SPC. The SUPL REPORT message includes the position result if the position estimate is calculated in the H-SPC and therefore needs to be sent to the SET. M. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met.
OMA-TS-ILP-V2_0_1-20121205-A
Page 207 (295)
N. If the area event was triggered the SET forwards the calculated position estimate to the internal SUPL Agent. O. If the SET decides to end the triggered session the SET proceeds to step P. Otherwise whenever the area event trigger mechanism in the SET indicates that a new position fix has to be performed, steps G to N are repeated. P. The SET ends the triggered session by sending a SUPL END message to the H-SPC. Q. The H-SPC informs the H-SLC about the end of the triggered session by sending a PEND message. PEND contains the session-id2. The flow described in Figure 68 is applicable to all positioning methods, however, individual steps within the flows are optional: Step J is not performed for cell-id based positioning methods. Steps H and I may or may not be performed for cell-id based positioning methods. In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the HSLP is required to calculate a position estimate. Interaction with the H-SLP is only required for GPS assistance data update in which case steps G to L are performed.
7.4.2
OMA-TS-ILP-V2_0_1-20121205-A
Page 208 (295)
H-SLC
V-SLC
V-SPC
Target SET
A B C D E F G H ST3
Routing Info
RLP SSRLIR(SUPL TRIGGERED START, SPC_SET_Key, SPC-TID) PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2)
LT1
RLP SSRLIA(SUPL TRIGGERED RESPONSE) SUPL TRIGGERED RESPONSE(session-id, posmethod, V-SPC address, SPC_SET_Key, SPC-TID)
I J K
L PRPT(session-id2, position)
M N O
UT3
P Q R S T RLP SSRP(SUPL END) PEND(session-id2)
position fix
Figure 69: SET Initiated Area Event Trigger Service Roaming Successful Case Non-Proxy with V-SPC positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for an area event triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case area event), Location ID (lid) and area event trigger parameters. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently SUPL Roaming.
OMA-TS-ILP-V2_0_1-20121205-A
Page 209 (295)
NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. Based on the received lid or other mechanisms, the H-SLC determines the V-SLC and sends an RLP SSRLIR including the SUPL TRIGGERED START message to the V-SLC to inform the V-SLC that the target SET will initiate a SUPL positioning procedure. The area event trigger parameters such as area information requested by SUPL Agent for the area event triggered session MAY be included in this message by the H-SLC. The H-SLC also creates SPC_SET_Key and SPC-TID to be used for mutual V-SPC/SET authentication. SPC_SET_Key and SPCTID are sent to the V-SLC as part of the RLP SSRLIR message. E. The V-SLC requests service from the V-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The PREQ MAY also optionally contain the QoP. The PREQ message also contains SPC_SET_Key and SPC-TID used for mutual V-SPC/SET authentication. The V-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the V-SPC SHALL assume that all its available positioning methods have been approved. F. The V-SPC accepts the service request for a SUPL session from the V-SLC with a PRES message containing the session-id2. The V-SPC MAY include a preferred positioning method in the PRES. The V-SPC MAY include its supported positioning methods in the PRES.
G. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the VSLC MAY determine the posmethod. If the V-SPC included a list of supported posmethods in step F, the chosen posmethod SHALL be on this list. If required for the posmethod, the V-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The V-SLC responds with a SUPL TRIGGERED RESPONSE tunnelled over RLP in a SSRLIA message back to the H-SLC that it is capable of supporting this request. The SUPL TRIGGERED RESPONSE contains at least the sessionid, posmethod and the V-SPC address. H. The H-SLC sends a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE message contains session-id, posmethod, V-SPC address and SPC_SET_Key and SPC-TID for mutual V-SPC/SET authentication. The SET and the H-SLC MAY release the secure connection. I. When the area event trigger in the SET indicates that a position fix has to be calculated the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the V-SPC. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position calculated based on information received in the SUPL POS INIT message is available (e.g. a cell-id based position fix) that meets any required QoP, the V-SPC MAY directly proceed to step M and not engage in a SUPL POS session. If the V-SPC cannot translate the lid received in step I into a coarse position, the V-SPC sends a PLREQ message to the V-SLC. The PLREQ message contains the session-id2 and the lid. This step is optional and not required if the VSPC can perform the translation from lid into coarse position itself.
J.
K. This step is conditional and only occurs if step J was performed. The V-SLC reports the coarse position result back to the V-SPC in a PLRES message. PLRES contains the session-id2 and the posresult. If the coarse position meets any required QoP, the V-SPC MAY directly proceed to step M and not engage in a SUPL POS session. L. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the V-SPC SHALL determine the posmethod. If the V-SLC included its approved positioning methods in step E, the V-SPC SHALL only choose an approved method. The SET and the V-SPC exchange several successive positioning procedure messages. The V-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance data obtained from the V-SPC (SET-Based).
OMA-TS-ILP-V2_0_1-20121205-A
Page 210 (295)
M. The V-SPC may optionally inform the V-SPC about the position fix or assistance data delivery process performed in step L. To this end the V-SPC sends a PRPT message to the V-SLC. PRPT contains at least session-id2 N. Once the position calculation is complete, the V-SPC sends a SUPL REPORT message to the SET. The SET and the H-SPC MAY release the secure connection. The SUPL REPORT message includes the position result if the position estimate is calculated in the V-SPC and therefore needs to be sent to the SET. O. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met. P. If the area event was triggered the SET forwards the calculated position estimate to the internal SUPL Agent. Q. If the SET decides to end the triggered session the SET proceeds to step R. Otherwise whenever the area event trigger mechanism in the SET indicates that a new position fix has to be performed, steps I to P are repeated. R. The SET ends the triggered session by sending a SUPL END message to the V-SPC. S. The V-SPC informs the V-SLC about the end of the triggered session by sending a PEND message. PEND contains the session-id2.
T. The V-SLC informs the H-SLC about the end of the triggered session by sending a SUPL END message using an RLP SSRP tunnel message to the H-SLC. The flow described in Figure 69 is applicable to all positioning methods, however, individual steps within the flows are optional: Step L is not performed for cell-id based positioning methods. Steps J and K may or may not be performed for cell-id based positioning methods. In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the HSLP is required to calculate a position estimate. Interaction with the H-SLP is only required for GPS assistance data update in which case steps I to N are performed.
7.4.3

OMA-TS-ILP-V2_0_1-20121205-A
Page 211 (295)
V-SLC
H-SLC
H-SPC
Target SET
A B C D E F LT1 G H
SUPL TRIGGERED START(session-id, trigger_type=area event, lid, SET capabilities, trigger_params)

Routing Info
RLP SSRLIR(SUPL TRIGGERED START) ST3 RLP SSRLIA(SUPL TRIGGERED RESPONSE) PREQ(session-id2, lid, SET capabilities, triggerparams, SPC_SET_Key, SPC-TID) PRES(session-id2) SUPL TRIGGERED RESPONSE(session-id, posmethod, H-SPC Address, SPC_SET_Key, SPC-TID) UT1
I J K L M N O P Q
PT2
UT2
PRPT(session-id2, position) SUPL REPORT(session-id, position) UT3
R S T U V RLP SSRP(SUPL END)
position fix
PEND(session-id2)
Figure 70: SET Initiated Area Event Trigger Service Roaming Successful Case Non-Proxy with H-SPC positioning NOTE 1: See Appendix C for timer descriptions. A. The SUPL Agent on the SET receives a request for an area event triggered service from an application running on the SET. The SET takes eighbour e action establishing or resuming a secure connection. B. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL TRIGGERED START message to start a positioning session with the
OMA-TS-ILP-V2_0_1-20121205-A
Page 212 (295)
H-SLP. The SUPL TRIGGERED START message contains session-id, SET capabilities, trigger type indicator (in this case area event), Location ID (lid) and area event trigger parameters. The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SET-Based A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). C. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0. However, there are various environment dependent mechanisms. D. Based on the received lid or other mechanisms, the H-SLC determines the V-SLP and sends an RLP SSRLIR including a SUPL TRIGGERED START message to the V-SLC to inform the V-SLP that an area event triggered session is in the progress of being initiated with the H-SLP. The area event trigger parameters such as area information requested by SUPL Agent for the area event triggered session MAY be included in this message by the H-SLC. E. The V-SLC acknowledges the RLP request received in step D with a SUPL TRIGGERED RESPONSE message which is carried inside an RLP SSRLIA message. F. The H-SLC requests service from the H-SPC for an area event triggered SUPL session by sending a PREQ message containing the session-id2, the SET capabilities, the triggerparams and the lid. The H-SLC also creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication. SPC_SET_Key and SPC-TID are forwarded to the H-SPC in the PREQ message. The PREQ MAY also optionally contain the QoP. The H-SLC MAY include its approved positioning methods for this session in the PREQ. If the approved positioning methods are not included, the H-SPC SHALL assume that all its available positioning methods have been approved.
G. The H-SPC accepts the service request for a SUPL session from the H-SLC with a PRES message containing the session-id2. The H-SPC MAY include a preferred positioning method in the PRES. The H-SPC MAY include its supported positioning methods in the PRES. H. Consistent with the SUPL TRIGGERED START message including posmethod(s) supported by the SET, the HSLC MAY determine the posmethod. If the H-SPC included a list of supported posmethods in step G, the chosen posmethod SHALL be on this list. If required for the posmethod, the H-SLC SHALL use the supported positioning protocol (e.g., RRLP, RRC, TIA-801 or LPP) from the SUPL TRIGGERED START message. The H-SLC sends a SUPL TRIGGERED RESPONSE message to the SET. The SUPL TRIGGERED RESPONSE message contains session-id, posmethod, H-SPC address and SPC_SET_Key and SPC-TID for mutual H-SPC/SET authentication. The SET and the H-SLC MAY release the secure connection. I. When the area event trigger in the SET indicates that a position fix has to be calculated the SET takes appropriate action establishing or resuming a secure connection. The SET then sends a SUPL POS INIT message to start a positioning session with the H-SPC. The SUPL POS INIT message contains at least session-id, SET capabilities and Location ID (lid). The SET capabilities include the supported positioning methods (e.g., SET-Assisted A-GPS, SETBased A-GPS) and associated positioning protocols (e.g., RRLP, RRC, TIA-801 or LPP). The SET MAY optionally provide NMR specific for the radio technology being used (e.g., for GSM: TA, RXLEV). The SET MAY provide its position, if this is supported. The SET MAY include the first SUPL POS element in the SUPL POS INIT message. The SET MAY set the Requested Assistance Data element in the SUPL POS INIT. If a position is received in the SUPL POS INIT message that meets any required QoP, the H-SPC MAY directly proceed to step O and not engage in a SUPL POS session. The H-SPC sends a PLREQ message to the H-SLC to request translation of the received lid into a coarse position. The PLREQ message contains the session-id2 and the lid.
J.
K. To obtain a coarse position the H-SLC sends an RLP SRLIR message to the V-SLP. L. The V-SLC translates the received lid into a position estimate and returns the result to the H-SLC in an RLP SRLIA message. M. The H-SLC reports the coarse position result back to the H-SPC in a PLRES message. PLRES contains the sessionid2 and the posresult. If the coarse position meets any required QoP, the H-SPC MAY directly proceed to step O and not engage in a SUPL POS session.
OMA-TS-ILP-V2_0_1-20121205-A
Page 213 (295)
N. Based on the SUPL POS INIT message including posmethod(s) supported by the SET the H-SPC SHALL determine the posmethod. If the H-SLC included its approved positioning methods in step F, the H-SPC SHALL only choose an approved method. The SET and the H-SPC exchange several successive positioning procedure messages. The H-SPC calculates the position estimate based on the received positioning measurements (SET-Assisted) or the SET calculates the position estimate based on assistance data obtained from the H-SPC (SET-Based). O. The H-SPC may optionally inform the H-SPC about the position fix or assistance data delivery process performed in step N. To this end the H-SPC sends a PRPT message to the H-SLC. PRPT contains at least session-id2. P. Once the position calculation is complete, the H-SPC sends a SUPL REPORT message to the SET. The SET and the H-SPC MAY release the secure connection. The SUPL REPORT message includes the position result if the position estimate is calculated in the V-SPC and therefore needs to be sent to the SET. Q. The SET compares the calculated position estimate with the event area to check if the event trigger condition has been met. R. If the area event was triggered the SET forwards the calculated position estimate to the internal SUPL Agent. S. If the SET decides to end the triggered session the SET proceeds to step T. Otherwise whenever the area event trigger mechanism in the SET indicates that a new position fix has to be performed, steps I to R are repeated.
T. The SET ends the triggered session by sending a SUPL END message to the H-SPC. U. The H-SPC informs the H-SLC about the end of the triggered session by sending a PEND message. PEND contains the session-id2. V. The H-SLC informs the V-SLC about the end of the triggered session by sending a SUPL END message using an RLP SSRP tunnel message to the V-SLC. The flow described in Figure 70 is applicable to all positioning methods, however, individual steps within the flows are optional: Step N is not performed for cell-id based positioning methods. Steps J, K, L and M may or may not be performed for cell-id based positioning methods. In A-GPS SET Based mode where no GPS assistance data is required from the network, no interaction with the HSLP/V-SLP is required to calculate a position estimate. Interaction with the H-SLP/V-SLP is only required for GPS assistance data update in which case steps I to P are performed.
7.5
Network/SET capabilities Change for Area Event Triggered Scenarios
This procedure which is defined in [SUPL 2 ULP TS] section 5.1.14 does not have implications for ILP since no routing info mechanism (i.e. to determine the SET s serving network) is defined in SUPL 2.0 (considered out of scope for SUPL 2.0) and a change in SET capabilities does not require additional ILP messaging.
OMA-TS-ILP-V2_0_1-20121205-A
Page 214 (295)
8. Detailed Flows SLC/SPC Heartbeat

8.1 Successful PALIVE exchange
SLC SPC
PALIVE (session-id2)
PALIVE (session-id2) B
Figure 71: Successsful PALIVE exchange NOTE 1: This callflow applies both to PALIVE exchanges between the H-SLC and H-SPC and between the V-SLC and V-SPC. NOTE 2: The use of guard timers for the PALIVE exchange is considered implementation dependent and out of scope for ILP. A. The SLC issues a PALIVE message to the SPC. The PALIVE message contains a session-id2 with an SLC Session ID. If a SET Session ID or SPC Session ID are included in the session-id2 parameter, they will be ignored B. The SPC SHALL respond with a PALIVE. The PALIVE message contains at least a session-id2. The SPC MAY include an SPCStatusCode in the PALIVE message.
8.2
PALIVE Error Handling

SLC SPC
PALIVE (session-id2)
PEND (session-id2, StatusCode) B
Figure 72: PALIVE Error handling NOTE 1: This callflow covers the exception handling for the Successful PALIVE Exchange shown in 8.1. It applies it situations where the PALIVE arriving at the SPC cannot be decoded, contains a protocol error or is an unsupported version of ILP. NOTE 2: This callflow applies both to PALIVE exchanges between the H-SLC and H-SPC and between the V-SLC and V-SPC. NOTE 3: The use of guard timers for the PALIVE exchange is considered implementation dependent and out of scope for ILP.
OMA-TS-ILP-V2_0_1-20121205-A
Page 215 (295)
A. The SLC issues a PALIVE message to the SPC. The PALIVE message contains a session-id2 with an SLC Session ID. If a SET Session ID or SPC Session ID are included in the session-id2 parameter, they will be ignored B. If the SPC cannot decode the incoming PALIVE message, or if it contains a protocol error or is a version of ILP that the SPC does not support, the SPC SHALL respond with a PEND with an appropriate Status Code.
OMA-TS-ILP-V2_0_1-20121205-A
Page 216 (295)
9. Security Considerations
This section describes the security considerations of ILP.
9.1
SLC-SPC Security
The connection between the SLC and SPC SHALL be secure. The specifics of which methods are used to secure the connection are beyond the scope of this document
9.2
Non-Proxy Mode Mutual Authentication Key Refresh Mechanism
The keys used for mutual authentication in non-proxy mode (SPC_SET_Key, SPC-TID, SPC_SET_Key_lifetime) require a refresh mechanism for triggered scenarios. For immediate scenarios, no refresh mechanism is required since the duration of an immediate SUPL session never exceeds the lifetime of the mutual authentication keys SPC_SET_Key and SPC-TID and each new authentication keys are generated at the beginning of each immediate SUPL session. The following sections describe a key refresh mechanism for non-roaming and roaming scenarios.
9.2.1
Mutual Authentication Key Refresh Mechanism for non roaming

SPC_SET_Key_lifetime expires Data Connection Setup
B C D E LT1 F G SUPL AUTH RESP(session-id, SPC_SET_Key, SPC-TID) SUPL AUTH REQ(session-id) PREQ(session-id2, SPC_SET_Key, SPC-TID) PRES(session-id2)
UT4
Figure 73: Mutual authentication key refresh mechanism for non roaming NOTE 1: See Appendix C for timer descriptions. A. The SET and the H-SLP are engaged in a non-proxy triggered SUPL session. B. A fixed (and configurable) amount of time before SPC_SET_Key_lifetime expires, the SET requires a new SPC_SET_Key and SPC-TID to be used for mutual SET/H-SPC authentication. C. The SET takes eighbour e action establishing or resuming a secure connection.
OMA-TS-ILP-V2_0_1-20121205-A
Page 217 (295)
D. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL AUTH REQ message to the H-SLC. The SUPL AUTH REQ message contains the session-id. E. The H-SLC creates SPC_SET_Key and SPC-TID to be used for mutual H-SPC/SET authentication and optionally also a new SPC_SET_Key_lifetime. The H-SLC forwards these keys to the H-SPC in a PREQ message. PREQ contains session-ids, SPC_SET_Key, SPC-TID and optionally SPC_SET_Key_lifetime. F. The H-SPC confirms the receipt of the PREQ message with a PRES message.
G. The H-SLC forwards SPC_SET_Key, SPC-TID and optionally SPC_SET_Key_lifetime to the SET in a SUPL AUTH RESP message. The SET MAY release the IP connection to the H-SLC.
9.2.2
Mutual Authentication Key Refresh Mechanism for roaming with VSLP

H-SLC V-SLC V-SPC Target SET
SPC_SET_Key_lifetime expires
C D E
Routing Info
SUPL AUTH REQ(session-id)
F G
RLP TSRLRR(SPC_SET_Key, SPC-TID) UT4 PREQ(session-id2, SPC_SET_Key, SPC-TID) ST3 LT1 PRES(session-id2) RLP TSRLRA
H I J
SUPL AUTH RESP(session-id, V-SPC address, SPC_SET_Key, SPC-TID)
Figure 74: Mutual authentication key refresh mechanism for roaming with V-SLP NOTE 1: See Appendix C for timer descriptions. A. The SET and the H/V-SLP are engaged in a non-proxy triggered SUPL session. B. A fixed (and configurable) amount of time before SPC_SET_Key_lifetime expires, the SET requires a new SPC_SET_Key and SPC-TID to be used for mutual SET/V-SPC authentication. C. The SET takes eighbour e action establishing or resuming a secure connection.
OMA-TS-ILP-V2_0_1-20121205-A
Page 218 (295)
D. The SUPL Agent on the SET uses the default address provisioned by the Home Network to establish a secure connection to the H-SLC and sends a SUPL AUTH REQ message to the H-SLC. The SUPL AUTH REQ message contains the session-id. E. The H-SLC verifies that the target SET is currently SUPL Roaming. NOTE 2: The specifics for determining if the SET is SUPL Roaming or not is considered outside scope of SUPL 2.0 (there are various environment dependent mechanisms). F. The H-SLC creates SPC_SET_Key and SPC-TID to be used for mutual V-SPC/SET authentication and optionally also a new SPC_SET_Key_lifetime. The H-SLC forwards these keys to the V-SPC in a RLP SSRLIR message.
G. The V-SLC forwards SPC_SET_Key, SPC-TID and optionally SPC_SET_Key_lifetime to the V-SPC in a PREQ message. H. The V-SPC confirms the receipt of the PREQ message with a PRES message. I. J. The V-SLC responds to the H-SLC with an RLP RSRLRA message. The H-SLC forwards V-SPC address, SPC_SET_Key, SPC-TID and optionally SPC_SET_Key_lifetime to the SET in a SUPL AUTH RESP message. The SET MAY release the IP connection to the H-SLC.
9.2.3
Mutual Authentication Key Refresh Mechanism for roaming with HSLP
The key refresh mechanism for roaming with H-SLP follows the exact same flow as for non-roaming (section 9.2.1).
OMA-TS-ILP-V2_0_1-20121205-A
Page 219 (295)
10.Protocols and Interfaces

The encoding for the ILP protocol SHALL be ASN.1 [ASN.1]. The encoding is BASIC-PER, unaligned encoding [PER.1]. The transport protocol between SLC and SPC SHALL be TCP/IP.
10.1 TCP/IP
An Llp reference point MAY provide two socket ports for operation, one for encryption with TLS 1.1 [TLS] and one without. The port numbers for ILP messages transported over TCP SHALL be as registered with IANA (Internet Assigned Numbers Authority). The port numbers are:
oma-ilp oma-ilp-s
7276/tcp 7277/tcp
OMA Internal Location Protocol OMA Internal Location Secure Protocol
Note: An SLC or SPC MAY choose to introduce other technologies for secure transfer. Any such technology SHALL be provided over a different port than the two mentioned above.
10.2 Llp
The function of the Llp reference point is logically separated into Positioning Control and Positioning Data .
10.2.1
Positioning Control
The Positioning Control interface is used in the establishment, maintenance and clearing of sessions between the SLC and SPC. It enables the SLC and SPC to perform Position Calculation Function. Table 1 shows the messages of the Llp Positioning Control interface.
Message Name Description
PREQ PRES PRPT PLREQ PLRES PAUTH PALIVE
The PREQ message is used by the SLC to request a SUPL session of the SPC. The PRES message is the response to a PREQ message and sent by the SPC to the SLC. The PRPT message is used by the SPC to report a position estimate or an error to the SLC. The PLREQ message is used by the SLC (or SPC) to request a cell-id translation into coarse position estimate from the SPC (or SLC). The PLRES message is used by the SPC (or SLC) to report a coarse position estimate based on cell-id translation to the SLC (or SPC). The PAUTH message is used by the SLC to send SUPL authentication parameters to the SPC. The PALIVE message is used by the SLC to verify the operational status of the SPC. The SLC may send the PALIVE message at any time. The SPC must then respond with a corresponding PALIVE message. The PEND message is used by the SLC (or SPC) to inform the SPC (or SLC) about the end of a SUPL session. Table 1: Llp Positioning Control
PEND
OMA-TS-ILP-V2_0_1-20121205-A
Page 220 (295)
10.2.2
Positioning Data
The Positioning Data interface is used to transport information used for the position calculation. This interface is used in proxy mode only. Table 2 shows the messages of the Positioning Data interface.
Message Name Description
PMESS PINIT
The PMESS message is bidirectional and is used to carry RRLP/RRC/TIA-801/LPP payload. The PINIT message is used by the SLC to initiate the positioning protocol session (RRLP/RRC/TIA-801/LPP) with the SPC. Table 2: Llp Positioning Data
For additional requirements concerning the use of positioning protocols and position determination messages, refer to [SUPL2 ULP TS].
OMA-TS-ILP-V2_0_1-20121205-A
Page 221 (295)
11.ILP Message Definitions (Normative)

This section contains a normative description of the ILP messages. All messages in ILP contain a common part and a message specific part.
11.1 Common Part

Parameter Message Length Presence Description The length of the entire ILP Message in octets. Note: The first two octets of a PER encoded ILP message contains the length of the entire message. These octets are set to the Message Length when the PER encoding is complete and the entire message length is known. Version of the ILP protocol, in the form Major, Minor, Service Indicator The unique Session ID2 This parameter contains one of the messages defined in ILP. Defined messages are: M Table 3: Common Part PREQ PRES PRPT PLREQ PLRES PINIT PAUTH PALIVE PEND PMESS
Version Session ID2 Message Payload
M M
11.2 Message Specific Part

The message specific part contains further parameters that are unique for each ILP message. The following sections describe the message specific part of ILP messages.
OMA-TS-ILP-V2_0_1-20121205-A
Page 222 (295)
11.2.1
PREQ
Presence M O Values/description Indicates whether proxy or non-proxy mode is used. Defines the list of positioning technologies approved by the SLC, which can be A-GNSS SET assisted, A-GNSS SET Based, Autonomous GNSS, EOTD, OTDOA, AFLT or Enhanced Cell ID. If this list is not present, the H-SPC SHALL assume all available positioning technologies have been approved by the SLC. Describes a globally unique cell, WLAN AP or WiMAX BS identification of the most current serving cell This parameter may contain current nonserving cell, current non-serving WLAN AP or current non-serving WiMAX BS information for the SET and/or historic serving or non-serving cell, or WLAN AP or WiMAX BS information for the SET. Defines the position estimate for the SET. This parameter is only required for triggered SUPL sessions and defines the trigger parameters. This parameter is only required for nonproxy mode for certain scenarios (not all scenarios) and is used for mutual SET H/VSPC authentication. This parameter defines the transaction ID used for mutual SET H/V-SPC authentication. It is only used for certain scenarios (not all scenarios). This parameter defines the lifetime of SPC_SET_Key. This parameter is optional. If not present, a default value of 24 hours is assumed. The units are in hours and the range is from 1 to 24 hours. Desired Quality of Position Defines the capabilities of the SET. This parameter MUST not be used for Immediate Network Initiated scenarios but MUST be used for all other scenarios. This parameter indicates whether any
The PREQ message is used by the SLC to request a SUPL session from the SPC. Parameter SLP Mode Approved Positioning Method List
Location ID
Multiple Location IDs O
Position Trigger Parameters
O CV
SPC_SET_Key
SPC-TID
SPC_SET_Key_lifetime
QoP SET Capabilities
O O
Notification Mode
OMA-TS-ILP-V2_0_1-20121205-A
Page 223 (295)
combination of notification or verification based on location is required. It is only applicable for Non-Proxy mode. If not present, the H-SPC SHALL assume notification or verification based on location is not required. Table 4: PREQ Message
11.2.2
PRES
Presence O Values/description Defines the SPCs preferred positioning method If the Preferred Positioning Method is AGNSS SET Assisted or AGNSS SET Based, the parameter GNSS Positioning Technology MUST be present to indicate the actual positioning technologies. If the Preferred Positioning Method is Autonomous GNSS, the parameter GNSS Positioning Technology MAY be present.
The PRES message is sent by the SPC in response to a PREQ message. Parameter Preferred Positioning Method
GNSS Positioning Technology
Defines the actual GNSSs allowed for AGNSS SET Assisted, AGNSS SET Based or Autonomous GNSS in the Preferred Positioning Method parameter. GPS Galileo SBAS Modernized GPS QZSS GLONASS Note: GPS MUST NOT be the only allowed GNSS in this parameter
Supported Positioning Method List Position
O O
Defines the list of positioning technologies supported by the SPC. Defines the position estimate for the SET. This parameter is used if PREQ contained a Location ID based on which the SPC calculated a position estimate. Defines the status code for error handling.
SPC Status Code
Table 5: PRES Message
OMA-TS-ILP-V2_0_1-20121205-A
Page 224 (295)
11.2.3
PRPT
Presence O Values/description Defines the position estimate for the SET. The position parameter may be omitted in error scenarios in which case the status code is present. Defines the number of the fix. Defines the status code for error handling.
The PRPT message is used by the SPC to report a position estimate. PRPT is only used for triggered services. Parameter Position
Number of fix Status Code
O O
Table 6: PRPT Message
11.2.4
PLREQ
Presence M Values/description Describes a globally unique cell , WLAN AP or WiMAX BS identification of the most current serving cell. This parameter may contain current nonserving cell, current non-serving WLAN AP or current non-serving WiMAX BS information for the SET and/or historic serving or non-serving cell, WLAN AP or WiMAX BS information for the SET according to the Supported Network Information received from the SLP.
The PLREQ message is used by the SLC (or SPC) to request a cell-id translation into a coarse position. Parameter Location ID
Multiple Location IDs
Table 7: PLREQ Message
11.2.5
PLRES
Presence O Values/description Defines either a position estimate or if no position could be calculated a status code. Can be either one single Position Result or multiple Position Results.
The PLRES message is used by the SPC (or SLC) to return a coarse position based on cell-id translation request. Parameter Position Results
Table 8: PLRES Message
OMA-TS-ILP-V2_0_1-20121205-A
Page 225 (295)
11.2.6
PINIT
The PINIT message is sent by the SLC to the SPC before the start of the positioning procedure message exchange. PINIT may optionally contain the positioning payload if the positioning protocol allows the SET to send the first message. Parameter SET Capabilities Location ID M Presence M Values/description Defines the capabilities of the SET. Describes a globally unique cell, WLAN AP or WiMAX BS identification of the most current serving cell.Defines the cell information of the SET. Defines the positioning method that the SPC SHALL use. If this is not present, the SPC MAY choose any positioning method that the SLC has previously approved. If the Positioning Method is AGNSS SET Assisted or AGNSS SET Based, the parameter GNSS Positioning Technology MUST be present to indicate the actual positioning technologies. If the Positioning Method is Autonomous GNSS, the parameter GNSS Positioning Technology MAY be present. Requested Assistance Data Defines the requested GPS and GANSS assistance data. The presence of this element indicates that the SET wants to obtain specific GPS and GANSS assistance data from the SLP. The SET might use this element in any combination of A-GPS SET assisted / A-GPS SET based/A-GANSS SET assisted/AGANSS SET based and Network initiated / SET initiated positioning. The Requested Assistance Data parameter is not applicable to TIA-801 [TIA-801] and LPP [3GPP LPP]. Position Positioning Payload O Defines the position of the SET. If a positioning protocol that allows the SET to send the first message is used, and the SUPL POS INIT contains a positioning protocol payload, the parameter also contains that payload. Any positioning protocol messages in this parameter that are not supported by the SPC SHALL be ignored by that SPC. Multiple Location IDs O This parameter may contain current nonserving cell, current non-serving WLAN AP
Positioning Method
OMA-TS-ILP-V2_0_1-20121205-A
Page 226 (295)
or current non-serving WiMAX BS information for the SET and/or historic serving or non-serving cell, WLAN AP or WiMAX BS information for the SET according to the Supported Network Information received from the SLP. UTRAN GPS Reference Time Result The UTRAN GPS Reference Time Result as measured by the SET. This parameter is sent by the SET to the SLC if available and requested by the SLC in the Supported Network Information parameter (in SUPL INIT, SUPL RESPONSE or SUPL TRIGGERED RESPONSE) if the serving cell is WCDMA/TD-SCDMA and RRLP is used as the positioning protocol. The UTRAN GANSS Reference Time Result as measured by the SET. This parameter is sent by the SET to the SLC if available and requested by the SLC in the Supported Network Information parameter (in SUPL INIT, SUPL RESPONSE or SUPL TRIGGERED RESPONSE) if the serving cell is WCDMA/TD-SCDMA and RRLP is used as the positioning protocol. Defines the actual GNSSs allowed for AGNSS SET Assisted, AGNSS SET Based or Autonomous GNSS in the Positioning Method parameter. GPS Galileo SBAS Modernized GPS QZSS GLONASS Note: GPS MUST NOT be the only allowed GNSS in this parameter. Table 9: PINIT Message
UTRAN GANSS Reference Time Result
GNSS Positioning Technology
CV
11.2.7
PAUTH
The PAUTH message is used by the SLC to send SUPL authentication parameter to the SPC. This message is only used in non-proxy mode. Parameter SPC_SET_Key SPC-TID Presence M M Values/description This parameter is used for mutual SET H/V-SPC authentication. This parameter is used for mutual SET
OMA-TS-ILP-V2_0_1-20121205-A
Page 227 (295)
H/V-SPC authentication.
This parameter defines the lifetime of SPC_SET_Key. This parameter is optional. If not present, a default value of 24 hours is assumed. The units are in hours and the range is from 1 to 24 hours.
Table 10: PAUTH Message
11.2.8
PALIVE
The PALIVE message is used by the SLC to verify the operational status of the SPC and by the SPC to respond to the SLCs query. Parameter SPC Status Code Presence CV Values/description This parameter is only required in the response of the SPC to the SLC and defines the operational status of the SPC.
Table 11: PALIVE Message
11.2.9
PEND
Presence O O Values/description Defines the position estimate for the SET. Defines the status code for error handling.
The PEND message is used by the SLC (or SPC) to inform the SPC (or SLC) about the end of a SUPL session. Parameter Position Status Code
Table 12: PEND Message
11.2.10 PMESS
The PMESS message is used for RRLP/RRC/TIA-801/LPP payload exchange between the SET and the SPC and may contain additional information such as velocity, UTRAN GPS/GANSS Reference Time Assistance or UTRAN GPS/GANSS Reference Time Result not carried within the positioning protocol payloads. Parameter Positioning Payload Velocity Presence M O Values/description The underlying TIA-801, RRLP, RRC or LPP elements. Velocity of the SET needed to overcome the lack of this information in RRLP and RRC. Defined in [3GPP GAD] The UTRAN GPS Reference Time Assistance is sent by the SLP to the SET if
UTRAN GPS Reference Time Assistance
OMA-TS-ILP-V2_0_1-20121205-A
Page 228 (295)
requested by the SET in the Requested Assistance Data parameter (in SUPL POS INIT) if the serving cell is WCDMA/TDSCDMA and RRLP is used as positioning protocol. If present, this parameter is always sent from the SPC to the SLC. UTRAN GPS Reference Time Result The UTRAN GPS Reference Time Result as measured by the SET. This parameter is sent by the SET to the SLP if available and requested by the SLP in the Supported Network Information parameter (in SUPL INIT, SUPL RESPONSE and SUPL TRIGGERED RESPONSE) if the serving cell is WCDMA/TD-SCDMA and RRLP is used as positioning protocol. If present, this parameter is always sent from the SLC to the SPC. The UTRAN GANSS Reference Time Assistance is sent by the SLP to the SET if requested by the SET in the Requested Assistance Data parameter (in SUPL POS INIT) if the serving cell is WCDMA/TDSCDMA and RRLP is used as positioning protocol. If present, this parameter is always sent from the SPC to the SLC. The UTRAN GANSS Reference Time Result as measured by the SET. This parameter is sent by the SET to the SLP if available and requested by the SLP in the Supported Network Information parameter (in SUPL INIT, SUPL RESPONSE and SUPL TRIGGERED RESPONSE) if the serving cell is WCDMA/TD-SCDMA and RRLP is used as positioning protocol. If present, this parameter is always sent from the SLC to the SPC.
UTRAN GANSS Reference Time Assistance O
UTRAN GANSS Reference Time Result
Table 13: PMESS Message
OMA-TS-ILP-V2_0_1-20121205-A
Page 229 (295)
12.Parameter Definitions (Normative)

This section contains descriptions of the parameters used in ILP messages.
12.1 Version
Parameter Version Presence Value/Description
Describes the protocol version of ILP When a ILP message is received, the receiving entity SHALL determine if the Major and Minor Versions specified in the message are supported by the receiving entity. If the Major Version and Minor Versions are not supported, the exception procedure for ILP protocol error SHALL be performed. Note that there is no requirement for backwards compatibility in ILP, unlike the mechanism used in ULP. Major Version, range: (0..255), MUST be 2 for the version described in this document Minor Version, range: (0..255), MUST be 0 for the version described in this document. Service Indicator, range: (0..255), MUST be 0 for the version described in this document.
>Maj
>Min
>Serv_ind
Table 14: Version Parameter
12.2 Session ID2

The Session ID2 SHALL be a unique value, consisting of two mandatory parts, a SLC value (SLC Session ID, see section 12.2.1) concatenated with an SPC value (SPC Session ID, see section 12.2.3). An optional SET value (SET Session ID, see section 12.2.2) MAY be included. For the SLC Session ID, the SLC SHALL reuse the values from the SLP Session ID.
OMA-TS-ILP-V2_0_1-20121205-A
Page 230 (295)
Parameter SLC Session ID SET Session ID SPC Session ID
Presence
Value/Description
M O M
Part of Session ID pertaining to the SLC Part of Session ID pertaining to the SET Part of Session ID pertaining to the SPC
Table 15: Session ID2 Parameter When sending a PREQ to the SPC, the SLC SHALL assign a value to the SLC Session ID, but the SLC SHALL not include the SPC Session ID in the message. The SPC SHALL then assign a value to the SPC Session ID when it receives the message. Any further messages SHALL contain the resultant combined Session ID for the remainder of the session. The SLC MAY add the optional SET Session ID to the session ID2 at any time.
12.2.1
SLC Session ID
Parameter Session ID Presence Value/Description
This section describes the construct of the SLP Session ID. M Session identifier, unique from SLC perspective. The SLC SHALL use the same value that it used in the SLP Session ID included in the ULP Session ID. The identity of the SLC. This parameter can be of type o o IPAddress Ipv4 Ipv6 FQDN.
SLC ID
The SLC SHALL use the same value that it used in the SLP ID included in the ULP Session ID.
Table 16: SLC Session ID Parameter
12.2.2 SET Session ID

This section describes the construct of the SET Session ID.
Session identifier, unique from SET perspective. This value SHALL be unique over all concurrently active ULP sessions on that particular SET. This value may be reused by the SET after the ULP session for which it is being used has ended.
OMA-TS-ILP-V2_0_1-20121205-A
Page 231 (295)
SET ID
SET identity value This parameter can be of type o o Table 17: SET Session ID Parameter MSISDN MDN MIN (encoded as per [TIA553] IMSI NAI IPAddress Ipv4 Ipv6
12.2.3
SPC Session ID
This section describes the construct of the SLP Session ID. M Session identifier, unique from SPC perspective. This value SHALL be unique over all concurrently active ILP sessions for that particular SPC. This value may be reused by the SP C after the ILP session for which it is being used has ended. This parameter is written into a 4octet-string. The identity of the SPC. This parameter can be of type o o IPAddress Ipv4 Ipv6 FQDN.
SPC ID
Table 18: SPC Session ID Parameter
12.3 Positioning Method

Parameter Position Method Presence Description Describes the positioning method: A-GPS SET assisted only
OMA-TS-ILP-V2_0_1-20121205-A
Page 232 (295)
A-GPS SET based only A-GPS SET assisted preferred (A-GPS SET based is the fallback mode) A-GPS SET based preferred (A-GPS SET assisted is the fallback mode) A-GNSS SET Assisted only A-GNSS SET Based only A-GNSS SET Assisted preferred (A-GANSS SET Based is the fallback mode) A-GNSS SET Based preferred (A-GANSS SET Assisted is the fallback mode) Autonomous GPS Autonomous GNSS AFLT Enhanced Cell/sector EOTD OTDOA
In case of A-GNSS SET Based, AGNSS SET Assisted, the GNSS Positioning Technology MUST be used to specify which GNSS is to be used. For Autonomous GNSS, the GNSS Positioning Technology MAY be used to specify which GNSS is to be used.. Table 19: Positioning Method Parameter
12.4 SLP Mode

Parameter SLP Mode Presence Value/Description
Describes the mode that the SLP uses. This parameter can be of type - Proxy mode - Non-proxy mode
OMA-TS-ILP-V2_0_1-20121205-A
Page 233 (295)
Table 20: SLP Mode Parameter
12.5 Location ID
Parameter Location ID Presence Values/description Defines the current serving cell, current serving WLAN AP or current serving WiMAX BS information of the SET. The following cell IDs are supported: >Status M GSM Cell Info WCDMA/TD-SCDMA Cell Info CDMA Cell Info HRPD Cell Info UMB Cell Info LTE Cell Info WLAN AP Info WiMAX BS Info
>Cell Info
Describes whether or not the cell, WLAN AP or WiMAX BS info is: Not Current, last known cell/AP/BS info Current, the present cell/AP/BS info Unknown (i.e. not known whether the cell/AP/BS id is current or not current)
NOTE: The Status parameter does NOT apply to WCDMA/TD-SCDMA optional parameters (Frequency Info, Primary Scrambling Code/Cell Parameters ID and Measured Results List). Frequency Info, Primary Scrambling Code/Cell Parameters ID and Measured Results List, if present, are always considered to be correct for the current cell. Table 21: Location ID Parameter
12.5.1
GSM Cell Info
The gsmCell parameter defines the parameter of a GSM radio cell.
OMA-TS-ILP-V2_0_1-20121205-A
Page 234 (295)
Parameter Gsm Cell Info >MCC >MNC >LAC >CI >NMR >>ARFCN >>BSIC >>RXLev >TA
Presence
Value/Description
M M M M O M M M O
GSM Cell ID Mobile Country Code, range: (0..999) Mobile Network Code, range: (0..999) Location Area Code, range: (0..65535) Cell Identity, range: (0..65535) Network Measurement Report can be present for 1 to 15 cells. ARFCN, range: (0..1023) BSIC, range: (0..63) RXLEV, range: (0..63) Timing Advance, range: (0..255)
Table 22: GSM Cell Info Parameter
12.5.2
WCDMA/TD-SCDMA Cell Info
The WCDMA/TD-SCDMA parameter defines the parameter of a WCDMA/TD-SCDMA radio cell.
OMA-TS-ILP-V2_0_1-20121205-A
Page 235 (295)
Parameter WCDMA/TD-SCDMA Cell Info >MCC >MNC >UC-ID
Presence
Value/Description
M M M
WCDMA/TD-SCDMA Cell ID Mobile Country Code, range: (0..999) Mobile Network Code, range: (0..999) Cell Identity, range: (0..268435455). NOTE: this information element contains the Cell Identity sent in SIB3 [3GPP RRC]. Frequency info can be: fdd: uarfcn-UL, ra nge : (0..16383) uarfcn-DL, ra nge : (0..16383) In case of fdd, uarfcn-UL is optional while uarfcn-DL is mandatory. If uarfcn-UL is not present, the default duplex distance defined for the operating frequency band shall be used [3GPP RRC]. Tdd uarfcn-Nt, range: (0..16383) NOTE: Frequency Info and Primary Scrambling Code are always those of the current cell.
>Frequency Info
>Primary Scrambling Code
Primary Scrambling Code, range: (0..511) NOTE: The field applies only in the case of a WCDMA cell. NOTE: Frequency Info and Primary Scrambling Code/Cell Parameters ID are always those of the current cell.
>Measured Results List
O
>Cell Parameters ID
Network Measurement Report for WCDMA/TD-SCDMA comprising both intra- and/or inter-frequency cell measurements (as per [3GPP RRC]). Cell Parameters ID, range: (0..127) NOTE: This field applies only to TDSCDMA
NOTE: Frequency info and Cell Parameters ID are always those of the current cell. NOTE: This parameter is mandatory for a TD-SCDMA cell. Timing advance
>Timing Advance
OMA-TS-ILP-V2_0_1-20121205-A
Page 236 (295)
>> TA
NOTE: This field applies only to TDSCDMA Timing advance measurement, range (0..8191) For 1.28Mcps TDD, it means uplink timing advance applied by the UE (as per 5.1.14 [3GPP 25.225]) For 3.84Mcps TDD, it means absolute timing advance value to be used to avoid large delay spread at the NodeB (as per 10.3.6.95 [3GPP RRC] and as per 10.3.6.95a [3GPP RRC]); In such case, 256 to 8191 value is spare; For 7.68Mcps TDD, it means absolute timing advance value to be used to avoid large delay spread at the NodeB (as per 10.3.6.95 [3GPP RRC] and as per 10.3.6.95a [3GPP RRC]); In such case, 512 to 8191 value is spare; Measurement resolution. Supported resolutions are 0.125, 0.5 and 1 chips. If this field is missing, the resolution is 0.125 chips. UTRA-TDD chip rate. Supported chip rates are 1.28, 3.84 and 7.68 Mchips/s.
O
>>TA Resolution
>> Chip Rate
If this field is missing, the rate is 1.28 Mchips/s. Table 23: WCDMA/TD-SCDMA Cell Info Parameter
12.5.3
LTE Cell Info
The LTE Cell Info parameter defines the parameter of a LTE radio cell [3GPP LTE].
Parameter LTE Cell Info >CellGlobalIdEUTRA >>PLMN-Identity >>>MCC >>>MNC >>CI >PhysCellId
Presence
Value/Description
M M M M M M
LTE Cell ID. Parameter definitions in [3GPP LTE].
Mobile Country Code, range: (0..999) Mobile Network Code, range: (0..999) Cell Identity, length 28 bits. Physical Cell ID, range: (0..503)
OMA-TS-ILP-V2_0_1-20121205-A
Page 237 (295)
>TrackingAreaCode >RSRPResult
M O
Tracking Area Code, length 16 bits Reference Signal Received Power, range: (0..97) Reference Signal Received Quality, range: (0..34) Currently used Timing Advance value, range: (0..1282) (NTA/16 as per [3GPP 36.213]). Network Measurement Report for LTE ([3GPP LTE]). Physical Cell ID, range: (0..503)
>RSRQPResult
O
>TA
O
>Measured Results List EUTRA >>PhysCellId >>cgi-Info >>>CellGlobalIdEUTRA >>>TrackingAreaCode >>MeasResult >>>RSRPResult >>>RSRQResult >>EARFCN
O M O M M M O O
Tracking Area Code, length 16 bits Reference Signal Received Power, range: (0..97) Reference Signal Received Quality, range: (0..34) This parameter is conditional and must be sent if cgi-Info is not present. If the cgi-Info is present, this parameter may be sent. E-UTRA ARFCN, range: (0..65535) E-UTRA ARFCN, range: (0..65535)
CV
>EARFCN
O Table 24: LTE Cell Info
12.5.4
CDMA Cell Info
The cdmaCell parameter defines the parameter of a CDMA radio cell.
OMA-TS-ILP-V2_0_1-20121205-A
Page 238 (295)
Parameter Cdma Cell Info >NID >SID >BASEID >BASELAT >BASELONG >REFPN
Presence
Value/Description
M M M M M
CDMA Cell ID Network ID, range: (0..65535) System ID, range: (0..32767) Base Station ID, range: (0..65535) Base Station Latitude, range: (0..4194303) Base Station Longitude, range: (0..8388607) Base Station PN Number, range: (0..511) This parameter is conditional and only used for 1x in which case it is mandatory. GPS Week number, range: (0..65535) GPS Seconds, range: (0..4194303)
>WeekNumber >Seconds
M M Table 25: CDMA Cell Info
12.5.5
HRPD Cell Info

Parameter Hrpd Cell Info >SECTORID >BASELAT >BASELONG >WeekNumber >Seconds Presence Value/Description
The HRPD Cell Info parameter defines the parameter of a HRPD radio cell [3GPP2 HRPD]. M M M M M Table 26: HRPD Cell Info HRPD Cell ID Sector ID, length 128 bits Base Station Latitude, range: (0..4194303) Base Station Longitude, range: (0..8388607) GPS Week number, range: (0..65535) GPS Seconds, range: (0..4194303)
12.5.6
UMB Cell Info
The UMB Cell Info parameter defines the parameter of a UMB radio cell [3GPP2 UMB].
Parameter Umb Cell Info >SECTORID >MCC >MNC >BASELAT >BASELONG
Presence
Value/Description
M M M M M
UMB Cell ID Sector ID, length 128 bits Mobile Country Code, range: (0..999) Mobile Network Code, range: (0..999) Base Station Latitude, range: (0..4194303) Base Station Longitude, range: (0..8388607)
OMA-TS-ILP-V2_0_1-20121205-A
Page 239 (295)
>WeekNumber >Seconds
M M Table 27: UMB Cell Info
GPS Week number, range: (0..65535) GPS Seconds, range: (0..4194303)
12.5.7
WLAN AP Info
Parameter WLAN AP Info >AP MAC Address >AP Transmit Power >AP Antenna Gain >AP S/N > Device Type Presence Value/Description
The WLAN AP Info parameter defines the parameters of a WLAN access point [IEEE 802.11]. M O O O WLAN Access Point ID Access Point MAC Address AP Transmit power in dBm AP antenna gain in dBi AP Signal to Noise received at the SET in Db Options are: 802.11a device, 802.11b device and 802.11g device. Future networks are permitted. AP signal strength received at the SET in dBm AP channel/frequency of Tx/Rx Round Trip Delay (RTD) between the SET and AP Measured RTD value Units for RTD value and RTD accuracy 0.1, 1, 10, 100 or 1000 nanoseconds RTD standard deviation in relative units SET Transmit power in dBm SET antenna gain in dBi SET Signal to Noise received at the AP in Db SET signal strength received at the AP in dBm Location of the Access Point as reported by the AP Location encoding description - LCI as per [RFC 3825] - ASN.1 as per [X.694] Location Data Location Accuracy in units of 0.1m Location value in the format defined in Location Encoding
O
>AP Signal Strength >AP Channel/Frequency >Round Trip Delay >>RTD Value >>RTD Units
O O O M M
>>RTD Accuracy >SET Transmit Power >SET Antenna Gain >SET S/N >SET Signal Strength >AP Reported Location >>Location Encoding
O O O O O O M
>>Location Data >>>Location Accuracy >>>Location Value
M O M Table 28: WLAN AP Info
OMA-TS-ILP-V2_0_1-20121205-A
Page 240 (295)
12.5.8
WiMAX BS Info
The WiMAX BS Info parameter defines the parameters of a WiMAX base station [IEEE 802.16-2004] and [IEEE 802.16e2005].
Parameter WiMAX BS Info >BS ID >RTD measurement Presence Value/Description
M O
>>Round Trip Delay
M
>>Round Trip Delay Uncertainty >WiMAX NMR List >> BS ID
O O M
>> Relative Delay
O
>> Relative Delay uncertainty
O
>>BS Signal Strength
O
>>BS Signal Strength Uncertainty >>BS Tx Power
O
>>BS CINR
O
>>BS CINR Uncertainty
O
>> BS Location >>>Location Encoding
O M
WiMAX Base Station Info Base Station Identifier Bit string of fix length of 48 Round Trip Delay (RTD) or relative RTD measurement between the SET and the serving BS Round Trip Delay (RTD) between the SET and the serving BS in units of 10 ns Range (0 .. 65535) Standard deviation of the Round Trip Delay measurement in units of 10 ns Range (0 .. 1023) WiMAX network measurements. Repeated 1-32 times. Base Station for the serving and neighboring cell measurement. Bit string of fixed length of 48 Relative Delay between the SET and the neighboring BS in units of 10 ns. Not applicable for the serving BS. Range (-32768..32767) Relative Delay uncertainty in units of 10 ns. Range (0 .. 1023) BS signal strength received at the SET in dBm Range (0 .. 255) Standard deviation of BS signal strength received at the SET in Db Range (0 .. 63) BS equivalent isotropic transmit power Range (0 .. 255) BS Carrier to Noise and Interference Ratio as received at the SET in Db Range (0 .. 255) Standard deviation of BS Carrier to Noise and Interference Ratio as received at the SET in Db Range (0 .. 63) Location of the BS as reported by the BS Location encoding description - LCI as per [RFC 3825] - ASN.1 as per [X.694]
OMA-TS-ILP-V2_0_1-20121205-A
Page 241 (295)
>>>>Location Data >>>>>Location Accuracy >>>>>Location Value
M O M Table 29: WiMAX BS Info
Location Data Location Accuracy in units of 0.1m Integer (0..4294967295) Location value in the format defined in Location Encoding Octet string of fix length of 128
OMA-TS-ILP-V2_0_1-20121205-A
Page 242 (295)
12.6 Position
Parameter Position Presence Values/description This parameter describes the position of the SET. The parameter also contains a timestamp and optionally the velocity. Time when position fix was calculated.
>Timestamp >Position Estimate >>Sign of latitude >>Latitude
M M M M
Indicates North or South. Integer (0..223-1). The latitude encoded value (N) is derived from the actual latitude X in degrees (0..90) by this formula: N 223 X /90 < N+1 Integer (-223.. 223-1). The longitude encoded value (N) is derived from the actual longitude X in degrees (180..+180) by this formula: N 224 X /360 < N+1 Contains the latitude/longitude uncertainty code associated with the major axis, and the uncertainty code associated with the minor axis and the orientation, in degrees, of the major axis with respect to the North. For the correspondence between the latitude/longitude uncertainty code and meters refer to [3GPP GAD] for details. Represents the confidence by which the position of a target entity is known to be within the shape description (i.e., uncertainty ellipse for 2D-description, uncertainty ellipsoid for 3D-description) and is expressed as a percentage. This is an integer (0..100). Shall be present for a 3D position information; it shall remain absent for 2D position information. Indicates height (above the WGS84 ellipsoid) or depth (below the WGS84 ellipsoid). Provides altitude information in meters. Integer (0..215-1). Refer to [3GPP GAD] for details Contains the altitude uncertainty code. Refer to [3GPP GAD] for details Speed and bearing values as defined by the Velocity type and as defined in [3GPP GAD]
>>Longitude
>>Uncertainty ellipse (semi major, semi minor, major axis)
>>Confidence
>>Altitude information
>>>Altitude direction >>>Altitude
M M
>>>Altitude uncertainty >Velocity
M O
Table 30: Position Parameter
OMA-TS-ILP-V2_0_1-20121205-A
Page 243 (295)
The definition and coding of the position estimate parameter (ellipsoid point with altitude, uncertainty ellipse and altitude uncertainty) is based on [3GPP GAD]. The Datum used for all positions are WGS-84.
12.7 Trigger Params

Parameter Trigger Type Presence M Values/description This parameter can be of type Periodic Trigger Parameters O Periodic Area Event
Periodic Trigger Parameters: Number of fixes Interval between fixes Start time
Table 31: Trigger Parameter
12.8 SPC_SET_Key
Parameter SPC_SET_Key Presence Values/description This parameter defines the authentication key used by the SET for H/V-SPC authentication.
Table 32: SPC_SET_Key Parameter
12.9 SPC-TID
Parameter SPC-TID Presence Values/description This parameter defines the transaction ID used for H/V-SPC authentication: RAND (random number) SLP FQDN (FQDN of the H-SLP).
Table 33: SPC-TID Parameter
12.10 SPC_SET_Key_lifetime
OMA-TS-ILP-V2_0_1-20121205-A
Page 244 (295)
Parameter
Presence
Values/description This parameter defines the lifetime of SPC_SET_Key. This parameter is optional. If not present, a default value of 24 hours is assumed. The units are in hours and the range is from 1 to 24 hours.
Table 34: SPC_SET_Key_lifetime Parameter
12.11 QoP
Parameter QoP >Horizontal accuracy >Vertical accuracy > Maximum Location Age Presence M O O Values/description Describes the desired Quality of Position Horizontal accuracy as defined in [3GPP GAD] (section 6.2 Uncertainty) Vertical accuracy as defined in [3GPP GAD] (section 6.4 Uncertainty Altitude) Maximum tolerable age of position estimates used for cached position fixes. Units in seconds from 0 to 65535. Values as defined for element Response Time in 3GPP TS 44.031 [3GPP RRLP]: 2^N, N from (0..7), unit is seconds
>Delay
Table 35: QoP Parameter
12.12 SPC Status Code

Parameter SPC Status Code Presence Values/description This parameter is only required in the response of the SPC to the SLC and defines the operational status of the SPC. The Status Code can assume the following values: operational(0), not_operational(1), reduced_availability(2) Table 36: Status Code Parameter
>SPC Status Code values
12.13 Number of Fix

Parameter Number of Fix Presence Values/description Defines the fix number within a triggered session.
Table 37: Number of Fix Parameter

OMA-TS-ILP-V2_0_1-20121205-A
Page 245 (295)
12.14 SET Capabilities

Parameter SET capabilities Presence Values/description SET capabilities (not mutually exclusive) in terms of supported positioning technologies and positioning protocols. Defines the positioning technology. Zero or more of the following positioning technologies (including those listed in the optional GANSS Position Methods structure): SET-assisted A-GPS >>GANSS Position Methods O SET-based A-GPS Autonomous GPS AFLT E-CID E-OTD OTDOA
>Pos Technology
Defines the supported GANSS (i.e. other than A-GPS). If included, this parameter is repeated for each supported GANSS. In addition, in the case of SBAS the parameter is repeated for each supported SBAS. Defines the GANSS. Integer (0..15) 0: Galileo 1: SBAS 2: Modernized GPS 3: QZSS 4: GLONASS 5-15: Reserved for future use
>>>GANSS ID
>>>SBAS ID
CV
>>>GANSS Positioning Modes
>>>GANSS Signals
Present if GANSS ID indicates SBAS. Bit string interpreted as: 000: WAAS 001: EGNOS 010: MSAS 011: GAGAN Bitmap defining the supported modes for GNSS indicated by GANSS ID. Bit 0: SET Assisted Bit 1: SET Based Bit 2: Autonomous Bitmap (length 8 bits) defining the supported signals for GNSS indicated by GANSS ID. For Galileo, the bits are interpreted as : Bit 0: E1 Bit 1: E5a Bit 2: E5b Bit 3: E5a+E5b
OMA-TS-ILP-V2_0_1-20121205-A
Page 246 (295)
Bit 4: E6 Bits 5-7: Spare For Modernized GPS, the bits are interpreted as: Bit 1: L1 C Bit 2: L2 C Bit 3: L5 Bits 0, 4-7: Spare For QZSS, the bits are interpreted as: Bit 0: L1 C/A Bit 1: L1 C Bit 2: L2 C Bit 3: L5 Bits 4-7: Spare For GLONASS, the bits are interpreted as: Bit 0: G1 Bit 1: G2 Bit 2: G3 Bits 3-7: Spare For SBAS, the bits are interpreted as: Bit 0: L1 Bits 1-7: Spare One of the following preferred modes: A-GNSS SET-assisted preferred >Pos Protocol M A-GNSS SET-based preferred No preferred mode
>Pref Method
Zero or more of the following positioning protocols (bitmap): RRLP RRC TIA-801 LPP
>>Pos Protocol Version RRLP >>>Major Version Field >>> Technical Version Field >>>Editorial Version Field >>Pos Protocol Version RRC
CV M M M CV
Describes the protocol version of RRLP Positioning Protocol. First (most significant) element of the version number for RRLP, range: (0..255) Second element of the version number for RRLP, range: (0..255) Third (least significant) element of the version number for RRLP, range: (0..255) Describes the protocol version of RRC Positioning Protocol. It is required if RRC is identified in the Pos Protocol parameter.
OMA-TS-ILP-V2_0_1-20121205-A
Page 247 (295)
>>>Major Version Field >>> Technical Version Field >>>Editorial Version Field >>Pos Protocol Version TIA801
M M M CV
>>>Supported Pos Protocol Version TIA-801
>>>>Revision Number
First (most significant) element of the version number for RRC, range: (0..255) Second element of the version number, range: (0..255) Third (least significant) element of the version number for RRC, range: (0..255) Describes the protocol version of TIA-801 Positioning Protocol. It is required if TIA-801 is identified in the Pos Protocol parameter. Specifies a list of up to 8 different supported 3GPP2 C.S0022 versions. This parameter is required (with at least one entry in the list) if TIA-801 is identified in the Pos Protocol parameter. Revision part of document number for the specifications of C.S0022 Functioning Protocol. Value: [0,A-Z] Point Release number for C.S0022, range: (0..255). Internal Edit Level for C.S0022, range: (0..255). Describes the protocol version of LPP Positioning Protocol. It is required if LPP is identified in the Pos Protocol parameter. First (most significant) element of the version number for LPP Positioning Protocol, range: (0..255) Second element of the version number for LPP Positioning Protocol, range: (0..255) Third (least significant) element of the version number for LPP Positioning Protocol, range: (0..255) This parameter indicates which bearers the SET supports. Note that each bearer in this list must be supported by the SET, but not all at the same time. The parameter indicates support for one or more of the following: GSM WCDMA/TD-SCDMA CDMA HRPD UMB LTE WLAN WiMAX
>>>>Point Release Number >>>> Internal Edit Level >>Pos Protocol Version LPP
M M CV
>>>Major Version Field
>>>Technical Version Field >>>Editorial Version Field
M M
> supported bearers
OMA-TS-ILP-V2_0_1-20121205-A
Page 248 (295)
Table 38: SET Capabilities Parameter
12.15 Requested Assistance Data

Parameter Requested assistance data Presence Values/description This parameter is applicable to A-GPS positioning methods only. It describes the requested A-GPS assistance data in the form of a bitmap: Almanac indicator UTC model Ionospheric model DGPS corrections Reference location Reference time Acquisition assistance Real-time integrity
Navigation model Note: Reference location Bit is used for requesting Reference Location also for GANSS. Navigation Model >GPS week >GPS Toe CV M M When the navigation model indicator is set, this field is present. Contains the GPS week of the assistance data currently held in the SET; range is 0 to 1023 Contains the GPS time of Ephemeris in hours of the newest set of Ephemeris contained in the SET; range is 0 to 167 Contains the number of satellites to be considered for the current GPS assistance data request (number of satellites for which ephemeris data is available in the SET); range is 0 to 31. If the SET has no ephemeris data, this field SHALL be set to zero. If the SET has ephemeris data whose age exceeds the T-Toe limit, this field may be set to zero. If the network receives a zero value for this field, it shall ignore the GPS week and GPS Toe fields and assume that the SET has no ephemeris data Contains the Ephemeris age tolerance of the SET to the network in hours; range is 0 to 10 Present if NSAT > 0, repeated NSAT times
>NSAT
>T-Toe limit >Satellite information
M CV
OMA-TS-ILP-V2_0_1-20121205-A
Page 249 (295)
>>SatId
Identifies the satellite and is equal to (SV ID No-1) where SV ID No is defined in ICDGPS-200C. Range is 0 to 63 Represents the satellite sequence number, range is 0 to 255
>>IODE
GANSS Requested Common Assistance Data >GANSS Reference Time
M O M M M M M O
GANSS reference time. Boolean, true if requested, false otherwise. GANSS Ionospheric model. Boolean, true if requested, false otherwise. GANSS Ionospheric model, see [3GPP 49.031] for further information on Data ID GANSS Ionospheric model, see [3GPP 49.031] for further information on Data ID Earth-Orientation Parameters for precise coordinate transformations Generic data requested for GANSS. If included, this parameter is repeated for each GANSS the assistance data is requested. In addition, in the case of SBAS this parameter is repeated for each SBAS the assistance data is requested. Defines the GANSS for which the assistance data is requested. 0: Galileo 1: SBAS 2: Modernized GPS 3: QZSS 4: GLONASS 5-15: Reserved for future use
>GANSS Ionospheric model
>GANSS Additional Ionospheric Model for Data ID=00 >GANSS Additional Ionospheric Model for Data ID=11 >GANSS Earth-Orientation Parameters GANSS Requested Generic Assistance Data
>GANSS ID
> SBAS ID
CV
>GANSS Real-Time Integrity
>DGANSS Differential Corrections
Present if GANSS ID indicates SBAS. Bit String interpreted as: 000: WAAS 001: EGNOS 010: MSAS 011: GAGAN Real Time integrity requested for a particular GANSS. Boolean, true if requested, false otherwise. If present, differential corrections are requested. Bitmap (length 8 bits) defining for which signals the corrections are requested. For Galileo, the bits are interpreted as: Bit 0: E1
OMA-TS-ILP-V2_0_1-20121205-A
Page 250 (295)
>GANSS Almanac
>GANSS Navigation Model >>GANSS Week or Day
O M
>>GANSS_Toe
Bit 1: E5a Bit 2: E5b Bit 3: E6 4-7: spare For Modernized GPS, the bits are interpreted as: Bit 0: L1 C Bit 1: L2 C Bit 2: L5 Bits 3-7: Spare For QZSS, the bits are interpreted as: Bit 0: L1 C/A Bit 1: L1 C Bit 2: L2 C Bit 3: L5 Bits 4-7: Spare For GLONASS, the bits are interpreted as: Bit 0: G1 Bit 1: G2 Bit 2: G3 Bits 3-7: Spare For SBAS, the bits are interpreted as: Bit 0: L1 Bits 1-7: Spare GANSS Almanacs for the particular GANSS Id. Boolean, true if requested, false otherwise. If GANSS ID indicates modernized GPS or QZSS and Almanac Model ID is not included in GANSS Additional Assistance Data Choices, this bit shall be interpreted as Model-4 for modernized GPS and as Model-2 for QZSS, defined in Table A.54 of [3GPP RRLP]. If present, GANSS navigation models are requested Week or Day number of the assistance data currently held in the SET. If GANSS ID does not indicate GLONASS this field is expressed in GANSS weeks. Range is 0 to 4095. If GANSS ID indicates GLONASS this field is expressed in days as defined in [3GPP 49.031]. Time-of-Ephemeris of the assistance data currently held in the SET, If GANSS ID does not indicate GLONASS this field is expressed in hours. Range is 0 to 167. If GANSS ID indicates GLONASS Toe is expressed in units of 15 minutes. Range then is 0 to 95 (0 to 1425 minutes).
OMA-TS-ILP-V2_0_1-20121205-A
Page 251 (295)
>>T-Toe limit
>>Satellites list related data >>>SatID
O M
>>>IOD >GANSS Time Model GNSS-GNSS
M O
>GANSS Reference Measurement Information
>GANSS data bits >>GANSS TOD minute
O M
Ephemeris age tolerance of the UE to network. If GANSS ID does not indicate GLONASS this field is expressed in hours. Range is 0 to 10. If GANSS ID indicates GLONASS Toe is expressed in units of 30 minutes. Range then is 0 to 15 (0 to 450 minutes). Information of the satellites for which the ephemeris data is available in SET. Identifies the satellite for which assistance is requested and is interpreted as in table A.10.14 in [3GPP RRLP]. Issue of Data for SatID as defined in table A.48.2 in [3GPP RRLP]. If present, time models to convert reference system time to GNSS system time are requested. Reference system is indicated by GANSS ID. Bitmap (length 16 bits) defining GNSS system for which GNSS the time models are requested: 0: GPS 1: Galileo 2: QZSS 3: GLONASS Bits 4-15: spare. Boolean value. If set to true, reference code and Doppler measurement information of satellites of a GANSS constellation are requested. Request Bit stream of GANSS The reference time modulo 60 s of the first data bit of the requested data in integer seconds in GNSS specific system time of the GNSS indicated by GANSS ID.
>>Data bit assistance >>>GANSS Signal
M M Bitmap (length 8 bits) defining the supported signals for GNSS indicated by GANSS ID. For Galileo, bits are interpreted as : Bit 0: E1 Bit 1: E5a Bit 2: E5b Bit 3: E5a+E5b Bit 4: E6 Bits 5-7: Spare For Modernized GPS, the bits are interpreted as: Bit 0: L1 C Bit 1: L2 C Bit 2: L5
OMA-TS-ILP-V2_0_1-20121205-A
Page 252 (295)
Bits 3-7: Spare For QZSS, the bits are interpreted as: Bit 0: L1 C/A Bit 1: L1 C Bit 2: L2 C Bit 3: L5 Bits 4-7: Spare For GLONASS, the bits are interpreted as: Bit 0: G1 Bit 1: G2 Bit 2: G3 Bits 3-7: Spare For SBAS, the bits are interpreted as: Bit 0: L1 Bits 1-7: Spare
>>>GANSS Data Bit Interval
This field represents the time length for which the Data Bit Assistance is requested. The Data Bit Assistance shall be relative to the time interval (GANSS TOD, GANSS TOD + Data Bit Interval). The Data Bit Interval r, expressed in seconds, is mapped to a binary number K with the following formula: r =0.1* 2 K Value K=15 means that the time interval is not specified.
>>>Satellite Information
This parameter may be included to indicate a list of satellites (up to 64) for which the Data Bit Assistance Request is applicable Identifies the satellite and is equal to (SV ID No 1). UTC model requested. Boolean, true if required, false otherwise. If GANSS ID indicates QZSS and UTC Model ID in GANSS Additional Assistance Data Choices is not included, this bit shall be interpreted as Model-1 as defined in Table A.55 of [3GPP RRLP]. If present, some GANSS Additional Assistance Data is requested. ID as defined in A.49.2 of [3GPP RRLP]. Missing field indicates request for the native model. ID as defined in A.49.1 of [3GPP RRLP]. Missing field indicates request for the native model. ID as defined in A.55/A.55.17 of [3GPP RRLP]. Missing field indicates request for
>>>>SatID
M M
>GANSS UTC model
>GANSS Additional Data Choices >> Orbit Model ID
O O
>> Clock Model ID
>>>UTC Model ID
OMA-TS-ILP-V2_0_1-20121205-A
Page 253 (295)
>>Almanac Model ID
>GANSS Auxiliary Information
the native model. ID as defined in A.54 of [3GPP RRLP]. Missing field indicates request for the native model. GANSS Auxiliary Information including signal availability for SVs and GLONASS frequency assignments requested.
>GANSS Extended Ephemeris >>Validity > GANSS Extended Ephemeris Check >Begin Time >End Time
O M O M M O M O M M Requested validity period for Extended ephemeris in steps of four hours See [3GPP 49.031] for further information on this field. Begin time of the Extended ephemeris currently held by the SET End time of the Extended ephemeris currently held by the SET Requested validity period for Extended ephemeris in steps of four hours See [3GPP 49.031] for further information on this field. Begin time of the Extended ephemeris currently held by the SET End time of the Extended ephemeris currently held by the SET
GPS Extended Ephemeris >Validity Hours GPS Extended Ephemeris Check >Begin Time >End Time
Table 39: Requested Assistance Data Parameter
12.16 Positioning Payload

Parameter Positioning payload Presence Values/description Describes the positioning payload for TIA801 [TIA-801], RRLP [3GPP RRLP] , RRC [3GPP RRC] and LPP [3GPP LPP]. The restrictions of maximum PDU size as specified in Section 2.1 of [3GPP RRLP] (242 octets) does not apply. If the size for rrlpPayload exceeds 65535 bits, pseudo segmentation according to [3GPP RRLP] SHALL be used. Up to three LPP messages and/or up to three TIA801 messages are allowed to be sent in a single Positioning Payload IE. Table 40: Positioning Payload Parameter
OMA-TS-ILP-V2_0_1-20121205-A
Page 254 (295)
12.17 Multiple Location IDs

Parameter Multiple Location IDs Presence Values/description This parameter contains a set of up to MaxLidSize(64) Location ID/Relative Timestamp/Serving Cell Flag data. If Relative Timestamp is present, the associated Location ID represents historical data; if Relative Timestamp is absent, the Location ID represents current data. Describes measured globally unique cell/WLAN AP/WiMAX BS identification of the serving cell/WLAN AP/WiMAX BS or cell/WLAN AP/WiMAX BS identification from any receivable radio network. If this information is historical, the Relative Timestamp parameter must be present. If this data is current, the Relative Timestamp parameter need not be present. >Relative Timestamp CV Time stamp of measured location Id relative to current Location ID in units of 0.01 sec. Range from 0 to 65535*0.01 sec. Time stamp for current Location Id if present is 0. This flag indicates whether the Location ID data represents a serving cell, WLAN AP or WiMAX BS or idle (i.e. camped-on) cell or WLAN AP. If set, the Location ID information represents serving cell,WLAN AP or WiMAX BS information; if not set, the Location ID information represents idle mode information or eighbour cell ,WLAN AP or WiMAX BS information.
>Location ID
>Serving Cell Flag
Table 41: Multiple Location ID Parameter
12.18 Velocity
Parameter Velocity Presence Values/description Describes the velocity of the SET as per [3GPP GAD]. One of the following four formats are supported: Horizontal Velocity a. b. Bearing Horizontal speed
Horizontal and Vertical Velocity a. b. Vertical Direction Bearing
OMA-TS-ILP-V2_0_1-20121205-A
Page 255 (295)
c. d.
Horizontal speed Vertical speed
Horizontal Velocity Uncertainty a. b. c. Bearing Horizontal speed Horizontal speed uncertainty
Horizontal and Vertical Velocity Uncertainty a. b. c. d. e. f. Vertical direction Bearing Horizontal speed Vertical speed Horizontal speed uncertainty Vertical speed uncertainty
Table 42: Velocity Parameter
12.19 UTRAN GPS Reference Time Result

Parameter UTRAN GPS Reference Time Result Presence Value/Description
>GPS Timing of Cell Frames
>Mode
>SFN
The UTRAN GPS Reference Time Result parameter describes the timing relationship between GPS time and WCDMA/TD-SCDMA cell frame timing as measured by the SET. This parameter is only applicable if the SET has sent current Location ID (lid) information. GPS Time of Week in units of 1/16th UMTS chip [as per 10.3.7.93 3GPP RRC]. Range: (0..37158911999999) The Mode value is either: Primary CPICH Info for FDD [as per 10.3.6.60 3GPP RRC]. Or: Cell Parameters Id for TDD [as per 10.3.6.9 3GPP The SFN at which the SET timing of cell frames is captured. Range: (0..4095)
This element provides the accuracy of the provided relation between GPS and UTRAN time. If GPS TOW is the GPS time corresponding to the UTRAN time provided, then the true
>GPS Reference Time Uncertainty
OMA-TS-ILP-V2_0_1-20121205-A
Page 256 (295)
GPS time lies in the interval [GPS TOW GPS Reference Time Uncertainty, GPS TOW + GPS Reference Time Uncertainty]. The uncertainty r, expressed in microseconds, is mapped to a number K with the following formula: K r = C*(((1+x) )-1) with C = 0.0022 and x = 0.18.
To encode any higher value of the uncertainty than that corresponding to K=127 in the formula above, or to indicate an undefined value of the GPS TOW, the same value, K=127, shall be used. [25.331 version 7.4.0] Table 43: UTRAN GPS Reference Time Result
12.20 UTRAN GANSS Reference Time Result

Parameter UTRAN GANSS Reference Time Result Presence Value/Description
>GANSS Time ID
>UE GANSS Timing of Cell Frames
>Mode
>SFN
>GANSS TOD Uncertainty
The UTRAN GANSS Reference Time Result parameter describes the timing relationship between GANSS time and WCDMA/TD-SCDMA cell frame timing as measured by the SET. This parameter is only applicable if the SET has sent current Location ID (lid) information. GANSS Time ID defines the satellite system used in UTRAN-GANSS time relation. 0: Galileo 1: QZSS 2: GLONASS Range: Enumerated(0..15) Values 3 15 reserved for future use. UE GANSS timing of cell frames subsecond part of GANSS Time of Day [as per 10.3.7.93a 3GPP RRC]. Range: (0.. 86399999999750) by step of 250 ns The Mode value is either: Primary CPICH Info for FDD [as per 10.3.6.60 3GPP RRC]. Or: Cell Parameters Id for TDD [as per 10.3.6.9 3GPP] The SFN at which the SET timing of cell frames is captured. Range: (0..4095) Uncertainty of the relation GANSS Time of Day/SFN [as per 10.3.7.93a 3GPP RRC].
OMA-TS-ILP-V2_0_1-20121205-A
Page 257 (295)
Range (0..127): The uncertainty r, expressed in microseconds, is mapped to a number K, with the following formula: r = C*(((1+x)K)-1), with C = 0.0022 and x = 0.18. [as per 10.3.7.96a 3GPP RRC]. Table 44: UTRAN GANSS Reference Time Result
12.21 UTRAN GPS Reference Time Assistance

Parameter UTRAN GPS Reference Time Assistance Presence Value/Description
> UTRAN GPS Reference Time
>>GPS Timing of Cell Frames
>>Mode
>>SFN
The UTRAN GPS Reference Time Assistance parameter provides UTRAN to GPS timing relationship assistance data for the current serving cell of the SET. This parameter is only applicable if the Location ID (lid) information is current. The UTRAN GPS Reference Time parameter describes the timing relationship between GPS time and WCDMA/TD-SCDMA cell frame timing [as per 10.3.7.96 3GPP RRC]. UTRAN GPS timing of cell frames in steps of 1 UMTS chip [as per 10.3.7.96 3GPP RRC]. Range: (0..2322431999999) The Mode value is either: Primary CPICH Info for FDD [as per 10.3.6.60 3GPP RRC]. Or: Cell Parameters Id for TDD [as per 10.3.6.9 3GPP RRC] The SFN which the UTRAN GPS timing of cell frame time stamps. Range: (0..4095)
This element provides the accuracy of the provided relation between GPS and UTRAN time. If GPS TOW is the GPS time corresponding to the UTRAN time provided, then the true GPS time lies in the interval [GPS TOW GPS Reference Time Uncertainty, GPS TOW + GPS Reference Time Uncertainty]. The uncertainty r, expressed in microseconds, is mapped to a number K with the following formula: K r = C*(((1+x) )-1) with C = 0.0022 and x = 0.18.
>GPS Reference Time Uncertainty
To encode any higher value of the uncertainty than that corresponding to K=127 in the formula above, or to indicate an undefined value of the
OMA-TS-ILP-V2_0_1-20121205-A
Page 258 (295)
>TUTRAN-GPS Drift Rate
GPS TOW, the same value, K=127, shall be used. [25.331 version 7.4.0] Drift rate of UTRAN to GPS timing [as per 10.3.7.96 3GPP RRC]. Range (enumerated): -50, -25, -15, 10, -5, -2, -1, 0, 1, 2, 5, 10, 15, 25, 50 Units: 1/256 chips per sec.
Table 45: UTRAN GPS Reference Time Assistance
12.22 UTRAN GANSS Reference Time Assistance

Parameter UTRAN GANSS Reference Time Assistance Presence Value/Description
>GANSS Day
>GANSS Time ID
The UTRAN GANSS Reference Time Assistance parameter provides UTRAN to GANSS timing relationship assistance data for the current serving cell of the SET. This parameter is only applicable if the Location ID (lid) information is current. The number of days from the beginning of GANSS system time (mod 8192) [as per 10.3.7.96o 3GPP RRC]. GANSS Time ID defines the satellite system used in UTRAN-GANSS time relation. 0: Galileo 1: QZSS 2: GLONASS Range: Enumerated(0..15) Values 3 15 reserved for future use. The UTRAN GANSS Reference Time parameter describes the timing relationship between GANSS time and WCDMA/TD-SCDMA cell frame timing [as per 10.3.7.96o 3GPP RRC]. GANSS time of day in seconds. Range: (0..86399) UTRAN GANSS timing of cell frames sub-second part of GANSS Time of Day [as per 10.3.7.96o 3GPP RRC]. Range: (0.. 999999750) by step of 250 ns The Mode value is either: Primary CPICH Info for FDD [as per 10.3.6.60 3GPP RRC]. Or: Cell Parameters Id for TDD [as per 10.3.6.9 3GPP RRC] The SFN which the UTRAN GANSS
> UTRAN GANSS Reference Time
>>GANSS TOD >>UTRAN GANSS Timing of Cell Frames
M O
>>Mode
>>SFN
OMA-TS-ILP-V2_0_1-20121205-A
Page 259 (295)
>>GANSS TOD Uncertainty
>TUTRAN-GANSS Drift Rate
timing of cell frame time stamps. Range: (0..4095) Uncertainty of the relation GANSS Time of Day/SFN [as per 10.3.7.96o 3GPP RRC]. Range (0..127): The uncertainty r, expressed in microseconds, is mapped to a number K, with the following formula: r = C*(((1+x)K)-1), with C = 0.0022 and x = 0.18. [as per 10.3.7.96a 3GPP RRC]. Drift rate of UTRAN to GANSS timing [as per 10.3.7.96o 3GPP RRC]. Range (enumerated): -50, -25, -15, 10, -5, -2, -1, 0, 1, 2, 5, 10, 15, 25, 50 Units: ns per sec.
Table 46: UTRAN GANSS Reference Time Assistance
12.23 GNSS Positioning Technology

Parameter GNSS Positioning Technology Presence Value/Description
Bitmap of GNSS Positioning Technology. This bitmap indicates the GNSS used or to be used for the positioning computation. GPS Galileo SBAS Modernized GPS QZSS GLONASS
When a Bit is set to FALSE: not used, when set to TRUE, used. Note that GPS SHALL not be the only bit set to TRUE. Table 47: GNSS Positioning Technology
12.24 Approved Positioning Methods

Parameter Positioning Technology Presence Value/Description
Defines the positioning technologies which the SLC has approved for the SPC. Zero or more of the following positioning technologies (bitmap and technologies listed in GANSS Position Methods structure):
OMA-TS-ILP-V2_0_1-20121205-A
Page 260 (295)
>>GANSS Position Methods O
SET-assisted A-GPS SET-based A-GPS Autonomous GPS AFLT E-CID E-OTD OTDOA
>>>GANSS ID
Defines the supported GANSS (i.e. other than A-GPS). If included, this parameter is repeated for each supported GANSS Defines the GANSS. Integer (0..15) 0: Galileo 1: SBAS 2: Modernized GPS 3: QZSS 4: GLONASS 5-15: Reserved for future use Bitmap defining the supported modes for GNSS indicated by GANSS ID. Bit 0: SET Assisted Bit 1: SET Based Bit 2: Autonomous Bitmap (length 8 bits) defining the supported signals for GNSS indicated by GANSS ID. For Galileo, the bits are interpreted as : Bit 0: E1 Bit 1: E5a Bit 2: E5b Bit 3: E5a+E5b Bit 4: E6 Bits 5-7: Spare For Modernized GPS, the bits are interpreted as: Bit 1: L1 C Bit 2: L2 C Bit 3: L5 Bits 0, 4-7: Spare For QZSS, the bits are interpreted as: Bit 0: L1 C/A
>>>GANSS Signals
OMA-TS-ILP-V2_0_1-20121205-A
Page 261 (295)
Bit 1: L1 C Bit 2: L2 C Bit 3: L5 Bits 4-7: Spare For GLONASS, the bits are interpreted as: Bit 0: G1 Bit 1: G2 Bit 2: G3 Bits 3-7: Spare For SBAS, the bits are interpreted as: Bit 0: L1 Bits 1-7: Spare Table 48: Approved Positioning Methods
12.25 Supported Positioning Methods

Parameter Positioning Technology Presence Value/Description
Defines the positioning technologies which the SPC supports. Zero or more of the following positioning technologies (bitmap and technologies listed in GANSS Position Methods structure): SET-assisted A-GPS SET-based A-GPS Autonomous GPS AFLT E-CID E-OTD OTDOA
>>GANSS Position Methods
>>>GANSS ID
Defines the supported GANSS (i.e. other than A-GPS). If included, this parameter is repeated for each supported GANSS Defines the GANSS. Integer (0..15) 0: Galileo 1: SBAS 2: Modernized GPS 3: QZSS 4: GLONASS 5-15: Reserved for future use
OMA-TS-ILP-V2_0_1-20121205-A
Page 262 (295)
>>>GANSS Signals
Bitmap defining the supported modes for GNSS indicated by GANSS ID. Bit 0: SET Assisted Bit 1: SET Based Bit 2: Autonomous Bitmap (length 8 bits) defining the supported signals for GNSS indicated by GANSS ID. For Galileo, the bits are interpreted as : Bit 0: E1 Bit 1: E5a Bit 2: E5b Bit 3: E5a+E5b Bit 4: E6 Bits 5-7: Spare For Modernized GPS, the bits are interpreted as: Bit 1: L1 C Bit 2: L2 C Bit 3: L5 Bits 0, 4-7: Spare For QZSS, the bits are interpreted as: Bit 0: L1 C/A Bit 1: L1 C Bit 2: L2 C Bit 3: L5 Bits 4-7: Spare For GLONASS, the bits are interpreted as: Bit 0: G1 Bit 1: G2 Bit 2: G3 Bits 3-7: Spare For SBAS, the bits are interpreted as: Bit 0: L1 Bits 1-7: Spare
Table 49: Supported Positioning Methods
12.26 Preferred Positioning Method

Parameter Position Method Presence Description Describes the positioning method:
OMA-TS-ILP-V2_0_1-20121205-A
Page 263 (295)
A-GPS SET assisted only A-GPS SET based only A-GPS SET assisted preferred (A-GPS SET based is the fallback mode) A-GPS SET based preferred (A-GPS SET assisted is the fallback mode) A-GNSS SET Assisted only A-GNSS SET Based only A-GNSS SET Assisted preferred (A-GANSS SET Based is the fallback mode) A-GNSS SET Based preferred (A-GANSS SET Assisted is the fallback mode) Autonomous GPS Autonomous GNSS AFLT Enhanced Cell/sector EOTD OTDOA
In case of A-GNSS SET Based, AGNSS SET Assisted, the GNSS Positioning Technology MUST be used to specify which GNSS is to be used. For Autonomous GNSS, the GNSS Positioning Technology MAY be used to specify which GNSS is to be used. Table 50: Preferred Positioning Method
12.27 Status Code

Parameter Status Code Presence Values/description This parameter is only required in the context of sending a position response or to terminate a SUPL session.
OMA-TS-ILP-V2_0_1-20121205-A
Page 264 (295)
> Status Code values
The Status Code can assume the following values:

unspecified(0), systemFailure(1), unexpectedMessage(2), protocolError(3), dataMissing(4), unexpectedDataValue(5), posMethodFailure(6), posMethodMismatch(7), posProtocolMismatch(8), targetSETnotReachable(9), versionNotSupported(10), resourceShortage(11), invalidSessionId(12), nonProxyModeNotSupported(13), proxyModeNotSupported(14), positioningNotPermitted(15), iLPTimeout(16)
Table 51: Status Code Parameter
OMA-TS-ILP-V2_0_1-20121205-A
Page 265 (295)
13.ASN.1 Encoding of ILP messages (Normative)

This section defines the ILP messages and common elements with ASN.1 (Normative).
13.1 Common Part

ILP DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS Version, SessionID2 FROM ILP-Components PREQ FROM ILP-PREQ PRES FROM ILP-PRES PRPT FROM ILP-PRPT PLREQ FROM ILP-PLREQ PLRES FROM ILP-PLRES PINIT FROM ILP-PINIT PAUTH FROM ILP-PAUTH PALIVE FROM ILP-PALIVE PEND FROM ILP-PEND PMESS FROM ILP-PMESS; -- general ILP PDU layout; ILP-PDU ::= SEQUENCE { length INTEGER(0..65535), version Version, sessionID2 SessionID2, message IlpMessage } IlpMessage ::= CHOICE { msPREQ PREQ, msPRES PRES, msPRPT PRPT, msPLREQ PLREQ, msPLRES PLRES, msPINIT PINIT, msPAUTH PAUTH, msPALIVE PALIVE, msPEND PEND, msPMESS PMESS, } END
OMA-TS-ILP-V2_0_1-20121205-A
Page 266 (295)
13.2 Message Specific Part

The message specific part contains further parameters that are unique for each ILP message. The following sections describe the message specific part of ILP messages.
13.2.1
PREQ
ILP-PREQ DEFINITIONS AUTOMATIC TAGS ::= BEGIN EXPORTS PREQ; IMPORTS LocationId, Position, QoP, SPCSETKey, SPCTID, SPCSETKeylifetime, MultipleLocationIds, PosTechnology, SETCapabilities FROM ILP-Components; PREQ ::= SEQUENCE { sLPMode SLPMode, approvedPosMethods locationId multipleLocationIds position triggerParams sPCSETKey Spctid sPCSETKeylifetime qoP sETCapabilities notificationMode }
PosTechnology OPTIONAL, LocationId OPTIONAL, MultipleLocationIds OPTIONAL, Position OPTIONAL, TriggerParams OPTIONAL, SPCSETKey OPTIONAL, SPCTID OPTIONAL, SPCSETKeylifetime OPTIONAL, QoP OPTIONAL, SETCapabilities OPTIONAL, NotificationMode OPTIONAL,
SLPMode ::= ENUMERATED {proxy(0), nonProxy(1)} TriggerParams ::= SEQUENCE { triggerType TriggerType, periodicTriggerParams PeriodicTriggerParams } TriggerType ::= ENUMERATED { periodic(0), areaEvent(1), } PeriodicTriggerParams ::= SEQUENCE{ numberOfFixes INTEGER(1..8639999), intervalBetweenFixes INTEGER(1..8639999), startTime INTEGER(0..2678400) OPTIONAL, } -- intervalBetweenFixes and startTime are in seconds. -- numberOfFixes * intervalBetweenFixes shall not exceed 8639999 -- (100 days in seconds) for compatibility with OMA MLP and RLP -- startTime is in relative time in units of seconds measured from now -- a value of 0 signifies now, a value of startTime signifies startTime -- seconds from now NotificationMode ::= ENUMERATED {normal(0), basedOnLocation(1), } END
OPTIONAL,
OMA-TS-ILP-V2_0_1-20121205-A
Page 267 (295)
13.2.2
PRES
ILP-PRES DEFINITIONS AUTOMATIC TAGS ::= BEGIN EXPORTS PRES; IMPORTS Position, SPCStatusCode, PosTechnology, PosMethod, GNSSPosTechnology FROM ILP-Components; PRES ::= SEQUENCE { preferredPosMethod gnssPosTechnology supportedPosMethods position sPCstatusCode } END PosMethod OPTIONAL, GNSSPosTechnology OPTIONAL, PosTechnology OPTIONAL, Position OPTIONAL, SPCStatusCode OPTIONAL,
13.2.3
PRPT
ILP-PRPT DEFINITIONS AUTOMATIC TAGS ::= BEGIN EXPORTS PRPT; IMPORTS Position, StatusCode FROM ILP-Components; PRPT ::= SEQUENCE { position Position, fixNumber INTEGER(1.. 8639999) OPTIONAL, statusCode StatusCode OPTIONAL, } END
13.2.4
PLREQ
ILP-PLREQ DEFINITIONS AUTOMATIC TAGS ::= BEGIN EXPORTS PLREQ; IMPORTS LocationId, MultipleLocationIds FROM ILP-Components; PLREQ ::= SEQUENCE { locationId multipleLocationIds } END
LocationId, MultipleLocationIds OPTIONAL,
OMA-TS-ILP-V2_0_1-20121205-A
Page 268 (295)
13.2.5
PLRES
ILP-PLRES DEFINITIONS AUTOMATIC TAGS ::= BEGIN EXPORTS PLRES; IMPORTS Position, StatusCode, maxPosSize FROM ILP-Components; PLRES ::= SEQUENCE { positionResults } PositionResults,
PositionResults ::= SEQUENCE SIZE (1..maxPosSize) OF PositionResult PositionResult ::= CHOICE { position Position, statusCode StatusCode, } END
13.2.6
PINIT
ILP-PINIT DEFINITIONS AUTOMATIC TAGS ::= BEGIN EXPORTS PINIT; IMPORTS LocationId, Position, PosMethod, MultipleLocationIds, PosPayLoad, SETCapabilities, UTRAN-GPSReferenceTimeResult, UTRAN-GANSSReferenceTimeResult, GNSSPosTechnology, GANSSSignals FROM ILP-Components; PINIT ::= SEQUENCE { sETCapabilities locationId posMethod requestedAssistData position posPayLoad multipleLocationIds utran-GPSReferenceTimeResult OPTIONAL, utran-GANSSReferenceTimeResult gnssPosTechnology } RequestedAssistData ::= SEQUENCE { almanacRequested utcModelRequested ionosphericModelRequested dgpsCorrectionsRequested referenceLocationRequested referenceTimeRequested SETCapabilities, LocationId, PosMethod OPTIONAL, RequestedAssistData OPTIONAL, Position OPTIONAL, PosPayLoad OPTIONAL, MultipleLocationIds OPTIONAL, UTRAN-GPSReferenceTimeResult UTRAN-GANSSReferenceTimeResult OPTIONAL, GNSSPosTechnology OPTIONAL,
BOOLEAN, BOOLEAN, BOOLEAN, BOOLEAN, BOOLEAN, -- Note: Used also for GANSS BOOLEAN,
OMA-TS-ILP-V2_0_1-20121205-A
Page 269 (295)
acquisitionAssistanceRequested BOOLEAN, realTimeIntegrityRequested BOOLEAN, navigationModelRequested BOOLEAN, navigationModelData NavigationModel OPTIONAL, ganssRequestedCommonAssistanceDataList GanssRequestedCommonAssistanceDataList OPTIONAL, ganssRequestedGenericAssistanceDataList GanssRequestedGenericAssistanceDataList OPTIONAL, extendedEphemeris ExtendedEphemeris OPTIONAL, extendedEphemerisCheck ExtendedEphCheck OPTIONAL, } ExtendedEphemeris ::= SEQUENCE { validity INTEGER (1..256), -- Requested validity in 4 hour steps } ExtendedEphCheck ::= SEQUENCE { beginTime GPSTime, -- Begin time of ephemeris extension held by SET endTime GPSTime, -- End time of ephemeris extension held by SET } GPSTime ::= SEQUENCE { gPSWeek INTEGER (0..1023), gPSTOWhour INTEGER (0..167), } GanssRequestedCommonAssistanceDataList ::= SEQUENCE { ganssReferenceTime BOOLEAN, ganssIonosphericModel BOOLEAN, ganssAdditionalIonosphericModelForDataID00 BOOLEAN, ganssAdditionalIonosphericModelForDataID11 BOOLEAN, ganssEarthOrientationParameters BOOLEAN, } GanssRequestedGenericAssistanceDataList ::= SEQUENCE(SIZE(1..maxGANSS)) OF GanssReqGenericData GanssReqGenericData ::= SEQUENCE { ganssId INTEGER(0..15), -- coding according to parameter definition in Section 12.14 ganssSBASid BIT STRING(SIZE(3)) OPTIONAL, --coding according to parameter definition in section 12.14 ganssRealTimeIntegrity BOOLEAN OPTIONAL, ganssDifferentialCorrection DGANSS-Sig-Id-Req OPTIONAL, ganssAlmanac BOOLEAN, ganssNavigationModelData GanssNavigationModelData OPTIONAL, ganssTimeModels BIT STRING(SIZE(16)) OPTIONAL, ganssReferenceMeasurementInfo BOOLEAN, ganssDataBits GanssDataBits OPTIONAL, ganssUTCModel BOOLEAN, ganssAdditionalDataChoices GanssAdditionalDataChoices OPTIONAL, ganssAuxiliaryInformation BOOLEAN, ganssExtendedEphemeris ExtendedEphemeris OPTIONAL, ganssExtendedEphemerisCheck GanssExtendedEphCheck OPTIONAL, } DGANSS-Sig-Id-Req ::= BIT STRING (SIZE(8)) - coding according to parameter definition in Section 12.15
OMA-TS-ILP-V2_0_1-20121205-A
Page 270 (295)
GanssNavigationModelData ::= SEQUENCE { ganssWeek INTEGER(0..4095), ganssToe INTEGER(0..167), t-toeLimit INTEGER(0..10), satellitesListRelatedDataList SatellitesListRelatedDataList OPTIONAL, ...} SatellitesListRelatedDataList ::= SEQUENCE(SIZE(0..maxGANSSSat)) OF SatellitesListRelatedData SatellitesListRelatedData ::= SEQUENCE { satId INTEGER(0..63), iod INTEGER(0..1023), ...} maxGANSS INTEGER ::= 16 maxGANSSSat INTEGER ::= 32 GanssDataBits ::= SEQUENCE { ganssTODmin INTEGER (0..59), reqDataBitAssistanceList ReqDataBitAssistanceList, } ReqDataBitAssistanceList ::= SEQUENCE { gnssSignals GANSSSignals, ganssDataBitInterval INTEGER (0..15), ganssDataBitSatList SEQUENCE (SIZE(1..maxGANSSSat)) OF INTEGER (0..63) OPTIONAL, } GanssAdditionalDataChoices ::= SEQUENCE orbitModelID INTEGER(0..7) clockModelID INTEGER(0..7) utcModelID INTEGER(0..7) almanacModelID INTEGER(0..7) } { OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
GanssExtendedEphCheck ::= SEQUENCE { beginTime GANSSextEphTime, -- Begin time of ephemeris extension held by SET endTime GANSSextEphTime, -- End time of ephemeris extension held by SET } GANSSextEphTime ::= SEQUENCE { gANSSday INTEGER (0..8191), gANSSTODhour INTEGER (0..23), } NavigationModel ::= SEQUENCE { gpsWeek INTEGER(0..1023), gpsToe INTEGER(0..167), Nsat INTEGER(0..31), toeLimit INTEGER(0..10), satInfo SatelliteInfo OPTIONAL, } SatelliteInfo ::= SEQUENCE (SIZE (1..31)) OF SatelliteInfoElement
OMA-TS-ILP-V2_0_1-20121205-A
Page 271 (295)
SatelliteInfoElement ::= SEQUENCE { satId INTEGER(0..63), Iode INTEGER(0..255), } END
13.2.7
PAUTH
ILP-PAUTH DEFINITIONS AUTOMATIC TAGS ::= BEGIN EXPORTS PAUTH; IMPORTS SPCSETKey, SPCTID, SPCSETKeylifetime FROM ILP-Components; PAUTH ::= SEQUENCE { sPCSETKey SPCSETKey, Spctid SPCTID, sPCSETKeylifetime SPCSETKeylifetime OPTIONAL, } END
13.2.8
PALIVE
ILP-PALIVE DEFINITIONS AUTOMATIC TAGS ::= BEGIN EXPORTS PALIVE; IMPORTS SPCStatusCode FROM ILP-Components; PALIVE ::= SEQUENCE { sPCStatusCode SPCStatusCode OPTIONAL, } END
13.2.9
PEND
ILP-PEND DEFINITIONS AUTOMATIC TAGS ::= BEGIN EXPORTS PEND; IMPORTS Position, StatusCode FROM ILP-Components; PEND ::= SEQUENCE { position Position OPTIONAL, statusCode StatusCode OPTIONAL, }
OMA-TS-ILP-V2_0_1-20121205-A
Page 272 (295)
END
13.2.10 PMESS
ILP-PMESS DEFINITIONS AUTOMATIC TAGS ::= BEGIN EXPORTS PMESS; IMPORTS Velocity, PosPayLoad, UTRAN-GPSReferenceTimeResult, UTRANGANSSReferenceTimeResult, UTRAN-GPSReferenceTimeAssistance, UTRANGANSSReferenceTimeAssistance FROM ILP-Components; PMESS ::= SEQUENCE { posPayLoad PosPayLoad, velocity Velocity OPTIONAL, utran-GPSReferenceTimeAssistance utran-GPSReferenceTimeResult OPTIONAL, utran-GANSSReferenceTimeAssistance utran-GANSSReferenceTimeResult } END
UTRAN-GPSReferenceTimeAssistance OPTIONAL, UTRAN-GPSReferenceTimeResult UTRAN-GANSSReferenceTimeAssistance OPTIONAL, UTRAN-GANSSReferenceTimeResult OPTIONAL,
13.3 Common Elements

ILP-Components DEFINITIONS AUTOMATIC TAGS ::= BEGIN EXPORTS Version, SessionID2, LocationId, PosTechnology, Position, StatusCode, QoP, PosMethod, Velocity, PosPayLoad, SETCapabilities, SPCStatusCode, SPCSETKey, SPCTID, SPCSETKeylifetime, maxPosSize, UTRAN-GPSReferenceTimeResult, UTRAN-GANSSReferenceTimeResult, GNSSPosTechnology, UTRANGPSReferenceTimeAssistance, UTRAN-GANSSReferenceTimeAssistance, MultipleLocationIds, GANSSSignals; -- protocol version expressed as x.y.z (e.g., 5.1.0) Version ::= SEQUENCE { maj INTEGER(0..255), min INTEGER(0..255), servind INTEGER(0..255)} SessionID2 ::= SEQUENCE { slcSessionID SlcSessionID, setSessionID SetSessionID OPTIONAL, spcSessionID SpcSessionID OPTIONAL -- the semantics of OPTIONAL applies to the encoding only. -- The parameter itself is MANDATORY. Since the spcSessionID is allocated by the SPC, -- there is no spcSessionID to be transmitted in the ILP PREQ message. } SetSessionID ::= SEQUENCE { sessionId INTEGER(0..65535),
OMA-TS-ILP-V2_0_1-20121205-A
Page 273 (295)
setId }
SETId
SETId ::= CHOICE { msisdn OCTET STRING(SIZE (8)), mdn OCTET STRING(SIZE (8)), min BIT STRING(SIZE (34)), -- coded according to TIA-553 imsi OCTET STRING(SIZE (8)), nai IA5String(SIZE (1..1000)), iPAddress IPAddress, } -- msisdn, mnd and imsi are a BCD (Binary Coded Decimal) string -- represent digits from 0 through 9, -- two digits per octet, each digit encoded 0000 to 1001 (0 to 9) -- bits 8765 of octet n encoding digit 2n -- bits 4321 of octet n encoding digit 2(n-1) +1 -- not used digits in the string shall be filled with 1111 SlcSessionID ::= SEQUENCE { sessionID OCTET STRING(SIZE (4)), slcId NodeAddress } SpcSessionID ::= SEQUENCE { sessionID OCTET STRING(SIZE (4)), spcId NodeAddress } IPAddress ::= CHOICE { ipv4Address OCTET STRING(SIZE (4)), ipv6Address OCTET STRING(SIZE (16)) } NodeAddress ::= CHOICE { iPAddress IPAddress, Fqdn FQDN, } FQDN ::= VisibleString(FROM (a..z | A..Z | 0..9 |.-))(SIZE (1..255)) LocationId ::= SEQUENCE { cellInfo CellInfo, status Status, } Status ::= ENUMERATED {stale(0), current(1), unknown(2), } MultipleLocationIds ::= SEQUENCE SIZE (1..maxLidSize) OF LocationIdData LocationIdData ::= SEQUENCE { locationId LocationId, relativetimestamp RelativeTime OPTIONAL, -- if relativetimestamp is present, -- then data represents historical measurement, if absent, data represents -- current measurements servingFlag BOOLEAN, -- if true measurements represent serving cell }
OMA-TS-ILP-V2_0_1-20121205-A
Page 274 (295)
-- status in locationId indicates whether cellInfo is current or stale relative to timestamp RelativeTime ::= INTEGER (0..65535) relative time to current Location Id in multiples of 0.01sec maxLidSize INTEGER ::= 64
SETCapabilities ::= SEQUENCE { posTechnology PosTechnology, prefMethod PrefMethod, posProtocol PosProtocol, supportedBearers SupportedBearers OPTIONAL, ...} PosTechnology ::= SEQUENCE { agpsSETassisted BOOLEAN, agpsSETBased BOOLEAN, autonomousGPS BOOLEAN, Aflt BOOLEAN, Ecid BOOLEAN, Eotd BOOLEAN, Otdoa BOOLEAN, gANSSPositionMethods GANSSPositionMethods OPTIONAL, } GANSSPositionMethods ::= SEQUENCE (SIZE(1..16)) OF GANSSPositionMethod GANSSPositionMethod ::= SEQUENCE { ganssId INTEGER(0..15), -- coding according to parameter definition in Section 12.14 ganssSBASid BIT STRING(SIZE(3)) OPTIONAL, --coding according to parameter definition in section 12.14 gANSSPositioningMethodTypes GANSSPositioningMethodTypes, gANSSSignals GANSSSignals, } GANSSPositioningMethodTypes ::= SEQUENCE { setAssisted BOOLEAN, setBased BOOLEAN, autonomous BOOLEAN, } -- indicates MS support for particular GANSS signals and frequencies -- coding according to parameter definition in Section 12.14 GANSSSignals ::= BIT STRING { signal1 (0), signal2 (1), signal3 (2), signal4 (3), signal5 (4), signal6 (5), signal7 (6), signal8 (7)} (SIZE (1..8)) PrefMethod ::= ENUMERATED {
OMA-TS-ILP-V2_0_1-20121205-A
Page 275 (295)
agnssSETAssistedPreferred, agnssSETBasedPreferred, noPreference, } -----Note: In ULP V2.0, the names of the enumerations are kept the same as in ULP V1.0. ie. Agps in the TS ULP actually shall be interpreted as agnss. This means that agpsSETassistedPreferred and agpsSETBasedPreferred in ULP V2.0 map to agnssSETAssistedPreferred and agnssSETBasedPreferred in ILP.
PosProtocol ::= SEQUENCE { tia801 BOOLEAN, rrlp BOOLEAN, rrc BOOLEAN, lpp BOOLEAN, posProtocolVersionRRLP PosProtocolVersion3GPP OPTIONAL, posProtocolVersionRRC PosProtocolVersion3GPP OPTIONAL, posProtocolVersionTIA801 PosProtocolVersion3GPP2 OPTIONAL, posProtocolVersionLPP PosProtocolVersion3GPP OPTIONAL, ...} PosProtocolVersion3GPP ::= SEQUENCE { majorVersionField INTEGER(0..255), technicalVersionField INTEGER(0..255), editorialVersionField INTEGER(0..255), } PosProtocolVersion3GPP2 ::= SEQUENCE (SIZE(1..8)) OF Supported3GPP2PosProtocolVersion Supported3GPP2PosProtocolVersion ::= SEQUENCE { revisionNumber BIT STRING(SIZE (6)), -- the location standard revision number the SET supports coded according to 3GPP2 C.S0022 pointReleaseNumber INTEGER(0..255), internalEditLevel INTEGER(0..255), } SupportedBearers ::= SEQUENCE { gsm BOOLEAN, wcdma BOOLEAN, lte BOOLEAN, cdma BOOLEAN, hprd BOOLEAN, umb BOOLEAN, wlan BOOLEAN, wiMAX BOOLEAN, } CellInfo ::= gsmCell wcdmaCell Information cdmaCell hrpdCell umbCell lteCell wlanAP wimaxBS } CHOICE { GsmCellInformation, WcdmaCellInformation, --WCDMA Cell Information/TD-SCDMA Cell CdmaCellInformation, HrpdCellInformation, UmbCellInformation, LteCellInformation, WlanAPInformation, WimaxBSInformation,
OMA-TS-ILP-V2_0_1-20121205-A
Page 276 (295)
UTRAN-GPSReferenceTimeResult ::= SEQUENCE { -- For ue-GPSTimingOfCell values above 37158911999999 are not -- used in this version of the specification -- Actual value utran-GPSTimingOfCell = (ms-part * 4294967296) + ls-part -- used on the uplink i.e. reported by the SET to the SLP set-GPSTimingOfCell SEQUENCE { ms-part INTEGER (0.. 16383), ls-part INTEGER (0..4294967295)}, modeSpecificInfo CHOICE { fdd SEQUENCE { referenceIdentity PrimaryCPICH-Info}, tdd SEQUENCE { referenceIdentity CellParametersID} }, sfn INTEGER (0..4095), gpsReferenceTimeUncertainty INTEGER (0..127) OPTIONAL, } UTRAN-GANSSReferenceTimeResult ::= SEQUENCE { ganssTimeID INTEGER (0..15), set-GANSSReferenceTime SET-GANSSReferenceTime, } SET-GANSSReferenceTime ::= SEQUENCE { -- Actual value [ns] = (ms-Part * 4294967296 + ls-Part) * 250 -- Actual values [ns] > 86399999999750 are reserved and are considered a -- protocol error set-GANSSTimingOfCell SEQUENCE { ms-part INTEGER (0..80), ls-part INTEGER (0..4294967295)} OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { referenceIdentity PrimaryCPICH-Info}, tdd SEQUENCE { referenceIdentity CellParametersID}} OPTIONAL, sfn INTEGER (0..4095), ganss-TODUncertainty INTEGER (0..127) OPTIONAL, } GNSSPosTechnology ::= SEQUENCE { gps BOOLEAN, galileo BOOLEAN, sbas BOOLEAN, modernized-gps BOOLEAN, qzss BOOLEAN, glonass BOOLEAN, } Position ::= SEQUENCE { timestamp UTCTime, -- shall include seconds and shall use UTC time. PositionEstimate PositionEstimate, velocity Velocity OPTIONAL, } PositionEstimate ::= SEQUENCE { latitudeSign ENUMERATED {north, south}, latitude INTEGER(0..8388607),
OMA-TS-ILP-V2_0_1-20121205-A
Page 277 (295)
longitude INTEGER(-8388608..8388607), uncertainty SEQUENCE {uncertaintySemiMajor INTEGER(0..127), uncertaintySemiMinor INTEGER(0..127), orientationMajorAxis INTEGER(0..180)} OPTIONAL, -- angle in degree between major axis and North confidence INTEGER(0..100) OPTIONAL, altitudeInfo AltitudeInfo OPTIONAL, } Coding as in [3GPP GAD] AltitudeInfo ::= SEQUENCE { altitudeDirection ENUMERATED {height, depth}, altitude INTEGER(0..32767), altUncertainty INTEGER(0..127), } based on 3GPP TS 23.032 CdmaCellInformation ::= SEQUENCE { refNID INTEGER(0..65535), -- Network Id refSID INTEGER(0..32767), -- System Id refBASEID INTEGER(0..65535), -- Base Station Id refBASELAT INTEGER(0..4194303), -- Base Station Latitude reBASELONG INTEGER(0..8388607), -- Base Station Longitude refREFPN INTEGER(0..511), -- Base Station PN Code refWeekNumber INTEGER(0..65535), -- GPS Week Number refSeconds INTEGER(0..4194303), -- GPS Seconds ...} GsmCellInformation ::= SEQUENCE { refMCC INTEGER(0..999), -- Mobile Country Code refMNC INTEGER(0..999), -- Mobile Network Code refLAC INTEGER(0..65535), -- Location area code refCI INTEGER(0..65535), -- Cell identity Nmr NMR OPTIONAL, Ta INTEGER(0..255) OPTIONAL, --Timing Advance } WcdmaCellInformation ::= refMCC refMNC refUC frequencyInfo primaryScramblingCode measuredResultsList cellParametersId timingAdvance } TimingAdvance ::= Ta tAResolution chipRate } SEQUENCE { INTEGER(0..999), -- Mobile Country Code INTEGER(0..999), -- Mobile Network Code INTEGER(0..268435455), -- Cell identity FrequencyInfo OPTIONAL, INTEGER(0..511) OPTIONAL, -- Not applicable for TDD MeasuredResultsList OPTIONAL, INTEGER(0..127) OPTIONAL, -- Not applicable for FDD TimingAdvance OPTIONAL, -- Not applicable for FDD
SEQUENCE { INTEGER (0..8191), TAResolution OPTIONAL, --If missing, resolution is 0.125 chips ChipRate OPTIONAL, -If missing, chip rate is 1.28 Mchip/s
TAResolution ::= ENUMERATED {res10chip(0),res05chip(1),res0125chip(2), } Corresponding to 1.0-chip, 0.5-chip and 0.125-chip resolutions, respectively ChipRate ::= ENUMERATED {tdd128(0),tdd384(1), tdd768(2), } - Corresponding to 1.28-Mchips/s, 3.84-Mchips/s and 7.68-Mchips/s chip rates, respectively
OMA-TS-ILP-V2_0_1-20121205-A
Page 278 (295)
HrpdCellInformation ::= SEQUENCE { refSECTORID BIT STRING(SIZE (128)) OPTIONAL, -- HRPD Sector Id refBASELAT INTEGER(0..4194303), -- Base Station Latitude reBASELONG INTEGER(0..8388607), -- Base Station Longitude refWeekNumber INTEGER(0..65535), -- GPS Week Number refSeconds INTEGER(0..4194303), -- GPS Seconds } UmbCellInformation ::= SEQUENCE { refSECTORID BIT STRING(SIZE (128)), -- UMB Sector Id refMCC INTEGER(0..999), -- Mobile Country Code refMNC INTEGER(0..999), -- Mobile Network Code refBASELAT INTEGER(0..4194303), -- Base Station Latitude reBASELONG INTEGER(0..8388607), -- Base Station Longitude refWeekNumber INTEGER(0..65535), -- GPS Week Number refSeconds INTEGER(0..4194303), -- GPS Seconds } -- LTE Cell info per 3GPP TS 36.331. -- If not otherwise stated info is related to serving cell LteCellInformation ::= SEQUENCE { cellGlobalIdEUTRA CellGlobalIdEUTRA, physCellId PhysCellId, trackingAreaCode TrackingAreaCode, rsrpResult RSRP-Range OPTIONAL, rsrqResult RSRQ-Range OPTIONAL, Ta INTEGER(0..1282) OPTIONAL, -- Currently used Timing Advance value (NTA/16 as per [3GPP 36.213]) measResultListEUTRA MeasResultListEUTRA OPTIONAL, -- Neighbour measurements , earfcn INTEGER(0..65535) OPTIONAL } -- Measured results of neighbours cells per 3GPP TS 36.331 MeasResultListEUTRA ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultEUTRA MeasResultEUTRA ::= physCellId cgi-Info SEQUENCE { cellGlobalId trackingAreaCode } OPTIONAL, measResult rsrpResult rsrqResult , earfcn } } SEQUENCE { PhysCellId, CellGlobalIdEUTRA, TrackingAreaCode SEQUENCE { RSRP-Range RSRQ-Range OPTIONAL, OPTIONAL, -- Mapping to measured values -- in 3GPP TS 36.133
INTEGER(0..65535) OPTIONAL
PhysCellId ::= INTEGER (0..503) TrackingAreaCode ::= BIT STRING (SIZE (16)) CellGlobalIdEUTRA ::= SEQUENCE {
OMA-TS-ILP-V2_0_1-20121205-A
Page 279 (295)
plmn-Identity PLMN-Identity, cellIdentity CellIdentity, } PLMN-Identity ::= SEQUENCE { mcc MCC OPTIONAL, mnc MNC } CellIdentity ::= BIT STRING (SIZE (28)) MCC ::= SEQUENCE (SIZE (3)) OF MCC-MNC-Digit MNC ::= SEQUENCE (SIZE (2..3)) OF MCC-MNC-Digit MCC-MNC-Digit ::= INTEGER (0..9) RSRP-Range ::= INTEGER(0..97) RSRQ-Range ::= INTEGER(0..34) maxCellReport INTEGER ::= 8 WlanAPInformation ::= SEQUENCE { -- as per 802.11v apMACAddress BIT STRING(SIZE (48)), -- AP MAC Address apTransmitPower INTEGER(-127..128) OPTIONAL, -- AP transmit power in dbm apAntennaGain INTEGER(-127..128) OPTIONAL, -- AP antenna gain in dBi apSignaltoNoise INTEGER(-127..128) OPTIONAL, -- AP S/N received at SET apDeviceType ENUMERATED {wlan802-11a(0), wlan802-11b(1), wlan802-11g(2), } OPTIONAL, apSignalStrength INTEGER(-127..128) OPTIONAL, -- AP signal strength at SET apChannelFrequency INTEGER(0..256) OPTIONAL, -- AP channel/frequency of Tx/Rx apRoundTripDelay RTD OPTIONAL, -- Round Trip Delay between SET and AP setTransmitPower INTEGER(-127..128) OPTIONAL, -- SET transmit power in dBm setAntennaGain INTEGER (-127..128) OPTIONAL, -- SET antenna gain in dBi setSignaltoNoise INTEGER (-127..128) OPTIONAL, -- SET S/N received at AP setSignalStrength INTEGER(-127..128) OPTIONAL, -- SET signal strength at AP apReportedLocation ReportedLocation OPTIONAL, -- AP Location reported by AP } RTD ::= SEQUENCE { -- as per 802.11v rTDValue INTEGER(0..16777216), -- measured RTD value corresponding to -- about 500km in units of 1/10 of nanoseconds rTDUnits RTDUnits, -- units of RTD rTDAccuracy INTEGER(0..255) OPTIONAL, -- RTD accuracy } RTDUnits ::= ENUMERATED { microseconds(0), hundredsofnanoseconds(1), tensofnanoseconds(2), nanoseconds(3), tenthsofnanoseconds(4), } ReportedLocation ::= SEQUENCE { -- as per 802.11v locationEncodingDescriptor LocationEncodingDescriptor, locationData LocationData, -- location data field } LocationEncodingDescriptor ::= ENUMERATED {
OMA-TS-ILP-V2_0_1-20121205-A
Page 280 (295)
Lci(0),Asn1(1), } LocationData ::= SEQUENCE { locationAccuracy INTEGER(0..4294967295) OPTIONAL, locationValue OCTET STRING (SIZE(1..128)), } WimaxBSInformation ::= SEQUENCE { wimaxBsID WimaxBsID, -- WiMax serving base station ID wimaxRTD WimaxRTD OPTIONAL, -- Round Trip Delay measurements wimaxNMRList WimaxNMRList OPTIONAL, -- Network measurements } WimaxBsID ::= SEQUENCE { bsID-MSB BIT STRING (SIZE(24)) OPTIONAL, bsID-LSB BIT STRING (SIZE(24)), } -- if only LSB is present, MSB is assumed to be identical to the current serving BS or clamped on network value WimaxRTD ::= SEQUENCE { Rtd INTEGER (0..65535), -- Round trip delay of serving BS in units of 10 ns rTDstd INTEGER (0..1023) OPTIONAL, -- Standard deviation of round trip delay in units of 10 ns } WimaxNMRList ::= SEQUENCE (SIZE (1..maxWimaxBSMeas)) OF WimaxNMR
WimaxNMR ::= SEQUENCE { wimaxBsID WimaxBsID, -- WiMax BS ID for the measurement relDelay INTEGER (-32768..32767) OPTIONAL, -- Relative delay for this neighbouring BSs to the serving cell in units of 10 ns relDelaystd INTEGER (0..1023) OPTIONAL, -- Standard deviation of Relative delay in units of 10 ns Rssi INTEGER (0..255) OPTIONAL, -- RSSI in 0.25 dBm steps, starting from 103.75 dBm rSSIstd INTEGER (0..63) OPTIONAL, -- Standard deviation of RSSI in Db bSTxPower INTEGER (0..255) OPTIONAL, -- BS transmit power in 0.25 dBm steps, starting from -103.75 dBm Cinr INTEGER (0..255) OPTIONAL, -- in Db cINRstd INTEGER (0..63) OPTIONAL, -- Standard deviation of CINR in Db bSLocation ReportedLocation OPTIONAL, -- Reported location of the BS } maxWimaxBSMeas INTEGER ::= 32 FrequencyInfo ::= SEQUENCE { modeSpecificInfo CHOICE {fdd tdd }, } FrequencyInfoFDD ::= SEQUENCE { uarfcn-UL UARFCN OPTIONAL, uarfcn-DL UARFCN, }
FrequencyInfoFDD, FrequencyInfoTDD,
OMA-TS-ILP-V2_0_1-20121205-A
Page 281 (295)
FrequencyInfoTDD ::= SEQUENCE {uarfcn-Nt } UARFCN ::= INTEGER(0..16383)
UARFCN,
NMR ::= SEQUENCE (SIZE (1..15)) OF NMRelement NMRelement ::= SEQUENCE { Arfcn INTEGER(0..1023), Bsic INTEGER(0..63), rxLev INTEGER(0..63), } MeasuredResultsList ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasuredResults MeasuredResults ::= SEQUENCE { frequencyInfo FrequencyInfo OPTIONAL, utra-CarrierRSSI UTRA-CarrierRSSI OPTIONAL, cellMeasuredResultsList CellMeasuredResultsList OPTIONAL} CellMeasuredResultsList ::= SEQUENCE (SIZE (1..maxCellMeas)) OF CellMeasuredResults -- SPARE: UTRA-CarrierRSSI, Max = 76 -- Values above Max are spare UTRA-CarrierRSSI ::= INTEGER(0..127) CellMeasuredResults ::= SEQUENCE { cellIdentity INTEGER(0..268435455) OPTIONAL, modeSpecificInfo CHOICE {fdd SEQUENCE {primaryCPICH-Info PrimaryCPICH-Info, cpich-Ec-N0 CPICH-Ec-N0 OPTIONAL, cpich-RSCP CPICH-RSCP OPTIONAL, pathloss Pathloss OPTIONAL}, tdd SEQUENCE {cellParametersID CellParametersID, proposedTGSN TGSN OPTIONAL, primaryCCPCH-RSCP PrimaryCCPCH-RSCP OPTIONAL, pathloss Pathloss OPTIONAL, timeslotISCP-List TimeslotISCP-List OPTIONAL - NOTE: TimeSlotISCP measurement list cannot be -- interpreted without the knowledge of Cell Info -- as defined in [3GPP RRC]. }}} CellParametersID ::= INTEGER(0..127) TGSN ::= INTEGER(0..14) PrimaryCCPCH-RSCP ::= INTEGER(0..127) -- SPARE: TimeslotISCP, Max = 91 -- Values above Max are spare TimeslotISCP ::= INTEGER(0..127) TimeslotISCP-List ::= SEQUENCE (SIZE (1..maxTS)) OF TimeslotISCP
OMA-TS-ILP-V2_0_1-20121205-A
Page 282 (295)
PrimaryCPICH-Info ::= SEQUENCE {primaryScramblingCode -- SPARE: CPICH-Ec-No, Max = 49 -- Values above Max are spare CPICH-Ec-N0 ::= INTEGER(0..63) ---------------
INTEGER(0..511)}
SPARE: CPICH- RSCP, data range from 0 to 91 and from 123 to 127. Values from 92 to 122 are spare the encoding of cpich-RSCP is (as per 25.331 V5.11.0) cpich-RSCP = 123 CPICH RSCP <-120 dBm cpich-RSCP = 124 -120 CPICH RSCP < -119 dBm cpich-RSCP = 125 -119 CPICH RSCP < -118 dBm cpich-RSCP = 126 -118 CPICH RSCP < -117 dBm cpich-RSCP = 127 -117 CPICH RSCP < -116 dBm cpich-RSCP = 0 -116 CPICH RSCP < -115 dBm cpich-RSCP = 1 -115 CPICH RSCP < -114 dBm cpich-RSCP = 89 -27 CPICH RSCP < -26 dBm cpich-RSCP = 90 -26 CPICH RSCP < -25 dBm cpich-RSCP = 91 -25 CPICH RSCP dBm
CPICH-RSCP ::= INTEGER(0..127) -- SPARE: Pathloss, Max = 158 -- Values above Max are spare Pathloss ::= INTEGER(46..173) maxCellMeas INTEGER ::= 32 maxFreq INTEGER ::= 8 maxTS INTEGER ::= 14 UTRAN-GPSReferenceTimeAssistance ::= SEQUENCE { utran-GPSReferenceTime UTRAN-GPSReferenceTime, gpsReferenceTimeUncertainty INTEGER (0..127) OPTIONAL, utranGPSDriftRate UTRANGPSDriftRate OPTIONAL} UTRAN-GPSReferenceTime ::= SEQUENCE { -- For utran-GPSTimingOfCell values above 2322431999999 are not -- used in this version of the specification -- Actual value utran-GPSTimingOfCell = (ms-part * 4294967296) + lspart -- used on the downlink i.e. sent from the SLP to the SET utran-GPSTimingOfCell SEQUENCE { ms-part INTEGER (0..1023), ls-part INTEGER (0..4294967295) }, modeSpecificInfo CHOICE { fdd SEQUENCE { referenceIdentity PrimaryCPICH-Info}, tdd SEQUENCE { referenceIdentity CellParametersID}} OPTIONAL, sfn INTEGER (0..4095) } UTRANGPSDriftRate ::= ENUMERATED {
OMA-TS-ILP-V2_0_1-20121205-A
Page 283 (295)
utran-GPSDrift0, utran-GPSDrift1, utran-GPSDrift2, utran-GPSDrift5, utran-GPSDrift10, utran-GPSDrift15, utran-GPSDrift25, utran-GPSDrift50, utran-GPSDrift-1, utran-GPSDrift-2, utran-GPSDrift-5, utran-GPSDrift-10, utran-GPSDrift-15, utran-GPSDrift-25, utran-GPSDrift-50 } UTRAN-GANSSReferenceTimeAssistance ::= SEQUENCE { ganssTimeID INTEGER (0..15), utran-GANSSReferenceTime UTRAN-GANSSReferenceTime, ganssDay INTEGER (0..8191) OPTIONAL, utranGANSSDriftRate UTRANGANSSDriftRate OPTIONAL } UTRAN-GANSSReferenceTime ::= SEQUENCE { ganssTOD INTEGER (0..86399), utran-GANSSTimingOfCell INTEGER (0..3999999) OPTIONAL, modeSpecificInfo CHOICE { fdd SEQUENCE { referenceIdentity PrimaryCPICH-Info}, tdd SEQUENCE { referenceIdentity CellParametersID}} OPTIONAL, sfn INTEGER (0..4095), ganss-TODUncertainty INTEGER (0..127) OPTIONAL, ...} UTRANGANSSDriftRate ::= ENUMERATED { utran-GANSSDrift0, utran-GANSSDrift1, utran-GANSSDrift2, utran-GANSSDrift5, utran-GANSSDrift10, utran-GANSSDrift15, utran-GANSSDrift25, utran-GANSSDrift50, utran-GANSSDrift-1, utran-GANSSDrift-2, utran-GANSSDrift-5, utran-GANSSDrift-10, utran-GANSSDrift-15, utran-GANSSDrift-25, utran-GANSSDrift-50} StatusCode ::= ENUMERATED { unspecified(0), systemFailure(1), unexpectedMessage(2), protocolError(3), dataMissing(4), unexpectedDataValue(5), posMethodFailure(6), posMethodMismatch(7), posProtocolMismatch(8), targetSETnotReachable(9), versionNotSupported(10), resourceShortage(11), invalidSessionId(12), nonProxyModeNotSupported(13), proxyModeNotSupported(14), positioningNotPermitted(15), iLPTimeout(16), } QoP ::= SEQUENCE { horacc INTEGER(0..127), veracc INTEGER(0..127) OPTIONAL, -- as defined in 3GPP TS 23.032 uncertainty altitude maxLocAge INTEGER(0..65535) OPTIONAL, delay INTEGER(0..7) OPTIONAL, -- as defined in 3GPP TS 44.031 } Velocity ::= CHOICE { -- velocity definition as per 23.032 horvel Horvel, horandvervel Horandvervel, horveluncert Horveluncert, horandveruncert Horandveruncert, } Horvel ::= SEQUENCE {
OMA-TS-ILP-V2_0_1-20121205-A
Page 284 (295)
bearing horspeed } Horandvervel verdirect bearing horspeed verspeed }
BIT STRING(SIZE (9)), BIT STRING(SIZE (16)), ::= BIT BIT BIT BIT SEQUENCE { STRING(SIZE STRING(SIZE STRING(SIZE STRING(SIZE
(1)), (9)), (16)), (8)),
Horveluncert ::= SEQUENCE { bearing BIT STRING(SIZE (9)), horspeed BIT STRING(SIZE (16)), uncertspeed BIT STRING(SIZE (8)), } Horandveruncert ::= SEQUENCE { verdirect BIT STRING(SIZE bearing BIT STRING(SIZE horspeed BIT STRING(SIZE verspeed BIT STRING(SIZE horuncertspeed BIT STRING(SIZE veruncertspeed BIT STRING(SIZE } (1)), (9)), (16)), (8)), (8)), (8)),
PosMethod ::= ENUMERATED { agpsSETassisted(0), agpsSETbased(1), agpsSETassistedpref(2), agpsSETbasedpref(3), autonomousGPS(4), Aflt(5), Ecid(6), Eotd(7), Otdoa(8), agnssSETassisted(9), agnssSETbased(10), agnssSETassistedpref(11), agnssSETbasedpref(12), autonomousGNSS(13), } SPCSETKey ::= BIT STRING(SIZE (128)) SPCTID ::= SEQUENCE { Rand BIT STRING(SIZE (128)), slpFQDN FQDN, } SPCSETKeylifetime ::= INTEGER (1..24) units in hours PosPayLoad ::= CHOICE { rrcPayload OCTET STRING(SIZE (1..8192)), rrlpPayload OCTET STRING(SIZE (1..8192)), multiPosPayload MultiPosPayLoad, } MultiPosPayLoad ::= SEQUENCE { lPPPayload SEQUENCE (SIZE (1..3)) OF OCTET STRING(SIZE (1..60000)) OPTIONAL, Tia801Payload SEQUENCE (SIZE (1..3)) OF OCTET STRING(SIZE (1..60000)) OPTIONAL, } SPCStatusCode ::= ENUMERATED {operational(0), notOperational(1), reducedAvailability(2), }
OMA-TS-ILP-V2_0_1-20121205-A
Page 285 (295)
maxPosSize INTEGER ::= 1024 END
OMA-TS-ILP-V2_0_1-20121205-A
Page 286 (295)
Appendix A.
A.1
Reference
Change History
Date
17 Apr 2012 05 Dec 2012
(Informative)
Description
Status changed to Approved by TP Ref TP Doc # OMA-TP-2012-0170-INP_SUPL_20_for_Final_Approval Status changed to Approved by TP Ref TP Doc # OMA-TP-2012-0455-INP_SUPL_2.0.1_ERP_for_Notification
Approved Version History
OMA-TS-ILP-V2_0-20120417-A OMA-TS-ILP-V2_0_1-20121205-A
A.1.1
Draft/Candidate Version 2.0.1 History

Document Identifier Date
4 Dec 2012
Sections
5.1.4, 12.5.3, 12.14, 13.3,
Description
Implemented CRs: OMA-LOC-2012-0293-CR_SUPL_2.0.1_TS_ILP_corrections
Draft Versions OMA-TS-IPL-V2_0_1
OMA-TS-ILP-V2_0_1-20121205-A
Page 287 (295)
Appendix B.
B.1
B.1.1 B.1.2
Static Conformance Requirements
(Normative)
The notation used in this appendix is specified in [IOPPROC].
SCR for SLC

SLC Procedures ILP Protocol Interface
Item Function Reference Status Requirement
SLC procedures follow SCR of [SUPL2 ULP TS].
ILP-B-SLC-001 ILP-B-SLC-002 ILP-B-SLC-003
ILP encoding ILP transport Support of TCP/IP port number
ILP 10 ILP 10 ILP 10
M M M
B.1.3
ILP Messages
ILP-C-SLC-001 ILP-C-SLC-002 ILP-C-SLC-003 ILP-C-SLC-004 ILP-C-SLC-005 ILP-C-SLC-006 ILP-C-SLC-007 ILP-C-SLC-008 ILP-C-SLC-009 ILP-C-SLC-010
Support of PREQ Support of PRES Support of PRPT Support of PLREQ Support of PLRES Support of PINIT Support of PMESS Support of PAUTH Support of PALIVE Support of PEND
ILP 11 ILP 11 ILP 11 ILP 11 ILP 11 ILP 11 ILP 11 ILP 11 ILP 11 ILP 11
M M M M M O O O M M
B.1.4
Support of Parameters for Optional Functions

ILP-D-SLC-0001 ILP-D-SLC-0002 ILP-D-SLC-0003 ILP-D-SLC-0004 ILP-D-SLC-0005 ILP-D-SLC-0006 ILP-D-SLC-0007 ILP-D-SLC-0008
Support of locationId parameter in PREQ Support of position parameter in PREQ Support of triggerParams parameter in PREQ Support of multipleLocationIds parameter in PREQ Support of sPCSETKey parameter in PREQ Support of sPCTID parameter in PREQ Support of sPCSETKeylifetime parameter in PREQ Support of qoP parameter in
ILP 12 ILP 12 ILP 12 ILP 12 ILP 12 ILP 12 ILP 12 ILP 12
O O O O O O O O
OMA-TS-ILP-V2_0_1-20121205-A
Page 288 (295)
Item
Function
Reference
Status
Requirement
ILP-D-SLC-0009 ILP-D-SLC-0010 ILP-D-SLC-0011 ILP-D-SLC-0012
ILP-D-SLC-0013 ILP-D-SLC-0014 ILP-D-SLC-0015 ILP-D-SLC-0016 ILP-D-SLC-0017 ILP-D-SLC-0018 ILP-D-SLC-0019 ILP-D-SLC-0020 ILP-D-SLC-0021 ILP-D-SLC-0022 ILP-D-SLC-0023
ILP-D-SLC-0024
ILP-D-SLC-0025 ILP-D-SLC-0026 ILP-D-SLC-0027 ILP-D-SLC-0028 ILP-D-SLC-0029 ILP-D-SLC-0030 ILP-D-SLC-0031
PREQ Support of sETCapabilities parameter in PREQ Support of preferredPosMethod parameter in PRES Support of gnssPosTechnology parameter in PRES Support of supportedPosMethods parameter in PRES Support of position parameter in PRES Support of sPCStatusCode parameter in PRES Support of fixNumber parameter in PRPT Support of statusCode parameter in PRPT Support of multipleLocationIds parameter in PLREQ Support of posMethod parameter in PINIT Support of requestedAssistData parameter in PINIT Support of position parameter in PINIT Support of posPayLoad parameter in PINIT Support of multipleLocationIds parameter in PINIT Support of utranGPSReferenceTimeResult parameter in PINIT Support of utranGANSSReferenceTimeResult parameter in PINIT Support of gnssPosTechnology parameter in PINIT Support of sPCSETKeylifetime parameter in PAUTH Support of sPCStatusCode parameter in PALIVE Support of position parameter in PEND Support of statusCode parameter in PEND Support of velocity parameter in PMESS Support of utranGPSReferenceTimeAssistance parameter in PMESS
ILP 12 ILP 12 ILP 12 ILP 12
O O O O
ILP 12 ILP 12 ILP 12 ILP 12 ILP 12 ILP 12 ILP 12 ILP 12 ILP 12 ILP 12 ILP 12
O O O O O O O O O O O
ILP 12
ILP 12 ILP 12 ILP 12 ILP 12 ILP 12 ILP 12 ILP 12
O O O O O O O
OMA-TS-ILP-V2_0_1-20121205-A
Page 289 (295)
Item
Function
Reference
Status
Requirement
ILP-D-SLC-0032
ILP-D-SLC-0033
ILP-D-SLC-0034
Support of utranGPSReferenceTimeResult parameter in PMESS Support of utranGANSSReferenceTimeAssistan ce parameter in PMESS Support of utranGANSSReferenceTimeResult parameter in PMESS
ILP 12
ILP 12
ILP 12
B.2
B.2.1 B.2.2
SCR for SPC

SPC Procedures ILP Protocol Interface
SPC procedures follow SCR of [SUPL2 ULP TS].
ILP-B-SPC-001 ILP-B-SPC-002 ILP-B-SPC-003
ILP encoding ILP transport Support of TCP/IP port number
M M M
B.2.3
ILP Messages
ILP-C-SPC-001 ILP-C-SPC-002 ILP-C-SPC-003 ILP-C-SPC-004 ILP-C-SPC-005 ILP-C-SPC-006 ILP-C-SPC-007 ILP-C-SPC-008 ILP-C-SPC-009 ILP-C-SPC-010
Support of PREQ Support of PRES Support of PRPT Support of PLREQ Support of PLRES Support of PINIT Support of PMESS Support of PAUTH Support of PALIVE Support of PEND
ILP 11 ILP 11 ILP 11 ILP 11 ILP 11 ILP 11 ILP 11 ILP 11 ILP 11 ILP 11
M M M M M O O O M M
B.2.4
Support of Parameters for Optional Functions

ILP-D-SPC-0001 ILP-D-SPC-0002 ILP-D-SPC-0003 ILP-D-SPC-0004
Support of locationId parameter in PREQ Support of position parameter in PREQ Support of triggerParams parameter in PREQ Support of
O O O O
OMA-TS-ILP-V2_0_1-20121205-A
Page 290 (295)
Item
Function
Reference
Status
Requirement
ILP-D-SPC-0005 ILP-D-SPC-0006 ILP-D-SPC-0007
ILP-D-SPC-0008 ILP-D-SPC-0009
ILP-D-SPC-0010
ILP-D-SPC-0011
ILP-D-SPC-0012
ILP-D-SPC-0023
ILP-D-SPC-0024
multipleLocationIds parameter in PREQ Support of sPCSETKey parameter in PREQ Support of sPCTID parameter in PREQ Support of sPCSETKeylifetime parameter in PREQ Support of qoP parameter in PREQ Support of sETCapabilities parameter in PREQ Support of preferredPosMethod parameter in PRES Support of gnssPosTechnology parameter in PRES Support of supportedPosMethods parameter in PRES Support of position parameter in PRES Support of sPCStatusCode parameter in PRES Support of fixNumber parameter in PRPT Support of statusCode parameter in PRPT Support of multipleLocationIds parameter in PLREQ Support of posMethod parameter in PINIT Support of requestedAssistData parameter in PINIT Support of position parameter in PINIT Support of posPayLoad parameter in PINIT Support of multipleLocationIds parameter in PINIT Support of utranGPSReferenceTimeResu lt parameter in PINIT Support of utranGANSSReferenceTimeR
O O O
ILP 12 ILP 12
O O
ILP 12
ILP 12
ILP 12
ILP 12 ILP 12
O O
O O O
ILP 12 ILP 12
O O
O O O
ILP 12
ILP 12
OMA-TS-ILP-V2_0_1-20121205-A
Page 291 (295)
Item
Function
Reference
Status
Requirement
ILP-D-SPC-0025
ILP-D-SPC-0026
ILP-D-SPC-0027
ILP-D-SPC-0028 ILP-D-SPC-0029 ILP-D-SPC-0030 ILP-D-SPC-0031
ILP-D-SPC-0032
ILP-D-SPC-0033
ILP-D-SPC-0034
esult parameter in PINIT Support of gnssPosTechnology parameter in PINIT Support of sPCSETKeylifetime parameter in PAUTH Support of sPCStatusCode parameter in PALIVE Support of position parameter in PEND Support of statusCode parameter in PEND Support of velocity parameter in PMESS Support of utranGPSReferenceTimeAssis tance parameter in PMESS Support of utranGPSReferenceTimeResu lt parameter in PMESS Support of utranGANSSReferenceTimeA ssistance parameter in PMESS Support of utranGANSSReferenceTimeR esult parameter in PMESS
ILP 12
ILP 12
ILP 12
O O O O
ILP 12
ILP 12
ILP 12
OMA-TS-ILP-V2_0_1-20121205-A
Page 292 (295)
Appendix C.
Timer Tables
This Section defines the ILP relevant timers. Note that default timer value is informative. As a reference, ULP timers are shown in Appendix C.2.
C.1
Timer LT1 LT2
ILP Timers
Default value 5 sec. 5 sec. Description From sending of PREQ to receipt of PRES (successful case) or PEND (error case). This timer is only applicable to triggered scenarios. From sending of PLREQ to receipt of PLRES (successful case) or PEND (error case). If PLRES is received after LT2 has expired (and no PEND was sent) and before a new PLREQ has been sent, the SLC SHALL ignore the PLRES. If a new PLREQ is received, the SPC SHALL clear any and all outstanding PLRES it might have stored for delivery and only respond to the latest PLREQ. Actions on expiration The SLC sends a PEND message to the SPC including a Status Code. Periodic Trigger scenarios: the SLC ignores timer expiration N times consecutively (N configurable) and then sends PEND including Status Code to the SPC. Area Event Triggered scenarios: the SLC sends PEND including Status Code to the SPC.
Table 52: SLC Timer Values
Timer PT1
Default value For Network Initiated scenarios: For proxy mode nonroaming: PT1 = 11 sec + (optionally) response time in QoP. For proxy mode roaming with VSLP: PT1 = ST1 + 10 sec. For proxy mode roaming with HSLP: PT1 = ST2 + ST4 + 10 sec. For non-proxy mode: PT 1 = UT4 + 10 sec. For SET Initiated scenarios: For proxy mode: PT1 = ST1 + 10 sec. For non-proxy mode: PT1 = 11 sec + (optionally) response time in QoP.
Description This timer is only applicable to immediate scenarios. From sending of PRES to receipt of PINIT (proxy mode) or SUPL POS INIT (non proxy mode) for the successful case or receipt of PEND for the error case.
Actions on expiration The SPC sends a PEND message to the SLC including a Status Code.
OMA-TS-ILP-V2_0_1-20121205-A
Page 293 (295)
Timer
Default value
Description
Actions on expiration
PT2
5 sec.
From sending of PLREQ to receipt of PLRES (successful case) and PEND (error case). If PLRES is received after PT2 has expired (and no PEND was sent) and before a new PLREQ has been sent, the SPC SHALL ignore the PLRES. If a new PLREQ is received, the SLC SHALL clear any and all outstanding PLRES it might have stored for delivery and only respond to the latest PLREQ.
For immediate scenarios: the SPC MAY either continue or send a PEND message to the SLC. For triggered periodic scenarios: the SPC continues the flow N times consecutively (N configurable) and MAY then decide to either send PEND to the SLC or to continue the flow. For triggered area event scenarios: the SPC MAY continue the flow or send PEND to the SLC.
Table 53: SPC Timer Values
C.2
ULP Timers
This section lists all the timer values used by ULP [SUPL2 ULP TS].
Timer UT1
Default value (sec.) 11
Description For immediate applications, from sending of SUPL START to receipt of SUPL RESPONSE or SUPL END. In trigger positioning, from sending of SUPL TRIGGERED START to receipt of SUPL TRIGGERED RESPONSE or SUPL END.
Actions on expiration The SET sends SUPL END to the SLP. The SET clears all session resources at the SET.
UT2
11
From sending of SUPL POS INIT to receipt of first SUPL POS message or receipt of SUPL END message. UT2 is not needed if the SUPL POS INIT message contains the first SUPL POS element. For cell id based scenarios, the UT2 will be reset by the SUPL END message. The SUPL END message is sent from the SLP to the SET after the SET sent a SUPL POS INIT message containing the lid to the SLP.
For immediate applications the SET sends SUPL END to the SLP and clears all session resources. For triggered applications, the SET skips the SUPL POS session and continues the triggered session.
UT3
10
From sending of the last SUPL POS message to receipt of SUPL END, SUPL REPORT or SUPL NOTIFY. In cases where there is no SUPL POS message sent from SET, timer UT3 is not used.
For immediate applications, the SET sends SUPL END to the SLP and clears all session resources. For triggered applications, the SET continues the triggered session. The SET sends SUPL END to the SLP. The SET clears all session resources. The SET sends SUPL END to the SLP. The SET clears all session resources.
UT4
10
Only applicable to non-proxy mode. From sending of SUPL AUTH REQ to receipt of SUPL AUTH RESP message.
UT5
10
Only applicable to notification based on location scenarios. From sending of SUPL NOTIFY RESPONSE to receipt of SUPL END.
UT6
10
Only applicable to notification based on location in nonproxy mode scenarios. From sending of SUPL REPORT to receipt of SUPL NOTIFY or SUPL END.
The SET sends SUPL END to the SLP. The SET clears all session resources.
OMA-TS-ILP-V2_0_1-20121205-A
Page 294 (295)
Timer UT7
Default value (sec.) 10
Description Only applicable to triggered scenarios. From sending of SUPL TRIGGERED STOP to receipt of SUPL END.
Actions on expiration The SET sends SUPL END to the SLP. The SET clears all session resources.
Table 54: SET Timer Values
Timer ST1
Default value (sec.) Proxy: 10 Non-proxy: 50+ (optionally) response time in QoP
Description For proxy mode: from sending of SUPL RESPONSE to receipt of SUPL POS INIT. For non-proxy mode: from sending of SUPL RESPONSE to receipt of the notification (internal communication between SPC and SLC) that SUPL END has been sent to the SET.
Actions on expiration For proxy: Send SUPL END to SET Clear session resources at SLP For non-proxy: Internal communication is used to send SUPL END to SET Clear session resources at SLC/SLP
ST2
Proxy: 10 Non-proxy: 50+ (optionally) response time in QoP
For proxy mode: from sending of SUPL INIT to receipt of SUPL POS INIT. For non-proxy mode: from sending SUPL INIT to (a) receipt of notification (internal communication between SPC and SLC) that SUPL POS INIT has been received or (b) receipt of RLP-SSRP(SUPL END) from V-SLP.
For non-roaming scenario: Send MLP-SLIA to SUPL agent For roaming scenario: Send RLP-SRLIA to R-SLP For proxy: Clear session resources at SLP For non-proxy: Clear session resources at SLC
ST3
10
From sending of RLP-SSRLIR(SUPL START) to receipt of RLP-SSRLIA(SUPL RESPONSE)
For network initiated scenario: Send RLP-SRLIA to R-SLP Clear session resources at SLP For SET initiated scenario: Send SUPL END to SET Clear session resources at SLP
ST4
10
From sending of RLP-SSRLIR(msid, lid) to receipt of RLPSSRLIA(msid, posresult)
For network initiated scenario: Send SUPL END to SET Send RLP-SRLIA to R-SLP Clear session resources at SLP For SET initiated scenario: Send SUPL END to SET Clear session resources at SLP
ST5
10
Only applicable to notification based on location scenarios. From sending SUPL NOTIFY to receipt of SUPL NOTIFY RESPONSE.
Send SUPL END to SET. Clear session resources at SLP.
OMA-TS-ILP-V2_0_1-20121205-A
Page 295 (295)
Table 55: SLP Timer Values
Timer RT1
Default value (sec.) 21+ (optionally) response time in QoP
Description From sending of RLP SRLIR (msid, client-id, QoP) to receipt of RLP SSRLIA (posresult).
Actions on expiration Send MLP SLIA(posresult) to the SUPL Agent.
Table 56 RLP Timer Values

OMA InternetLocationProtocol

Uploaded by

Copyright:

Available Formats

OMA InternetLocationProtocol

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OMA InternetLocationProtocol

Uploaded by

Copyright:

Available Formats

Internal Location Protocol

Approved Version 2.0.1 5 Dec 2012

Open Mobile Alliance OMA-TS-ILP-V2_0_1-20121205-A

[3GPP RRC] [3GPP RRLP]

[RFC 2119] [RFC 3825]

[SUPLAD2] [SUPLRD2] [SUPL2 ULP TS] [TIA-553]

3. Terminology and Conventions

Location ID Major Version

Multiple Location IDs

Quality of Position Service Indicator SUPL Roaming

GLONASS GNSS GPS LAC Lid LTE MCC MNC

5. Detailed Flows Immediate Service

Network Initiated Proxy Mode

Non-Roaming Successful Case

MLP SLIR(ms-id, client-id, eqop)

PREQ(session-id2, QoP) PRES(session-id2) SUPL INIT(session-id, posmethod, SLP mode)

Data Connection Setup

SUPL POS(session-id, RRLP/RRC/TIA-801/LPP) PMESS(session-id2, RRLP/RRC/TIA-801)

PEND(session-id2, position) SUPL END(session-id)

Roaming with V-SLP Positioning Successful Case

SUPL Roaming where the V-SLP is involved in the positioning calculation.

MLP SLIR(ms-id, client-id, eqop)

RLP SRLIR(ms-id, client-id, eqop)

SET Lookup, Routing Info

SUPL INIT(session-id, posmethod, SLP mode)

Data Connection Setup

SUPL POS INIT(session-id, lid, SET capabilities, ver) UT2

RLP SSRP(SUPL POS) RLP SSRP(SUPL POS) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)

SUPL POS SUPL POS

Roaming with H-SLP Positioning Successful Case

SUPL Roaming where the H-SLP is involved in the positioning calculation.

MLP SLIR(ms-id, client-id, eqop)

RLP SRLIR(ms-id, client-id, eqop)

PREQ(session-id2, QoP) PRES(session-id2) SUPL INIT(session-id, posmethod, SLP mode)

Data Connection Setup

I J RT1 RLP SRLIR(msid, lid) ST4 K L RLP SRLIA(ms-id, posresult)

SUPL POS INIT(session-id, lid, SET capabilities, ver)

PINIT(session-id2, lid, SET capabilities) SUPL POS

SUPL POS(session-id, RRLP/RRC/TIA-801) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)

N O P Q MLP SLIA(posresult) RLP SRLIA(posresult)

PEND(session-id2, position) SUPL END(session-id)

Non-Roaming Successful Case, Notification/Verification based on current location

MLP SLIR(ms-id, client-id, eqop)

PREQ(session-id2, QoP) PRES(session-id2) SUPL INIT(session-id, posmethod, SLP mode, ...)

Data Connection Setup

SUPL POS(session-id, RRLP/RRC/TIA-801) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)

L M N O P MLP SLIA(posresult) ST5

SUPL Roaming where the V-SLP is involved in the positioning calculation.

MLP SLIR(ms-id, client-id, eqop)

RLP SRLIR(ms-id, client-id, eqop)

SET Lookup, Routing Info

SUPL INIT(session-id, posmethod, SLP mode, ...)

SUPL POS INIT(session-id, lid, SET capabilities, ver) UT2

RLP SSRP(SUPL POS) RLP SSRP(SUPL POS) PMESS(session-id2, RRLP/RRC/TIA-801/LPP)

SUPL POS SUPL POS

SUPL Roaming where the H-SLP is involved in the positioning calculation.

MLP SLIR(ms-id, client-id, eqop)

RLP SRLIR(ms-id, client-id, eqop)

PREQ(session-id2, QoP) PRES(session-id2) SUPL INIT(session-id, posmethod, SLP mode, ...)

Data Connection Setup