ETSI TS 149 031 V13.0.0 (2016-01)
Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE) (3GPP TS 49.031 version 13.0.0 Release 13)
Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE) (3GPP TS 49.031 version 13.0.0 Release 13)
RTS/TSGG-0249031vd00
General Information
Standards Content (Sample)
ETSI TS 1149 031 V13.0.0 (201616-01)
TECHNICAL SPECIFICATIONION
Digital cellular telecocommunications system (Phahase 2+);
Locatcation Services (LCS);
Base Stattation System Application
Part LCSS Extension (BSSAP-LE)
(3GPP TS 49.0.031 version 13.0.0 Release 13 13)
R
GLOBAL SYSTTEME FOR
MOBILE COMMUUNNICATIONS
3GPP TS 49.031 version 13.0.0 Release 13 1 ETSI TS 149 031 V13.0.0 (2016-01)
Reference
RTS/TSGG-0249031vd00
Keywords
GSM
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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI 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 49.031 version 13.0.0 Release 13 2 ETSI TS 149 031 V13.0.0 (2016-01)
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 (https://ipr.etsi.org/).
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.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 3 ETSI TS 149 031 V13.0.0 (2016-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions, abbreviations and symbols . 8
4 Definition of BSSAP-LE . 8
4.1 DTAP-LE Messages . 9
4.2 BSSMAP-LE Messages . 9
5 Procedures applicable to use of BSSAP-LE . 9
5.1 Location Request . 9
5.1.1 Successful Operation . 10
5.1.2 Unsuccessful Operation . 11
5.1.3 Abnormal Conditions . 11
5.1.4 Overload . 11
5.2 Connection Oriented Information Transfer . 12
5.2.1 Successful Operation . 12
5.2.2 Abnormal Conditions . 12
5.2.3 Segmentation . 12
5.3 Connectionless Information Transfer . 13
5.3.1 Successful Operation . 13
5.3.2 Unsuccessful Operation . 13
5.3.3 Abnormal Conditions . 14
5.3.4 Segmentation . 14
5.4 LMU Connection Establishment . 14
5.4.1 LMU Connection Establishment initiated by the SMLC . 14
5.4.1.1 Successful Operation . 14
5.4.1.2 Unsuccessful Operation . 15
5.4.1.3 Abnormal Conditions . 15
5.4.2 LMU Connection Establishment initiated by the MSC . 15
5.4.2.1 Successful Operation . 15
5.4.2.2 Unsuccessful Operation . 15
5.4.2.3 Abnormal Conditions . 15
5.5 (void) . 16
5.6 DTAP-LE Information Transfer . 16
5.6.1 DTAP-LE Information Transfer Initiated by the SMLC . 16
5.6.2 DTAP-LE Information Transfer Initiated by the BSC . 16
5.7 Reset . 16
5.7.1 Normal Operation . 16
5.7.2 Abnormal Conditions . 16
5.8 Perform Location Information . 17
6 Usage of BSSAP-LE and BSSAP on the Lb Interface . 17
6.1 Applicable Message Sets . 17
6.2 MTP Functions . 18
6.3 SCCP Functions . 18
6.3.1 General . 18
6.3.2 Modifications for Connectionless SCCP . 19
6.3.3 Modifications for Connection Oriented SCCP . 19
6.3.4 Contents of the SCCP Data Field . 19
6.3.5 Abnormal Conditions . 20
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 4 ETSI TS 149 031 V13.0.0 (2016-01)
7 (void) . 20
8 Use of BSSAP-LE on the Lp Interface. 20
8.1 Applicable Message Sets . 20
8.2 MTP Functions . 20
8.3 SCCP functions . 21
8.3.1 General . 21
8.3.2 Allowed Exceptions to ITU-T Recommendations Q.711-714 . 21
8.3.3 Allowed Exceptions to ANSI T1.112 . 21
8.3.4 Usage of Connectionless SCCP . 21
8.3.5 Usage of Connection Oriented SCCP . 22
8.3.6 Contents of the SCCP Data Field . 22
9 Message Functional Definitions and Contents . 22
9.1 BSSMAP-LE PERFORM LOCATION REQUEST message . 23
9.1.1 Location Type . 23
9.1.2 Cell Identifier . 23
9.1.3 Classmark Information Type 3 . 23
9.1.4 LCS Client Type . 23
9.1.5 Chosen Channel . 23
9.1.6 LCS Priority . 24
9.1.6a LCS QoS . 24
9.1.7 Requested GPS Assistance Data . 24
9.1.8 BSSLAP APDU . 24
9.1.9 LCS Capability . 24
9.1.10 Packet Measurement Report . 24
9.1.11 Measured Cell Identity List . 24
9.1.12 IMSI . 24
9.1.13 IMEI. 24
9.1.14 GANSS Location Type . 24
9.1.15 Requested GANSS Assistance Data . 24
9.2 BSSMAP-LE PERFORM LOCATION RESPONSE message . 24
9.2.1 Location Estimate . 25
9.2.2 Positioning Data . 25
9.2.3 Deciphering Keys . 25
9.2.4 LCS Cause . 25
9.2.5 Velocity Data . 25
9.2.6 GANSS Positioning Data . 25
9.3 BSSMAP-LE PERFORM LOCATION ABORT message . 25
9.3.1 LCS Cause . 26
9.4 (void) . 26
9.5 (void) . 26
9.6 (void) . 26
9.7 (void) . 26
9.8 BSSMAP-LE CONNECTION ORIENTED INFORMATION message . 26
9.8.1 BSSLAP APDU . 26
9.8.2 Segmentation . 26
9.9 BSSMAP-LE CONNECTIONLESS INFORMATION message . 26
9.9.1 Source Identity . 27
9.9.2 Destination Identity. 27
9.9.3 APDU . 27
9.9.4 Segmentation . 27
9.9.5 Return Error Request . 27
9.9.6 Return Error Cause . 27
9.10 BSSMAP-LE RESET message . 27
9.11 BSSMAP-LE RESET ACKNOWLEDGE message . 28
9.12 BSSMAP-LE PERFORM LOCATION INFORMATION message . 28
9.12.1 Cell Identifier . 28
9.12.2 BSSLAP APDU . 28
10 Message format and information element coding . 28
10.1 Message type . 29
10.2 Information Element Identifiers . 29
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 5 ETSI TS 149 031 V13.0.0 (2016-01)
10.3 APDU . 30
10.4 Cause . 31
10.5 Cell Identifier . 31
10.6 Chosen Cha nne l . 31
10.7 Classmark Information Type 3 . 31
10.8 Deciphering Keys . 32
10.9 Geographic Location . 32
10.10 Requested GPS Assistance Data . 32
10.11 IMSI . 35
10.12 (void) . 35
10.13 LCS Cause . 35
10.14 LCS Client Type . 36
10.15 LCS Priority . 37
10.16 LCS QoS . 37
10.17 (void) . 38
10.18 Location Type . 38
10.19 Network Element Identity . 39
10.20 Positioning Data . 40
10.21 Return Error Request . 41
10.22 Return Error Cause . 41
10.23 (void) . 42
10.24 Segmentation . 42
10.25 (void) . 43
10.26 LCS Capability . 43
10.27 Packet Measurement Report . 43
10.28 Cell Identity List . 43
10.29 IMEI . 43
10.30 Velocity Data . 44
10.31 Requested GANSS Assistance Data . 44
10.32 GANSS Positioning Data . 51
10.33 GANSS Location Type . 51
Annex A (informative): Change history . 52
History . 53
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 6 ETSI TS 149 031 V13.0.0 (2016-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The present document defines the coding of information in an extension of the Base Station System Application Part
(BSSAP) that is needed to support location services on interfaces based on use of BSSAP.
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 49.031 version 13.0.0 Release 13 7 ETSI TS 149 031 V13.0.0 (2016-01)
1 Scope
The present document specifies procedures and information coding that are needed to define and support the BSSAP
LCS Extension (BSSAP-LE). The BSSAP-LE message set is applicable to the following GSM interfaces defined in
3GPP TS 43.059:
- Lb interface (BSC-SMLC).
- Lp interface (SMLC-SMLC).
The present document defines message formats and encoding for BSSAP-LE and the particular subsets of it that are
applicable to each of the above interfaces. The present document also defines the support for BSSAP-LE message
transfer on each of these interfaces using either ITU-T and ANSI versions of SS7 MTP or IETF M3UA/SCTP and
SCCP. Additional requirements for the above interfaces that are applicable to BSSAP-LE are also defined – e.g. usage
of BSSAP (as defined in 3GPP TS 24.008 and 48.008) on the Lb interface.
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".
[1a] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[2] 3GPP TS 43.059: "Functional Stage 2 Description of Location Services in GERAN".
[3] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[3a] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols; Stage 3".
[4] 3GPP TS 44.031: "Location Services (LCS); Mobile Station (MS) – Serving Mobile Location
Center (SMLC); Radio Resource LCS Protocol (RRLP)".
[5] 3GPP TS 44.071: "Location Services (LCS); Mobile radio interface layer 3 Location Services
(LCS) specification".
[6] 3GPP TS 48.006: "Signaling transport mechanism specification for the Base Station Subsystem –
Mobile-services Switching Centre (BSS - MSC) interface".
[7] 3GPP TS 48.008: "Mobile-services Switching Centre – Base Station System (MSC-BSS)
interface; Layer 3 specification".
[8] 3GPP TS 48.031: "Location Services (LCS); Serving Mobile Location Center – Serving Mobile
Location Center (SMLC - SMLC); SMLCPP specification".
[9] 3GPP TS 48.071: "Serving Mobile Location Center – Base Station Subsystem (SMLC-BSS)
interface Layer 3 specification".
[10] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[10a] 3GPP TS 23.003: "Numbering, addressing and identification".
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 8 ETSI TS 149 031 V13.0.0 (2016-01)
[11] ITU-T Recommendation Q.702: "Signalling data link".
[12] ITU-T Recommendation Q.703: "Signalling link".
[13] ITU-T Recommendation Q.704: "Signalling network functions and messages".
[14] ITU-T Recommendation Q.707: "Testing and maintenance".
[15] ITU-T Recommendation Q.711: "Functional description of the signalling connection control part".
[16] ITU-T Recommendation Q.712: "Definition and function of signalling connection control part
messages".
[17] ITU-T Recommendation Q.713: "Signalling connection control part formats and codes".
[18] ITU-T Recommendation Q.714: "Signalling connection control part procedures".
[19] ANSI T1.111 (1996): "Signalling System Number 7 – Message Transfer Part".
[20] ANSI T1.112 (1996): "Signalling System Number 7 (SS7) - Signalling Connection Control Part
Functional Description".
[21] TIA/EIA/IS-J-STD-036 (2000): "Wireless Enhanced Emergency Services".
[22] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving
GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)".
[23] IETF STD 51, RFC 1661(07/1994): "The Point-To-Point Protocol (PPP)".
[24] IETF STD 51, RFC 1662(07/1994): "PPP in HDLC-like Framing".
[25] IETF RFC 2507(02/1999): "IP header compression".
[26] IETF RFC 1990(07/1994): "The PPP Multilink Protocol (MP)".
[27] IETF RFC 2686(09/1999): "The Multi-Class Extension to Multi-Link PPP".
[28] IETF RFC 2509(02/1999): "IP Header Compression over PPP".
[29] 3GPP TS 29.202: "SS7 Signalling Transport in Core Network; Stage 3".
[30] Galileo OS SIS ICD/D.0 "Galileo Open Service, Signal In Space Interface Control
Document/Draft 0".
[31] Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002.
[32] BDS-SIS-ICD-B1I-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control
Document Open Service Signal B1I (Version 1.0)", December 2012.
3 Definitions, abbreviations and symbols
For the purposes of the present document, the definitions, symbols and abbreviations listed in 3GPP TS 21.905 and
3GPP TS 43.059 apply.
4 Definition of BSSAP-LE
BSSAP-LE is an extension to BSSAP that contains messages and parameters specific to the support of LCS. The
following subsets of BSSAP-LE are defined: DTAP-LE, BSSMAP-LE.
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 9 ETSI TS 149 031 V13.0.0 (2016-01)
4.1 DTAP-LE Messages
DTAP-LE messages are transfered between an SMLC and a Type A LMU and comprise the following individual
messages:
- REGISTER;
- FACILITY;
- RELEASE COMPLETE.
The content, encoding and certain procedures asssociated with DTAP-LE messages are defined in 3GPP TS 44.071.
4.2 BSSMAP-LE Messages
BSSMAP-LE messages are transferred between a BSS and SMLC and comprise the following individual messages:
BSSMAP-LE Positioning Messages:
- Perform Location Request;
- Perform Location Response;
- Perform Location Abort;
- Perform Location Information.
BSSMAP-LE Information Messages:
- Connection Oriented Information;
- Connectionless Information.
BSSMAP-LE General Messages:
- Reset;
- Reset Acknowledge.
The content and encoding of BSSMAP-LE messages are defined in the present document.
5 Procedures applicable to use of BSSAP-LE
5.1 Location Request
The Location Request procedure is applicable to the Lb interface. Its purpose is to obtain a location estimate for a target
MS that is already in dedicated mode, in packet transfer mode, in packet idle mode, or in dual transfer mode. It is also
used to provide an MS with LCS assistance data or with a deciphering key for LCS broadcast assistance data. The
initiator of a location request is the BSS. The procedure makes use of SCCP connection oriented signaling on the Lb
interface.
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 10 ETSI TS 149 031 V13.0.0 (2016-01)
5.1.1 Successful Operation
The initiator of the location request sends a BSSMAP-LE Perform Location Request to the SMLC associated with the
current serving cell for the target MS. The message contains the following mandatory (M), conditional (C) and optional
(O) information, where conditional parameters are required if available.
- Location Type (M).
- GANSS Location Type (C)
- Cell Identifier (M).
- Classmark Information Type 3 (C).
- LCS Client Type (C).
- Chosen Channel (C).
- LCS Priority (C).
- LCS QoS (C).
- Requested GPS Assistance Data (C).
- BSSLAP APDU (C).
- LCS Capability (O).
- Packet Measurement Report (O).
- Measured Cell Identity List (O).
- IMSI of target MS (O).
- IMEI of target MS (O).
- Requested GANSS Assistance Data (C).
If requested, the SMLC performs positioning of the target MS using a particular position method or a combination of
more than one positioning method. If neither the Classmark Information Type 3 IE nor the LCS Capability IE is present,
the SMLC shall instigate only network based positioning methods (e.g. TA and U-TDOA but not GPS or E-OTD).
Alternatively, if requested otherwise, the SMLC may provide positioning assistance data to the MS. The SMLC may
invoke the following other BSSAP-LE procedures to perform these procedures:
- connection oriented information transfer;
- connectionless information transfer;
- LMU connection establishment;
- LMU connection release;
- DTAP-LE information transfer.
Additional procedures defined in 3GPP TS 24.008 and 3GPP TS 48.008 may also be performed. If a location estimate
was requested and was subsequently obtained, the SMLC shall return a BSSMAP-LE Perform Location Response to the
initiator of the location request. This message contains the following mandatory, conditional and optional parameters.
- Location Estimate (M).
- Positioning Data (C).
- GANSS Positioning Data (C).
Restrictions on the geographic shape encoded within the Location Estimate parameter may exist for certain LCS client
types. The SMLC shall comply with any restrictions defined in 3GPP specifications and, in a particular country, with
any restrictions defined for a specific LCS client type in relevant national standards. For example, in the US, national
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 11 ETSI TS 149 031 V13.0.0 (2016-01)
interim standard TIA/EIA/IS-J-STD-036 [21] restricts the geographic shape for an emergency services LCS client to
minimally either an "ellipsoid point" or an "ellipsoid point with uncertainty circle and confidence" as defined in
3GPP TS 23.032.
If assistance data was instead requested for an MS and the SMLC was able successfully to transfer this to the MS, the
SMLC shall return a BSSMAP-LE Perform Location Response to the initiator of the location request (serving BSC).
This message shall contain no parameters. The absence of an LCS Cause parameter in this case implies that the transfer
was successful.
Otherwise, if a deciphering key was requested for LCS broadcast assistance data and the SMLC has access to the
appropriate keys, the SMLC shall return a BSSMAP-LE Perform Location Response to the initiator of the location
request. This message contains the following mandatory parameters.
- Deciphering Keys (M).
5.1.2 Unsuccessful Operation
If the SMLC is unable to obtain any of the location information requested or if requested LCS assistance data could not
be transferred or requested deciphering keys for broadcast assistance data could not be returned, the SMLC shall return
a BSSMAP-LE Perform Location Response to the initiator of the Location Request carrying the following parameters:
- LCS Cause (M);
- Positioning Data (O).
- GANSS Positioning Data (O).
If assistance data or deciphering keys for a specific positioning method is not supported in the network or in the location
area, the SMLC shall indicate this with LCS Cause value "Position method failure" accompanied with diagnostic value
"Position Method Not Available in Network" or "Position Method Not Available in Location Area".
5.1.3 Abnormal Conditions
If an ongoing location request is preempted at the initiator by an inter-BSC handover or if the main signaling link to the
target MS is lost or released or if there is a timeout waiting for the positioning response, or if there is an Inter NSE cell
change in the PS Domain (e.g. detected by the BSS at receipt of BSSGP FLUSH-LL PDU) for which the BSS is unable
to maintain the positioning procedure, the initiator shall send a BSSMAP-LE Perform Location Abort to the SMLC
containing the following parameters.
- LCS Cause (M).
On receipt of this message, the SMLC shall stop positioning of the target MS and may release any resources
(e.g. LMUs) previously allocated. If the SMLC has not yet returned a BSSMAP-LE Perform Location Response to the
initiator, it shall return this message containing an LCS Cause indicating an abort and, optionally, positioning data,
GANSS positioning data. The initiator shall then release the SCCP connection. If the SMLC cannot proceed with
positioning due to some protocol violation or error condition (e.g. inter-BSC handover indication received from the
serving BSC), it shall return a BSSMAP-LE Perform Location Response to the initiator containing an LCS cause and,
optionally, positioning data, GANSS positioning data. The initiator need not reply at the BSSAP-LE level to this
message. However, the initiator may return a BSSMAP-LE perform Location Abort which shall not be treated as an
error by the SMLC.
5.1.4 Overload
If the SMLC is in an overload condition, it may reject a BSSMAP-LE Perform Location request by returning a
BSSMAP-LE Perform Location response containing an LCS Cause parameter indicating congestion. The initiator of the
location service request (BSC) may reduce the frequency of future location service requests until rejection due to
overload has ceased. In reducing the frequency of location service requests, a BSC shall reduce lower priority requests,
to zero if necessary, before reducing the frequency of higher priority requests. An SMLC shall similarly reject location
service requests of a lower priority, to zero if necessary, due to overload before rejecting location service requests of a
higher priority. An SMLC in an overload condition may optionally employ the following procedures to alleviate
overload:
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 12 ETSI TS 149 031 V13.0.0 (2016-01)
a) Allow higher priority location service requests to preempt lower priority requests for which location service
procedures are already in progress.
b) Abort lower priority location service requests already in progress.
c) Reduce the supported QoS for lower priority requests for a location estimate – e.g. by reducing accuracy or
increasing response time.
d) Employ MS based positioning methods, where supported by the target MS and SMLC, rather than MS assisted
or network based methods (except TA).
The priority of a location service request shall be defined according to the value in the LCS Priority parameter. If this
parameter is absent in a BSSMAP-LE Perform Location request, the lowest priority shall be assumed.
5.2 Connection Oriented Information Transfer
The Connection Oriented Information transfer procedure is applicable to the Lb interface. It enables two way transfer of
BSSLAP messages between an SMLC and the BSS serving a target MS. The initiator of the procedure can be either the
BSS serving the target MS or the SMLC. The procedure is only valid while a location request procedure for the target
MS is ongoing. The procedure makes use of SCCP connection oriented signaling on the Lb interface and uses the same
SCCP connection as the location request procedure for the particular target MS.
5.2.1 Successful Operation
An SMLC or BSS with a BSSLAP message to transfer concerning a particular target MS sends a BSSMAP-LE
Connection Oriented Information message to a recipient carrying the following parameters:
- BSSLAP APDU (M);
- (Segmentation (C)).
If the sender is an SMLC, the message is transferred to the BSS. The BSS shall then perform the positioning operation
requested by the BSSLAP APDU (refer to 3GPP TS 48.071). If the BSSLAP APDU contains an RRLP APDU, the BSS
shall transfer this to the target MS.
If the sender is a BSS and the intended recipient is the SMLC for a target MS, the message is transferred to the SMLC.
The SMLC shall then perform interpretation of the BSSLAP APDU.
5.2.2 Abnormal Conditions
At an intermediate entity, if a received BSSMAP-LE Connection Oriented Information message contains unrecognized
information or if the mess
...
ETSI TS 1149 031 V13.0.0 (201616-01)
TECHNICAL SPECIFICATIONION
Digital cellular telecocommunications system (Phahase 2+);
Locatcation Services (LCS);
Base Stattation System Application
Part LCSS Extension (BSSAP-LE)
(3GPP TS 49.0.031 version 13.0.0 Release 13 13)
R
GLOBAL SYSTTEME FOR
MOBILE COMMUUNNICATIONS
3GPP TS 49.031 version 13.0.0 Release 13 1 ETSI TS 149 031 V13.0.0 (2016-01)
Reference
RTS/TSGG-0249031vd00
Keywords
GSM
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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI 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 49.031 version 13.0.0 Release 13 2 ETSI TS 149 031 V13.0.0 (2016-01)
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 (https://ipr.etsi.org/).
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.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 3 ETSI TS 149 031 V13.0.0 (2016-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions, abbreviations and symbols . 8
4 Definition of BSSAP-LE . 8
4.1 DTAP-LE Messages . 9
4.2 BSSMAP-LE Messages . 9
5 Procedures applicable to use of BSSAP-LE . 9
5.1 Location Request . 9
5.1.1 Successful Operation . 10
5.1.2 Unsuccessful Operation . 11
5.1.3 Abnormal Conditions . 11
5.1.4 Overload . 11
5.2 Connection Oriented Information Transfer . 12
5.2.1 Successful Operation . 12
5.2.2 Abnormal Conditions . 12
5.2.3 Segmentation . 12
5.3 Connectionless Information Transfer . 13
5.3.1 Successful Operation . 13
5.3.2 Unsuccessful Operation . 13
5.3.3 Abnormal Conditions . 14
5.3.4 Segmentation . 14
5.4 LMU Connection Establishment . 14
5.4.1 LMU Connection Establishment initiated by the SMLC . 14
5.4.1.1 Successful Operation . 14
5.4.1.2 Unsuccessful Operation . 15
5.4.1.3 Abnormal Conditions . 15
5.4.2 LMU Connection Establishment initiated by the MSC . 15
5.4.2.1 Successful Operation . 15
5.4.2.2 Unsuccessful Operation . 15
5.4.2.3 Abnormal Conditions . 15
5.5 (void) . 16
5.6 DTAP-LE Information Transfer . 16
5.6.1 DTAP-LE Information Transfer Initiated by the SMLC . 16
5.6.2 DTAP-LE Information Transfer Initiated by the BSC . 16
5.7 Reset . 16
5.7.1 Normal Operation . 16
5.7.2 Abnormal Conditions . 16
5.8 Perform Location Information . 17
6 Usage of BSSAP-LE and BSSAP on the Lb Interface . 17
6.1 Applicable Message Sets . 17
6.2 MTP Functions . 18
6.3 SCCP Functions . 18
6.3.1 General . 18
6.3.2 Modifications for Connectionless SCCP . 19
6.3.3 Modifications for Connection Oriented SCCP . 19
6.3.4 Contents of the SCCP Data Field . 19
6.3.5 Abnormal Conditions . 20
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 4 ETSI TS 149 031 V13.0.0 (2016-01)
7 (void) . 20
8 Use of BSSAP-LE on the Lp Interface. 20
8.1 Applicable Message Sets . 20
8.2 MTP Functions . 20
8.3 SCCP functions . 21
8.3.1 General . 21
8.3.2 Allowed Exceptions to ITU-T Recommendations Q.711-714 . 21
8.3.3 Allowed Exceptions to ANSI T1.112 . 21
8.3.4 Usage of Connectionless SCCP . 21
8.3.5 Usage of Connection Oriented SCCP . 22
8.3.6 Contents of the SCCP Data Field . 22
9 Message Functional Definitions and Contents . 22
9.1 BSSMAP-LE PERFORM LOCATION REQUEST message . 23
9.1.1 Location Type . 23
9.1.2 Cell Identifier . 23
9.1.3 Classmark Information Type 3 . 23
9.1.4 LCS Client Type . 23
9.1.5 Chosen Channel . 23
9.1.6 LCS Priority . 24
9.1.6a LCS QoS . 24
9.1.7 Requested GPS Assistance Data . 24
9.1.8 BSSLAP APDU . 24
9.1.9 LCS Capability . 24
9.1.10 Packet Measurement Report . 24
9.1.11 Measured Cell Identity List . 24
9.1.12 IMSI . 24
9.1.13 IMEI. 24
9.1.14 GANSS Location Type . 24
9.1.15 Requested GANSS Assistance Data . 24
9.2 BSSMAP-LE PERFORM LOCATION RESPONSE message . 24
9.2.1 Location Estimate . 25
9.2.2 Positioning Data . 25
9.2.3 Deciphering Keys . 25
9.2.4 LCS Cause . 25
9.2.5 Velocity Data . 25
9.2.6 GANSS Positioning Data . 25
9.3 BSSMAP-LE PERFORM LOCATION ABORT message . 25
9.3.1 LCS Cause . 26
9.4 (void) . 26
9.5 (void) . 26
9.6 (void) . 26
9.7 (void) . 26
9.8 BSSMAP-LE CONNECTION ORIENTED INFORMATION message . 26
9.8.1 BSSLAP APDU . 26
9.8.2 Segmentation . 26
9.9 BSSMAP-LE CONNECTIONLESS INFORMATION message . 26
9.9.1 Source Identity . 27
9.9.2 Destination Identity. 27
9.9.3 APDU . 27
9.9.4 Segmentation . 27
9.9.5 Return Error Request . 27
9.9.6 Return Error Cause . 27
9.10 BSSMAP-LE RESET message . 27
9.11 BSSMAP-LE RESET ACKNOWLEDGE message . 28
9.12 BSSMAP-LE PERFORM LOCATION INFORMATION message . 28
9.12.1 Cell Identifier . 28
9.12.2 BSSLAP APDU . 28
10 Message format and information element coding . 28
10.1 Message type . 29
10.2 Information Element Identifiers . 29
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 5 ETSI TS 149 031 V13.0.0 (2016-01)
10.3 APDU . 30
10.4 Cause . 31
10.5 Cell Identifier . 31
10.6 Chosen Cha nne l . 31
10.7 Classmark Information Type 3 . 31
10.8 Deciphering Keys . 32
10.9 Geographic Location . 32
10.10 Requested GPS Assistance Data . 32
10.11 IMSI . 35
10.12 (void) . 35
10.13 LCS Cause . 35
10.14 LCS Client Type . 36
10.15 LCS Priority . 37
10.16 LCS QoS . 37
10.17 (void) . 38
10.18 Location Type . 38
10.19 Network Element Identity . 39
10.20 Positioning Data . 40
10.21 Return Error Request . 41
10.22 Return Error Cause . 41
10.23 (void) . 42
10.24 Segmentation . 42
10.25 (void) . 43
10.26 LCS Capability . 43
10.27 Packet Measurement Report . 43
10.28 Cell Identity List . 43
10.29 IMEI . 43
10.30 Velocity Data . 44
10.31 Requested GANSS Assistance Data . 44
10.32 GANSS Positioning Data . 51
10.33 GANSS Location Type . 51
Annex A (informative): Change history . 52
History . 53
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 6 ETSI TS 149 031 V13.0.0 (2016-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The present document defines the coding of information in an extension of the Base Station System Application Part
(BSSAP) that is needed to support location services on interfaces based on use of BSSAP.
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 49.031 version 13.0.0 Release 13 7 ETSI TS 149 031 V13.0.0 (2016-01)
1 Scope
The present document specifies procedures and information coding that are needed to define and support the BSSAP
LCS Extension (BSSAP-LE). The BSSAP-LE message set is applicable to the following GSM interfaces defined in
3GPP TS 43.059:
- Lb interface (BSC-SMLC).
- Lp interface (SMLC-SMLC).
The present document defines message formats and encoding for BSSAP-LE and the particular subsets of it that are
applicable to each of the above interfaces. The present document also defines the support for BSSAP-LE message
transfer on each of these interfaces using either ITU-T and ANSI versions of SS7 MTP or IETF M3UA/SCTP and
SCCP. Additional requirements for the above interfaces that are applicable to BSSAP-LE are also defined – e.g. usage
of BSSAP (as defined in 3GPP TS 24.008 and 48.008) on the Lb interface.
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".
[1a] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[2] 3GPP TS 43.059: "Functional Stage 2 Description of Location Services in GERAN".
[3] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[3a] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols; Stage 3".
[4] 3GPP TS 44.031: "Location Services (LCS); Mobile Station (MS) – Serving Mobile Location
Center (SMLC); Radio Resource LCS Protocol (RRLP)".
[5] 3GPP TS 44.071: "Location Services (LCS); Mobile radio interface layer 3 Location Services
(LCS) specification".
[6] 3GPP TS 48.006: "Signaling transport mechanism specification for the Base Station Subsystem –
Mobile-services Switching Centre (BSS - MSC) interface".
[7] 3GPP TS 48.008: "Mobile-services Switching Centre – Base Station System (MSC-BSS)
interface; Layer 3 specification".
[8] 3GPP TS 48.031: "Location Services (LCS); Serving Mobile Location Center – Serving Mobile
Location Center (SMLC - SMLC); SMLCPP specification".
[9] 3GPP TS 48.071: "Serving Mobile Location Center – Base Station Subsystem (SMLC-BSS)
interface Layer 3 specification".
[10] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[10a] 3GPP TS 23.003: "Numbering, addressing and identification".
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 8 ETSI TS 149 031 V13.0.0 (2016-01)
[11] ITU-T Recommendation Q.702: "Signalling data link".
[12] ITU-T Recommendation Q.703: "Signalling link".
[13] ITU-T Recommendation Q.704: "Signalling network functions and messages".
[14] ITU-T Recommendation Q.707: "Testing and maintenance".
[15] ITU-T Recommendation Q.711: "Functional description of the signalling connection control part".
[16] ITU-T Recommendation Q.712: "Definition and function of signalling connection control part
messages".
[17] ITU-T Recommendation Q.713: "Signalling connection control part formats and codes".
[18] ITU-T Recommendation Q.714: "Signalling connection control part procedures".
[19] ANSI T1.111 (1996): "Signalling System Number 7 – Message Transfer Part".
[20] ANSI T1.112 (1996): "Signalling System Number 7 (SS7) - Signalling Connection Control Part
Functional Description".
[21] TIA/EIA/IS-J-STD-036 (2000): "Wireless Enhanced Emergency Services".
[22] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving
GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)".
[23] IETF STD 51, RFC 1661(07/1994): "The Point-To-Point Protocol (PPP)".
[24] IETF STD 51, RFC 1662(07/1994): "PPP in HDLC-like Framing".
[25] IETF RFC 2507(02/1999): "IP header compression".
[26] IETF RFC 1990(07/1994): "The PPP Multilink Protocol (MP)".
[27] IETF RFC 2686(09/1999): "The Multi-Class Extension to Multi-Link PPP".
[28] IETF RFC 2509(02/1999): "IP Header Compression over PPP".
[29] 3GPP TS 29.202: "SS7 Signalling Transport in Core Network; Stage 3".
[30] Galileo OS SIS ICD/D.0 "Galileo Open Service, Signal In Space Interface Control
Document/Draft 0".
[31] Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002.
[32] BDS-SIS-ICD-B1I-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control
Document Open Service Signal B1I (Version 1.0)", December 2012.
3 Definitions, abbreviations and symbols
For the purposes of the present document, the definitions, symbols and abbreviations listed in 3GPP TS 21.905 and
3GPP TS 43.059 apply.
4 Definition of BSSAP-LE
BSSAP-LE is an extension to BSSAP that contains messages and parameters specific to the support of LCS. The
following subsets of BSSAP-LE are defined: DTAP-LE, BSSMAP-LE.
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 9 ETSI TS 149 031 V13.0.0 (2016-01)
4.1 DTAP-LE Messages
DTAP-LE messages are transfered between an SMLC and a Type A LMU and comprise the following individual
messages:
- REGISTER;
- FACILITY;
- RELEASE COMPLETE.
The content, encoding and certain procedures asssociated with DTAP-LE messages are defined in 3GPP TS 44.071.
4.2 BSSMAP-LE Messages
BSSMAP-LE messages are transferred between a BSS and SMLC and comprise the following individual messages:
BSSMAP-LE Positioning Messages:
- Perform Location Request;
- Perform Location Response;
- Perform Location Abort;
- Perform Location Information.
BSSMAP-LE Information Messages:
- Connection Oriented Information;
- Connectionless Information.
BSSMAP-LE General Messages:
- Reset;
- Reset Acknowledge.
The content and encoding of BSSMAP-LE messages are defined in the present document.
5 Procedures applicable to use of BSSAP-LE
5.1 Location Request
The Location Request procedure is applicable to the Lb interface. Its purpose is to obtain a location estimate for a target
MS that is already in dedicated mode, in packet transfer mode, in packet idle mode, or in dual transfer mode. It is also
used to provide an MS with LCS assistance data or with a deciphering key for LCS broadcast assistance data. The
initiator of a location request is the BSS. The procedure makes use of SCCP connection oriented signaling on the Lb
interface.
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 10 ETSI TS 149 031 V13.0.0 (2016-01)
5.1.1 Successful Operation
The initiator of the location request sends a BSSMAP-LE Perform Location Request to the SMLC associated with the
current serving cell for the target MS. The message contains the following mandatory (M), conditional (C) and optional
(O) information, where conditional parameters are required if available.
- Location Type (M).
- GANSS Location Type (C)
- Cell Identifier (M).
- Classmark Information Type 3 (C).
- LCS Client Type (C).
- Chosen Channel (C).
- LCS Priority (C).
- LCS QoS (C).
- Requested GPS Assistance Data (C).
- BSSLAP APDU (C).
- LCS Capability (O).
- Packet Measurement Report (O).
- Measured Cell Identity List (O).
- IMSI of target MS (O).
- IMEI of target MS (O).
- Requested GANSS Assistance Data (C).
If requested, the SMLC performs positioning of the target MS using a particular position method or a combination of
more than one positioning method. If neither the Classmark Information Type 3 IE nor the LCS Capability IE is present,
the SMLC shall instigate only network based positioning methods (e.g. TA and U-TDOA but not GPS or E-OTD).
Alternatively, if requested otherwise, the SMLC may provide positioning assistance data to the MS. The SMLC may
invoke the following other BSSAP-LE procedures to perform these procedures:
- connection oriented information transfer;
- connectionless information transfer;
- LMU connection establishment;
- LMU connection release;
- DTAP-LE information transfer.
Additional procedures defined in 3GPP TS 24.008 and 3GPP TS 48.008 may also be performed. If a location estimate
was requested and was subsequently obtained, the SMLC shall return a BSSMAP-LE Perform Location Response to the
initiator of the location request. This message contains the following mandatory, conditional and optional parameters.
- Location Estimate (M).
- Positioning Data (C).
- GANSS Positioning Data (C).
Restrictions on the geographic shape encoded within the Location Estimate parameter may exist for certain LCS client
types. The SMLC shall comply with any restrictions defined in 3GPP specifications and, in a particular country, with
any restrictions defined for a specific LCS client type in relevant national standards. For example, in the US, national
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 11 ETSI TS 149 031 V13.0.0 (2016-01)
interim standard TIA/EIA/IS-J-STD-036 [21] restricts the geographic shape for an emergency services LCS client to
minimally either an "ellipsoid point" or an "ellipsoid point with uncertainty circle and confidence" as defined in
3GPP TS 23.032.
If assistance data was instead requested for an MS and the SMLC was able successfully to transfer this to the MS, the
SMLC shall return a BSSMAP-LE Perform Location Response to the initiator of the location request (serving BSC).
This message shall contain no parameters. The absence of an LCS Cause parameter in this case implies that the transfer
was successful.
Otherwise, if a deciphering key was requested for LCS broadcast assistance data and the SMLC has access to the
appropriate keys, the SMLC shall return a BSSMAP-LE Perform Location Response to the initiator of the location
request. This message contains the following mandatory parameters.
- Deciphering Keys (M).
5.1.2 Unsuccessful Operation
If the SMLC is unable to obtain any of the location information requested or if requested LCS assistance data could not
be transferred or requested deciphering keys for broadcast assistance data could not be returned, the SMLC shall return
a BSSMAP-LE Perform Location Response to the initiator of the Location Request carrying the following parameters:
- LCS Cause (M);
- Positioning Data (O).
- GANSS Positioning Data (O).
If assistance data or deciphering keys for a specific positioning method is not supported in the network or in the location
area, the SMLC shall indicate this with LCS Cause value "Position method failure" accompanied with diagnostic value
"Position Method Not Available in Network" or "Position Method Not Available in Location Area".
5.1.3 Abnormal Conditions
If an ongoing location request is preempted at the initiator by an inter-BSC handover or if the main signaling link to the
target MS is lost or released or if there is a timeout waiting for the positioning response, or if there is an Inter NSE cell
change in the PS Domain (e.g. detected by the BSS at receipt of BSSGP FLUSH-LL PDU) for which the BSS is unable
to maintain the positioning procedure, the initiator shall send a BSSMAP-LE Perform Location Abort to the SMLC
containing the following parameters.
- LCS Cause (M).
On receipt of this message, the SMLC shall stop positioning of the target MS and may release any resources
(e.g. LMUs) previously allocated. If the SMLC has not yet returned a BSSMAP-LE Perform Location Response to the
initiator, it shall return this message containing an LCS Cause indicating an abort and, optionally, positioning data,
GANSS positioning data. The initiator shall then release the SCCP connection. If the SMLC cannot proceed with
positioning due to some protocol violation or error condition (e.g. inter-BSC handover indication received from the
serving BSC), it shall return a BSSMAP-LE Perform Location Response to the initiator containing an LCS cause and,
optionally, positioning data, GANSS positioning data. The initiator need not reply at the BSSAP-LE level to this
message. However, the initiator may return a BSSMAP-LE perform Location Abort which shall not be treated as an
error by the SMLC.
5.1.4 Overload
If the SMLC is in an overload condition, it may reject a BSSMAP-LE Perform Location request by returning a
BSSMAP-LE Perform Location response containing an LCS Cause parameter indicating congestion. The initiator of the
location service request (BSC) may reduce the frequency of future location service requests until rejection due to
overload has ceased. In reducing the frequency of location service requests, a BSC shall reduce lower priority requests,
to zero if necessary, before reducing the frequency of higher priority requests. An SMLC shall similarly reject location
service requests of a lower priority, to zero if necessary, due to overload before rejecting location service requests of a
higher priority. An SMLC in an overload condition may optionally employ the following procedures to alleviate
overload:
ETSI
3GPP TS 49.031 version 13.0.0 Release 13 12 ETSI TS 149 031 V13.0.0 (2016-01)
a) Allow higher priority location service requests to preempt lower priority requests for which location service
procedures are already in progress.
b) Abort lower priority location service requests already in progress.
c) Reduce the supported QoS for lower priority requests for a location estimate – e.g. by reducing accuracy or
increasing response time.
d) Employ MS based positioning methods, where supported by the target MS and SMLC, rather than MS assisted
or network based methods (except TA).
The priority of a location service request shall be defined according to the value in the LCS Priority parameter. If this
parameter is absent in a BSSMAP-LE Perform Location request, the lowest priority shall be assumed.
5.2 Connection Oriented Information Transfer
The Connection Oriented Information transfer procedure is applicable to the Lb interface. It enables two way transfer of
BSSLAP messages between an SMLC and the BSS serving a target MS. The initiator of the procedure can be either the
BSS serving the target MS or the SMLC. The procedure is only valid while a location request procedure for the target
MS is ongoing. The procedure makes use of SCCP connection oriented signaling on the Lb interface and uses the same
SCCP connection as the location request procedure for the particular target MS.
5.2.1 Successful Operation
An SMLC or BSS with a BSSLAP message to transfer concerning a particular target MS sends a BSSMAP-LE
Connection Oriented Information message to a recipient carrying the following parameters:
- BSSLAP APDU (M);
- (Segmentation (C)).
If the sender is an SMLC, the message is transferred to the BSS. The BSS shall then perform the positioning operation
requested by the BSSLAP APDU (refer to 3GPP TS 48.071). If the BSSLAP APDU contains an RRLP APDU, the BSS
shall transfer this to the target MS.
If the sender is a BSS and the intended recipient is the SMLC for a target MS, the message is transferred to the SMLC.
The SMLC shall then perform interpretation of the BSSLAP APDU.
5.2.2 Abnormal Conditions
At an intermediate entity, if a received BSSMAP-LE Connection Oriented Information message contains unrecognized
information or if the mess
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...