9.1.10 Circuit Switched Post Positioning Notification and Verification Procedure

23.2713GPPFunctional stage 2 description of Location Services (LCS)Release 17TS

Figure 9.10 illustrates the post positioning notification and verification procedure.

Figure 9.10: CS Post Positioning Notification and Verification Procedure

1) Common PS and CS MT-LR procedure as described in clause 9.1.1.

2) The GMLC sends a PROVIDE_ SUBSCRIBER _LOCATION message to the MSC/MSC server with an indication of "notification only". This message carries the UE subscriber’s IMSI. For a call related location request, the message also carries the LCS client’s called party number. For a value added LCS client, the message shall carry the client name, the external identity of the LCS client and the Requestor Identity (if that is both supported and available). Also the message may carry the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. For a PLMN operator LCS client, the message shall carry the internal identity of the LCS client. Moreover the message may also carry the Service Type. If the result of the privacy check at H-GMLC/PPR indicated that the codeword shall be sent to the UE user, the message may carry also the codeword received from the LCS client. For a PLMN operator LCS client, the message shall carry the internal identity of the LCS client. If the Requestor Identity is provided, the GMLC shall send it as separate information. In addition, in order to display the requestor identity in case of pre Rel-5 network elements (i.e. MSC and/or UE), the requestor identity may be also added to the LCS client name by the GMLC. When the Requestor identity is added to the LCS client name the practice described in the Annex D should be followed.

3) If the UE is in idle mode, the Core Network performs paging, authentication and ciphering. The MSC will page a GPRS attached UE either through A/Iu or Gs interface, depending on the presence of the Gs interface.

4) An LCS Location Notification Invoke message is sent to the target UE indicating a location type of notification and verification only, the identity of the LCS client, the Requestor Identity (if that is both supported and available) and whether privacy verification is required. Also the message may indicate the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. Moreover, the message may carry also the service type and the codeword.4).

5) The target UE notifies the UE user of the location request. If privacy verification was requested, the target UE indicates to the UE user whether the location report will be allowed or not allowed in the absence of a response and waits for the user to grant or withhold permission. The UE then returns an LCS Location Notification Return Result to the VMSC/MSC server indicating, if privacy verification was requested, whether permission is granted or denied. If the UE user does not respond after a predetermined time period, the VMSC/MSC server shall infer a "no response" condition. The VMSC/MSC server shall return an error response to the GMLC if privacy verification was requested and either the UE user denies permission or there is no response with the UE subscription profile indicating barring of the location request in the absence of a response.

6) The VMSC/MSC server returns the indication of successful notification and verification result, if it has received a LCS Location Notification Return Result indicating that permission is granted. If a LCS Location Notification Return Result message indicating that permission is not granted is received, or there is no response, with the requested privacy action or the UE subscription profile indicating barring of location in the absence of a response, the VMSC/MSC server shall return an error response to the GMLC. The MSC/MSC server may then release the Mobility Management connection to the UE, if the UE was previously idle, and the MSC/MSC server may record charging information.

7) Common MT-LR procedure in PS and CS domain as described in clause 9.1.1.