7.12 Privacy

03.713GPPFunctional descriptionLocation Services (LCS)Release 1999Stage 2TS

7.12.1 Privacy Override Indicator (POI)

The POI is used to determine whether the privacy settings of the subscriber to be positioned shall be overridden by the request for location services. The assignment of a POI value with an ‘override’ or ‘not override’ value in the LCS client profile is done during the LCS client provisioning. The type of LCS client requesting location information (i.e.emergency, law-enforcement etc.) shall determine the value of the POI assigned to the LCS client profile.

There are two distinct cases regarding the handling of the privacy override indicator.

Procedure A: If the subscriber to be positioned is in the same country as the GMLC then the POI shall override the subscriber’s privacy options, as allowed by regulatory requirements.

Procedure B: Otherwise the POI shall not override the subscriber’s privacy options.

7.12.2 Privacy Procedures

The SLPP shall contain the privacy options defined in the HLR of the MS subscriber.

The SLPP shall be downloaded to the VMSC together with the rest of his subscription information in the existing MAP operation INSERT_SUBSCRIBER_DATA. It will be deleted with the existing MAP operation DELETE_SUBSCRIBER_DATA.

The POI is transferred from the GMLC to the VMSC in the location request. Based on the location of the GMLC the VMSC evaluates whether to accept or ignore the received POI according to the definition in Section 6.6.1.

If the POI is accepted the location requested is unconditionally performed. Otherwise if the POI is ignored the VMSC evaluates the privacy options in the MS subscriber’s subscription profile (assuming this is held in the VLR). If the VLR does not contain the MS subscription profile, LCS will rely on the existing GSM recovery mechanisms to obtain the profile.

Note: If more than one privacy class are subscribed for the MS, the privacy class for an MT-LR is selected according to the rule described in the informative ANNEX E.

If the location request is allowed by the privacy options the location request is performed. Otherwise, if the location request is barred by the privacy options, the location request is refused an error response is returned to the GMLC with a cause code indicating that the request was rejected by the subscriber.

7.12.3 MS Privacy Options

The MS privacy options in the SLPP apply to an MT-LR or NI-LR and either indicate that no MT-LR or NI-LR is allowed for the MS (except as may be overridden by the POI or local regulatory requirements) or define the particular classes of LCS client for which an MT-LR or NI-LR for location are allowed, with the following classes being possible:

a) Universal Class – allow positioning by all LCS clients

b) Call related Class – comprises any LCS client to which the MS originated a call that is currently established. For all clients in the call related class, one of the following subscription options shall apply:

– positioning allowed without notifying the MS user (default case);

– positioning allowed with notification to the MS user;

– positioning requires notification and verification by the MS user; positioning is allowed only if granted by the MS user or if there is no response to the notification;

– positioning requires notification and verification by the MS user; positioning is allowed only if granted by the MS user;

c) Non-Call related Class – allow positioning by specific identified LCS Clients or groups of LCS Client with the following restrictions allowed for each identified LCS Client or group of LCS Clients

– Location request allowed only from GMLCs identified in the SLPP

– Location request allowed only from a GMLC in the home country

– Location request allowed from any GMLC

For each identified value added LCS client in the privacy exception list one of the following subscription options shall apply:

– positioning allowed without notifying the MS user (default case);

– positioning allowed with notification to the MS user;

– positioning requires notification and verification by the MS user; positioning is allowed only if granted by the MS user or if there is no response to the notification;

– positioning requires notification and verification by the MS user; positioning is allowed only if granted by the MS user;

For all value added LCS clients sending a non-call related MT-LR that are not identified in the privacy exception list, one of the following subscription option shall apply:

– positioning not allowed (default case);

– positioning allowed with notification to the MS user;

– positioning requires notification and verification by the MS user; positioning is allowed only if granted by the MS user or if there is no response to the notification;

– positioning requires notification and verification by the MS user; positioning is allowed only if granted by the MS user;

d) PLMN operator Class – allow positioning by specific types of client within or associated with the VPLMN, with the following types of client identified:

– clients providing a location related broadcast service

– O&M client in the HPLMN (when the MS is currently being served by the HPLMN)

– O&M client in the VPLMN

– Clients recording anonymous location information without any MS identifier

– Clients enhancing or supporting any supplementary service, IN service, bearer service or teleservice subscribed to by the target MS subscriber

If the MS subscribes to the universal class, any MT-LR or NI-LR shall be allowed by the VMSC. If local regulatory requirements mandate it, any MT-LR for an emergency services LCS client and any NI-LR for an emergency services call origination shall be allowed by the VMSC.

If the MS subscribes to the call-related class, an MT-LR may be allowed if the MS previously originated a call that is still established and the called party number dialed by the MS matches the called party number received from the GMLC. If the called party number conditions are satisfied, the MT-LR shall be allowed if the MS user subscribes to either location without notification or location with notification. If the MS user subscribes to location with notification and privacy verification, the MT-LR shall be allowed following notification to the MS if the MS user either returns a response indicating that location is allowed or returns no response but subscribes to allowing location in the absence of a response. In all other cases, the MT-LR shall be restricted.

If the MS subscribes to the non-call related class, an MT-LR may be allowed by the network if the identity of the LCS client or LCS client group supplied by the GMLC matches the identity of any LCS Client or LCS Client group contained in the MS’s SLPP and any other GMLC restrictions associated with this LCS Client identity in the SLPP are also met. If the LCS client is correctly matched in this way and any GMLC restrictions are satisfied, the MT-LR shall be allowed if the MS user subscribes to either location without notification or location with notification. If the MS user subscribes to location with notification and privacy verification, the MT-LR shall be allowed following notification to the MS if the MS user either returns a response indicating that location is allowed or returns no response but subscribes to location in the absence of a response. In all other cases, the MT-LR shall be restricted.

If the MS subscribes to the non-call related class, an MT-LR from an LCS client that is not contained in the MS’s SLPP shall allowed or restricted according to the following conditions. For any non-matched LCS client, the MT-LR shall be allowed if the MS user subscribes to location with notification. If the MS user subscribes to location with notification and privacy verification, the MT-LR shall be allowed following notification to the MS if the MS user either returns a response indicating that location is allowed or returns no response but subscribes to location in the absence of a response. In all other cases, the MT-LR shall be restricted.

If the MS subscribes to the PLMN class, an NI-LR or MT-LR shall be allowed if the client within the VPLMN, for an NI-LR, or the client identified by the GMLC, for an MT-LR, either matches a generic type of client contained in the MS’s SLPP or is otherwise authorized by local regulatory requirements to locate the MS.

In evaluating privacy where any address "A" associated with the LCS client (e.g. LCS client ID or GMLC address) needs to be compared with a corresponding address "B" in the target MS’s SLPP, a match shall be determined if a match is found for each of the following components of each address:

a) Numbering Plan

b) Nature of Address Indicator

c) Corresponding address digits for all digits in "B" (the digits or initial digits in "A" must match all the digits in "B", but "A" may contain additional digits beyond those in "B")

All addresses shall be transferred to the MSC/VLR in international format, except for the called party number received from the GMLC during a Call Related MT-LR when the LCS client was reached via IN or abbreviated number routing (e.g. toll free number or emergency call routing). In these cases it is up to the GMLC to use the valid national specific number of the visited country.