Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.271  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.2…   7…   8…   9…   9.1.1A…   9.1.2…   9.1.5…   9.1.6…   9.1.8…   9.1.9…   9.1.12…   9.1.13…   9.1.15…   9.1.19…   9.2…   9.2.2…   9.2.3…   9.3…   9.4…   9.5…   9.6…   10…   11…   A…   B…   E   F… 
9.5 Privacy  9.5.1 Privacy Override Indicator (POI)  9.5.2 Privacy Procedures  9.5.3 UE Privacy Options  9.5.3.1 Universal class  9.5.3.2 Call/Session related class  9.5.3.3 Call/Session-unrelated class  9.5.3.4 PLMN operator class  9.5.3.5 Service type checking  9.5.3.6 Matching of LCS client identities  9.5.4 Indicator of privacy check related action 
...

 

9.5  Privacy  p. 152

9.5.1  Privacy Override Indicator (POI)  p. 152

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 POI is applicable only to Emergency service and Lawful intercept service. 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.
POI is not sent to the MME.
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 or if the subscriber to be positioned is in a different country than the GMLC and an appropriate bilateral agreement exists between operators, 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.
Up

9.5.2  Privacy Procedures  p. 152

The privacy profile of the UE subscriber (SLPP) may for GSM and UMTS be stored in HLR/HSS and/or in H-GMLC/PPR. The privacy profile of the UE subscriber (SLPP) shall for EPS be stored in H-GMLC/PPR. If the privacy profile data are stored in SLPP of H-GMLC/PPR, then the pseudo external identities, if required, shall be contained in the SLPP of the HLR/HSS. Also if the privacy profile data are stored in H-GMLC/PPR, H-GMLC/PPR sends the indicators of privacy related action or the pseudo external identities to the serving nodes in order to inform the results of the privacy check procedures in H-GMLC/PPR.
The SLPP stored in the HLR/HSS shall be downloaded to the VMSC, MSC Server and SGSN together with the rest of his subscription information in the existing operation INSERT_SUBSCRIBER_DATA. It will be deleted with the existing operation DELETE_SUBSCRIBER_DATA.
In case of an Emergency Services location request, based on the location of the VMSC/MSC Server/SGSN and the R-GMLC, the V -GMLC evaluates whether to accept or ignore the received POI, according to the definition in clause 9.1.5. If privacy override is not allowed, then the V-GMLC rejects the request.
In case the privacy override i s allowed, the POI is transferred from the GMLC to the VMSC/MSC Server/SGSN in the location request. Based on the location of the GMLC the VMSC/MSC Server/SGSN evaluates whether to accept or ignore the received POI according to the definition in clause 9.5.1.
If the POI is accepted the location requested is unconditionally performed. Otherwise the VMSC/MSC Server/SGSN evaluates the privacy options in the UE subscriber's subscription profile (assuming this is held in the VLR/MSC Server/SGSN) or evaluates the received privacy related action indicators. If the corresponding register does not contain the UE subscription profile, LCS will rely on the existing GSM recovery mechanisms to obtain the profile.
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/MSC Server/SGSN/MME.
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 LCS client with a cause code indicating that the request was rejected by the subscriber.
Up

9.5.3  UE Privacy Options  p. 153

The UE privacy options in the SLPP apply to an CS-MT-LR/PS-MT-LR or NI-LR/PS-NI-LR and either indicate that no CS-MT-LR/PS-MT-LR or NI-LR/PS-NI-LR is allowed for the UE (except as may be overridden by the POI or local regulatory requirements) or define the particular classes of LCS client for which an CS-MT-LR/PS-MT-LR or NI LR/PS-NI-LR for location are allowed, with the following classes being possible:
  1. Universal Class - allow positioning by all LCS clients;
  2. Call/Session related Class
  3. Call/Session-unrelated Class
  4. PLMN operator Class
Moreover the SLPP may contain the service types allowed by the subscriber.
All UE privacy options of above four classes are commonly used for both CS and PS domain.
The privacy classes are selected according to the rules described in the Annex A. If more than one privacy class are subscribed in the UE's SLPP, the looser privacy setting shall be selected. Annex A applies also in case service types privacy checking are subscribed together with one or more other privacy classes.
Up

9.5.3.1  Universal class  p. 153

When the user of the UE subscribes to the "Universal Class" the CS-MT-LR/PS-MT-LR or NI-LR/PS-NI-LR positioning is allowed by all LCS clients.
If the UE subscribes to the universal class, any CS-MT-LR or NI-LR shall be allowed by the VMSC/MSC Server and any PS-MT-LR or PS-NI-LR shall be allowed by the SGSN.
If the UE subscribes to the universal class and H-GMLC/PPR knows that the serving node supports the indicator of privacy check related action, H-GMLC/PPR sends the indicators for call/session unrelated class, which indicates "Location allowed without notification". If the UE subscribes to the universal class and H-GMLC/PPR knows that the serving node does not support the indicator of privacy check related action, H-GMLC/PPR may sends the appropriate pseudo external identity as described in Annex C.
Up

