ETSI TS 144 031 V13.0.0 (2016-01)

Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP) (3GPP TS 44.031 version 13.0.0 Release 13)

RTS/TSGG-0244031vd00

General Information

• Status: Published
• Publication Date: 24-Jan-2016
• Technical Committee: 3GPP GERAN 2 - Protocol aspects
• Current Stage: 12 - Completion
• Due Date: 20-Jan-2016
• Completion Date: 25-Jan-2016

Standards Content (Sample)

ETSI TS 1144 031 V13.0.0 (201616-01)

TECHNICAL SPECIFICATIONION
Digital cellular telecocommunications system (Phahase 2+);
Locatcation Services (LCS);
Mobile Station (MS) - SeServing Mobile Location Centntre (SMLC)
Radio Ressoource LCS Protocol (RRLP)
(3GPP TS 44.0.031 version 13.0.0 Release 13 13)

R
GLOBAL SYSTTEME FOR
MOBILE COMMUUNNICATIONS
3GPP TS 44.031 version 13.0.0 Release 13 1 ETSI TS 144 031 V13.0.0 (2016-01)

Reference
RTS/TSGG-0244031vd00
Keywords
GSM
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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 44.031 version 13.0.0 Release 13 2 ETSI TS 144 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 44.031 version 13.0.0 Release 13 3 ETSI TS 144 031 V13.0.0 (2016-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
1.1 References . 6
1.2 Abbreviations . 7
2 Functionality of Protocol . 7
2.1 General . 7
2.2 Position Measurement Procedure . 8
2.3 Assistance Data Delivery Procedure . 9
2.3a Positioning Capability Transfer Procedure . 10
2.4 (void) . 10
2.5 Error Handling Procedures . 10
2.5.1 General . 10
2.5.1a Message Too Short . 10
2.5.2 Unknown Reference Number . 11
2.5.3 Missing Information Element or Component Element . 11
2.5.4 Incorrect Data . 11
2.5.5 Repeated Component . 11
2.5.6 (void) . 12
2.5.7 Missing Component . 12
2.5.8 Unforeseen Component . 12
2.5.8a RRLP Procedure . 12
2.5.9 Pseudo-Segmentation. 13
3 Message Structure . 13
3.1 General Format of RRLP Message . 13
3.2 Reference Number IE . 14
3.3 Component IE . 15
4 Components . 15
4.1 Measure Position Request . 16
4.2 Measure Position Response . 16
4.3 Assistance Data . 16
4.4 Assistance Data Acknowledgement . 17
4.5 Protocol Error . 17
4.6 Positioning Capability Request . 17
4.7 Positioning Capability Response . 18
5 Elements of Components. 18
5.1 ASN.1 Description . 18
6 TOM Protocol Header for RRLP Transport . 54
6.1 General . 54
6.2 Remaining Octets of TOM Protocol Header for RRLP . 54
Annex A (informative): Description of Components . 56
A.1 Introduction . 56
A.2 Measure Position Request . 56
A.2.1 General . 56
A.2.2 Elements . 56
A.2.2.1 Positioning Instructions Element . 56
A.2.2.1a GANSS Positioning Method Element . 58
A.2.2.2 E-OTD Reference BTS for Assistance Data Element . 58
A.2.2.3 E-OTD Measurement Assistance Data Element . 59
ETSI
3GPP TS 44.031 version 13.0.0 Release 13 4 ETSI TS 144 031 V13.0.0 (2016-01)
A.2.2.4 E-OTD Measurement Assistance Data for System Information List Element . 61
A.2.2.4a GPS Time Assistance Measurement Request element . 63
A.2.2.4b GPS Reference Time Uncertainty element . 64
A.2.2.4c Velocity Request element . 64
A.2.2.4d GANSS Carrier-Phase Measurement Request Element . 64
A.2.2.4e GANSS TOD - GSM Time Association Request Element . 64
A.2.2.4f Required Response Time . 64
A.2.2.4g GANSS Multi-frequency Measurement Request Element . 64
A.2.2.5 Extended Reference IE . 65
A.3 Measure Position Response . 65
A.3.1 General . 65
A.3.2 Elements . 66
A.3.2.1 Multiple Sets Element . 66
A.3.2.2 Reference BTS Identity Element . 66
A.3.2.3 E-OTD Measurement Information Element . 67
A.3.2.3a E-OTD Measurement Extended Information Element . 71
A.3.2.4 Location Information Element . 72
A.3.2.5 GPS Measurement Information Element . 73
A.3.2.6 Location Information Error Element . 77
A.3.2.6a GPS Time Assistance Measurements Element . 77
A.3.2.6b Velocity Estimate Element . 78
A.3.2.7 Extended Reference IE . 79
A.3.2.8 Uplink RRLP Pseudo Segmentation Indication . 79
A.3.2.9 GANSS Location Information Element . 79
A.3.2.10 GANSS Measurement Information Element . 82
A.3.2.10.1 GANSS Generic Measurement Information Element . 85
A.4 Assistance Data . 88
A.4.1 General . 88
A.4.2 Elements . 89
A.4.2.1 E-OTD Reference BTS for Assistance Data Element . 89
A.4.2.2 E-OTD Measurement Assistance Data Element . 89
A.4.2.3 E-OTD Measurement Assistance Data for System Information List Element . 89
A.4.2.4 GPS Assistance Data Element. 89
A.4.2.4a GPS Time Assistance Measurement Request Element . 101
A.4.2.4b GPS Reference Time Uncertainty Element . 101
A.4.2.4c Additional GPS Assistance Data . 101
A.4.2.5 More Assistance Data To Be Sent Element . 111
A.4.2.5 More Assistance Data To Be Sent Element . 111
A.4.2.6 GANSS Assistance Data . 111
A.4.2.6.1 GANSS Common Assistance Data . 112
A.4.2.6.2 GANSS Generic Assistance Data . 115
A.4.2.7 GANSS Carrier-Phase Measurement Request Element . 150
A.4.2.8 GANSS TOD - GSM Time Association Request Element . 151
A.5 Assistance Data Acknowledgement . 151
A.5.1 General . 151
A.6 Protocol Error . 151
A.6.1 General . 151
A.6.2 Extended Reference IE . 151
A.7 Positioning Capability Request . 151
A.7.1 General . 151
A.8 Positioning Capability Response . 152
A.8.1 General . 152
A.8.2 Elements . 152
A.8.2.1 Positioning Capabilities . 152
A.8.2.2 Assistance Data Supported . 154
A.8.2.3 Assistance Data Needed . 156
Annex B (informative): Change History . 157
History . 158

ETSI
3GPP TS 44.031 version 13.0.0 Release 13 5 ETSI TS 144 031 V13.0.0 (2016-01)
Foreword
rd
This Technical Specification has been produced by the 3 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 44.031 version 13.0.0 Release 13 6 ETSI TS 144 031 V13.0.0 (2016-01)
1 Scope
The present document contains the definition of the Radio Resource LCS Protocol (RRLP) to be used between the
Mobile Station (MS) and the Serving Mobile Location Centre (SMLC).
Clause 2 defines the functionality of the protocol. Clause 3 describes the message structure, and Clause 4 the structure
of components. Clause 5 contains the ASN.1 description of the components.
1.1 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 43.059: "Functional Stage 2 Description of Location Services in GERAN".
[3] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[4] ITU-T Recommendation X.691: "Information technology - ASN.1 encoding rules: Specification of
Packed Encoding Rules (PER)".
[5] ITU-T Recommendation X.680: "Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation".
[6] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[7] 3GPP TS 49.031: "Location Services (LCS); Base Station System Application Part LCS Extension
(BSSAP-LE)".
[8] ICD-GPS-200, Navstar GPS Space Segment/Navigation User Interfaces.
[9] RTCM-SC104, RTCM Recommended Standards for Differential GNSS Service (v.2.2).
[10] 3GPP TS 44.064: "General Packet Radio Service (GPRS); Mobile Station - Serving GPRS
Support Node (MS-SGSN); Logical Link Control (LLC) layer specification".
[11] Galileo OS Signal in Space ICD (OS SIS ICD), Issue 1.12, September February 20104, European
Union.
th
[12] IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7 ,
2006.
[13] IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, September 22, 2005.
[14] IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, March 31, 2008.
[15] Specification for the Wide Area Augmentation System (WAAS), US Department of
Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001.
[16] IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS,
Ver.1.0, June 17, 2008.
[17] Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002.
ETSI
3GPP TS 44.031 version 13.0.0 Release 13 7 ETSI TS 144 031 V13.0.0 (2016-01)
[18] BDS-SIS-ICD-2.0: "BeiDou Navigation Satellite System Signal In Space Interface Control
Document Open Service Signal (Version 2.0)", December 2013.
1.2 Abbreviations
For the purposes of the present document, the following abbreviations and the abbreviations given in 3GPP TR 21.905
or in 3GPP TS 43.059 apply.
ADR Accumulated Delta-Range
BDS BeiDou Navigation Satellite System
CNAV Civil Navigation
ECEF Earth-Centered, Earth-Fixed
ECI Earth-Centered-Inertial
EGNOS European Geostationary Navigation Overlay Service
FEC Forward Error Correction
GAGAN GPS Aided Geo Augmented Navigation
ICD Interface Control Document
GANSS Galileo and Additional Navigation Satellite Systems
GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System)
GNSS Global Navigation Satellite System
IOD Issue of Data
LSB Least Significant Bit
MSAS Multi-functional Satellite Augmentation System
MSB Most Significant Bit
msd mean solar day
NAV Navigation
NICT National Institute of Information and Communications Technology
NTSC National Time Service Center
PZ-90 Parametry Zemli 1990 Goda – Parameters of the Earth Year 1990
QZSS Quasi-Zenith Satellite System
SBAS Space Based Augmentation System
SV Space Vehicle
USNO US Naval Observatory
WAAS Wide Area Augmentation System
WGS-84 World Geodetic System 1984
2 Functionality of Protocol
2.1 General
The present document defines one generic RRLP message that is used to transfer Location Services (LCS) related
information between the Mobile Station (MS) and the Serving Mobile Location Centre (SMLC). Usage of the RRLP
protocol on a general level is described in 3GPP TS 43.059 that includes Stage 2 description of LCS.
One message includes one of the following components:
- Measure Position Request;
- Measure Position Response;
- Assistance Data;
- Assistance Data Acknowledgement;
- Protocol Error;
- Positioning Capability Request;
- Positioning Capability Response.
ETSI
3GPP TS 44.031 version 13.0.0 Release 13 8 ETSI TS 144 031 V13.0.0 (2016-01)
Next sub-clauses describe the usage of these components.
Delivery of components may be supported in the RRLP level using pseudo-segmentation by sending several shorter
messages instead of one long message. Any assistance data that is successfully delivered to an MS and acknowledged
prior to the interruption of the positioning procedure by an event like handover, or by any other event that causes an MS
to terminate the positioning procedure or delivery of assistance data (see 3GPP TS 43.059), shall be retained by the MS
and need not be resent by the SMLC when positioning or delivery of assistance data is again re-attempted.
The RRLP maximum PDU size is 242 octets. If the amount of data that needs to be sent is larger than RRLP maximum
PDU size, the RRLP pseudo-segmentation shall be used. The RRLP pseudo-segmentation is the use of several RRLP
components (one in each RRLP message) to deliver a large amount of information. For SMLC to MS messages, the
Assistance Data component is the one that is sent several times in order to deliver the information. For MS to SMLC
messages, the Measure Position Response component may be sent twice in order to deliver the information. Legacy MS
and SMLC (3GPP Rel-4 or older) may send RRLP components that are larger than the RRLP maximum PDU size. In
this case lower level segmentation will be used.
2.2 Position Measurement Procedure
The purpose of this procedure is to enable the SMLC to request for position measurement data or location estimate from
the MS, and the MS to respond to the request with measurements or location estimate.

