6 ELP Procedures
29.1723GPPEvolved Packet Core (EPC) LCS Protocol (ELP) between the Gateway Mobile Location Centre (GMLC) and the Mobile Management Entity (MME)Location Services (LCS)Release 18SLg interfaceTS
6.1 General
The ELP procedures, between the GMLC and the MME over SLg interface and between GMLC and SGSN over Lgd interface, are used to exchange messages related to location services. The ELP can be divided into the following sub-procedures.
– Provide Subscriber Location
– Subscriber Location Report
6.2 Provide Subscriber Location
6.2.1 General
The Provide Subscriber Location operation is used by a GMLC to request the location of a target UE from the MME or SGSN at any time, as part of EPC-MT-LR or PS-MT-LR positioning procedures. The response contains a location estimate of the target UE and other additional information.
The Provide Subscriber Location operation is also used by a GMLC to request the location of the target UE from the SGSN or MME at any time, as part of deferred MT-LR procedure. The response contains the acknowledgment of the receipt of the request and other additional information.
6.2.2 Successful Operation
Figure 6.2.2-1: Provide Subscriber Location procedure. Successful operation.
The GMLC initiates the procedure by sending a PROVIDE SUBSCRIBER LOCATION REQUEST message to the MME or SGSN. This message carries the type of location information requested (e.g. current location and optionally, velocity), the UE subscriber’s IMSI, LCS QoS information (e.g. accuracy, response time), an indication of whether the LCS client has the override capability, and an indication of whether delayed location reporting for UEs transiently not reachable (e.g. UEs in extended idle mode DRX or Power Saving Mode) is supported as specified in clauses 9.1.6 and 9.1.15 of 3GPP TS 23.271 [2]. The message also carries an LCS reference number, if delayed location reporting is supported. For deferred MT-LR procedure, additionally, the message carries Deferred location type, LCS reference number, H-GMLC address, periodic LDR info, triggered LDR info, etc.
Upon reception of PROVIDE SUBSCRIBER LOCATION REQUEST message, the MME or SGSN shall perform authentication privacy verification on the location request. After that, for EPC-MT-LR or PS-MT-LR procedures the MME or SGSN shall retrieve the location information of the target UE from E-UTRAN or UTRAN/GERAN according to the procedures described in 3GPP TS 23.271 [2]. For a deferred EPC-MT-LR procedure, the MME shall wait until the UE becomes reachable before performing authentication privacy verification on the location request and instigating periodic or triggered location in the UE.
The MME or SGSN returns a PROVIDE SUBSCRIBER LOCATION RESPONSE to the GMLC. For EPC-MT-LR or PS-MT-LR procedures, if the target UE is transiently not reachable and delayed location reporting for UEs transiently not reachable is supported, the message shall contain an indication that the UE is transiently not reachable; otherwise the message shall contain the location estimate, its age and obtained accuracy. If the MME or SGSN failed to get the current location and the LCS client is requesting the current or last known location, the MME or SGSN may return the last known location of the target UE if this is known.
For a deferred EPC-MT-LR procedure for periodic or triggered location, the MME returns a PROVIDE SUBSCRIBER LOCATION RESPONSE to the GMLC to indicate that the MME is able and willing to support the procedure. After the MME has performed successful authentication privacy verification on the location request and successfully instigated periodic or triggered location in the UE, the MME returns a SUBSCRIBER LOCATION REPORT to the GMLC to indicate that periodic or triggered location has been activated in the UE. The MME (or a different MME) returns additional SUBSCRIBER LOCATION REPORT messages to the GMLC (or possibly to a different GMLC if not the HGMLC) for each periodic or triggered location event detected by the UE. For details, refer to 3GPP TS 23.271 [2].
If the GMLC has received indication from the HSS indicating the combined MME/SGSN node supporting the optimized LCS procedure (see 3GPP TS 29.173 [18] clause 5.2.1.2) and if the GMLC also supports optimized LCS procedure, the GMLC shall set the "Optimized-LCS-Proc-Req" bit within the PLR-Flags of the PROVIDE SUBSCRIBER LOCATION REQUEST message during EPC-MT-LR and/or PS-MT-LR procedures. When the combined MME/SGSN receives this message with "Optimized-LCS-Proc-Req" bit within the PLR-Flags set, the combined MME/SGSN shall perform EPC-MT-LR or PS-MT-LR procedure depending upon the knowledge of the current RAT type of the UE. E.g. if the UE is in active mode in E-UTRAN, the combined MME/SGSN shall perform only EPC-MT-LR procedure; if the ISR activated UE is in idle mode, the combined MME/SGSN shall perform the paging followed by either EPC-MT-LR or PS-MT-LR procedure (depending upon the RAT where the UE is active). Hence, the combined MME/SGSN shall perform optimized LCS procedure to retrieve the location information of the target UE from either E-UTRAN or UTRAN/GERAN.
The combined MME/SGSN shall return a PROVIDE SUBSCRIBER LOCATION RESPONSE to the GMLC. If the target UE is transiently not reachable and delayed location reporting for UEs transiently not reachable is supported, the message shall contain an indication that the UE is transiently not reachable; otherwise the message shall contain the location estimate, its age and obtained accuracy. If the combined MME/SGSN failed to get the current location and the LCS client is requesting the current or last known location, the combined MME/SGSN should return the latest of the last known EPS or UTRAN/GERAN location of the target UE if this is known. In both the cases, the combined MME/SGSN may set "Optimized-LCS-Proc-Performed" bit within PLA-Flags, if it has performed optimized LCS procedure.
This procedure is mapped to the commands Provide-Location-Request/Answer in the Diameter application specified in clauses 7.3.1 and 7.3.2.
Table 6.2.2-1: Provide Subscriber Location Request
|
Information element name |
Mapping to Diameter AVP |
Cat. |
Description |
|
Location Type |
SLg-Location-Type |
M |
This Information Element shall contain the type of location measurement requested, such as current location, initial location, last known location, etc. (see 3GPP TS 22.071 [15]). |
|
IMSI |
User-Name |
C |
If present, this Information Element shall contain the IMSI of the user whose UE is to be positioned (see Note 1). |
|
MSISDN |
MSISDN |
C |
If present, this Information Element shall contain the MSISDN of the user whose UE is to be positioned (see Note 1). |
|
IMEI |
IMEI |
C |
If present, this Information Element shall contain the IMEI of the UE to be positioned (see Note 1). |
|
Client Name |
LCS-EPS-Client-Name |
M |
This Information Element shall contain the name of the LCS client issuing the positioning request. |
|
Client Type |
LCS-Client-Type |
M |
This Information Element shall contain the type of LCS client (Emergency, Lawful Interception …) issuing the positioning request (see 3GPP TS 23.271 [2] and 3GPP TS 32.299 [10]). |
|
Requestor Name |
LCS-Requestor-Name |
O |
If present, this Information Element contains the identity of the originating entity which has requested the location of the target UE from the LCS Client. |
|
Priority |
LCS-Priority |
O |
If present, this Information Element shall contain the priority of the LCS client issuing the positioning request. |
|
QoS |
LCS-QoS |
O |
If present, this Information Element shall contain the quality of service requested, such as the accuracy of the positioning measurement and the response time of the positioning operation. |
|
Velocity Requested |
Velocity-Requested |
O |
If present, this information element shall contain an indication of whether or not the Velocity of the target UE is requested. |
|
Supported GAD Shapes |
LCS-Supported-GAD-Shapes |
O |
If present, this Information Element shall contain the list of supported GAD shapes by the LCS client. |
|
Service Type ID |
LCS-Service-Type-ID |
O |
If present, this Information Element shall contain the service type associated for the particular positioning request (the meaning of the different service types is defined in 3GPP TS 22.071 [15]). |
|
Codeword |
LCS-Codeword |
O |
If present, this Information Element shall contain the Codeword to be used between an LCS client and a target UE in order to check and accept or reject the positioning request. |
|
APN |
Service-Selection |
C |
If present, this Information Element shall contain the Access Point Name (APN) Network Identifier of the LCS client, as used by the target UE. It shall only be included in session-related location requests. |
|
Session-Related Privacy Check |
LCS-Privacy-Check-Session |
O |
If present, this Information Element shall contain an indication of how the positioning operation should proceed in the relation to the checking of the session-related privacy settings of the user. |
|
Non-Session-Related Privacy Check |
LCS-Privacy-Check-Non-Session |
O |
If present, this Information Element shall contain an indication of how the positioning operation should proceed in the relation to the checking of the non-session-related privacy settings of the user. |
|
Deferred Location Type |
Deferred-Location-Type |
O |
If present, this Information Element shall contain the type of the event until when the location estimation is deferred. Applicable event types are: UE available, UE entering or leaving or being in a pre-defined geographical area, periodic location, UE moving by more than a minimum linear distance (NOTE). This Information Element is applicable only for the deferred MT-LR procedure. NOTE: this value is only applicable to a deferred EPC-MT-LR. |
|
LCS-Reference Number |
LCS-Reference-Number |
O |
If present, this Information Element shall contain the reference number identifying the deferred location request or identifying the request for which delayed location reporting for UEs transiently not reachable is supported. This Information Element is applicable only when: – the deferred MT-LR procedure is initiated; or – an EPC-MT-LR or PS-MT-LR procedure is initiated and the message includes the indication that delayed location reporting for UEs transiently not reachable is supported. |
|
Area Event Info |
Area-Event-Info |
O |
If present, this Information Element shall contain area definition, type of area event, occurrence info and minimum interval time. For a deferred EPC-MT-LR, this Information Element may also contain the duration of event reporting, the maximum time interval between event reports, the maximum event sampling interval, and whether location estimates shall be included in event reports. This Information Element is applicable only when the deferred MT-LR is initiated for the area event (UE entering or leaving or being in a pre-defined geographical area). |
|
H-GMLC Address |
GMLC-Address |
O |
If present, this Information Element shall contain the address identifying the H-GMLC which initiated the deferred MT-LR procedure. This Information Element is applicable only when the deferred MT-LR procedure is performed. |
|
PLR Flags |
PLR-Flags |
O |
This Information Element contains a bit mask. See 7.4.52 for the meaning of the bits. |
|
Periodic LDR Information |
Periodic-LDR-Information |
O |
If present, this Information Element shall contain reporting amount and reporting interval of deferred periodic location. This Information Element is applicable only when the deferred MT-LR procedure is initiated for the periodic location event. |
|
Reporting PLMN List |
Reporting-PLMN-List |
O |
If present, this Information Element shall contain a list of PLMNs in which the subsequent location estimates must be obtained, or the subsequent triggered or periodic events must be reported, by the UE as part of a periodic MO-LR TTTP or periodic MT-LR procedure. |
|
Supported Features (See 3GPP TS 29.229 [17]) |
Supported-Features |
O |
If present, this information element shall contain the list of features supported by the origin host. |
|
Motion Event Info |
Motion-Event-Info |
O |
If present, this Information Element shall contain information for motion event reporting. This information includes the minimum linear distance for a motion event report, the duration of event reporting, the minimum and maximum time intervals between event reports, the maximum event sampling interval, whether location estimates shall be included in event reports, and whether only one location report is required or more than one. This Information Element is applicable only for a deferred EPC-MT-LR. |
|
NOTE 1: At least one of these IEs shall be present in the message. |
|||
Table 6.2.2-2: Provide Subscriber Location Answer
|
Information element name |
Mapping to Diameter AVP |
Cat. |
Description |
|
Result |
Result-Code / Experimental-Result |
M |
This Information Element shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]). The Experimental-Result AVP shall be used for ELP errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. |
|
Location Estimate |
Location-Estimate |
O |
If present, this Information Element shall contain an estimate of the location of the UE in universal coordinates and the accuracy of the estimate. This Information Element shall not be included if the PLA Flags Information Element is present and if the bit corresponding to the "UE-Transiently-Not-Reachable-Indicator" is set. |
|
Accuracy Fulfilment Indicator |
Accuracy-Fulfilment-Indicator |
O |
If present, this Information Element shall contain an indication of whether the requested accuracy (as indicated in the LCS-QoS IE in the request message) was fulfilled or not. |
|
Age of Location Estimate |
Age-of-Location-Estimate |
O |
If present, this Information Element shall contain an indication of how long ago the location estimate was obtained. |
|
Velocity Estimate |
Velocity-Estimate |
O |
If present, this Information Element shall contain an estimate of the velocity of the target UE, composed by horizontal speed, vertical speed, and their respective uncertainty (see 3GPP TS 23.032 [3]). |
|
EUTRAN Positioning Data |
EUTRAN-Positioning-Data |
O |
If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. The internal structure and encoding is defined in 3GPP TS 29.171 [7]. This Information Element is applicable only when the UE is attached to E-UTRAN access and when the message is sent by the MME or the combined MME/SGSN. |
|
ECGI |
ECGI |
O |
If present, this Information Element shall contain the current cell location of the target UE as delivered by the eNB to the MME. The E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell. This Information Element is applicable only when the UE is attached to E-UTRAN access and when the message is sent by the MME or combined MME/SGSN. |
|
GERAN Positioning Info |
GERAN-Positioning-Info |
O |
If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. This Information Element is applicable only when the UE is attached to GERAN access and when the message is sent by the SGSN or combined MME/SGSN. |
|
CGI |
Cell-Global-Identity |
O |
If present, this Information Element shall contain the current cell location of the target UE. The Cell Global Identifier (CGI) is used to globally identify a cell. This Information Element is applicable only when the UE is attached to GERAN access and when the message is sent by the SGSN or combined MME/SGSN. |
|
UTRAN Positioning Info |
UTRAN-Positioning-Info |
O |
If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. This Information Element is applicable only when the UE is attached to UTRAN access and when the message is sent by the SGSN or combined MME/SGSN. |
|
SAI |
Service-Area-Identity |
O |
If present, this Information Element shall contain the current service area of the target UE. The Service Area Identifier (SAI) is used to globally identify a service area. This Information Element is applicable only when the UE is attached to UTRAN access and when the message is sent by the SGSN or combined MME/SGSN. |
|
Target Serving Node Identity |
Serving-Node |
O |
If present, this information element shall contain the address of the target side serving node for handover of an IMS Emergency Call. |
|
PLA Flags |
PLA-Flags |
O |
This Information Element contains a bit mask. See 7.4.53 for the meaning of the bits. If this Information Element is present and if it the bit corresponding to the "Deferred-MT-LR-Response-Indicator" is set, the "Location-Estimate" Information Element is ignored in this message. |
|
E-SMLC provided Cell Info |
ESMLC-Cell-Info |
O |
If present, this Information Element shall contain the current cell information of the target UE as known by E-SMLC. |
|
Civic Address |
Civic-Address |
O |
If present, this Information Element contains a location estimate for the target UE expressed as a Civic address. |
|
Barometric Pressure |
Barometric-Pressure |
O |
If present, this Information Element contains the barometric pressure measurement as reported by the target UE. |
|
Supported Features (See 3GPP TS 29.229 [17]) |
Supported-Features |
O |
If present, this information element shall contain the list of features supported by the origin host. |
6.2.3 Unsuccessful Operation
On receipt of a PROVIDE SUBSCRIBER LOCATION RESPONSE with a Result-Code or Experimental-Result AVP indicating failure the GMLC considers the positioning request as failed.
If the GMLC receives "Optimized-LCS-Proc-Performed" bit within PLA-Flags set, it shall assume that the combined MME/SGSN has either performed EPC-MT-LR or PS-MT-LR procedure to retrieve the location of the target UE. And hence, it need not send another PROVIDE SUBSCRIBER LOCATION REQUEST message to the combined MME/SGSN.
6.3 Subscriber Location Report
6.3.1 General
The Subscriber Location Report operation is used by an MME or SGSN to provide the location of a target UE to a GMLC, when a request for location has been implicitly issued or when a Delayed Location Reporting is triggered after receipt of a request for location for a UE transiently not reachable.
6.3.2 Successful Operation
Figure 6.3.2-1: Subscriber Location Report procedure. Successful operation.
The MME or SGSN initiates the procedure by sending a SUBSCRIBER LOCATION REPORT message to the GMLC. The message may carry the identity of the UE, the location estimate and its age, and the event causing the location report.
Upon reception of SUBSCRIBER LOCATION REPORT message, the GMLC shall return a SUBSCRIBER LOCATION REPORT ACK to the MME or SGSN and process the location report accordingly, e.g. transfer of the location estimate to an external LCS Client according to procedure described in 3GPP TS 23.271 [2].
If the Location-Event indicates a DEFERRED_LR_RESPONSE then the Location-Estimate shall not be sent if the LCS-Supported-GAD-Shapes had been received in Provide Subscriber Location request and the shape encoded in Location-Estimate was not marked as supported in LCS-Supported-GAD-Shapes. In such a case Termination-Cause in Deferred-MT-LR-Data shall be present with value SHAPE_OF_LOCATION_ESTIMATE_NOT_SUPPORTED.
This procedure is mapped to the commands Location-Report-Request/Answer in the Diameter application specified in clauses 7.3.3 and 7.3.4.
Table 6.3.2-1: Subscriber Location Report
|
Information element name |
Mapping to Diameter AVP |
Cat. |
Description |
|
Location Event |
Location-Event |
M |
This Information Element shall contain the type of event that caused the location procedure to be initiated. |
|
IMSI |
User-Name |
C |
If present, this Information Element shall contain the IMSI of the user whose UE is to be positioned (see Note 1). |
|
MSISDN |
MSISDN |
C |
If present, this Information Element shall contain the MSISDN of the user whose UE is to be positioned (see Note 1). |
|
IMEI |
IMEI |
C |
If present, this Information Element shall contain the IMEI of the UE to be positioned (see Note 1). |
|
Client Name |
LCS-EPS-Client-Name |
O |
If present, this Information Element shall contain the name of the LCS client where the result of the positioning operation should be sent. |
|
Location Estimate |
Location-Estimate |
O |
If present, this Information Element shall contain an estimate of the location of the UE in universal coordinates and the accuracy of the estimate. |
|
Accuracy Fulfilment Indicator |
Accuracy-Fulfilment-Indicator |
O |
If present, this Information Element shall contain an indication of whether the requested accuracy was fulfilled or not. |
|
Age of Location Estimate |
Age-of-Location-Estimate |
O |
If present, this Information Element shall contain an indication of how long ago the location estimate was obtained. |
|
Velocity Estimate |
Velocity-Estimate |
O |
If present, this Information Element shall contain an estimate of the velocity of the UE, composed by horizontal speed, vertical speed, and their respective uncertainty (see 3GPP TS 23.032 [3]). |
|
EUTRAN Positioning Data |
EUTRAN-Positioning-Data |
O |
If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. The internal structure and encoding is defined in 3GPP TS 29.171 [7]. This Information Element is applicable only when the UE is attached to E-UTRAN access and when the message is sent by the MME or the MME part of the combined MME/SGSN. |
|
ECGI |
ECGI |
O |
If present, this Information Element shall contain the current cell location of the target UE as delivered by the eNB to the MME. The E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell. This Information Element is applicable only when the UE is attached to E-UTRAN access and when the message is sent by the MME or the MME part of the combined MME/SGSN. |
|
GERAN Positioning Info |
GERAN-Positioning-Info |
O |
If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. This Information Element is applicable only when the UE is attached to GERAN access and when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. |
|
CGI |
Cell-Global-Identity |
O |
If present, this Information Element shall contain the current cell location of the target UE. The Cell Global Identifier (CGI) is used to globally identify a cell. This Information Element is applicable only when the UE is attached to GERAN access and when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. |
|
UTRAN Positioning Info |
UTRAN-Positioning-Info |
O |
If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. This Information Element is applicable only when the UE is attached to UTRAN access and when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. |
|
SAI |
Service-Area-Identity |
O |
If present, this Information Element shall contain the current service area of the target UE. The Service Area Identifier (SAI) is used to globally identify a service area. This Information Element is applicable only when the UE is attached to UTRAN access and when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. |
|
Service Type ID |
LCS-Service-Type-ID |
O |
If present, this Information Element shall contain the service type associated for the particular positioning report identifying the service at the receiving LCS Client (the meaning of the different service types is defined in 3GPP TS 22.071 [15]). |
|
Pseudonym Indicator |
Pseudonym-Indicator |
O |
If present, this Information Element shall contain an indication of whether or not a pseudonym must be allocated by the network and transferred to the LCS client as the identity of the UE. |
|
Supported Features (See 3GPP TS 29.229 [17]) |
Supported-Features |
O |
If present, this information element shall contain the list of features supported by the origin host. |
|
LCS QoS Class |
LCS-QoS-Class |
O |
If present, this Information Element shall contain the LCS-QoS-Class requested by the target UE. |
|
Target Serving Node Identity |
Serving-Node |
O |
If present, this information element shall contain the address of the target side serving node for handover of an IMS Emergency Call. |
|
LRR Flags (See 7.4.35) |
LRR-Flags |
C |
This Information Element contains a bit mask. See 7.4.35 for the meaning of the bits. It shall be present when the message is sent over Lgd interface. |
|
LCS-Reference Number |
LCS-Reference-Number |
O |
If present, this Information Element shall contain the reference number identifying the deferred location request or identifying the request for which Delayed Location Reporting is triggered. This is same as the reference number included in the Provide Subscriber Location request for the deferred MT-LR procedure or for the EPC-MT-LR or PS-MT-LR with the Delayed-Location-Reporting-Support indication, or the reference number included in the Subscriber Location Report Ack for periodic MO-LR TTTP procedure. This Information Element shall be included if the Location-Event is set to: – "DEFERRED_MT_LR_RESPONSE"; or – "DELAYED_LOCATION_REPORTING". |
|
Deferred MT-LR Data |
Deferred-MT-LR-Data |
O |
If present, this Information Element is used to report the deferred location event type, the location information and optionally a reason why the serving node or UE aborted monitoring the event to the GMLC. The deferred location event type may correspond to the location event type requested in the Provide Subscriber Location Request. For a deferred EPC-MT-LR, the deferred location event type may also indicate LDR activation in the UE or expiration of the maximum time interval between event reports. This Information Element shall be included when the Location-Event is set to "DEFERRED_MT_LR_RESPONSE". |
|
H-GMLC Address |
GMLC-Address |
O |
If present, this Information Element shall contain the address identifying the H-GMLC which should receive location estimates. This is the same as the H-GMLC address included in the Provide Subscriber Location request for the deferred MT-LR procedure or the H-GMLC address included in the Subscriber Location Report Ack for periodic MO-LR TTTP procedure. |
|
Sequence Number |
Reporting-Amount |
O |
If present, this parameter contains the number of the periodic location reports completed. The sequence number would be set to 1 in the first location report and increment by 1 for each new report. When the number reaches the reporting amount value, the H-GMLC (for a periodic MT-LR or a periodic MO-LR TTTP) will know the procedure is complete. This Information Element is applicable only when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. |
|
Periodic LDR Information |
Periodic-LDR-Information |
O |
If present, this Information Element shall contain the UE requested reporting amount and reporting interval of deferred periodic location reporting. This Information Element is applicable only when the periodic MO-LR TTTP procedure is initiated by the UE and when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. |
|
E-SMLC provided Cell Info |
ESMLC-Cell-Info |
O |
If present, this Information Element shall contain the current cell information of the target UE as known by E-SMLC. |
|
1xRTT Reference Cell ID |
1xRTT-RCID |
O |
If present, this Information Element shall contain the 1xRTT Reference Cell ID uniquely identifying of the target cell location for handover of an IMS ermergency call. This Information Element is applicable only when the UE is making handover toa cdma2000 1xRTT access and when the message is sent by the MME or the MME part of the combined MME/SGSN. |
|
Delayed Location Reporting Data |
Delayed-Location-Reporting-Data |
O |
If present, this Information Element is used to report to the GMLC the reason why the serving node ended an earlier EPC-MT-LR or PS-MT-LR with the Delayed-Location-Reporting-Support indication received for a UE transiently not reachable. This Information Element shall be included when the Location-Event is set to "DELAYED_LOCATION_REPORTING". |
|
Civic Address |
Civic-Address |
O |
If present, this Information Element contains a location estimate for the target UE expressed as a Civic address. |
|
Barometric Pressure |
Barometric-Pressure |
O |
If present, this Information Element contains the barometric pressure measurement as reported by the target UE. |
|
NOTE 1: At least one of these IEs shall be present in the message. |
|||
Table 6.3.2-2: Subscriber Location Report Ack
|
Information element name |
Mapping to Diameter AVP |
Cat. |
Description |
|
Result |
Result-Code / Experimental-Result |
M |
This Information Element shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]). The Experimental-Result AVP shall be used for ELP errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. |
|
H-GMLC Address |
GMLC-Address |
O |
If present, this Information Element shall contain the address identifying the H-GMLC which should receive location estimates as part of periodic MO-LR TTTP procedure. This Information Element is applicable only when the message is sent towards the SGSN or the SGSN part of the combined MME/SGSN. |
|
LRA Flags |
LRA-Flags |
O |
This Information Element contains a bit mask. See 7.4.56 for the meaning of the bits. |
|
Reporting PLMN List |
Reporting-PLMN-List |
O |
If present, this Information Element shall contain a list of PLMNs in which the subsequent location estimates must be obtained as part of periodic MO-LR TTTP procedure. This Information Element is applicable only when the message is sent towards the SGSN or the SGSN part of the combined MME/SGSN. |
|
LCS Reference Number |
LCS-Reference-Number |
O |
If present, this Information Element shall contain the reference number identifying the deferred location request or identifying the request for which Delayed Location Reporting was triggered. This Information Element is applicable only when the message is sent towards the SGSN or the SGSN part of the combined MME/SGSN. |
|
Supported Features (See 3GPP TS 29.229 [17]) |
Supported-Features |
O |
If present, this information element shall contain the list of features supported by the origin host. |
6.3.3 Unsuccessful Operation
If for some reason the GMLC does not accept the SUBSCRIBER LOCATION REPORT APDU, the GMLC shall send a SUBSCRIBER LOCATION REPORT ACK message with a Result-Code or Experimental-Result AVP indicating failure.