9.5.3.2  Call/Session related class  p. 154

When the user of the UE subscribes to the "Call/Session related Class" the CS-MT-LR/PS-MT-LR/EPC-MT-LR or NI-LR/PS-NI-LR positioning is allowed in the following cases:
Allow positioning by specific identified value added LCS client or groups of value added LCS Client to which the UE originated a call in CS domain or a value added LCS client with which the UE has a session via an active PDP context in PS domain indicated by a specific APN-NI. For each identified LCS client or group of LCS Clients, one of the following subscription options shall apply:
  • 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 (default case).
For each identified value added LCS client or group of LCS Clients in the privacy exception list, one of the following subscription options shall apply:
  • positioning allowed without notifying the UE user (default case);
  • positioning allowed with notification to the UE user;
  • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification;
  • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user.
For all value added LCS clients sending a call related CS-MT-LR/PS-MT-LR/EPC-MT-LR that are not identified in the privacy exception list, one of the following subscription option shall apply:
  • positioning not allowed;
  • positioning allowed without notifying the UE user (default case);
  • positioning allowed with notification to the UE user;
  • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification;
  • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user.
Up
9.5.3.2.1  Call/session-related class in the CS-domain  p. 154
If the UE subscribes to the call/session-related class, an CS-MT-LR may be allowed if both of following conditions are met:
  • The UE previously originated a call in CS domain that is still established and the called party number dialled by the UE matches the called party number received from the GMLC.
  • 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 UE's SLPP and any other GMLC restrictions associated with this LCS Client identity in the SLPP are also met
If these conditions are satisfied, the CS-MT-LR shall be allowed if the UE user subscribes to either location without notification or location with notification. If the UE user subscribes to location with notification and privacy verification, the CS-MT-LR shall be allowed following notification to the UE if the UE 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 CS-MT-LR shall be restricted.
Up
9.5.3.2.2  Call/session-related class in the PS-domain  p. 155
If the UE subscribes to the call/session-related class, a PS-MT-LR/EPC-MT-LR may be allowed if all of the following conditions are met:
  • The UE previously originated a PDP/EPS Bearer-context towards the network where the external client is located and that this context is still established.
  • The APN-NI negotiated between the UE and SGSN/MME matches the APN-NI received from the GMLC.
  • 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 UE's SLPP and any other GMLC restrictions associated with this LCS Client identity in the SLPP are also met.
If these conditions are satisfied, the PS-MT-LR/EPC-MT-LR shall be allowed if the UE user subscribes to either location without notification or location with notification. If the UE user subscribes to location with notification and privacy verification, the PS-MT-LR/EPC-MT-LR shall be allowed following notification to the UE if the UE 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 PS-MT-LR/EPC-MT-LR shall be restricted.
Up
9.5.3.2.3  Call/session-related class when LCS client not in SLPP  p. 155
If the UE subscribes to the call/session related class, a CS-MT-LR, PS-MT-LR or EPC-MT-LR from an LCS client that is NOT contained in the SLPP of the target UE shall be allowed or restricted according to the following conditions:
  • For any non-matched LCS client, the CS-MT-LR, PS-MT-LR or EPC-MT-LR shall be allowed, if the UE user subscribes to either location without notification or location with notification.
If the UE user subscribes to location with notification and privacy verification, the CS-MT-LR, PS-MT-LR or EPC-MT-LR shall be allowed following notification to the UE if the UE 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 CS-MT-LR, PS-MT-LR or EPC-MT-LR shall be restricted.
Up

9.5.3.3  Call/Session-unrelated class  p. 155

When the user of the UE subscribes to the "Call/Session unrelated Class" the CS-MT-LR/PS-MT-LR/EPC-MT-LR or NI-LR/PS-NI-LR positioning is allowed in the following cases:
Allow positioning by specific identified value added LCS Clients or groups of value added LCS Client with the following restrictions allowed for each identified value added LCS Client or group of value added 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 (default case).
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 UE user (default case);
  • positioning allowed with notification to the UE user;
  • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification;
  • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user.
For all value added LCS clients sending a non-call/session related CS-MT-LR/PS-MT-LR/EPC-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 UE user;
  • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification;
  • positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user.