SMLC MS
1. Positioning Capability Transfer Procedure
2. Assistance Data Delivery Procedure
3. RRLP(Measure Position Request)
4. RRLP(Protocol Error)
5. RRLP(Measure Position Response)
5. RRLP(Measure Position Response)

Figure 2.1: Position Measurement procedure
1. The Measure Position Request component and any Assistance Data Delivery Procedure may be preceded by a
Positioning Capability Transfer procedure (see sub-clause 2.3a) to transfer the MS positioning capabilities to the
SMLC.
2. The Measure Position Request component may be preceded by an Assistance Data Delivery Procedure (see sub-
clause 2.3) to deliver some or all of the entire set of assistance data that is needed by the subsequent positioning
procedure (steps 3-5).
3. The SMLC sends the Measure Position Request component in a RRLP message to the MS. The component
includes QoS, other instructions, and possible assistance data to the MS. The RRLP message contains a
reference number and an extended reference ID of the request.
4. The MS sends a RRLP message containing the Protocol Error component to the SMLC, if there is a problem that
prevents the MS to receive a complete and understandable Measure Position Request component. The RRLP
message contains the reference number and, if available, the extended reference ID included in the Measure
Position Request received incomplete. The Protocol Error component includes a more specific reason. When the
SMLC receives the Protocol Error component, it may try to resend the Measure Position Request (go back to the
step 3), abort location, or start a new position measurement procedure (e.g. with updated assistance data).
5. The MS tries to perform the requested location measurements, and possibly calculates it own position. When the
MS has location measurements, location estimate, or an error indication (measurements/location estimation not
ETSI
3GPP TS 44.031 version 13.0.0 Release 13 9 ETSI TS 144 031 V13.0.0 (2016-01)
possible), it sends the results in the Measure Position Response component to the SMLC. The RRLP message
contains the reference number and, if received, the extended reference ID of the request originally received in
the step 3. The MS may optionally send one additional Measure Position Response component in a second
RRLP message to the SMLC if the amount of information it needs to transfer to the SMLC is too large to fit into
one single Measure Position Response component (uplink RRLP pseudo-segmentation). This RRLP message
also contains the reference number and, if received, the extended reference ID of the request originally received
in the step 3. If two components are sent, the MS shall indicate in the first component that it is the first of many
components and in the second one that it is the second of many components. If there is a problem that prevents
the SMLC to receive a complete and understandable Measure Position Response component, the SMLC may
decide to abort location, or start a new position measurement procedure instead. If additional Measure Position
st nd
Response components are received by the SMLC after the 1 and optional 2 one, they shall be ignored.
2.3 Assistance Data Delivery Procedure
The purpose of this procedure is to enable the SMLC to send assistance data to the MS related to position measurement
and/or location calculation. Notice that RRLP protocol is not used by the MS to request assistance data, only to deliver
it to the MS. The entire set of assistance data (i.e. the total amount of assistance data that the SMLC has decided to send
in the current procedure) may be delivered in one or several Assistance Data components. In this case steps 1 and 3
below may be repeated several times by the SMLC. If several components are sent, the SMLC shall await the
acknowledgement of each component before the next Assistance Data component is sent. If Assistance Data Delivery is
used as part of the Position Measurement Procedure, as described in sub-clause 2.2, then some assistance data may be
delivered in the final RRLP Measure Position Request.
SMLC MS
1. RRLP(Assistance Data)
2. RRLP(Protocol Error)
3. RRLP(Assistance Data Ack.)
Figure 2.2: Assistance Data Delivery procedure
1. The SMLC sends the Assistance Data component to the MS. The component includes assistance data for
location measurement and/or location calculation. The RRLP message contains a reference number and an
extended reference ID of the delivery. The More Assistance Data To Be Sent Element in the Assistance Data
component is used by the SMLC to indicate to the MS if either more Assistance Data components (in the current
Assistance Data Delivery procedure) or a final RRLP Measure Position Request (if the Assistance Data Delivery
Procedure forms part of a Position Measurement procedure as described in sub-clause 2.2) will be sent.
2. The MS sends a RRLP message containing the Protocol Error component to the SMLC, if there is a problem that
prevents the MS to receive a complete and understandable Assistance Data component. The RRLP message
contains the reference number and, if available, the extended reference ID included in the Assistance Data
component received incomplete. The Protocol Error component includes a more specific reason. When the
SMLC receives the Protocol Error component, it may try to resend the Assistance Data component (go back to
the step 1), send a new measure Assistance Data set (e.g. with updated assistance data), or abort the delivery.
3. When the MS has received a complete Assistance Data component, it send the Assistance Data
Acknowledgement component to the SMLC. The RRLP message contains the reference number of the
Assistance Data originally received in step 1.
ETSI
3GPP TS 44.031 version 13.0.0 Release 13 10 ETSI TS 144 031 V13.0.0 (2016-01)
2.3a Positioning Capability Transfer Procedure
The purpose of this procedure is to enable the SMLC to obtain the positioning capabilities of the MS, the types of
assistance supported and the types of assistance data that may be needed from the SMLC. MS support for this
procedure can be indicated to the SMLC using the MS Classmark 3 IE for GSM (see 3GPP TS 24.008), the PS LCS
Capability IE for GERAN Gb mode (see 3GPP TS 24.008) and the MS Positioning Capability IE for GERAN Iu mode
(see 3GPP TS 44.118).
SMLC MS
1. RRLP (Positioning Capability Request)
2. RRLP (Protocol Error)
3. RRLP (Positioning Capability Response)

