Network Privacy API

Introduction

The Network Privacy API supports device creators who wish to use the Symbian LBS subsystem to handle only privacy requests but not to perform position fix calculations.

The Network Privacy API is intended to be used to process privacy requests received from the network. To process multiple privacy requests from local applications, it is recommended that the Privacy Request API be used.

Description

The Network Privacy API is implemented on the client-side by the Network Privacy Client DLL. This DLL is the interface to the Privacy Protocol Module.

The Network Privacy API does not guarantee performance in low memory conditions for which a privacy request may fail. For this reason the Privacy Protocol Module must not be used when there is a need to support emergency services privacy requests from the network (MT-LR or NI-LR). A Protocol Module that handles location requests must be used if emergency services requests must be supported.

Figure 1 shows the Network Privacy Client DLL in the context of the LBS subsystem. The most important points to note are:

• The Network Privacy Client DLL exposes the Network Privacy API which is described in this document. The DLL is used to send privacy requests into the Symbian LBS subsystem from a component running in the licensee's domestic OS (outside of the Symbian platform).

• The Network Privacy Client DLL connects to a server implementation in the Privacy Protocol Module.

• A device creator does not create their own implementation of the Network Privacy Client DLL or the Privacy Protocol Module. A device creator chooses to build a ROM containing the Privacy Protocol Module and the Network Privacy Client DLL. See LBS Integration and Configuration Guide for more information about building and configuring the LBS subsystem.

• To use the Network Privacy API a device creator must implement some kind of client process in their domestic operating system which uses the Network Privacy API.

  The Network Privacy API client process must implement the API observer interface to receive privacy responses. The client process, and not Symbian LBS is responsible for sending these privacy responses to the network.

Figure 1. Figure 1. The Network Privacy API and the Privacy Protocol Module.

Network Privacy API description

Figure 2 shows the classes of the Network Privacy API.

Figure 2. Figure 2. Network Privacy API classes

The following table lists the classes and types that define the Network Privacy API. Further details can be found by following the links to other sections of this document and to Symbian Developer Library reference documentation.

The Network Privacy API has publishedPartner interface access.

Libraries

The Network Privacy API is packaged in eposnwprv.dll. Clients link to eposnwprv.lib.

Capabilities

To use the Network Privacy API a client requires the following capabilities: Location, NetworkServices and ReadDeviceData.

To maintain backwards compatibility with existing clients of the Network Privacy API the alternative capability CommDD is also supported. However, new clients should be created to have the three capabilities listed above.

LBS configuration

The Network Privacy API is only available when the Privacy Protocol Module is included in an LBS subsystem. See LBS Integration and Configuration Guide for details about how to build a ROM image that supports the Network Privacy API.

Multiple simultaneous privacy requests

The LBS subsystem can be configured to handle multiple simultaneous privacy requests from the Network Privacy API. The LBS Administration setting KLbsSettingMaximumExternalLocateRequests defines the maximum number of privacy requests that can be handled simultaneously by the LBS subsystem.

If an additional privacy request is sent into the LBS subsystem such that the total number of requests exceeds KLbsSettingMaximumExternalLocateRequests, the additional request is always rejected i.e. the LBS subsystem calls MPosVerificationObserver::HandleVerifyComplete() with aCompletionCode = KErrAccessDenied.

Maximum number of API sessions

The LBS Administration setting KLbsSettingPrivacyMaxNetworkSessions defines the maximum number of concurrent sessions allowed with the Network Privacy API.

Session timeouts

The LBS Administration setting KLbsSettingPrivacyConnectionTimeout controls the connection timeout for sessions using the Network Privacy API. This value can be overriden by an API client by calling CPosNetworkPrivacy::SetConnectionTimeout().

LBS shutdown delay

The LBS subsystem is transient when it is built to include a Privacy Protocol Module and the Network Privacy API. The LBS Administration setting KLbsSettingPrivacyShutdownDelay sets the delay between closure of the last client connection and LBS subsystem shutdown.