Up
9.5.3.3.1  Call/session-unrelated class when LCS client identities match  p. 156
If the UE subscribes to the call/session-unrelated class, an CS-MT-LR/PS-MT-LR/EPC-MT-LR may be allowed by the MSC/MSC server, SGSN or MME 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 UE'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 CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be allowed if the UE user subscribes to either location without notification or location with notification. If the UE user subscribes to location with notification and privacy verification, the CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be allowed following notification to the UE if the UE 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 CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be restricted.
Up
9.5.3.3.2  Call/session-unrelated class when LCS client identities do not match  p. 156
If the UE subscribes to the call/session-unrelated class, an CS-MT-LR/PS-MT-LR/EPC-MT-LR from an LCS client that is not contained in the UE's SLPP shall be allowed or restricted according to the following conditions. For any non-matched LCS client, the CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be allowed if the UE user subscribes to location with notification. If the UE user subscribes to location with notification and privacy verification, the CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be allowed following notification to the UE if the UE 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 CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be restricted.
Up

9.5.3.4  PLMN operator class  p. 156

When the user of the UE subscribes to the " PLMN operator Class" the CS-MT-LR/PS-MT-LR or NI-LR/PS-NI-LR positioning is allowed in the following cases:
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 UE is currently being served by the HPLMN);
* O&M client in the VPLMN;
* clients recording anonymous location information without any UE identifier;
* clients enhancing or supporting any supplementary service, IN service, bearer service or teleservice subscribed to by the target UE subscriber.
If the UE subscribes to the PLMN class, an NI-LR/PS-NI-LR or CS-MT-LR/PS-MT-LR shall be allowed if the client within the VPLMN, for an NI-LR/PS-NI-LR, or the client identified by the GMLC, for an CS-MT-LR/PS-MT-LR, either matches a generic type of client contained in the UE's SLPP or is otherwise authorized by local regulatory requirements to locate the UE. If H-GMLC/PPR knows that the serving node supports LCS capability set 4 or later, then H-GMLC/PPR will send the indicators for call/session unrelated class, which indicates 'location allowed without notification'. If H-GMLC/PPR is notified that the serving node does not support the LCS capability set 4 or later, then it will not send any indicator.
Up

9.5.3.5  Service type checking  p. 157

If the SLPP contains service types, a CS-MT-LR/PS-MT-LR may be allowed if the service type supplied by the LCS client matches the identity of any service type contained in the UE's SLPP and any other GMLC restrictions associated with this service type in the SLPP are also met.
If the service type is correctly matched in this way and any GMLC restrictions are satisfied, the CS-MT-LR/PS-MT-LR shall be allowed if the UE user subscribes to either location without notification or location with notification. If the UE user subscribes to location with notification and privacy verification, the CS-MT-LR/PS-MT-LR shall be allowed following notification to the UE if the UE 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 CS-MT-LR/PS-MT-LR shall be restricted.
Up

9.5.3.6  Matching of LCS client identities |R5|  p. 157

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 UE's SLPP, a match shall be determined if a match is found for each of the following components of each address:
  1. numbering plan;
  2. nature of address indicator;
  3. 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, MSC server or SGSN in international format, except for the called party number received from the GMLC during a Call-Related CS 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.
In evaluating privacy where an APN-NI associated with the LCS client notified by the GMLC needs to be compared with a corresponding APN-NI that is used to set up the associated PDP context, a match shall be determined if a match is found for each component of APN-NI.
Up

9.5.4  Indicator of privacy check related action |R6|  p. 157

When the client type indicates value added service and the serving node supports LCS capability set 4 or later, H-GMLC/PPR shall select indicators for privacy check related action and the indicators shall be included in the Provide_Subscriber_Location request towards the serving node. The indication is sent to the serving node directly from the H-GMLC or via V-GMLC. There shall be an indicator for the call/session unrelated. For GSM and UMTS there shall be an optional indicator for the call/session related and it shall be sent only if call/session related identity, i.e. the number dialled by UE or APN-NI, is sent to the serving node. For EPS, there shall be an optional indicator for the session related and it shall be sent only if session related identity, i.e. APN-NI, is sent to the serving node.
The possible values of the indicator of privacy check related action for call/session unrelated case shall be:
  • Location allowed without notification
  • Location allowed with notification
  • Location with notification and privacy verification; location allowed if no response
  • Location with notification and privacy verification; location restricted if no response
  • Location not allowed (only applicable when the indicator for call/session related case is sent, or the POI is included in the provide subscriber location request)
The possible values of the indicator of privacy check related action for call/session related case shall be:
  • Location allowed without notification
  • Location allowed with notification
  • Location with notification and privacy verification; location allowed if no response
  • Location with notification and privacy verification; location restricted if no response
If both indicators are sent but indicating different actions and the call/session related criteria met in the serving node then an action according to the indicator with the looser action according to the definition in Annex A shall be chosen as shown in Annex A.3.
If the UE subscribes service types, then the result of the service type checking may be included in any of the privacy check indicators, as it is described in Annex A.3.
If the UE subscribes either to PLMN class or to the universal class, H-GMLC/PPR sends the indicator for call/session unrelated class with the value of "Location allowed without notification".
Up

Up   Top   ToC