<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
<!-- This component and the accompanying materials are made available under the terms of the License 
"Eclipse Public License v1.0" which accompanies this distribution, 
and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
<!-- Initial Contributors:
    Nokia Corporation - initial contribution.
Contributors: 
-->
<!DOCTYPE concept
  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept xml:lang="en" id="GUID-2E565B8E-D262-5769-96E6-A532154D57E6"><title>Privacy Requests Overview</title><shortdesc>This document provides background information on privacy requests which are sent to LBS to obtain permission to send the device location to another party. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody><section><title>Purpose</title> <p id="GUID-47C88C54-6BDC-5777-A661-A3EB7162A89E">  A privacy request is a request for permission to obtain the mobile device's location. A request is sent from an agent known as the requester. A request that requires a response is called a privacy verification request. A request that does not require a response is called a privacy notification request. </p> <p>A location request follows a privacy request. In the case where a privacy verification request was sent, a location request follows only if the privacy request was accepted. The location request causes the LBS subsystem to calculate a position and send it to the requester. </p> <p>Note that privacy requests from local applications are supported in the <xref href="GUID-D18B4715-3942-52EA-9D2F-E145037FA47A.dita">Standalone Privacy Mode configuration</xref> only. </p> <p>This document explains the concepts of LBS privacy requests and the methods that the LBS subsystem can use to handle and process the requests. </p> </section> <section><title>Contents</title> <ul><li id="GUID-42895EA1-153D-59E9-B73C-A57B6A1C3EC9"><p><xref href="GUID-2E565B8E-D262-5769-96E6-A532154D57E6.dita#GUID-2E565B8E-D262-5769-96E6-A532154D57E6/GUID-64BFDD62-7E1C-5F04-A2F7-426F40BFADA7">Introduction</xref>  </p> </li> <li id="GUID-C3E4FA4E-0602-592B-B529-E8BBFB98E5D2"><p><xref href="GUID-2E565B8E-D262-5769-96E6-A532154D57E6.dita#GUID-2E565B8E-D262-5769-96E6-A532154D57E6/GUID-47F9AED8-53D5-5C52-854D-A455770E8D1C">Key concepts</xref>  </p> </li> <li id="GUID-B147E355-13B1-59B7-B0A4-6D40F74411EC"><p><xref href="GUID-2E565B8E-D262-5769-96E6-A532154D57E6.dita#GUID-2E565B8E-D262-5769-96E6-A532154D57E6/GUID-5D079E0C-A64E-51A1-8794-009A199CE65F">Privacy request verification and notification</xref>  </p> <ul><li id="GUID-DEDC7C94-23E2-5628-BE88-9C068531E6AD"><p><xref href="GUID-2E565B8E-D262-5769-96E6-A532154D57E6.dita#GUID-2E565B8E-D262-5769-96E6-A532154D57E6/GUID-5939104B-84F3-53B5-AE32-816015E4640D">Privacy verification request</xref>  </p> </li> <li id="GUID-FF8EECDF-48B7-56C1-B601-03508771B153"><p><xref href="GUID-2E565B8E-D262-5769-96E6-A532154D57E6.dita#GUID-2E565B8E-D262-5769-96E6-A532154D57E6/GUID-97F3AE63-D529-54DC-9C77-8B0AE1DA150A">Privacy notification request</xref>  </p> </li> </ul> </li> <li id="GUID-C465B7B8-4014-5636-870E-C024522F196F"><p><xref href="GUID-2E565B8E-D262-5769-96E6-A532154D57E6.dita#GUID-2E565B8E-D262-5769-96E6-A532154D57E6/GUID-A207FD17-1EBE-5360-8AE5-89598BBDDBB8">See also</xref>  </p> </li> </ul> </section> <section id="GUID-64BFDD62-7E1C-5F04-A2F7-426F40BFADA7"><title>Introduction</title> <p>When a request for a mobile device's location is received it is important to protect the user's privacy. Users of LBS-enabled mobile devices need to be able to decide to whom their location can be sent and when it can be sent. </p> <p>Users may want to control access to their location on a per-request basis or by defining a set of rules to allow a response to be sent automatically without manual intervention. </p> <p>The requester can be: </p> <ul><li id="GUID-7197EA07-4F44-52AB-9107-55BE98DB0F79"><p>An address book contact sending the request via a network service </p> </li> <li id="GUID-9BD0A12F-A682-5775-982C-15CC22111422"><p>An emergency services network-based application that requests location when the user makes an emergency services call </p> </li> <li id="GUID-E40EC871-0C9C-5810-9C13-45E0A4E0FD37"><p>A non-emergency network service </p> </li> <li id="GUID-CE30071C-F056-5CB3-81D4-CC2D58790EB0"><p>An application installed on the mobile device (in the <xref href="GUID-D18B4715-3942-52EA-9D2F-E145037FA47A.dita">Standalone Privacy Mode configuration</xref> only) </p> </li> </ul> <p>The special case of emergency services requests is very important. When a user makes an emergency services call a network operator may respond by sending an emergency services location request to the mobile device. The LBS subsystem must be capable of responding to such requests even in low memory conditions. </p> <p>The privacy request handling mechanisms of LBS process privacy requests in ways that both protect a user's privacy but also allow the user's location to be sent quickly to emergency services. </p> <p>How LBS handles privacy and location requests is one of the main differentiators between the <i>Full LBS configuration</i> and the <i>Standalone Privacy Mode configuration</i>. See <xref href="GUID-D18B4715-3942-52EA-9D2F-E145037FA47A.dita">LBS integration and configuration guide</xref> for more information. </p> </section> <section id="GUID-47F9AED8-53D5-5C52-854D-A455770E8D1C"><title>Key concepts</title> <p><b>MO-LR </b> </p> <p>Mobile Originated Location Request. A request for location that may be received by the LBS subsystem from a local application. </p> <p><b>MT-LR </b> </p> <p>Mobile Terminated Location Request. A request for location received from the network. MT-LRs are classified as emergency or non-emergency requests depending on the originator of the request. Emergency MT-LRs may be sent to a mobile device as part of an emergency services call and are given priority by the LBS subsystem. </p> <p>Note however that only the <i>Full LBS configuration</i> supports guaranteed handling of emergency MT-LRs. The <i>Standalone Privacy Mode configuration</i> does not support guaranteed handling of the requests. </p> <p>An MT-LR consists of two parts: the privacy request and the location request. The two parts of the request are sent as separate requests from the network to the mobile device. The privacy request is processed first followed by the location request (if the privacy request is approved). </p> <p>The choice of whether emergency MT-LR or emergency NI-LR (see below) are sent from the network depends on the network operator. </p> <p>In the Standalone Privacy Mode, a privacy request may be received as part of an MT-LR or it may be sent from an application installed on the mobile device. </p> <p><b>NI-LR </b> </p> <p>Network Induced Location Request. A location request sent from the network without first sending a network privacy request. An NI-LR can be sent for emergency or non-emergency location requests. Emergency NI-LRs may be sent to a mobile device as part of an emergency services call and are given priority by the LBS subsystem. </p> <p>The choice of whether emergency NI-LR or emergency MT-LR (see above) are sent from the network depends on the network operator. </p> <p><b>Network privacy request </b> </p> <p>A privacy request received from the network </p> <p><b>Local privacy request </b> </p> <p>A privacy request received from a local application. Note that this is only supported in the <xref href="GUID-D18B4715-3942-52EA-9D2F-E145037FA47A.dita">Standalone Privacy Mode configuration</xref> and this is not the same as requesting location via the <xref href="GUID-D0318BB6-0B9F-5A1C-AB0B-61BA22D28661.dita">Location Acquisition API</xref>. </p> <p><b>Privacy verification request </b> </p> <p>A privacy request that requires a user response. The user can choose to either accept or reject the privacy request. </p> <p><b>Privacy notification request </b> </p> <p>A privacy request that does not require a user response. Typically generated for an emergency services request. It is not a request in the true sense of the word, since the user cannot reject it. </p> <p><b>Privacy response </b> </p> <p>The response to a privacy verification request. It is specified either by the user accepting or rejecting the request or automatically by a Privacy Controller configured to respond automatically to privacy requests. </p> <p><b>Privacy Controller </b> </p> <p>An application that implements the <xref href="GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0.dita#GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0/GUID-126FAEA8-3E7F-5988-AB6C-F93E63B09E2F">LBS Privacy Controller API</xref> to receive privacy requests, process them and respond to them. A Privacy Controller is typically used to handle privacy requests when an automated response is required based on a set of privacy rules. </p> <p><b>Privacy Notifier </b> </p> <p>A Symbian <xref href="GUID-E049772D-A96F-592F-AF59-C9B69E8D24C1.dita">notifier</xref> that can be used by the LBS subsystem to handle privacy and location requests. Privacy Notifiers are used to display <i>privacy verification</i> and <i>privacy notification</i> dialogs (see below) to the device user. </p> </section> <section id="GUID-5D079E0C-A64E-51A1-8794-009A199CE65F"><title>Privacy verification requests and privacy notification
          requests</title> <p>A privacy request sent from the network (or from a local application for the <xref href="GUID-D18B4715-3942-52EA-9D2F-E145037FA47A.dita">Standalone Privacy Mode configuration</xref>) can be of one of two types: </p> <ul><li id="GUID-C7F3863F-2099-57BE-A435-82E819A8F9CB"><p>A privacy verification request </p> </li> <li id="GUID-60AD7F3C-C989-58D4-AD01-AE4AE4B81EDC"><p>A privacy notification request </p> </li> </ul> <p id="GUID-5939104B-84F3-53B5-AE32-816015E4640D"><b>Privacy verification request</b> </p> <p>A <i>privacy verification request</i> must be authorised by the mobile device user. Privacy verification is the process of accepting or rejecting a privacy verification request. </p> <p>Privacy verification may be performed either: </p> <ul><li id="GUID-2131B641-FEE9-5544-AF37-686C623E8848"><p>On a per-request basis by the device user by responding to privacy verification dialogs launched by LBS <xref href="GUID-F8C5A22F-8433-5F50-B12A-E964572E6C23.dita#GUID-F8C5A22F-8433-5F50-B12A-E964572E6C23/GUID-DC80984B-7B46-5C2D-A1EF-EDBB0983159D">Privacy Notifiers</xref>. </p> </li> <li id="GUID-20000403-515B-525F-8239-9264F0CF0B54"><p>Automatically if a <xref href="GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0.dita#GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0/GUID-126FAEA8-3E7F-5988-AB6C-F93E63B09E2F">Privacy Controller</xref> configured with privacy rules is installed and configured by a Symbian licensee/device manufacturer. A Privacy Controller can also use privacy verification dialogs for per-request processing. </p> </li> </ul> <p>A typical scenario requiring privacy verification for a network privacy request follows: </p> <ol id="GUID-9FCF620E-E725-5DA6-A8B7-C0FD50D57CFA"><li id="GUID-D341B527-94CB-5FCF-9574-C9BF79BCCEA8"><p>A remote requester wants to get a mobile device user's location. The requester may be a user contact or a network service (but not an emergency services request which does not require privacy verification). </p> <p>The request for the mobile device location is made via some type of network service. The exact method by which requests are routed to the mobile device is outside of the scope of this documentation and is not relevant to the way in which such requests are handled by the LBS subsystem. </p> </li> <li id="GUID-882777F9-5DA7-5E09-A6EB-154C4890B065"><p>The network generates a non-emergency MT-LR that is sent to the mobile device. </p> </li> <li id="GUID-A7FD84A0-BB04-5D83-A2F0-0F41E3B74950"><p>The LBS subsystem receives the MT-LR and processes the privacy request. As the privacy request is a non-emergency request the LBS subsystem requests verification either from the user via Privacy Notifiers or from a Privacy Controller (which may handle the request itself or display dialogs to the user). </p> <p>The choice of which method of verification is used depends on the <xref href="GUID-23BBC1D8-B3A0-5148-A4F1-22ECF3043E4E.dita">LBS administration</xref> settings for privacy. </p> <p>When the privacy request has been processed (accepted or rejected), the LBS subsystem returns a <i>privacy response</i> to the network. The response indicates if the privacy request was accepted or rejected. </p> <p>If the privacy request is accepted, the location request part of the MT-LR can be processed. </p> </li> <li id="GUID-DBE1EECC-234D-5053-B258-69EB131FB21E"><p>The network sends a location request to the device (although in practice the network may not wait to receive the privacy response before it sends the location request - the exact behaviour is specific to the network operator). </p> </li> <li id="GUID-544C5BCC-F118-5203-889F-4BB11953382C"><p>Handling of the location request depends on the LBS configuration built by the Symbian licensee. </p> <p>The location request can be handled either: </p> <ul><li id="GUID-BAF1C8F4-9004-5489-A0A8-AB050C36DF2E"><p>In the Symbian LBS subsystem itself when the licensee has built LBS in the Full LBS configuration. </p> </li> <li id="GUID-E72395FC-A247-5487-B0E7-266BA2C29F6F"><p>In the mobile device's domestic OS when the licensee has built a Standalone Privacy Mode configuration. </p> </li> </ul> <p>The choice of where to handle the location request part of an MT-LR or an NI-LR is a fundamental design and implementation decision that must be made by the Symbian licensee manufacturer before the LBS subsystem ROM image is built. The <xref href="GUID-D18B4715-3942-52EA-9D2F-E145037FA47A.dita">LBS Integration and Configuration guide</xref> gives details. </p> <p>For detailed privacy request verification sequence diagrams see <xref href="GUID-F8C5A22F-8433-5F50-B12A-E964572E6C23.dita#GUID-F8C5A22F-8433-5F50-B12A-E964572E6C23/GUID-DC80984B-7B46-5C2D-A1EF-EDBB0983159D">Privacy Notifiers</xref> and <xref href="GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0.dita#GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0/GUID-126FAEA8-3E7F-5988-AB6C-F93E63B09E2F">Privacy Controller</xref> documentation. </p> </li> </ol> <p id="GUID-97F3AE63-D529-54DC-9C77-8B0AE1DA150A"><b>Privacy notification request</b> </p> <p>A <i>privacy notification request</i> does not require authorisation by the mobile device user. A privacy notification request is typically received as part of an emergency services request for location. </p> <p>A typical scenario involving privacy notification is as follows: </p> <ol id="GUID-96475AE9-CBF1-5FFD-9FE6-173B1C7B88A0"><li id="GUID-F146290F-45D5-541E-97D2-B15381726ED2"><p>An MT-LR containing a privacy notification request is received and the LBS subsystem notifies the user. The associated location request may be sent at the same time as the privacy request or as a separate request. The main point to note is that the network does not wait for a privacy response before sending the location request. </p> </li> <li id="GUID-D8DBB781-EEEC-540E-8B0C-B4A5717B226F"><p>The LBS subsystem either starts a <xref href="GUID-F8C5A22F-8433-5F50-B12A-E964572E6C23.dita#GUID-F8C5A22F-8433-5F50-B12A-E964572E6C23/GUID-DC80984B-7B46-5C2D-A1EF-EDBB0983159D">Privacy Notifier</xref> or sends the notification to a <xref href="GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0.dita#GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0/GUID-126FAEA8-3E7F-5988-AB6C-F93E63B09E2F">Privacy Controller</xref>. </p> </li> <li id="GUID-8F796DF8-B0D1-54C4-A49E-CBF113EE04F5"><p>The LBS subsystem either processes the location request or it is handled in the licensee domestic OS. Where the location request is processed depends on whether the LBS subsystem is configured in the Full LBS configuration or the Standalone Privacy Mode configuration. </p> </li> </ol> <p>For detailed privacy notification request sequence diagrams see <xref href="GUID-F8C5A22F-8433-5F50-B12A-E964572E6C23.dita#GUID-F8C5A22F-8433-5F50-B12A-E964572E6C23/GUID-DC80984B-7B46-5C2D-A1EF-EDBB0983159D">Privacy Notifiers</xref> and <xref href="GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0.dita#GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0/GUID-126FAEA8-3E7F-5988-AB6C-F93E63B09E2F">Privacy Controller</xref> documentation. </p> </section> </conbody></concept>