ETSI TS 129 172 V9.1.0 (2010-06)
Technical Specification
Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS);
LTE;
Location Services (LCS);
Evolved Packet Core (EPC) LCS Protocol (ELP)
between the Gateway Mobile Location Centre (GMLC)
and the Mobile Management Entity (MME);
SLg interface
(3GPP TS 29.172 version 9.1.0 Release 9)
3GPP TS 29.172 version 9.1.0 Release 9
1
ETSI TS 129 172 V9.1.0 (2010-06)
Reference
RTS/TSGC-0429172v910
Keywords
GSM, LTE, UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2010.
All rights reserved.
TM
TM
TM
TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
2
ETSI TS 129 172 V9.1.0 (2010-06)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
3
ETSI TS 129 172 V9.1.0 (2010-06)
Contents
Intellectual Property Rights ................................................................................................................................2
Foreword.............................................................................................................................................................2
Foreword.............................................................................................................................................................5
1
Scope ........................................................................................................................................................6
2
References ................................................................................................................................................6
3
Definitions, symbols and abbreviations ...................................................................................................7
3.1
3.2
3.3
4
4.1
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
6
6.1
6.2
6.2.1
6.2.2
6.2.3
6.3
6.3.1
6.3.2
6.3.3
6.4
6.4.1
6.4.2
7
7.1
7.2
7.3
7.3.1
7.3.2
7.3.3
7.3.4
7.4
7.4.1
7.4.2
7.4.3
7.4.4
7.4.5
7.4.6
7.4.7
7.4.8
7.4.9
Definitions .......................................................................................................................................................... 7
Symbols .............................................................................................................................................................. 7
Abbreviations ..................................................................................................................................................... 7
Functional Overview ................................................................................................................................7
General ............................................................................................................................................................... 7
ELP Message Transport ...........................................................................................................................8
General ............................................................................................................................................................... 8
Use of Diameter base protocol ........................................................................................................................... 8
Securing Diameter Messages ............................................................................................................................. 8
Accounting functionality .................................................................................................................................... 9
Use of sessions ................................................................................................................................................... 9
Transport protocol .............................................................................................................................................. 9
Routing considerations ....................................................................................................................................... 9
Advertising Application Support ........................................................................................................................ 9
ELP Procedures ......................................................................................................................................10
General ............................................................................................................................................................. 10
Provide Subscriber Location ............................................................................................................................ 10
General........................................................................................................................................................ 10
Successful Operation .................................................................................................................................. 10
Unsuccessful Operation .............................................................................................................................. 12
Subscriber Location Report .............................................................................................................................. 12
General........................................................................................................................................................ 12
Successful Operation .................................................................................................................................. 13
Unsuccessful Operation .............................................................................................................................. 15
Error Handling.................................................................................................................................................. 15
Protocol Errors ............................................................................................................................................ 15
Restoration and Recovery ........................................................................................................................... 15
ELP Messages and Message Formats ....................................................................................................15
General ............................................................................................................................................................. 15
Message Formats .............................................................................................................................................. 15
ELP Messages .................................................................................................................................................. 16
Provide-Location-Request (PLR) Command .............................................................................................. 16
Provide-Location-Answer (PLA) Command .............................................................................................. 16
Location-Report-Request (LRR) Command ............................................................................................... 17
Location-Report-Answer (LRA) Command ............................................................................................... 17
Information Elements ....................................................................................................................................... 18
General........................................................................................................................................................ 18
Location-Type............................................................................................................................................. 19
LCS-EPS-Client-Name ............................................................................................................................... 19
LCS-Requestor-Name ................................................................................................................................. 19
LCS-Priority ............................................................................................................................................... 19
LCS-QoS .................................................................................................................................................... 19
Horizontal-Accuracy ................................................................................................................................... 19
Vertical-Accuracy ....................................................................................................................................... 20
Vertical-Requested...................................................................................................................................... 20
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
7.4.10
7.4.11
7.4.12
7.4.13
7.4.14
7.4.15
7.4.16
7.4.17
7.4.18
7.4.19
7.4.20
7.4.21
7.4.22
7.4.23
7.4.24
7.4.25
7.4.26
7.4.27
7.4.28
7.5
7.5.1
7.5.2
7.5.3
7.5.3.1
7.5.3.2
7.5.4
7.5.4.1
7.5.4.2
7.5.4.3
7.5.4.4
7.5.4.5
7.5.4.6
4
ETSI TS 129 172 V9.1.0 (2010-06)
Velocity-Requested ..................................................................................................................................... 20
Response-Time ........................................................................................................................................... 20
Supported-GAD-Shapes ............................................................................................................................. 20
LCS-Codeword ........................................................................................................................................... 20
LCS-Privacy-Check .................................................................................................................................... 21
Accuracy-Fulfilment-Indicator ................................................................................................................... 21
Age-Of-Location-Estimate ......................................................................................................................... 21
Velocity-Estimate ....................................................................................................................................... 21
EUTRAN-Positioning-Data ........................................................................................................................ 21
ECGI ........................................................................................................................................................... 21
Location-Event ........................................................................................................................................... 21
Pseudonym-Indicator .................................................................................................................................. 21
LCS-Service-Type-ID ................................................................................................................................. 22
LCS-Privacy-Check-Non-Session .............................................................................................................. 22
LCS-Privacy-Check-Session....................................................................................................................... 22
Feature-List-ID ........................................................................................................................................... 22
Feature-List ................................................................................................................................................. 22
LCS-QoS-Class........................................................................................................................................... 22
Serving-Node .............................................................................................................................................. 22
Result-Code AVP and Experimental-Result AVP Values ............................................................................... 23
General........................................................................................................................................................ 23
Success........................................................................................................................................................ 23
Permanent Failures ..................................................................................................................................... 23
DIAMETER_ERROR_USER_UNKNOWN (5001) ............................................................................ 23
DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_NETWORK (5490) ............................. 23
Transient Failures ....................................................................................................................................... 23
DIAMETER_ERROR_UNREACHABLE_USER (4221).................................................................... 23
DIAMETER_ERROR_SUSPENDED_USER (4221) .......................................................................... 23
DIAMETER_ERROR_DETACHED_USER (4223)............................................................................ 23
DIAMETER_ERROR_POSITIONING_DENIED (4224) ................................................................... 23
DIAMETER_ERROR_POSITIONING_FAILED (4225) .................................................................... 23
DIAMETER_ERROR_UNKNOWN_UNREACHABLE LCS_CLIENT (4226) ................................ 24
Annex A (informative):
Change history ...............................................................................................25
History ..............................................................................................................................................................26
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
5
ETSI TS 129 172 V9.1.0 (2010-06)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
1
6
ETSI TS 129 172 V9.1.0 (2010-06)
Scope
The present document specifies the procedures and information coding for the EPC LCS Protocol (ELP) that is needed
to support the location services in E-UTRAN. The ELP message set is applicable to the SLg interface between the
MME and the GMLC. ELP is developed in accordance to the general principles stated in 3GPP TS 23.271 [3].
2
References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
-
References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
-
For a specific reference, subsequent revisions do not apply.
-
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1]
3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[3]
3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[4]
IETF RFC 3588: "Diameter Base Protocol".
[5]
IETF RFC 2234: "Augmented BNF for syntax specifications".
[6]
3GPP TS 23.003: "Numbering, addressing and identification".
[7]
3GPP TS 29.171: "LCS Application Protocol (LCS-AP) between the MME and E-SMLC".
[8]
3GPP TS 29.274: "Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control
plane (GTPv2-C)".
[90]
IETF Draft draft-ietf-dime-rfc3588bis-18: "Diameter Base Protocol", work in progress.
[10]
3GPP TS 32.299: "Charging management; Diameter charging applications".
[11]
3GPP TS 29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on
Diameter Protocol".
[12]
3GPP TS 29.329: "Sh Interface based on the Diameter protocol".
[13]
3GPP TS 33.210: "3G Security; Network Domain Security; IP Network Layer Security".
[14]
IETF RFC 4960: "Stream Control Transmission Protocol".
[15]
3GPP TS 22.071: "Location Services (LCS); Service description".
[16]
IETF Draft draft-ietf-dime-mip6-split-17: "Diameter Mobile IPv6: Support for Home Agent to
Diameter Server Interaction", work in progress.
[17]
3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol; protocol details".
[18]
3GPP TS 29.173: "Location Services; Diameter-based SLh interface for Control Plane LCS".
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
7
ETSI TS 129 172 V9.1.0 (2010-06)
3
Definitions, symbols and abbreviations
3.1
Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
EPC-MO-LR: EPC Mobile Originating Location Request
EPC-MT-LR: EPC Mobile Terminating Location Request
EPC-NI-LR: EPC Network Induced Location Request
LCS: LoCation Services
LCS Client: software and/or hardware entity that interacts with a LCS Server (in this case, the GMLC) for the purpose
of obtaining location information for one or more Mobile Stations. LCS Clients subscribe to LCS in order to obtain
location information. LCS Clients may or may not interact with human users. The LCS Client is responsible for
formatting and presenting data and managing the user interface (dialogue). The LCS Client may reside in the Mobile
Station (UE).
LCS QoS: The QoS class determines the degree of adherence to the quality of service information as required by the
source of a location request.
Target: UE being positioned
3.2
Symbols
For the purposes of the present document, the following symbols apply:
SLg
3.3
Interface between GMLC and MME
Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
GMLC
EPC
IMEI
IMS
IMSI
MME
UE
Gateway Mobile Location Centre
Enhanced Packet Core
International Mobile Equipment Identity
IP Multimedia Subsystem
International Mobile Subscriber Identity
Mobility Management Entity
User Equipment, as defined in 3GPP TS 23.032 [3]
4
Functional Overview
4.1
General
This document defines the EPC LCS Protocol (ELP) used on the SLg interface between the GMLC and the MME in the
Evolved Packet Core (EPC).
The location of the SLg interface within the LCS logical architecture is shown in Figure 4.1-1.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
8
ETSI TS 129 172 V9.1.0 (2010-06)
HSS
UE
eNB
GMLC
MME
LRF
SLg
E-SMLC
Serving
Gateway
PDN
Gateway
IMS
PSAP
Figure 4.1-1 SLg interface in the LCS Architecture
The high level functions of the ELP protocol are described in 3GPP TS 23.271 [2].
The main functions of the protocol are:
- To allow the GMLC to request position estimates for a particular target UE from the MME in order to support
the EPC-MT-LR positioning procedures. This is achieved using the Provide Subscriber Location message;
-
To allow the MME to return a position estimate or an error report to the GMLC in response to a Provide
Subscriber Location request as part of an EPC-MT-LR positioning procedure;
-
To allow the MME to forward an unsolicited position estimate to the GMLC as part of the EPC-MO-LR or EPCNI-LR procedures;
-
To allow the GMLC to acknowledge receipt of an unsolicited position estimate as part of the EPC-MO-LR or
EPC-NI-LR procedures;
-
To support the procedures for handover of an IMS emergency call with EPS/GPRS access.
5
ELP Message Transport
5.1
General
The ELP protocol is defined as a Vendor Specific diameter application (SLg application). It reuses the basic
mechanisms defined by the diameter base protocol, and it defines a number of additional commands and AVPs to
implement the SLg specific procedures.
5.2
Use of Diameter base protocol
The Diameter Base Protocol as specified in IETF RFC 3588 [4] shall apply except as modified by the defined support
of the methods and the defined support of the commands and AVPs, result and error codes as described in this
specification. Unless otherwise specified, the procedures (including error handling and unrecognised information
handling) shall be used unmodified.
5.3
Securing Diameter Messages
For secure transport of Diameter messages, see 3GPP TS 33.210 [13].
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
5.4
9
ETSI TS 129 172 V9.1.0 (2010-06)
Accounting functionality
Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on
the SLg interface.
5.5
Use of sessions
Between the MME and the GMLC, Diameter sessions shall be implicitly terminated. An implicitly terminated session is
one for which the server does not maintain state information. The client shall not send any re-authorization or session
termination requests to the server.
The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of
implicitly terminated sessions.
The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value
NO_STATE_MAINTAINED (1), as described in IETF RFC 3588 [4]. As a consequence, the server shall not maintain
any state information about this session and the client shall not send any session termination request. Neither the
Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses.
5.6
Transport protocol
Diameter messages over the SLg interface shall make use of SCTP (see IETF RFC 4960 [14]).
5.7
Routing considerations
This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host.
The SLg reference point is defined as "intra-domain", i.e., between the GMLC and the MME inside the same domain
(either visited or home domains). It shall not be used between an H-GMLC and a V-MME.
Destination-Realm AVP shall always be included in all diameter requests, and therefore is declared as mandatory in the
ABNF for all commands.
When a request is initiated by the GMLC, the name of the MME shall be determined by querying the HSS over the SLh
interface, and retrieve the specific MME that is currently serving the UE. Therefore, Destination-Host AVP shall always
be included in the commands originated at the GMLC, and is declared as mandatory in the ABNF.
When a request is initiated by the MME, the name of the GMLC may be either locally configured in the MME, or it is
known from a previously received location procedure initiated at the GMLC. Therefore, this AVP is declared as
mandatory in the ABNF of the commands originated at the MME.
5.8
Advertising Application Support
The MME and GMLC shall advertise support of the Diameter SLg Application by including the value of the application
identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the CapabilitiesExchange-Request and Capabilities-Exchange-Answer commands.
The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the CapabilitiesExchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the VendorSpecific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer
commands.
The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is
not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the
Diameter node as per RFC 3588 [4].
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
6
ELP Procedures
6.1
General
10
ETSI TS 129 172 V9.1.0 (2010-06)
The ELP procedures, between the GMLC and the MME, are used to exchange messages related to location services
over the SLg interface. 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 at
any time. The response contains a location estimate of the target UE and other additional information.
6.2.2
Successful Operation
MME
GMLC
PROVIDE SUBSCRIBER LOCATION REQUEST
PROVIDE SUBSCRIBER LOCATION RESPONSE
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. 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) and an indication of whether the LCS
client has the override capability.
Upon reception of PROVIDE SUBSCRIBER LOCATION REQUEST message, the MME shall perform authentication
privacy verification on the location request. After that, the MME shall retrieve the location information of the target UE
from E-UTRAN according to the procedures described in 3GPP TS 23.271 [2].
The MME returns a PROVIDE SUBSCRIBER LOCATION RESPONSE to the GMLC. The message shall contain the
location estimate, its age and obtained accuracy. If the MME failed to get the current location and the LCS client is
requesting the current or last known location, the MME may return the last known location of the target UE if this is
known.
This procedure is mapped to the commands Provide-Location-Request/Answer in the Diameter application specified in
sections 7.3.1 and 7.3.2.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
11
ETSI TS 129 172 V9.1.0 (2010-06)
Table 6.2.2-1: Provide Subscriber Location Request
Information
element name
Location Type
Mapping to
Diameter AVP
Location-Type
IMSI
User-Name
C
MSISDN
MSISDN
C
IMEI
IMEI
C
Client Name
LCS-EPS-ClientName
LCS-Client-Type
M
Requestor Name
LCS-RequestorName
O
Priority
LCS-Priority
O
QoS
LCS-QoS
O
Velocity Requested
VelocityRequested
LCS-SupportedGAD-Shapes
LCS-ServiceType-ID
O
Codeword
LCS-Codeword
O
APN
Service-Selection
C
Session-Related
Privacy Check
LCS-PrivacyCheck-Session
O
Client Type
Supported GAD
Shapes
Service Type ID
Cat.
Description
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]).
If present, this Information Element shall contain the IMSI of the user
whose UE is to be positioned (see Note 1).
If present, this Information Element shall contain the MSISDN of the
user whose UE is to be positioned (see Note 1).
If present, this Information Element shall contain the IMEI of the UE
to be positioned (see Note 1).
This Information Element shall contain the name of the LCS client
issuing the positioning request.
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]).
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.
If present, this Information Element shall contain the priority of the
LCS client issuing the positioning request.
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.
If present, this information element shall contain an indication of
whether or not the Velocity of the target UE is requested.
If present, this Information Element shall contain the list of supported
GAD shapes by the LCS client.
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]).
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.
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.
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.
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.
If present, this information element shall contain the list of features
supported by the origin host.
M
O
O
Non-SessionLCS-PrivacyO
Related Privacy
Check-NonCheck
Session
Supported Features SupportedO
(See 3GPP TS
Features
29.229 [17])
NOTE 1: At least one of these IEs shall be present in the message.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
12
ETSI TS 129 172 V9.1.0 (2010-06)
Table 6.2.2-2: Provide Subscriber Location Answer
Information
element name
Result
Mapping to
Diameter AVP
Result-Code /
ExperimentalResult
Location Estimate
LocationEstimate
O
Accuracy Fulfilment
Indicator
O
Age of Location
Estimate
Velocity Estimate
AccuracyFulfilmentIndicator
Age-of-LocationEstimate
Velocity-Estimate
EUTRAN
Positioning Data
EUTRANPositioning-Data
O
ECGI
ECGI
O
Target Serving
Node Identity
Supported Features
(See 3GPP TS
29.229 [17])
Serving-Node
O
SupportedFeatures
O
6.2.3
Cat.
M
O
O
Description
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.
The Experimental-Result AVP shall be used for ELP errors. This is a
grouped AVP which shall contain the 3GPP Vendor ID in the VendorId AVP, and the error code in the Experimental-Result-Code AVP.
If present, this Information Element shall contain an estimate of the
location of the UE in universal coordinates and the accuracy of the
estimate.
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.
If present, this Information Element shall contain an indication of how
long ago the location estimate was obtained.
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]).
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
is defined in 3GPP TS 29.171 [7].
If present, this Information Element shall contain the current cell
location of the target UE. The E-UTRAN Cell Global Identifier (ECGI)
is used to globally identify a cell.
If present, this information element shall contain the address of the
target side serving node for handover of an IMS Emergency Call.
If present, this information element shall contain the list of features
supported by the origin host.
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.
6.3
Subscriber Location Report
6.3.1
General
The Subscriber Location Report operation is used by an MME to provide the location of a target UE to a GMLC when a
request for location has been implicitly issued.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
6.3.2
13
ETSI TS 129 172 V9.1.0 (2010-06)
Successful Operation
MME
GMLC
SUBSCRIBER LOCATION REPORT
SUBSCRIBER LOCATION REPORT ACK
Figure 6.3.2-1: Subscriber Location Report procedure. Successful operation.
The MME 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 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].
This procedure is mapped to the commands Location-Report-Request/Answer in the Diameter application specified in
sections 7.3.3 and 7.3.4.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
14
ETSI TS 129 172 V9.1.0 (2010-06)
Table 6.3.2-1: Subscriber Location Report
Information
element name
Location Event
Mapping to
Diameter AVP
Location-Event
IMSI
User-Name
C
MSISDN
MSISDN
C
IMEI
IMEI
C
Client Name
LCS-EPS-ClientName
LocationEstimate
O
O
Age of Location
Estimate
Velocity Estimate
AccuracyFulfilmentIndicator
Age-of-LocationEstimate
Velocity-Estimate
EUTRAN
Positioning Data
EUTRANPositioning-Data
O
ECGI
ECGI
O
Service Type ID
LCS-ServiceType-ID
O
Pseudonym
Indicator
PseudonymIndicator
O
Supported Features
(See 3GPP TS
29.229 [17])
LCS QoS Class
SupportedFeatures
O
LCS-QoS-Class
O
Location Estimate
Accuracy Fulfilment
Indicator
Cat.
Description
M
This Information Element shall contain the type of event that caused
the location procedure to be initiated.
If present, this Information Element shall contain the IMSI of the user
whose UE is to be positioned (see Note 1).
If present, this Information Element shall contain the MSISDN of the
user whose UE is to be positioned (see Note 1).
If present, this Information Element shall contain the IMEI of the UE
to be positioned (see Note 1).
If present, this Information Element shall contain the name of the LCS
client where the result of the positioning operation should be sent.
If present, this Information Element shall contain an estimate of the
location of the UE in universal coordinates and the accuracy of the
estimate.
If present, this Information Element shall contain an indication of
whether the requested accuracy was fulfilled or not.
O
O
O
If present, this Information Element shall contain an indication of how
long ago the location estimate was obtained.
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]).
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
is defined in 3GPP TS 29.171 [7].
If present, this Information Element shall contain the current cell
location of the target UE. The E-UTRAN Cell Global Identifier (ECGI)
is used to globally identify a cell..
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]).
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.
If present, this information element shall contain the list of features
supported by the origin host.
If present, this Information Element shall contain the LCS-QoS-Class
requested by the target UE.
Target Serving
Serving-Node
O
If present, this information element shall contain the address of the
Node Identity
target side serving node for handover of an IMS Emergency Call.
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
Result
Mapping to
Diameter AVP
Result-Code /
ExperimentalResult
Supported Features
(See 3GPP TS
29.229 [17])
SupportedFeatures
Cat.
M
O
Description
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.
The Experimental-Result AVP shall be used for ELP errors. This is a
grouped AVP which shall contain the 3GPP Vendor ID in the VendorId AVP, and the error code in the Experimental-Result-Code AVP.
If present, this information element shall contain the list of features
supported by the origin host.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
6.3.3
15
ETSI TS 129 172 V9.1.0 (2010-06)
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.
6.4
Error Handling
6.4.1
Protocol Errors
6.4.2
Restoration and Recovery
7
ELP Messages and Message Formats
7.1
General
The Diameter Base Protocol as specified in IETF RFC 3588 [4] shall apply except as modified by the defined support
of the methods and the defined support of the commands and AVPs, result and error codes as specified in this
specification. Unless otherwise specified, the procedures (including error handling and unrecognised information
handling) shall be used unmodified.
This clause specifies a Diameter application that allows a Diameter server and a Diameter client:
-
to retrieve the location information of a target UE
-
to report the location information of a target UE
The SLg interface protocol is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The
vendor identifier assigned by IANA to 3GPP (http://www.iana.org/assignments/enterprise-numbers) is 10415.
The Diameter application identifier assigned to the SLg interface application is 16777255 (allocated by IANA).
7.2
Message Formats
This section defines Command-Code values for the SLg interface application.
Every command is defined by means of the ABNF syntax IETF RFC 2234 [5], according to the rules in IETF RFC
3588 [4]. If the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 3588 [4]
shall apply.
For these commands, the Application-ID field shall be set to16777255 (application identifier of the SLg interface
application).
The following Command Codes are defined in this specification:
Table 7.2-1: Command-Code values
Command-Name
Provide-Location-Request
Provide-Location -Answer
Location-Report-Request
Location-Report-Answer
Abbreviation
PLR
PLA
LRR
LRA
Code
Tbd
Tbd
Tbd
Tbd
Section
7.3.1
7.3.2
7.3.3
7.3.4
Editor"s Note: The Command Codes for Provide-Location (Request/Answer) and Location-Report
(Request/Answer) must be allocated by IANA. The same code is used for the Request and Answer
commands.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
16
7.3
ELP Messages
7.3.1
Provide-Location-Request (PLR) Command
ETSI TS 129 172 V9.1.0 (2010-06)
The Provide-Location-Request (PLR) command, indicated by the Command-Code field set to tbd and the "R" bit set in
the Command Flags field, is sent by the GMLC in order to request subscriber location to the MME.
Message Format
< Provide-Location-Request> ::= < Diameter Header: tbd, REQ, PXY, 16777255 >
< Session-Id >
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{Destination-Host }
{ Destination-Realm }
{ Location-Type }
[ User-Name ]
[ MSISDN]
[ IMEI ]
{ LCS-EPS-Client-Name }
{ LCS-Client-Type }
[ LCS-Requestor-Name ]
[ LCS-Priority ]
[ LCS-QoS ]
[ Velocity-Requested ]
[ Supported-GAD-Shapes ]
[ LCS-Service-Type-ID ]
[ LCS-Codeword ]
[ LCS-Privacy-Check-Non-Session ]
[ LCS-Privacy-Check-Session ]
[Service-Selection ]
*[ Supported-Features ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.3.2
Provide-Location-Answer (PLA) Command
The Provide-Location-Answer (PLA) command, indicated by the Command-Code field set to tbd and the "R" bit
cleared in the Command Flags field, is sent by the MME to the GMLC in response to the Provide-Location-Request
command.
Message Format
< Provide-Location-Answer > ::= < Diameter Header: tbd, PXY, 16777255 >
< Session-Id >
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Location-Estimate ]
[ Accuracy-Fulfilment-Indicator ]
[ Age-Of-Location-Estimate]
[ Velocity-Estimate ]
[ EUTRAN-Positioning-Data]
[ ECGI ]
[ Serving-Node ]
*[ Supported-Features ]
*[ AVP ]
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
17
ETSI TS 129 172 V9.1.0 (2010-06)
*[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.3.3
Location-Report-Request (LRR) Command
The Location-Report-Request (LRR) command, indicated by the Command-Code field set to tbd and the "R" bit set in
the Command Flags field, is sent by the MME in order to provide subscriber location data to the GMLC.
Message Format
< Location-Report-Request> ::=
7.3.4
< Diameter Header: tbd, REQ, PXY, 16777255 >
< Session-Id >
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Host }
{ Destination-Realm }
{ Location-Event }
[ LCS-EPS-Client-Name ]
[ User-Name ]
[ MSISDN]
[ IMEI ]
[ Location-Estimate ]
[ Accuracy-Fulfilment-Indicator ]
[ Age-Of-Location-Estimate ]
[ Velocity-Estimate ]
[ EUTRAN-Positioning-Data ]
[ ECGI]
[ LCS-Service-Type-ID ]
[ Pseudonym-Indicator ]
[ LCS-QoS-Class ]
[ Serving-Node ]
*[ Supported-Features ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
Location-Report-Answer (LRA) Command
The Location-Report-Answer (LRA) command, indicated by the Command-Code field set to tbd and the "R" bit cleared
in the Command Flags field, is sent by the GMLC to the MME in response to the Location-Report-Request command.
Message Format
< Location-Report-Answer > ::=
< Diameter Header: tbd, PXY, 16777255>
< Session-Id >
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
*[ Supported-Features ]
*[ AVP ]
*[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
18
7.4
Information Elements
7.4.1
General
ETSI TS 129 172 V9.1.0 (2010-06)
The following table describes the Diameter AVPs defined for the SLg interface protocol, their AVP Code values, types,
possible flag values and whether the AVP may or not be encrypted.
Table 7.4.1-1: Diameter ELP Application AVPs
Attribute Name
AVP
Code
2500
2501
2502
2503
2504
2523
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
Section
defined
7.4.2
7.4.3
7.4.4
7.4.5
7.4.6
7.4.27
7.4.7
7.4.8
7.4.9
7.4.10
7.4.11
7.4.12
7.4.13
7.4.14
7.4.15
7.4.16
7.4.17
7.4.18
7.4.19
7.4.20
7.4.21
7.4.22
7.4.23
Value Type
AVP Flag rules
Must May Should Must
not
not
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
M, V
May
Encrypt
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
Location-Type
Enumerated
LCS-EPS-Client-Name
Grouped
LCS-Requestor-Name
Grouped
LCS-Priority
Unsigned32
LCS-QoS
Grouped
LCS-QoS-Class
Enumerated
Horizontal-Accuracy
Unsigned32
Vertical-Accuracy
Unsigned32
Vertical-Requested
Enumerated
Velocity-Requested
Enumerated
Response-Time
Enumerated
Supported-GAD-Shapes
Unsigned32
LCS-Codeword
UTF8String
LCS-Privacy-Check
Enumerated
Accuracy-Fulfilment-Indicator
Enumerated
Age-Of-Location-Estimate
Unsigned32
Velocity-Estimate
OctetString
EUTRAN-Positioning-Data
OctetString
ECGI
OctetString
Location-Event
Enumerated
Pseudonym-Indicator
Enumerated
LCS-Service-Type-ID
Unsigned32
LCS-Privacy-Check-NonGrouped
Session
LCS-Privacy-Check-Session
2522
7.4.24
Grouped
M, V
No
Note:
The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header
bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header.
For further details, see IETF RFC 3588 [4].
Table 7.4.1-2: Diameter ELP Application reused AVPs
Attribute Name
LCS-Format-Indicator
LCS-Name-String
LCS-Client-Type
LCS-Requestor-Id-String
Location-Estimate
IMEI
MSISDN
Service-Selection
User-Name
Supported-Features
Feature-List-ID
Feature-List
Serving-Node
AVP
Reference
Code
1237 3GPP TS 32.299 [10]
1238 3GPP TS 32.299 [10]
1241 3GPP TS 32.299 [10]
1240 3GPP TS 32.299 [10]
1242 3GPP TS 32.299 [10]
1402 3GPP TS 29.272 [11]
701 3GPP TS 29.329 [12]
493 3GPP TS 29.272 [11],
IETF Draft draft-ietfdime-mip6-split [16]
1
IETF RFC 3588 [4]
628 3GPP TS 29.229 [17]
629 3GPP TS 29.229 [17]
630 3GPP TS 29.229 [17]
2401 3GPP TS 29.173 [18]
ETSI
Value Type
Comment
UTF8String
UTF8String
Enumerated
UTF8String
UTF8String
UTF8String
OctetString
UTF8String It is used to define the APN
UTF8String
Grouped
Unsigned32
Unsigned32
Grouped
It is used to include the user's IMSI
See clause 7.4.25
See clause 7.4.26
See clause 7.4.28
3GPP TS 29.172 version 9.1.0 Release 9
7.4.2
19
ETSI TS 129 172 V9.1.0 (2010-06)
Location-Type
The Location-Type AVP is of type Enumerated. The following values are defined:
CURRENT_LOCATION (0)
CURRENT_OR_LAST_KNOWN_LOCATION (1)
INITIAL_LOCATION (2)
7.4.3
LCS-EPS-Client-Name
The LCS-EPS-Client-Name AVP is of type Grouped.
AVP format:
LCS-EPS-Client-Name ::= <AVP header: 2501 10415>
[ LCS-Name-String ]
[ LCS-Format-Indicator ]
The details of the LCS-Name-String AVP and the LCS-Format-Indicator AVP are described in 3GPP TS 32.299 [10].
7.4.4
LCS-Requestor-Name
The LCS-Requestor-Name AVP is of type Grouped.
AVP format:
LCS-Requestor-Name ::= <AVP header: 2502 10415>
[ LCS-Requestor-Id-String ]
[ LCS-Format-Indicator ]
The details of the LCS-Requestor-Id-String AVP and the LCS-Format-Indicator AVP are described in 3GPP TS 32.299
[10].
7.4.5
LCS-Priority
The LCS-Priority AVP is of type Unsigned32. It indicates the priority of the location request.
7.4.6
LCS-QoS
The LCS-QoS AVP is of type Grouped.
AVP format:
LCS-QoS ::= <AVP header: 2504 10415>
[ LCS-QoS-Class ]
[ Horizontal-Accuracy ]
[ Vertical-Accuracy ]
[ Vertical-Requested ]
[ Response-Time]
7.4.7
Horizontal-Accuracy
The Horizontal-Accuracy AVP is of type Unsigned32. Bits 7-1 corresponds to Uncertainty Code defined in 3GPP TS
23.032 [3]. The horizontal location error should be less than the error indicated by the uncertainty code with 67%
confidence. Bits 8 to 31 shall be ignored.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
7.4.8
20
ETSI TS 129 172 V9.1.0 (2010-06)
Vertical-Accuracy
The Vertical-Accuracy AVP is of type Unsigned32. Bits 7-1 corresponds to Uncertainty Code defined in 3GPP TS
23.032 [3]. The vertical location error should be less than the error indicated by the uncertainty code with 67%
confidence. Bits 8 to 31 shall be ignored.
7.4.9
Vertical-Requested
The Vertical-Requested AVP is of type Enumerated. The following values are defined:
VERTICAL_COORDINATE_IS_NOT REQUESTED (0)
VERTICAL_COORDINATE_IS_REQUESTED (1)
Default value if AVP is not present is: VERTICAL_COORDINATE_IS_NOT_REQUESTED (0).
7.4.10
Velocity-Requested
The Velocity-Requested AVP is of type Enumerated. The following values are defined:
VELOCITY_IS_NOT_REQUESTED (0)
VELOCITY_IS_REQUESTED (1)
Default value if AVP is not present is: VELOCITY_IS_NOT_REQUESTED (0).
7.4.11
Response-Time
The Response-Time AVP is of type Enumerated. The following values are defined:
LOW_DELAY (0)
DELAY_TOLERANT (1)
7.4.12
Supported-GAD-Shapes
The Supported-GAD-Shapes AVP is of type Unsigned32 and it shall contain a bitmask.
A node shall mark in the BIT STRING all Shapes defined in 3GPP TS 23.032 [3] it supports.
Bits 6-0 in shall indicate the supported Shapes defined in 3GPP TS 23.032 [3]. Bits 7 to 31 shall be ignored.
ellipsoidPoint (0)
ellipsoidPointWithUncertaintyCircle (1)
ellipsoidPointWithUncertaintyEllipse (2)
polygon (3)
ellipsoidPointWithAltitude (4)
ellipsoidPointWithAltitudeAndUncertaintyElipsoid (5)
ellipsoidArc (6)
7.4.13
LCS-Codeword
The LCS-Codeword AVP is of type UTF8String. It indicates the potential codeword string to send in a notification
message to the UE.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
7.4.14
21
ETSI TS 129 172 V9.1.0 (2010-06)
LCS-Privacy-Check
The LCS-Privacy-Check AVP is of type Enumerated. The following values are defined:
ALLOWED_WITHOUT_NOTIFICATION (0)
ALLOWED_WITH_NOTIFICATION (1)
ALLOWED_IF_NO_RESPONSE (2)
RESTRICTED_IF_NO_RESPONSE (3)
NOT_ALLOWED (4)
Default value if AVP is not present is: ALLOWED_WITHOUT_NOTIFICATION (0).
7.4.15
Accuracy-Fulfilment-Indicator
The Accuracy-Fulfilment-Indicator AVP is of type Enumerated. The following values are defined:
REQUESTED_ACCURACY_FULFILLED (0)
REQUESTED_ACCURACY_NOT_FULFILLED (1)
7.4.16
Age-Of-Location-Estimate
The Age-Of-Location-Estimate AVP is of type Unsigned32. It indicates how long ago the location estimate was
obtained.
7.4.17
Velocity-Estimate
The Velocity-Estimate AVP is of type OctetString. It is composed of 4 or more octets with an internal structure
according to 3GPP TS 23.032 [3].
7.4.18
EUTRAN-Positioning-Data
The EUTRAN-Positioning-Data AVP is of type OctetString. It is composed of octets with an internal structure
according to 3GPP TS 29.171 [7].
7.4.19
ECGI
The ECGI AVP is of type OctetString. It indicates the E-UTRAN Cell Global Identifier. It is coded according to clause
8.21.5, in 3GPP TS 29.274 [8].
7.4.20
Location-Event
The Location-Event AVP is of type Enumerated. The following values are defined:
EMERGENCY_CALL_ORIGINATION (0)
EMERGENCY_CALL_RELEASE (1)
MO_LR (2)
EMERGENCY_CALL_HANDOVER (3)
7.4.21
Pseudonym-Indicator
The Pseudonym-Indicator AVP is of type Enumerated. It defines if a pseudonym is requested. The following values are
defined:
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
22
ETSI TS 129 172 V9.1.0 (2010-06)
PSEUDONYM_NOT_REQUESTED (0)
PSEUDONYM_REQUESTED (1)
Default value if AVP is not present is: PSEUDONYM_NOT_REQUESTED (0).
7.4.22
LCS-Service-Type-ID
The LCS-Service-Type-ID is of type Unsigned32. It defines the identifier associated to one of the Service Types for
which the LCS client is allowed to locate the particular UE.
7.4.23
LCS-Privacy-Check-Non-Session
The LCS-Privacy-Check-Non-Session AVP is of type Grouped.
AVP format:
LCS-Privacy-Check-Non-Session ::= <AVP header: 2521 10415>
{ LCS-Privacy-Check }
Default value if AVP is not present is that AVP LCS-Privacy-Check take value:
ALLOWED_WITHOUT_NOTIFICATION (0).
7.4.24
LCS-Privacy-Check-Session
The LCS-Privacy-Check-Session AVP is of type Grouped.
AVP format:
LCS-Privacy-Check-Session ::= <AVP header: 2522 10415>
{ LCS-Privacy-Check }
Default value if AVP is not present is that AVP LCS-Privacy-Check take value: NOT_ALLOWED (4).
7.4.25
Feature-List-ID
The syntax of this AVP is defined in 3GPP TS 29.229 [17]. For this release, the Feature-List-ID AVP value shall be set
to 1.
7.4.26
Feature-List
The syntax of this AVP is defined in 3GPP TS 29.229 [17]. A null value indicates that there is no feature used by the
application.
NOTE:
7.4.27
There are no features defined for this release.
LCS-QoS-Class
The LCS-QoS-Class AVP is of the type Enumerated. The following values are defined.
ASSURED (0)
BEST EFFORT (1)
7.4.28
Serving-Node
The Serving-Node AVP is of type Grouped. This AVP shall contain the information about the network node serving the
targeted user.7.5 Result-Code AVP and Experimental-Result AVP Values
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
23
ETSI TS 129 172 V9.1.0 (2010-06)
7.5
Result-Code AVP and Experimental-Result AVP Values
7.5.1
General
This section defines result code values that shall be supported by all Diameter implementations that conform to this
specification.
7.5.2
Success
Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully
completed. The Result-Code AVP values defined in Diameter Base Protocol RFC 3588 [4] shall be applied.
7.5.3
Permanent Failures
Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and
should not be attempted again. The Result-Code AVP values defined in Diameter Base Protocol RFC 3588 [5] shall be
applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result
AVP and the Result-Code AVP shall be absent.
7.5.3.1
DIAMETER_ERROR_USER_UNKNOWN (5001)
This result code shall be sent by the MME to indicate that the user is unknown. This error code is defined in 3GPP TS
29.229 [17]
7.5.3.2
DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_NETWORK (5490)
This result code shall be sent by the MME to indicate that the requesting GMLC's network is not authorized to request
UE location information. This error code is defined in 3GPP TS 29.173 [18]
7.5.4
Transient Failures
Errors that fall within the transient failures category are those used to inform a peer that the request could not be
satisfied at the time that it was received. The request may be able to be satisfied in the future.
7.5.4.1
DIAMETER_ERROR_UNREACHABLE_USER (4221)
This result code shall be sent by the MME to indicate that the user could not be reached in order to perform positioning
procedure.
7.5.4.2
DIAMETER_ERROR_SUSPENDED_USER (4221)
This result code shall be sent by the MME to indicate that the user is suspended in the MME.
7.5.4.3
DIAMETER_ERROR_DETACHED_USER (4223)
This result code shall be sent by the MME to indicate that the user is detached in the MME.
7.5.4.4
DIAMETER_ERROR_POSITIONING_DENIED (4224)
This result code shall be sent by the MME to indicate that the positioning procedure was denied.
7.5.4.5
DIAMETER_ERROR_POSITIONING_FAILED (4225)
This result code shall be sent by the MME to indicate that the positioning procedure failed.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
7.5.4.6
24
ETSI TS 129 172 V9.1.0 (2010-06)
DIAMETER_ERROR_UNKNOWN_UNREACHABLE LCS_CLIENT (4226)
This result code shall be sent by the GMLC to indicate that the LCS Client was not known or could not be reached.
ETSI
3GPP TS 29.172 version 9.1.0 Release 9
25
ETSI TS 129 172 V9.1.0 (2010-06)
Annex A (informative):
Change history
Change history
Date
2010-03
2010-06
TSG #
CT-47
CT-48
TSG Doc. CR
Rev Subject/Comment
CP-100055
3GPP TS presented for approval in CT#47
CP-100286 0001
Velocity-Requested IE
ETSI
Old
2.0.0
9.0.0
New
9.0.0
9.1.0
3GPP TS 29.172 version 9.1.0 Release 9
26
History
Document history
V9.0.0
April 2010
Publication
V9.1.0
June 2010
Publication
ETSI
ETSI TS 129 172 V9.1.0 (2010-06)