Jump to content, skipping navigation

Secure User Plane Location 2.0 Reference Guide

Secure User Plane Location (SUPL) 2.0 Reference Guide

SUPL 1.0 has proved to be the favorite method for deploying LBS, but the availability of OMA SUPL 2.0 and its numerous key capabilities makes it more ideal for the next generation of location-enabled services.

This document introduces the new features of SUPL 2.0 that will change the LBS market and how smartphones will be used in the future. The outline also includes:

  • SUPL 2.0 Feature Summary
  • SUPL 1.0 vs. SUPL 2.0
  • SUPL 2.0 Test Validation
  • Spirent Test Coverage

    * Required Field

    Cancel

    Secure User Plane Location (SUPL) 2.0 Reference Guide April 2011 SPIRENT 541 Industrial Way West Eatontown, NJ 07724 USA Email: sales@spirent.com Web: http://www.spirent.com Page Part Number: 71-006460, Version A1 AMERICAS 1-800-SPIRENT • +1-818-676-2683 • sales@spirent.com EUROPE AND THE MIDDLE EAST +44 (0) 1293 767979 • emeainfo@spirent.com ASIA AND THE PACIFIC +86-10-8518-2539 • salesasia@spirent.com © 2011 Spirent. All Rights Reserved. All of the company names and/or brand names and/or product names referred to in this document, in particular, the name “Spirent” and its logo device, are either registered trademarks or trademarks of Spirent plc and its subsidiaries, pending registration in accordance with relevant national laws. All other registered trademarks or trademarks are the property of their respective owners. The information contained in this document is subject to change without notice and does not represent a commitment on the part of Spirent. The information in this document is believed to be accurate and reliable; however, Spirent assumes no responsibility or liability for any errors or inaccuracies that may appear in the document. Table of Contents Introduction ............................................................................................... 1 Feature Summary ....................................................................................... 2 LTE A-GNSS ................................................................................................. 2 Emergency Services ..................................................................................... 3 Triggered Services ....................................................................................... 3 Third Party Positioning ................................................................................. 4 Notification and Verification ......................................................................... 5 Reporting .................................................................................................... 5 SUPL 1.0 vs. 2.0 ......................................................................................... 6 Spirent Test Systems ................................................................................. 7 Validated Test Systems ................................................................................ 7 Performance Test Systems ........................................................................... 9 Spirent System Requirements.................................................................. 10 Supported Air Interfaces ............................................................................ 10 Supported Payload Protocols ..................................................................... 10 Protocol Conformance TTCN Test Environment ............................................ 11 Spirent Test Coverage .............................................................................. 12 SUPL 2.0 ETS Protocol Conformance ........................................................... 12 SUPL 2.0 Minimum Performance ................................................................ 12 SUPL 2.0 ETS Protocol Conformance – Detailed Coverage Grid ..................... 14 Summary of PTCRB and GCF Validation ....................................................... 21 References ............................................................................................... 22 Secure User Plane Location (SUPL) 2.0 Reference Guide 1 INTRODUCTION Assisted GPS (A-GPS) is no longer a high-end “nice to have” feature for today’s mobile devices. The growing demand for mobile Location Based Services (LBS) has pushed A- GPS into most devices in developed markets. Many of the supporting wireless networks have deployed LBS based on A-GPS using the Secure User Plane Location (SUPL) protocol. So far, SUPL 1.0 has proved to be the favorite method for deploying LBS, but despite having the needed features to support A-GPS positioning, SUPL 1.0 lacks many key capabilities that are needed to support next-generation wireless networks, hybrid positioning technologies, and revenue-generating location services. To meet these needs, SUPL 2.0 is emerging as the protocol most likely to power next-generation location services on wireless networks. Like its predecessor, SUPL 2.0 is a user plane protocol used for exchanging location information between mobile devices and network positioning servers. However, SUPL 2.0 offers a range of additional features that will enable operators to provide location services on LTE networks. In addition, operators can use SUPL 2.0 to expand the ability of their services to support multiple types of positioning technologies and create new revenue-generating services and applications such as geo-fencing and triggered services. Mobile device manufacturers, and the technologies that enable LBS, have to support the massive need for “everywhere, anytime, and accurate location.” Fortunately, we now have a vastly-improved SUPL protocol to help the successful deployment of next- generation LBS. This document outlines the new features of SUPL 2.0 that will change the LBS market and how smartphones will be used in future. There are three key reasons why SUPL 2.0 is quickly becoming a dominant protocol for enabling location services on mobile devices: • LTE: SUPL 2.0 is a critical enabler for offering LBS (and in some cases Emergency Services) over LTE. As a result, it will replace existing user plane protocols for legacy technologies such as WCDMA and CDMA. • Hybrid Positioning: SUPL 2.0 will make LBS applications faster, more accurate, and available in more places through its support for hybrid positioning—most likely a combination of A-GLONASS, A-GPS, WiFi, and Cellular positioning technology • Commercial Services: SUPL 2.0 will drive more revenue opportunities with advanced features, including:  Triggered Services  Third Party Positioning  Improved Notification & Verification  Reporting (Batch, Quasi Real-Time, and Intermediate) Secure User Plane Location (SUPL) 2.0 Reference Guide 2 FEATURE SUMMARY The sections below provide detailed descriptions of the new features included in SUPL 2.0. These include: • LTE A-GNSS • Emergency Services • Triggered Services • Third Party Positioning • Notification and Verification • Reporting LTE A-GNSS SUPL 2.0 enables positioning over many new wireless data bearers such as LTE, WiMAX , I-WLAN and eHRPD, allowing it to work on just about all IP-capable networks. This is important because it allows for a single location protocol to be used across all air interface technologies, and this fact is driving the adoption of SUPL 2.0 by wireless carriers all over the world. SUPL 2.0 also supports several new GNSS positioning technologies, including GLONASS, Galileo, Modernized GPS, QZSS, and SBAS. These can be used by themselves or combined, making position fixes faster and more accurate. Support for several new bearers, not supported in the previous version, has been added to SUPL 2.0: • LTE • WiMAX • I-WLAN • eHRPD SUPL 2.0 also adds support for several new positioning technologies that are not covered by SUPL 1.0: • GLONASS • Galileo • Modernized GPS • QZSS • SBAS Secure User Plane Location (SUPL) 2.0 Reference Guide 3 EMERGENCY SERVICES SUPL 2.0 adds support for enhanced emergency services (e.g. E911 in the US) by introducing the concept of an Emergency SUPL Location Platform (E-SLP) in addition to the Home SUPL Location Platform (H-SLP) which has been traditionally supported. In order to improve reliability, SUPL-enabled terminals (SETs) are required to accept emergency SUPL initiation messages (SUPL INITs) from any E-SLP, and all non-emergency SUPL INITs must be ignored when in emergency mode. In addition, security requirements for emergency requests are relaxed in order to make the sessions faster and more likely to succeed. The call flow is compatible with 3GPP TS 23.167 (IMS Emergency Sessions). Emergency Services Features: • Any H-SLP can act as a E-SLP • The addition of SIP Push and UDP/IP Push in SUPL 2.0 enables establishment of an E911 call over IMS Network • Emergency sessions are given priority, and non-emergency sessions are ignored, to ensure speed and reliability TRIGGERED SERVICES SUPL 2.0 also includes provisions for periodic triggering and area event triggering. This means that location measurements can be triggered by the network or the SET, based on user’s location. A geographic region can be divided into small parts and each of these regions, or a group of them, can be assigned specific Area IDs. As soon as a user enters or leaves the target area, a position event can be triggered and can continue to be triggered at periodic intervals (if required) as long as user is in the area. This is expected to be a very useful feature for enabling new revenue-generating location service applications. There are four types of triggers: • Entering • Within • Leaving • Outside Secure User Plane Location (SUPL) 2.0 Reference Guide 4 Figure 1: i Geographic Target Area iiiii Figure 2: ivv Area Event Triggers vivii THIRD PARTY POSITIONING SUPL 2.0 allows the SET to securely deliver its position to third parties. In comparison with SUPL 1.0, more control of privacy is provided, enabling more finely-tuned management of security settings. An example of this is defining a group of family members who can see your location everywhere, while another group of friends can only see your location at specified times. This is a commercially-attractive option that could enhance existing LBS applications such as friend finder and tracking services. Secure User Plane Location (SUPL) 2.0 Reference Guide 5 NOTIFICATION AND VERIFICATION SUPL 2.0 ensures the privacy of the SET user is honored by forcing it to adhere to the notification and verification settings of the target SET user, regardless of SUPL network- initiated services or SET-initiated services. Notification is also enhanced by supporting two new SUPL INIT delivery mechanisms, in addition to OMA Push and SMS which are already supported by SUPL 1.0. New SUPL INIT Delivery Mechanisms: • SIP Push: Uses existing secure connection to the SET and makes SUPL 2.0 more easily integrated with IMS networks. • UDP/IP Push: UDP datagram sent to the SET’s IP address (requires IP address of SET to be known); can also be used for group notification. REPORTING SUPL 2.0 provides various options for reporting including batch, quasi-real-time, and intermediate (see below). This feature allows positions to be stored locally on a device and then reported back to the network at a later time, reducing signaling overhead and battery consumption for applications that repeatedly track the location of a device over time (such as fleet management applications). • Batch Reporting: Stored positions are reported to the network in a group after a fixed interval of time. • Quasi Real-Time Reporting: Positions can be stored and sent later in case it is not possible at desired time. • Intermediate Reporting: Intermediate reports are sent in case the SET runs out of available memory. Secure User Plane Location (SUPL) 2.0 Reference Guide 6 SUPL 1.0 VS. 2.0 SUPL 2.0 introduces many new features that make location services possible on LTE networks. It also opens up opportunities for higher-quality location services and more reliable emergency services. These enhanced features come at the price of complexity. The SUPL 1.0 standard weighs in at around 200 pages, whereas the SUPL 2.0 standard is closer to 800 pages. While no device will support every feature any time soon, there is no doubt that device complexity will increase as a result of this increased feature set. Secure User Plane Location (SUPL) 2.0 Reference Guide 7 SPIRENT TEST SYSTEMS No matter which Spirent Location Test System you are starting from, there is an upgrade path to SUPL 2.0 support. The Spirent PLTS can be upgraded to support SUPL 2.0 over CDMA (1x, EV-DO, and eHRPD) and LTE. Spirent’s ULTS can be upgraded to support SUPL 2.0 over GPRS, WCDMA/HSPA and LTE. The following systems represent Spirent’s portfolio of validated and performance test systems supporting SUPL 2.0. VALIDATED TEST SYSTEMS viii 8100-A500: Validated for SUPL 2.0 with GPRS and WCDMA Air Interfaces. Secure User Plane Location (SUPL) 2.0 Reference Guide 8 8100-B500: Validated for SUPL 2.0 with LTE, GPRS, WCDMA, and CDMA Air Interfaces. Secure User Plane Location (SUPL) 2.0 Reference Guide 9 PERFORMANCE TEST SYSTEMS ix 8100-A750: Performance testing for SUPL 2.0 with GPRS & WCDMA Air Interfaces. 8100-B750: Performance testing for SUPL 2.0 with LTE Air Interface. Secure User Plane Location (SUPL) 2.0 Reference Guide 10 SPIRENT SYSTEM REQUIREMENTS SUPPORTED AIR INTERFACES Spirent SUPL 2.0 test solutions support the following air interfaces: • LTE: Requires E2010S LTE Network Emulator *NOTE: Some Area Event Triggering tests require 2 nd LTE cell • WCDMA/HSPA and GSM/GPRS: Requires SR3420 Network Emulator *NOTE: Some Area Event Triggering tests require 2 nd WCDMA cell (enabled by Multi- cell Software Option) • CDMA: Requires SR3562/SR3452 CDMA Network Emulators  CDMA 1x  EVDO  eHRPD SUPPORTED PAYLOAD PROTOCOLS The following Control Plane payloads are supported in SUPL 2.0 test cases: • RRLP v5 & v8: Supported on GPRS, WCDMA/HSPA, and LTE Air Interfaces • IS-801-1: Supported on CDMA 1x, EVDO, and eHRPD Air Interfaces • LTE Positioning Protocol (LPP): Will be supported in 2H2011 on LTE Air Interface Secure User Plane Location (SUPL) 2.0 Reference Guide 11 PROTOCOL CONFORMANCE TTCN TEST ENVIRONMENT Spirent uses a best-in-class TTCN-3 test environment for executing SUPL 2.0 protocol conformance test scripts. This tool is offered in two versions: • TTworkbench Express: Automates execution of standard OMA TTCN-3 test scripts for SUPL 2.0. • TTworkbench Pro: In addition to executing standard scripts, test scripts can be customized to meet specific user needs. Figure 3: Test Results and Debugging Information Secure User Plane Location (SUPL) 2.0 Reference Guide 12 SPIRENT TEST COVERAGE SUPL 2.0 ETS PROTOCOL CONFORMANCE Available in the bearer/payload configurations as shown in the table below. • “Bearer” refers to the Air Interface used for signaling. • “SUPL Payload” refers to the control plane protocol used for the positioning session. Bearer SUPL Payload # Test Cases Supported by Spirent x LTE RRLP 102 WCDMA RRLP 118 GSM RRLP 102 CDMA 1x, HRPD, eHRPD IS-801-1 86 SUPL 2.0 test packs are divided into three test packages: Test Pack #1 (TP1), Test Pack #2 (TP2), and Test Pack #3 (TP3) xi . Test Type TP1 TP2 TP3 Network Initiated: Common Part 6 14 7 Network Initiated: Notification and Verification 0 13 2 Network Initiated: Single Sessions 5 8 11 Network Initiated: Triggered Services (all) 11 8 11 Network Initiated: Timer Expiration 5 3 1 SET Initiated: Common Part 2 7 0 SET Initiated: Single Sessions 4 5 6 SET Initiated: Triggered Services (all) 14 8 3 SET Initiated: Timer Expiration 0 3 1 Common: Basic Functionality 0 4 3 Total 47 73 45 Refer to the detailed coverage grid at the end of this document for more information. SUPL 2.0 MINIMUM PERFORMANCE Most devices in the market use the SUPL 1.0 protocol for enabling location services, yet minimum performance testing of devices in 3GPP standards is only mandated using control plane. Testing the devices using scenarios that are closer to real-world would help to shorten product development cycles, so Spirent is providing a new option for LTE devices: A-GPS minimum performance testing with SUPL 2.0 RRLP payload over LTE bearer. Back-to-back SUPL 2.0 sessions with challenging GPS scenarios using IMS and RRLP payload mimic real-world LTE LBS sessions and help identify potential issues in device performance. Spirent offers flexible and configurable SUPL 2.0 Minimum Performance test cases xii . Device response time, accuracy, and positioning yield can be tested under a variety of GNSS conditions and SUPL 2.0 configurations. Secure User Plane Location (SUPL) 2.0 Reference Guide 13 The following are some of the SUPL 2.0 Minimum Performance tests that can be performed: • A-GPS Nominal Accuracy • A-GPS Multi-path • A-GPS Dynamic Range • A-GPS Sensitivity • A-GPS Moving Scenario For more information on Spirent’s Performance test capabilities, refer to the Spirent Application Note 121: Testing Real-World A-GNSS Performance in the Lab using ULTS. Secure User Plane Location (SUPL) 2.0 Reference Guide 14 SUPL 2.0 ETS PROTOCOL CONFORMANCE – DETAILED COVERAGE GRID Reference: “Enabler Test Specification for SUPL V2.0” Candidate Version 2.0 – 14 Sep 2010 Legend: Some of the test cases might be available only in UMTS mode in 5.11, refer to the legend notes below for availability in other Air Interface Technologies "1": Test case to be delivered by ULTS 6.0 "2": GLONASS assistance data not yet available. "3". Support for these test cases may be considered for future release Test Case ID Test Case Name Sub-test Description TP# LTS Release Available WCDMA GSM CDMA LTE Network Initiated Common Part of ULP Message, Basic Functionality, and Cross Version Compatibility CON-000 - 1 SUPL INIT Delivery OMA Push TP2 6.00     CON-000 - 2 SUPL INIT Delivery MT SMS TP2 6.00     CON-000 - 3 SUPL INIT Delivery SIP Push TP3 Future CON-000 - 4 SUPL INIT Delivery UDP Push TP2 6.00 n/a n/a n/a  CON-001 Incorrect OMA Push Message Content Incorrect OMA Push TP2 6.00     CON-002 Incorrect MT SMS Message Content Incorrect MT SMS TP2 6.00     CON-003 Incorrect SIP Push Message Content Incorrect SIP Push TP3 Future CON-004 - 1 Correct Session ID IPAddress, IPv4 TP2 6.00     CON-004 - 2 Correct Session ID IPAddress, IPv6 TP2 6.00     CON-004 - 3 Correct Session ID FQDN TP2 6.00     CON-005 - 1 Invalid SET Session ID SUPL INIT TP2 6.00     CON-005 - 2 Invalid SET Session ID SUPL POS (Session ID) TP2 6.00     CON-005 - 3 Invalid SET Session ID SUPL POS (SET ID) TP2 6.00     CON-006 - 1 Missing or Invalid SLP Session ID SUPL INIT TP2 6.00     CON-006 - 2 Missing or Invalid SLP Session ID SUPL POS (Session ID) TP2 6.00     CON-006 - 3 Missing or Invalid SLP Session ID SUPL POS (SLP ID) TP2 6.00     CON-009 - 1 Basic SUPL INIT Protection Correct support TP3 Future CON-009 - 2 Basic SUPL INIT protection Correct discard procedure – Incorrect Protection Level TP3 Future CON-009 - 3 Basic SUPL INIT Protection Correct discard procedure – Incorrect Key Identity TP3 Future CON-009 - 4 Basic SUPL INIT Protection Correct discard procedure – Incorrect Basic Replay Counter TP3 Future Secure User Plane Location (SUPL) 2.0 Reference Guide 15 Test Case ID Test Case Name Sub-test Description TP# LTS Release Available WCDMA GSM CDMA LTE CON-010 - 1 Compatible Versions Higher versions TP1 5.11     CON-010 - 2 Compatible Versions Lower versions TP1 5.11     CON-010 - 3 Compatible Versions SLP supports 2.0 and 3.0 TP1 5.11     CON-010 - 4 Compatible Versions SLP supports 1.0 only TP1 5.11     CON-011 - 1 Unsupported Versions Higher version not supported TP1 5.11     CON-011 - 2 Unsupported Versions Lower version not supported TP1 5.11     CON-012 Incorrect UDP TP3 Future Notification and Verification CON-020 - 1 No Notification and No Verification Notification not set TP2 6.00     CON-020 - 2 No Notification and No Verification Notification set to No notification & no verification TP2 6.00     CON-021 Notification-only Notification Only TP2 6.00     CON-022 - 1 Notification and Verification Allowed on no answer. User accepts. TP2 6.00     CON-022 - 2 Notification and Verification Allowed on no answer. User denies. TP2 6.00     CON-022 - 3 Notification and Verification Allowed on no answer. No response. TP2 6.00     CON-022 - 4 Notification and Verification Denied on no answer. User accepts. TP2 6.00     CON-022 - 5 Notification and Verification Denied on no answer. User denies. TP2 6.00     CON-022 - 6 Notification and Verification Denied on no answer. No response. TP2 6.00     CON-023 Privacy Override Privacy Override TP2 6.00     CON-024 - 1 Requestor ID and Client Name Encoding type UCS2 TP2 6.00     CON-024 - 2 Requestor ID and Client Name Encoding type GSM-default TP2 6.00     CON-024 - 3 Requestor ID and Client Name Encoding type UTF-8 TP2 6.00     CON-025 - 1 Notification and Verification: Based on current location User accepts the verification TP3 Future CON-025 - 2 Notification and Verification: Based on current location User denies the verification TP3 Future Single Sessions CON-030 - 1 Positioning Method A-GPS SET assisted TP2 6.00     Secure User Plane Location (SUPL) 2.0 Reference Guide 16 Test Case ID Test Case Name Sub-test Description TP# LTS Release Available WCDMA GSM CDMA LTE CON-030 - 2 Positioning Method A-GPS SET based TP2 6.00     CON-030 - 3 Positioning Method Autonomous GPS TP2 6.00     CON-030 - 4 Positioning Method Enhanced Cell ID TP2 6.00     CON-030 - 5 Positioning Method Cell ID TP2 6.00     CON-030 - 6 Positioning Method A-GANSS SET assisted –Galileo TP3 Future CON-030 - 7 Positioning Method A-GANSS SET assisted –GLONASS TP1 5.11  2  2  2  2 CON-030 - 8 Positioning Method A-GANSS SET based –Galileo TP3 Future CON-030 - 9 Positioning Method A-GANSS SET based –GLONASS TP1 5.11  2  2  2  2 CON-030 - 10 Positioning Method Autonomous GANSS TP1 5.11  2  2  2  2 CON-030 - 11.1 Positioning Method A-GPS Preferred methods - A-GPS SET assisted TP2 6.00     CON-030 - 11.2 Positioning Method A-GPS Preferred methods - A-GPS SET based TP2 6.00     CON-030 - 12.1 Positioning Method A-GANSS Preferred methods - A- GANSS SET assisted TP1 5.11  2  2  2  2 CON-030 - 12.2 Positioning Method A-GANSS Preferred methods - A- GANSS SET based TP1 5.11  2  2  2  2 CON-030 - 13 Positioning Method OTDOA TP3 Future CON-031 No Position TP2 6.00     CON-033 - 1 Emergency Services Location Requests E-SLP address sent in SUPL INIT TP3 Future CON-033 - 2 Emergency Services Location Requests Use of provisioned H-SLP address TP3 Future CON-033 - 3 Emergency Services Location Requests Use of default E-SLP address TP3 Future CON-034 - 1 Emergency Services Location Request – Interaction with Normal SUPL Session Normal SUPL session already in progress before Emergency SUPL session TP3 Future CON-034 - 2 Emergency Services Location Request – Interaction with Normal SUPL Session Normal SUPL session attempted during Emergency SUPL session TP3 Future CON-035 - 1 Retrieval of Historical Positions Position estimates only TP3 Future CON-035 - 2 Retrieval of Historical Positions Enhanced cell/sector measurements only TP3 Future CON-035 - 3 Retrieval of Historical Positions Both position estimates and enhanced cell/sector measurements TP3 Future Triggered Services: Periodic Triggers CON-040 - 1 Real-time Reporting A-GPS SET assisted TP1 5.11     Secure User Plane Location (SUPL) 2.0 Reference Guide 17 Test Case ID Test Case Name Sub-test Description TP# LTS Release Available WCDMA GSM CDMA LTE CON-040 - 2 Real-time Reporting A-GPS SET based TP1 5.11     CON-041 - 1 Basic Quasi Real- time Reporting A-GPS SET assisted TP3 Future CON-041 - 2 Basic Quasi Real- time Reporting A-GPS SET based TP3 Future CON-042 - 1.1 Basic Batch Reporting A-GPS SET assisted - every 8fixes/measurements TP3 Future CON-042 - 1.2 Basic Batch Reporting A-GPS SET assisted - every 5 minutes TP3 Future CON-042 - 1.3 Basic Batch Reporting A-GPS SET assisted - at the end of the session TP3 Future CON-042 - 2.1 Basic Batch Reporting A-GPS SET based - every 8 fixes/measurements TP3 Future CON-042 - 2.2 Basic Batch Reporting A-GPS SET based - every 5 minutes TP3 Future CON-042 - 2.3 Basic Batch Reporting A-GPS SET based - at the end of the session TP3 Future Triggered Services: Area Event Triggers CON-050 - 1.1 Geographic Target Area A-GPS SET assisted - entering event TP1 5.11   3  1 CON-050 - 1.2 Geographic Target Area A-GPS SET assisted - inside event TP1 5.11   3  1 CON-050 - 1.3 Geographic Target Area A-GPS SET assisted - outside event TP1 5.11   3  1 CON-050 - 1.4 Geographic Target Area A-GPS SET assisted - leaving event TP1 5.11   3  1 CON-050 - 2.1 Geographic Target Area A-GPS SET based - entering event TP1 5.11   3  1 CON-050 - 2.2 Geographic Target Area A-GPS SET based - inside event TP1 5.11   3  1 CON-050 - 2.3 Geographic Target Area A-GPS SET based - outside event TP1 5.11   3  1 CON-050 - 2.4 Geographic Target Area A-GPS SET based - leaving event TP1 5.11   3  1 CON-051 - 1.1 Area ID A-GPS SET assisted - entering event TP2 6.00  3 3 3 CON-051 - 1.2 Area ID A-GPS SET assisted - inside event TP2 6.00  3 3 3 CON-051 - 1.3 Area ID A-GPS SET assisted - outside event TP2 6.00  3 3 3 CON-051 - 1.4 Area ID A-GPS SET assisted - leaving event TP2 6.00  3 3 3 CON-051 - 2.1 Area ID A-GPS SET based - entering event TP2 6.00  3 3 3 CON-051 - 2.2 Area ID A-GPS SET based - inside event TP2 6.00  3 3 3 CON-051 - 2.3 Area ID A-GPS SET based - outside event TP2 6.00  3 3 3 CON-051 - 2.4 Area ID A-GPS SET based - leaving event TP2 6.00  3 3 3 Secure User Plane Location (SUPL) 2.0 Reference Guide 18 Test Case ID Test Case Name Sub-test Description TP# LTS Release Available WCDMA GSM CDMA LTE Triggered Services: Other Scenarios CON-060 Network Capabilities Change TP3 Future CON-061 - 1 Network cancels Triggered Location Request The secure IP connection is not released TP1 5.11     CON-061 - 2 Network cancels Triggered Location Request The secure IP connection is released TP3 Future CON-062 V-SLP to V-SLP Handover TP3 Future Timer Expiration CON-070 - 1 Timeout UT2 SUPL POS session (Immediate session) TP2 6.00     CON-070 - 2 Timeout UT2 SUPL POS session (Triggered session) TP1 5.11     CON-070 - 3 Timeout UT2 No SUPL POS session (Immediate session) TP2 6.00     CON-070 - 4 Timeout UT2 No SUPL POS session (Triggered session) TP1 5.11     CON-071 - 1 Timeout UT3 Immediate session TP2 6.00     CON-071 - 2 Timeout UT3 Triggered session TP1 5.11     CON-072 Timeout UT5 TP3 Future CON-073 Timeout UT7 . TP1 5.11     CON-074 Timeout UT8 TP1 5.11     SET Initiated Common Part of ULP Message, Basic Functionality, and Cross Version Compatibility CON-100 - 1 Correct Session ID IPAddress, IPv4 TP2 6.00     CON-100 - 2 Correct Session ID IPAddress, IPv6 TP2 6.00     CON-100 - 3 Correct Session ID FQDN TP2 6.00     CON-101 - 1 Invalid SET Session ID Session ID TP2 6.00     CON-101 - 2 Invalid SET Session ID SET ID TP2 6.00     CON-102 - 1 Invalid SLP Session ID Session ID TP2 6.00     CON-102 - 2 Invalid SLP Session ID SLP ID TP2 6.00     CON-103 - 1 Compatible Versions Higher versions TP1 5.11     CON-103 - 2 Compatible Versions Lower versions TP1 5.11     Single Sessions CON-110 - 1 Positioning Method A-GPS SET assisted TP2 6.00     Secure User Plane Location (SUPL) 2.0 Reference Guide 19 Test Case ID Test Case Name Sub-test Description TP# LTS Release Available WCDMA GSM CDMA LTE CON-110 - 2 Positioning Method A-GPS SET based TP2 6.00     CON-110 - 3 Positioning Method Autonomous GPS TP2 6.00     CON-110 - 4 Positioning Method Enhanced Cell ID TP2 6.00     CON-110 - 5 Positioning Method Cell ID TP2 6.00     CON-110 - 6 Positioning Method A-GANSS SET assisted –Galileo TP3 Future CON-110 - 7 Positioning Method A-GANSS SET assisted –GLONASS TP1 5.11  2  2  2  2 CON-110 - 8 Positioning Method A-GANSS SET based –Galileo TP3 Future CON-110 - 9 Positioning Method A-GANSS SET based –GLONASS TP1 5.11  2  2  2  2 CON-110 - 10 Positioning Method Autonomous GANSS TP1 5.11  2  2  2  2 CON-110 - 11 Positioning Method A-GNSS Set Assisted Preferred method TP3 Future CON-110 - 12 Positioning Method A-GANSS Preferred methods - A-GPS SET based TP1 5.11  2  2  2  2 CON-110 - 13 Positioning Method OTDOA TP3 Future CON-111 SET Initiated Location Request of another SET TP3 Future CON-113 Transfer Location to Third Party TP3 Future Triggered Services: Periodic Triggers CON-120 - 1 Periodic Reporting A-GPS SET assisted TP3 Future CON-120 - 2 Periodic Reporting A-GPS SET based TP3 Future Triggered Services: Area Event Triggers CON-130 - 1.1 Geographic Target Area A-GPS SET assisted - entering event TP1 5.11   3  1 CON-130 - 1.2 Geographic Target Area A-GPS SET assisted - inside event TP1 5.11   3  1 CON-130 - 1.3 Geographic Target Area A-GPS SET assisted - outside event TP1 5.11   3  1 CON-130 - 1.4 Geographic Target Area A-GPS SET assisted - leaving event TP1 5.11   3  1 CON-130 - 2.1 Geographic Target Area A-GPS SET based - entering event TP1 5.11   3  1 CON-130 - 2.2 Geographic Target Area A-GPS SET based - inside event TP1 5.11   3  1 CON-130 - 2.3 Geographic Target Area A-GPS SET based - outside event TP1 5.11   3  1 CON-130 - 2.4 Geographic Target Area A-GPS SET based - leaving event TP1 5.11   3  1 CON-131 - 1.1 Area ID A-GPS SET assisted - entering event TP2 6.00  3 3 3 CON-131 - 1.2 Area ID A-GPS SET assisted - inside event TP2 6.00  3 3 3 Secure User Plane Location (SUPL) 2.0 Reference Guide 20 Test Case ID Test Case Name Sub-test Description TP# LTS Release Available WCDMA GSM CDMA LTE CON-131 - 1.3 Area ID A-GPS SET assisted - outside event TP2 6.00  3 3 3 CON-131 - 1.4 Area ID A-GPS SET assisted - leaving event TP2 6.00  3 3 3 CON-131 - 2.1 Area ID A-GPS SET based - entering event TP2 6.00  3 3 3 CON-131 - 2.2 Area ID A-GPS SET based - inside event TP2 6.00  3 3 3 CON-131 - 2.3 Area ID A-GPS SET based - outside event TP2 6.00  3 3 3 CON-131 - 2.4 Area ID A-GPS SET based - leaving event TP2 6.00  3 3 3 Triggered Services: Other Scenarios CON-135 Network Cancels Triggered Location Request TP3 Future Timer Expiration CON-140 - 1 Timeout UT1 Immediate session TP2 6.00     CON-140 - 2 Timeout UT1 Triggered session TP1 5.11     CON-141 - 1 Timeout UT2 SUPL POS session (Immediate session) TP2 6.00     CON-141 - 2 Timeout UT2 SUPL POS session (Triggered session) TP1 5.11     CON-141 - 3 Timeout UT2 No SUPL POS session (Immediate session) TP1 5.11     CON-141 - 4 Timeout UT2 No SUPL POS session (Triggered session) TP1 5.11     CON-142 - 1 Timeout UT3 Immediate session TP2 6.00     CON-142 - 2 Timeout UT3 Triggered session TP1 5.11     CON-143 Timeout UT7 TP1 5.11     CON-144 Timeout UT9 TP3 Future Common Basic Functionality CON-007 - 1 Alternative H-SLP Addresses H-SLP address stored on UICC TP2 6.00     CON-007 - 2 Alternative H-SLP Addresses H-SLP address stored on SET TP3 Future CON-007 - 3 Alternative H-SLP Addresses Auto configuration of H-SLP address TP2 6.00     CON-007 - 4 Alternative H-SLP Addresses Auto configuration of H-SLP address following authentication failure TP2 6.00     CON-007 - 5 Alternative H-SLP Addresses Clearing of old H-SLP address following change of IMSI TP2 6.00     CON-008 - 1 Optional Ciphering Suites TLS_RSA_WITH_3DES_EDE_CBC_SHA TP3 Future CON-008 - 2 Optional Ciphering Suites TLS_PSK_WITH_3DES_EDE_CBC_SHA TP3 Future Secure User Plane Location (SUPL) 2.0 Reference Guide 21 SUMMARY OF PTCRB AND GCF VALIDATION PTCRB RFT 89: • 108 SUPL 2.0 ETS Test Cases • 1 test validated on Spirent Platform with more coming soon GCF WI (provisional): • 110 SUPL 2.0 ETS Test Cases part of provisional WI • Validations expected to begin in August Secure User Plane Location (SUPL) 2.0 Reference Guide 22 REFERENCES i “Secure User Plane Location Architecture” Candidate Version 2.0 – 21 March 2011 ii “Secure User Plane Location Architecture” Candidate Version 2.0 – 21 March 2011 iv “Secure User Plane Location Architecture Candidate” Version 2.0 – 21 March 2011 v “Secure User Plane Location Architecture Candidate” Version 2.0 – 21 March 2011 vi “Secure User Plane Location Architecture Candidate” Version 2.0 – 21 March 2011 vii “Secure User Plane Location Architecture Candidate” Version 2.0 – 21 March 2011 viii Validation has currently been completed for one test case on 8100-A500, but all test cases will eventually be validated on 8100-A500 (no LTE or CDMA) and 8100-B500. ix Performance test systems support all the same features as validated test systems, but they are not validated to be used for official device certification. x As of March 2011 xi Test Pack #3 is not yet commercially released xii SUPL 2.0 Minimum Performance for GPRS and WCDMA is commercially available. LTE will be commercially supported in 2Q 2011.