Figure 2.3: Positioning Capability Transfer procedure
1. The SMLC sends the Positioning Capability Request component to the MS. The RRLP message contains a
reference number and an extended reference ID of the request. The message may contain indication of GANSS
positioning support.
2. The MS sends a RRLP message containing the Protocol Error component to the SMLC, if there is a problem that
prevents the MS to receive a complete and understandable Positioning Capability Request component. The
RRLP message contains the reference number and the extended reference ID included in the Positioning
Capability Request component. The Protocol Error component includes a more specific reason. When the SMLC
receives the Protocol Error component, it may try to resend the Positioning Capability Request component (go
back to the step 1) or abort the request.
3. When the MS has received a complete Positioning Capability Request component, it sends the Positioning
Capability Response component to the SMLC. The component shall include the positioning capabilities of the
MS and the types of supported assistance data. The component may include the types of assistance needed by the
MS to obtain a location estimate or positioning measurements. The RRLP message also contains the reference
number and extended Reference ID of the Positioning Capability Request originally received in step 1.
2.4 (void)
2.5 Error Handling Procedures
2.5.1 General
In this sub-clause it is described how a receiving entity behaves in cases when it receives erroneous data or detects that
certain data is missing.
2.5.1a Message Too Short
When MS receives a RRLP message, that is too short to contain all mandatory IEs, the MS sends a Protocol Error
component with indication "Message Too Short". If the Reference Number can be found, it is included. If the Reference
Number is not available, the Reference Number of the RRLP message carrying the Protocol Error component is set to
'0'. If the Extended Reference IE can be found, it shall be included in the returned Protocol Error Component. If the
Extended Reference IE is not available, an Extended Reference IE shall not be included. The original sending entity that
receives the Protocol Error, may then resend the original message, or abort the procedure.
ETSI
3GPP TS 44.031 version 13.0.0 Release 13 11 ETSI TS 144 031 V13.0.0 (2016-01)
2.5.2 Unknown Reference Number
A SMLC detects that it has received a RRLP message with an unknown or invalid Reference Number, when one or
more of the following conditions occur:
- a Measure Position Response, Assistance Data Acknowledgement, Positioning Capability Response or Protocol
Error component is received with a Reference Number that the SMLC has not sent in a Measure Position
Request, Assistance Data or Positioning Capability Request component during a pending Position Measurement,
Assistance Data Delivery or Positioning Capability Transfer procedure.
- a Measure Position Response, Positioning Capability Response or Protocol Error component is received with an
Extended Reference IE value that the SMLC has not sent in a Measure Position Request Assistance Data or
Positioning Capability Request component during a pending Position Measurement, Assistance Data Delivery or
Positioning Capability Transfer procedure.
- a Measure Position Response, Positioning Capability Response or Protocol Error component is received with a
Reference Number and an Extended Reference IE value that the SMLC has not sent together in the same
Measure Position Request, the same Assistance Data or the same Positioning Capability Request component
during a pending Position Measurement, Assistance Data Delivery or Positioning Capability Transfer procedure.
The SMLC shall then discard the message. If the SMLC receives a Measure Position Response or a Protocol Error
component containing no Extended Reference ID, then the SMLC shall assume that the target MS is for Release 4 or
earlier and shall only verify the received Reference Number.
2.5.3 Missing Information Element or Component Element
When MS receives a RRLP message, that does not contain IEs or component elements expected to be present, the MS
sends a Protocol Error component with indication "Missing Information Element or Component Element". If the
Reference Number can be found, it is included. If the Reference Number is not available, the Reference Number of the
RRLP message carrying the Protocol Error component is set to '0'. If the Extended Reference IE can be found, it shall
be included in the returned Protocol Error Component. If the Extended Reference IE is not available, an Extended
Reference IE shall not be included. The SMLC that receives the Protocol Error, may then resend the original message,
or abort the procedure.
2.5.4 Incorrect Data
When MS receives a RRLP message, that is contains IEs or elements of components that are syntactically incorrect, the
MS sends a Protocol Error component with indication "Incorrect Data". If the Reference Number can be found, it is
included. If the Reference Number is not available, the Reference Number of the RRLP message carrying the Protocol
Error component is set to '0'. If the Extended Reference IE can be found, it shall be included in the returned Protocol
Error Component. If the Extended Reference IE is not available, an Extended Reference IE shall not be included. The
SMLC that receives the Protocol Error, may then resend the original message, or abort the procedure.
2.5.5 Repeated Component
When after the reception of a Measure Position Request component, but before responding with a Measure Position
Response or a Protocol Error component, the MS receives a new RRLP message with the Measure Position Request
component, it acts as follows:
- if the old and new Measure Position Request components have the same Reference Number and, if included, the
same Extended Reference IE, the MS ignores the later component;
- if the old and new Measure Position Request components have different Reference Numbers or, if included,
different Extended Reference IEs or if one Measure Position Request component (old or new) contains an
Extended Reference IE but the other component does not, the MS aborts activity for the former component, and
starts to acts according to the later component, and sends a response to that.
When after the reception of an Assistance Data component, but before responding with an Assistance Data
Acknowledgement or a Protocol Error component, the MS receives a new RRLP message with the Assistance Data
component, it acts as follows:
ETSI
3GPP TS 44.031 version 13.0.0 Release 13 12 ETSI TS 144 031 V13.0.0 (2016-01)
- if the old and new Assistance Data components have the same Reference Number and, if included, the same
Extended Reference IE and if pseudo-segmentation does not apply (see sub-clause 2.5.9), the MS ignores the
later component;
- if the old and new Assistance Data components have different Reference Numbers or, if included, different
Extended Reference IEs or if one Assistance Data component (old or new) contains an Extended Reference IE
but the other component does not, the MS ignores the former component and sends an acknowledgement to the
latter component.
When after the reception of a Positioning Capability Request component, but before responding with a Positioning
Capability Response or a Protocol Error component, the MS receives a new RRLP message with the Positioning
Capability Request component, it acts as follows:
- if the old and new Positioning Capability Request components have the same Reference Number and the same
Extended Reference IE, the MS ignores the later component;
- if the old and new Positioning Capability Request components have different Reference Numbers or different
Extended Reference IEs, the MS aborts activity for the former component, starts to act according to the later
component and sends a response to that.
When after the reception of an Measure Position Response component, the SMLC receives a new RRLP message with
the Measure Position Response component, it acts as follows:
- if the old and new Measure Position Response components have the same Reference Number and, if included,
the same Extended Reference IE values, the SMLC may ignore the later component;
2.5.6 (void)
2.5.7 Missing Component
When the SMLC sends a Measure Position Request component to the MS, it starts a timer. If the timer expires before
the SMLC receives the last Measure Position Response component or a Protocol Error component from the MS with
the same Reference Number and, if included, the same Extended Reference IE value as in the sent component, it may
abort location attempt or send a new Measure Position Request.
When the SMLC receives a Measure Position Response component with the same Reference Number and, if included,
the same Extended Reference IE value as in the sen
...