7 LCS-AP Messages and Message Formats

29.1713GPPLCS Application Protocol (LCS-AP) between the Mobile Management Entity (MME) and Evolved Serving Mobile Location Centre (E-SMLC)Location Services (LCS)Release 17SLs interfaceTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

7.1 General

This clause describes the structure of the messages and information elements required for the LCS-AP messages.

7.2 Message Formats

LCS-AP ASN.1 definition conforms to ITU-T Recommendations ITU-T Recommendation X.680 (07/2002) [8] and ITU-T Recommendation X.681 (07/2002) [9]. The ASN.1 definition specifies the structure and content of LCS-AP messages. The LCS-AP messages may contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a LCS-AP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids):

– IEs shall be ordered (in an IE container) in the order they appear in object set definitions.

– Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements.

If a LCS-AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error.

For the handling of unknown, unforeseen and erroneous protocol data, please refer to 3GPP TS 36.413 [7].

7.3 LCS-AP Messages

The following attributes are used for the tabular description of the messages and information elements: Presence, Range Criticality and Assigned Criticality. Their definition and use can be found in 3GPP TS 36.413 [7].

7.3.1 LCS-AP Location Request message

This message is sent by the MME to request a location estimate for a target UE and contains sufficient information to enable location according to the required QoS using any positioning method supported. The message is also used to request LCS assistance data transfer to an UE.

Direction: MME → E-SMLC

Table 7.3.1-1: Location Request message contents

IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		7.4.2		YES	reject
Correlation ID	M		7.4.28		YES	reject
Location Type	M		7.4.3		YES	reject
E-UTRAN Cell Identifier	M		E-CGI / 7.4.4		YES	ignore
LCS Client Type	O		7.4.5		YES	reject
LCS Priority	O		7.4.6		YES	reject
LCS QoS	O		7.4.7		YES	reject
LCS Service Type ID	O		7.4.30		YES	ignore
UE Positioning Capability	O		7.4.8		YES	reject
Include Velocity	O		7.4.9		YES	reject
IMSI	O		7.4.10		YES	ignore
IMEI	O		7.4.11		YES	ignore
Multiple APDUs		0..3
APDU	M		7.4.18		YES	reject
RAT Type	O		7.4.34		YES	ignore
Coverage Level	O		7.4.35		YES	ignore
UE Country Determination Indication	O		7.4.47		YES	ignore
NOTE: The IMSI should be sent preferably if known. The IMEI may be sent if the IMSI is not known, or in addition to the IMSI for the purpose of allowing correlation between the two identities.

7.3.2 LCS-AP Location Response message

This message is sent in response to a LCS-AP Location Request to return a successful location estimate for a target UE or to indicate some failure in obtaining this. The message is also sent in response to a LCS-AP Location Request to return an indication that LCS assistance data has been successfully delivered to an UE.

Direction: E-SMLC → MME

Table 7.3.2-1: Location Response message contents

IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		7.4.2		YES	reject
Correlation ID	M		7.4.28		YES	reject
Location Estimate	O		Geographic Area / 7.4.12		YES	reject
Positioning Data	O		7.4.13		YES	reject
Velocity Estimate	O		7.4.14		YES	reject
Accuracy Fulfilment Indicator	O		7.4.15		YES	reject
LCS Cause	O		7.4.16		YES	ignore
E-UTRAN Cell Identifier	O		E-CGI / 7.4.4		YES	ignore
Cell Portion ID	O		7.4.31		YES	ignore
Civic Address	O		7.4.32		YES	ignore
Barometric Pressure	O		7.4.33		YES	ignore
UE Area Indication	O		7.4.48		YES	ignore

7.3.3 LCS-AP Location Abort Request message

This message is sent by the MME to abort the positioning attempt or the request for assistance data.

Direction: MME → E-SMLC

Table 7.3.3-1: Location Abort Request message contents

IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		7.4.2		YES	reject
Correlation ID	M		7.4.28		YES	reject
LCS Cause	M		7.4.16		YES	ignore

7.3.4 LCS-AP Connection Oriented Information message

This message is sent in association with an existing signalling connection between an E-SMLC and another entity to transfer information between the E-SMLC and other entity belonging to a higher level protocol.

Direction: E-SMLC → MME or MME → E-SMLC

Table 7.3.4-1: Connection Oriented Information message contents

IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		7.4.2		YES	reject
Correlation ID	M		7.4.28		YES	reject
Payload Type	M		7.4.17		YES	reject
APDU	M		7.4.18		YES	reject

7.3.5 LCS-AP Connectionless Information message

This message conveys signalling information associated with a higher protocol level between an E-SMLC and another entity when there is no existing signalling connection association.

Direction: E-SMLC → MME or MME → E-SMLC

Table 7.3.5-1: Connectionless Information message contents

IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		7.4.2		YES	reject
Source Identity	M		Network Element / 7.4.19		YES	reject
Destination Identity	M		Network Element / 7.4.19		YES	reject
APDU	M		7.4.18		YES	reject
Return Error Request	O		7.4.20		YES	reject
Return Error Cause	O		7.4.21		YES	ignore

7.3.6 LCS-AP Reset Request message

This message is sent to indicate a failure in the sending entity with loss of location service transactions that were established or were being established.

Direction: E-SMLC → MME or MME → E-SMLC

Table 7.3.6-1: Reset Request message contents

IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		7.4.2		YES	reject
LCS Cause	M		7.4.16		YES	ignore

7.3.7 LCS-AP Reset Acknowledge message

This message is sent in response to a LCS-AP Reset message to indicate that references and resources associated with location service transactions towards the entity sending the LCS-AP Reset have been released.

Direction: E-SMLC → MME or MME → E-SMLC

Table 7.3.7-1: Reset Acknowledge message contents

IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		7.4.2		YES	reject

7.3.8 LCS-AP Ciphering Key Data message

This message is used by the E-SMLC to send ciphering keys for broadcast assistance data to the MME.

Direction: E-SMLC → MME

Table 7.3.8-1: Ciphering Key Data message contents

IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		7.4.2		YES	reject
Ciphering Data	M		7.4.36		YES	reject

7.3.9 LCS-AP Ciphering Key Data Result message

This message is used by the MME to indicate to the E-SMLC whether the MME was able to successfully store the ciphering data sets received from the E-SMLC in a Ciphering Data Key message.

Direction: MME → E-SMLC

Table 7.3.9-1: Ciphering Key Data Result message contents

IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		7.4.2		YES	reject
Ciphering Data Ack	C		7.4.37		YES	reject
Ciphering Data Error Report	C		7.4.38		YES	reject

7.4 Information Elements

7.4.1 General

When specifying information elements which are to be represented by bit strings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits:

– The first bit (leftmost bit) contains the most significant bit (MSB)

– The last bit (rightmost bit) contains the least significant bit (LSB)

– When importing bit strings from other specifications, the first bit of the bit string contains the first bit of the concerned information

7.4.2 Message Type

The Message Type IE uniquely identifies the message being sent. It is mandatory for all messages.

Table 7.4.2-1: Message Type

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Procedure Code

INTEGER (0..255)

"0" = LCS-AP LOCATION SERVICE REQUEST

"1" = LCS-AP CONNECTION ORIENTED INFORMATION TRANSFER

"2" = LCS-AP CONNECTIONLESS INFORMATION TRANSFER

"3" = LCS-AP LOCATION ABORT

"4" = LCS-AP RESET

"5" = LCS-AP CIPHERING KEY DATA

Type of Message

ENUMERATED (Initiating Message, Successful Outcome, Unsuccessful Outcome, …)

7.4.3 Location Type

This parameter defines the type of location information being requested.

Table 7.4.3-1: Location Type

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Location Type

ENUMERATED (geographic location, assistance information,

…,

last known location)

7.4.4 E-CGI

This parameter gives the current cell location of the target UE or the last known cell location for the case when the Location Type IE is set to last known location. The E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell.

Table 7.4.4-1: ECGI

IE/Group Name	Presence	Range	IE type and reference	Semantics description
PLMN Identity	M		7.4.27
Cell Identity	M		BIT STRING (28)	The leftmost bits of the Cell Identity correspond to the eNB ID (defined in 7.4.19).

7.4.5 LCS Client Type

This parameter defines the type of the originating LCS Client. It shall be included if the Location Type indicates a request for a location estimate and may be included in other cases to assist an SMLC to appropriately prioritize a location request.

Table 7.4.5-1: LCS Client Type

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Client Type

ENUMERATED

(Emergency Services, Value Added Services, PLMN Operator Services, Lawful Intercept Services, PLMN Operator – broadcast services, PLMN Operator – O&M, PLMN Operator – anonymous statistics, PLMN Operator – Target MS service support,

…)

Identifies the category of LCS client.

7.4.6 LCS Priority

This parameter defines the priority of the location request.

Table 7.4.6-1: LCS Priority

IE/Group Name

Presence

Range

IE type and reference

Semantics description

LCS Priority

OCTET STRING (SIZE(1))

0= highest priority

1= normal priority

all other values treated as 1

For details, refer to 3GPP TS 22.071 [10].

7.4.7 LCS QoS

This parameter provides the required Quality of Service for the LCS Request. Quality of Service may include horizontal accuracy, vertical accuracy and allowed response time.

Table 7.4.7-1: LCS QoS

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Horizontal Accuracy	O		INTEGER( 0..127)	bit 8 = 0 bits 7-1 = 7 bit Uncertainty Code defined in 3GPP TS 23.032 [6]. The horizontal location error should be less than the error indicated by the uncertainty code with 67% confidence.
Vertical Requested	O		ENUMERATED( Vertical Coordinate Is Not Requested (0), Vertical Coordinate Is Requested (1) )	Default value if this IE is not present is: Vertical Coordinate Is Not Requested (0).
Vertical Accuracy	O		INTEGER( 0..127)	bit 8 = 0 bits 7-1 = 7 bit Vertical Uncertainty Code defined in 3GPP TS 23.032 [6]. The vertical location error should be less than the error indicated by the uncertainty code with 67% confidence. If the vertical requested IE is not present or present with a value of 0, then this vertical accuracy will be ignored, if present.
Response Time	O		ENUMERATED (Low Delay(0), Delay Tolerant (1), …)	For details, refer to 3GPP TS 22.071 [10].

7.4.8 UE Positioning Capability

This parameter provides information about the LCS capabilities of the target UE.

Table 7.4.8-1: UE Positioning Capability

IE/Group Name	Presence	Range	IE Type and Reference	Semantics Description	Criticality	Assigned Criticality
LPP Support	M		BOOLEAN	Defines if the UE supports LPP or not. TRUE means supported.	–

7.4.9 Include Velocity

This parameter indicates if the Velocity of the target UE is requested in the Location Response.

Table 7.4.9-1: Include Velocity

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Velocity Indicator

ENUMERATED (requested,

not requested,

…)

Specify if Velocity of UE is requested.

7.4.10 IMSI

This parameter identifies the IMSI of the target UE.

Table 7.4.10-1: IMSI

IE/Group Name	Presence	Range	IE type and reference	Semantics description
IMSI	M		OCTET STRING (SIZE (3..8))	The number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity. It is encoded with TBCD String, two digits per octet.

7.4.11 IMEI

This parameter identifies the IMEI of the target UE.

Table 7.4.11-1: IMEI

IE/Group Name

Presence

Range

IE type and reference

Semantics description

IMEI

OCTET STRING (SIZE (8))

Refers to International Mobile Station Equipment Identity and Software Version Number (SVN) defined in TS 3GPP TS 23.003 [11].

This IE is 16 digits encoded with TBCD String, two digits per octet.

If the SVN is not present the last octet shall contain the digit 0 as filler.

If present the SVN shall be included in the last octet.

7.4.12 Geographic Area

This parameter provides a location estimate for the target UE in the case of a successful location attempt.

Table 7.4.12-1: Geographic Area

IE/Group Name	Presence	Range	IE type and reference	Semantics description
CHOICE Geographical Area
>Point				Ellipsoid point
>>Geographical Coordinates	M		7.4.23
>Point With Uncertainty				Ellipsoid point with uncertainty circle
>>Geographical Coordinates	M		7.4.23
>>Uncertainty Code	M		INTEGER ( 0..127)	The uncertainty "r" expressed in meters is derived from the "Uncertainty Code" k by r = 10x(1.1^k-1)
>Ellipsoid point with uncertainty Ellipse
>>Geographical Coordinates	M		7.4.23
>>Uncertainty Ellipse	M		7.4.24
>>Confidence	M		INTEGER ( 0..100)	In percentage
>Polygon				List of Ellipsoid points
>>Polygon Point		1..<maxnoofPoints>		The minimum number of points allowed is 3.
>>>Geographical Coordinates	M		7.4.23
>Ellipsoid point with altitude
>>Geographical Coordinates	M		7.4.23
>>Altitude and direction	M		7.4.22
>Ellipsoid point with altitude and uncertainty Ellipsoid
>>Geographical Coordinates	M		7.4.23
>>Altitude and direction	M		7.4.22
>>Uncertainty Ellipse	M		7.4.24
>>Uncertainty Altitude	M		INTEGER ( 0..127)	The uncertainty altitude "h" expressed in metres is derived from the "Uncertainty Altitude" k, by: h=45x(1.025^k-1)
>>Confidence	M		INTEGER ( 0..100)	In percentage
>Ellipsoid Arc
>>Geographical Coordinates	M		7.4.23
>>Inner radius	M		INTEGER ( 0..2¹⁶-1)	The relation between the value (N) and the radius (r) in meters it describes is 5N≤ r <5(N+1), except for N=2¹⁶-1 for which the range is extended to include all grater values of (r).
>>Uncertainty radius	M		INTEGER ( 0..127)	The uncertainty "r" is derived from the "Uncertainty radius" k by r = 10x(1.1^k-1)
>>Offset angle	M		INTEGER ( 0..179)	The relation between the value (N) and the angle (a) in degrees it describes is 2N≤ a <2(N+1)
>>Included angle	M		INTEGER ( 0..179)	The relation between the value (N) and the angle (a) in degrees it describes is 2N< a ≤2(N+1)
>>Confidence	M		INTEGER ( 0..100)
>High Accuracy Ellipsoid point with uncertainty Ellipse
>>High Accuracy Geographical Coordinates	M		7.4.41
>>High Accuracy Uncertainty Ellipse	M		7.4.42
>>Confidence	M		INTEGER ( 0..100)	In percentage
>High Accuracy Ellipsoid point with Scalable uncertainty Ellipse
>>High Accuracy Geographical Coordinates	M		7.4.41
>>High Accuracy Scalable Uncertainty Ellipse	M		7.4.45
>>Confidence	M		INTEGER ( 0..100)	In percentage
>High Accuracy Ellipsoid point with altitude and uncertainty Ellipsoid
>>High Accuracy Geographical Coordinates	M		7.4.41
>>High Accuracy Altitude	M		7.4.43
>>High Accuracy Uncertainty Ellipse	M		7.4.42
>>Confidence	M		INTEGER ( 0..100)	In percentage
>>High Accuracy Uncertainty Altitude	M		INTEGER ( 0..255)	The high accuracy uncertainty altitude "h" expressed in metres is derived from the high accuracy uncertainty code "k", by: h=0.3x(1.02^k-1)
>>Vertical Confidence	M		INTEGER ( 0..100)	In percentage
>High Accuracy Ellipsoid point with altitude and scalable uncertainty Ellipsoid
>>High Accuracy Geographical Coordinates	M		7.4.41
>>High Accuracy Altitude	M		7.4.43
>>High Accuracy Scalable Uncertainty Ellipse	M		7.4.45
>>Confidence	M		INTEGER ( 0..100)	In percentage
>>High Accuracy Scalable Uncertainty Altitude	M		7.4.46
>>Vertical Confidence	M		INTEGER ( 0..100)	In percentage

Table 7.4.12-2: Range bound

Range bound	Explanation
maxnoofPoints	Maximum no. of points in polygon. Value is 15.

7.4.13 Positioning Data

This parameter provides additional information for the positioning attempt from the E-SMLC.

Table 7.4.13-1: Positioning Data

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Position Data	M
>Positioning Data Set	O
>>Positioning Method and Usage		1..<maxSet>	OCTET STRING (1)	Coding of positioning method (bits 8-4): 00000 Cell ID 00001 Reserved 00010 E-CID 00011 Reserved 00100 OTDOA 00101 Reserved 00110 Reserved 00111 Reserved 01000 U-TDOA 01001 Reserved 01010 Reserved 01011 Reserved 01100 to 01111 reserved for other location technologies 10000 to 11111 reserved for network specific positioning methods Coding of usage (bits 3-1): 000 Attempted unsuccessfully due to failure or interruption – not used. 001 Attempted successfully: results not used to generate location – not used. 010 Attempted successfully: results used to verify but not generate location – not used. 011 Attempted successfully: results used to generate location. 100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined.
>GNSS Positioning Data Set	O
>>GNSS Positioning Method and Usage	O	1..<maxGNSSSet>	OCTET STRING (1)	Coding of Method (Bits 8-7) : 00 : UE-Based 01 : UE-Assisted 10 : Conventional 11 : Reserved Coding of GNSS ID (Bits 6-4) : 000 : GPS 001 : Galileo 010 : SBAS 011 : Modernized GPS 100 : QZSS 101 : GLONASS other values reserved Coding of usage (bits 3-1): 000 Attempted unsuccessfully due to failure or interruption 001 Attempted successfully: results not used to generate location 010 Attempted successfully: results used to verify but not generate location 011 Attempted successfully: results used to generate location 100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined.
>Additional Positioning Data Set	O
>>Additional Positioning Method and Usage		1 to <maxAddPosSet>	OCTET STRING (SIZE(1))	Coding of positioning method (bits 8-7): 00 UE-Based; 01 UE-Assisted; 10 Standalone; 11 Reserved. Coding of Additional Positioning ID (bits 6-4): 000 Barometric Pressure; 001 WLAN; 010 Bluetooth; 011 MBS; 100 Motion-Sensor(s); other values reserved. Coding of usage (bits 3-1): 000 Attempted unsuccessfully due to failure or interruption 001 Attempted successfully: results not used to generate location 010 Attempted successfully: results used to verify but not generate location 011 Attempted successfully: results used to generate location 100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined.

Table 7.4.13-2: Range bound

Range bound	Explanation
maxSet	Maximum size of the data set. Value is 9.
maxGNSSSet	Maximum size of the data. Value is 9.
maxAddPosSet	Maximum size of the data Value is 8.

7.4.14 Velocity Estimate

This parameter provides the velocity estimate for the target UE.

Table 7.4.14-1: Velocity Estimate

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Choice Velocity Estimate
>Horizontal Velocity				Horizontal speed and bearing (the direction of travel).
>>Horizontal Speed and Bearing	M		7.4.25
>Horizontal with Vertical Velocity				Horizontal speed and bearing (the direction of travel) as well as vertical speed and the direction (upward or downward)
>>Horizontal Speed and Bearing	M		7.4.25
>>Vertical Velocity	M		7.4.26
>Horizontal Velocity with Uncertainty				Horizontal speed, bearing (the direction of travel), and the uncertainty of the reported speed.
>>Horizontal Speed and Bearing	M		7.4.25
>>Uncertainty Speed	M		INTEGER (0..255)	Uncertainty speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified
>Horizontal with Vertical Velocity and Uncertainty				Horizontal speed and bearing (the direction of travel) as well as vertical speed and the direction (upward or downward) and the uncertainty of the reported speed.
>>Horizontal Speed and Bearing	M		7.4.25
>>Vertical Velocity	M		7.4.26
>>Horizontal Uncertainty Speed	M		INTEGER (0..255)	Horizontal Uncertainty Speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified
>>Vertical Uncertainty Speed	M		INTEGER (0..255)	Vertical Uncertainty Speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified

7.4.15 Accuracy Fulfilment Indicator

This parameter whether the returned position estimate satisfies the requested accuracy or not.

Table 7.4.15-1: Accuracy Fulfilment Indicator

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Accuracy Fulfilment Indicator	O		ENUMERATED (requested accuracy fulfilled, requested accuracy not fulfilled, …)	Indicates if the requested accuracy is fulfilled or not.

7.4.16 LCS Cause

The LCS Cause is included if and only if a requested location estimate was not successfully obtained (e.g. location estimate not available), requested LCS assistance data was not successfully transferred to the UE or location-related data has been lost. The parameter provides the reason for the failure.

Table 7.4.16-1: LCS Cause

IE/Group Name	Presence	Range	IE Type and Reference	Semantics Description
CHOICE Cause Group
>Radio Network Layer
>>Radio Network Layer Cause	M		ENUMERATED ( Unspecified …)
>Transport Layer
>>Transport Layer Cause	M		ENUMERATED (Transport Resource Unavailable, Unspecified, …)
>Protocol
>>Protocol Cause	M		ENUMERATED (Transfer Syntax Error, Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and Notify), Message not Compatible with Receiver State, Semantic Error, Unspecified, Abstract Syntax Error (Falsely Constructed Message), …)
>Misc
>>Misc Cause	M		ENUMERATED (Processing Overload, Hardware Failure, O&M Intervention, Unspecified, …, Ciphering Key Data Lost)

7.4.17 Payload Type

This parameter indicates the type of APDU included in LCS-AP Connected Oriented Information message. The supported information types are LPP and LPPa.

Table 7.4.17-1: Payload Type

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Payload Type

ENUMERATED

(LPP,

LPPa,

…)

7.4.18 APDU

This parameter contains an embedded APDU. For information transfer between an E-SMLC and an eNB this shall be an LPPa APDU. For information transfer between an E-SMLC and a target UE, this shall be an LPP APDU.

Table 7.4.18-1: APDU

IE/Group Name	Presence	Range	IE type and reference	Semantics description
APDU	M		OCTET STRING	This IE contains a message whose content and encoding are defined according to the Payload Type.

7.4.19 Network Element

This parameter identifies the source or destination of the message. The network element is identified by association with either an eNB ID or the identity of an E-SMLC.

Table 7.4.19-1: Network Element

IE/Group Name	Presence	Range	IE type and reference	Semantics description
CHOICE Network Element	M
>Global eNB ID				The global identity of the eNB
>>PLMN Identity			7.4.27
>>eNB ID			7.4.29
>E-SMLC Identity			INTEGER (0..255)	The identity of the E-SMLC (an index to identify an specific E-SMLC among all the available E-SMLCs in the network)

7.4.20 Return Error Request

This parameter may be included to request an error response if LCS-AP message cannot be delivered successfully to its final destination. This parameter shall not be included if the Return Error cause is present.

Table 7.4.20-1: Return Error Type

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Return Error Type

ENUMERATED (

Yes,

)

7.4.21 Return Error Cause

This parameter indicates an error response for a LCS-AP connectionless information message that could not be delivered to its final destination. The APDU should be present and the same as the APDU in the original undelivered message. The source and destination identities shall be included and the same as the destination and source identities, respectively, in the original undelivered message.

Table 7.4.21-1: Return Error Cause

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Return Error Cause	M		ENUMERATED (systemfailure, protocolerror, destinationunkown, destinationunreachable, congestion,…)

7.4.22 Altitude and direction

Table 7.4.22-1: Altitude and direction

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Direction of Altitude

ENUMERATED (Height, Depth)

Altitude

INTEGER (

0..2¹⁵-1)

The relation between the value (N) and the altitude (a) in meters it describes is N ≤ a < N+1, except for N=2¹⁵-1 for which the range is extended to include all greater values of (a).

7.4.23 Geographical Coordinates

This IE contains the geographical coordinates.

Table 7.4.23-1: Geographical Coordinates

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Latitude Sign	M		ENUMERATED (North, South)
Degrees Of Latitude	M		INTEGER ( 0..2²³-1)	The IE value (N) is derived by this formula: N2²³ X /90  N+1 X being the latitude in degree (0°.. 90°)
Degrees Of Longitude	M		INTEGER ( -2²³..2²³-1)	The IE value (N) is derived by this formula: N2²⁴ X /360  N+1 X being the longitude in degree (-180°..+180°)

7.4.24 Uncertainty Ellipse

This IE contains the uncertainty ellipse of a geographical area.

Table 7.4.24-1: Uncertainty Ellipse

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Uncertainty semi-major	M		INTEGER (0..127)	The uncertainty "r" is derived from the "uncertainty code" k by r = 10x(1.1^k-1)
Uncertainty semi-minor	M		INTEGER (0..127)	The uncertainty "r" is derived from the "uncertainty code" k by r = 10x(1.1^k-1)
Orientation of major axis	M		INTEGER (0..89)	The relation between the IE value (N) and the angle (a) in degrees it describes is 2N≤ a <2(N+1)

7.4.25 Horizontal Speed and Bearing

This IE contains the two components of horizontal velocity: speed and bearing

Table 7.4.25-1: Horizontal Speed and Bearing

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Bearing

INTEGER

(0..359)

The direction of movement is given in degrees where ‘0’ represents North, ’90’ represents East, etc.

Horizontal Speed

INTEGER

(0..< 2¹¹-1)

The relationship between (N) and the horizontal speed (h) in kilometers per hour it describes is:

N ≤ h < N + 0.5 (N=0)

N – 0.5 ≤ h < N + 0.5 (0<N<2¹¹-1)

N – 0.5 ≤ h(N = 2¹¹-1)

7.4.26 Vertical Velocity

This IE contains the two components of vertical velocity: speed and direction

Table 7.4.26-1: Vertical Velocity

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Vertical Speed

INTEGER

(0..2⁸-1)

The relationship between (N) and the vertical speed (v) in kilometers per hour it describes is:

N ≤ v < N + 0.5 (N = 0)

N – 0.5 ≤ v < N + 0.5 (0 < N < 2⁸-1)

N – 0.5 ≤ v (N = 2⁸-1)

Vertical Speed Direction

ENUMERATED (upward, downward)

7.4.27 PLMN Identity

This information element indicates the PLMN Identity.

Table 7.4.27-1: PLMN Identity

IE/Group Name

Presence

Range

IE type and reference

Semantics description

PLMN identity

OCTET STRING (SIZE (3))

– digits 0 to 9, encoded 0000 to 1001,

– 1111 used as filler digit,

two digits per octet,

– bits 4 to 1 of octet n encoding digit 2n-1

– bits 8 to 5 of octet n encoding digit 2n

-The Selected PLMN identity consists of 3 digits from MCC followed by either
-a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
-3 digits from MNC (in case of a 3 digit MNC).

7.4.28 Correlation ID

This IE indicates a specific location session. It is used in order to correlate request/response and an ongoing location session.

Table 7.4.28-1: Correlation ID

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Correlation ID	M		OCTET STRING (SIZE (4))	The identifier of a location session in E-UTRAN. It should be unique for all concurrently active location sessions in a particular MME.

7.4.29 eNB ID

This information element is used to identify an eNB.

Table 7.4.29-1: eNB ID

IE/Group Name	Presence	Range	IE type and reference	Semantics description
CHOICE eNB ID
>Macro eNB ID	M		BIT STRING (20)	Equal to the 20 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see clause 7.4.4) of each cell served by the eNB
>Home eNB ID	M		BIT STRING (28)	Equal to the Cell Identity IE contained in the E-UTRAN CGI IE (see clause 7.4.4) of the cell served by the eNB
>Short Macro eNB ID	M		BIT STRING (18)	Equal to the 18 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see clause 7.4.4) of each cell served by the eNB
>Long Macro eNB ID	M		BIT STRING (21)	Equal to the 21 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see clause 7.4.4) of each cell served by the eNB

7.4.30 LCS Service Type ID

This parameter defines the service type ID for the location request.

Table 7.4.30-1: LCS Service Type ID

IE/Group Name

Presence

Range

IE type and reference

Semantics description

LCS Service Type ID

INTEGER(

0..127)

Identifies the type of service requested. The meaning of the different service types is defined in 3GPP TS 22.071 [10].

7.4.31 Cell Portion ID

This parameter gives the current Cell Portion location of the target UE. The Cell Portion ID is the unique identifier for a cell portion within a cell.

Table 7.4.31-1: Cell Portion

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Cell Portion ID	M		INTEGER (0..255,…, 256..4095)

7.4.32 Civic Address

This information element contains a location estimate for the target UE expressed as a Civic address.

Table 7.4.32-1: Civic Address

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Civic Address	O		OCTET STRING	This IE contains a UTF-8 encoded PIDF-LO XML document as defined in IETF RFC 4119 [13]. The document shall only contain a civic address using the namespaces "urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" per IETF RFC 5139 [14] and "urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr:ext" per IETF RFC 6848 [15].

7.4.33 Barometric Pressure

This information element contains the barometric pressure measurement as reported by the target UE.

Table 7.4.33-1: Barometric Pressure

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Barometric Pressure	O		INTEGER (30000..115000)	This IE specifies the measured uncompensated atmospheric pressure in units of Pascal (Pa).

7.4.34 RAT Type

This parameter provides the serving RAT type for the target UE or the last known serving RAT type for the case when the Location Type IE is set to last known location.

Table 7.4.34-1: RAT Type

IE/Group Name	Presence	Range	IE type and reference	Semantics description
RAT Type	O		ENUMERATED (lte-wb, nb-iot, lte-m, …)	This IE provides the serving RAT type.

7.4.35 Coverage Level

This parameter defines the type of coverage level being requested.

Table 7.4.35-1: Coverage Level

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Coverage Level

ENUMERATED (Extended Coverage,

…)

7.4.36 Ciphering Data

This parameter contains the ciphering data sets sent by the E-SMLC to the MME.

Table 7.4.36-1: Ciphering Data

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Ciphering Data	M
>Ciphering Data Set	M	1..<maxCipherSet>	7.4.39

Table 7.4.36-2: Range bound

Range bound	Explanation
maxCipherSet	Maximum size of the data set. Value is 16

7.4.37 Ciphering Data Ack

This parameter contains the ciphering data acknowledgement information sent by the MME to the E-SMLC.

Table 7.4.37-1: Ciphering Data Ack

IE/Group Name

Presence

Range

IE type and reference

Semantics description

Ciphering Data Ack

This IE contains the list of ciphering set IDs for which the MME is sending an acknowledgement

>Ciphering Set ID

1..<maxCipherSet>

INTEGER

(0..65535)

Table 7.4.37-2: Range bound

Range bound	Explanation
maxCipherSet	Maximum size of the data set. Value is 16

7.4.38 Ciphering Data Error Report

This parameter contains a list of ciphering data sets with the associated outcome of storage attempt at the MME.

Table 7.4.38-1: Ciphering Data Error Report

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Ciphering Data Error Report	M
>Ciphering Data Error Report Contents	M	1..<maxCipherSet>	7.4.40

Table 7.4.38-2: Range bound

Range bound	Explanation
maxCipherSet	Maximum size of the data set. Value is 16

7.4.39 Ciphering Data Set

This parameter contains a ciphering data set sent by the E-SMLC to the MME.

Table 7.4.39-1: Ciphering Data Set

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Ciphering Data Set	M
>Ciphering Set ID	M		INTEGER (0..65535)
>Ciphering Key	M		OCTET STRING (SIZE(16))
>c0	M		BIT STRING (SIZE (1..128))
>SIB Types	M		OCTET STRING (SIZE(4))	This IE contains a bitmap indicating the positioning SIB types for which the ciphering data set is applicable: — a bit set to 0 indicates that the ciphering data set is not applicable to the corresponding positioning SIB type – a bit set to 1 indicates that the ciphering data set is applicable to the corresponding positioning SIB type The mapping of the bits to the positioning SIB types is as follows: — bit 8 in the first octet maps to positioning SIB Type 1-1 — bit 7 in the first octet maps to positioning SIB Type 1-2 — bit 6 in the first octet maps to positioning SIB Type 1-3 — bit 5 in the first octet maps to positioning SIB Type 1-4 — bit 4 in the first octet maps to positioning SIB Type 1-5 — bit 3 in the first octet maps to positioning SIB Type 1-6 — bit 2 in the first octet maps to positioning SIB Type 1-7 — bit 1 in the first octet maps to positioning SIB Type 2-1 — bit 8 in the second octet maps to positioning SIB Type 2-2 — bit 7 in the second octet maps to positioning SIB Type 2-3 — bit 6 in the second octet maps to positioning SIB Type 2-4 — bit 5 in the second octet maps to positioning SIB Type 2-5 — bit 4 in the second octet maps to positioning SIB Type 2-6 — bit 3 in the second octet maps to positioning SIB Type 2-7 — bit 2 in the second octet maps to positioning SIB Type 2-8 — bit 1 in the second octet maps to positioning SIB Type 2-9 — bit 8 in the third octet maps to positioning SIB Type 2-10 — bit 7 in the third octet maps to positioning SIB Type 2-11 — bit 6 in the third octet maps to positioning SIB Type 2-12 — bit 5 in the third octet maps to positioning SIB Type 2-13 — bit 4 in the third octet maps to positioning SIB Type 2-14 — bit 3 in the third octet maps to positioning SIB Type 2-15 — bit 2 in the third octet maps to positioning SIB Type 2-16 — bit 1 in the third octet maps to positioning SIB Type 2-17 — bit 8 in the fourth octet maps to positioning SIB Type 2-18 — bit 7 in the fourth octet maps to positioning SIB Type 2-19 — bit 6 in the fourth octet maps to positioning SIB Type 3-1 Bits 5 to 1 in the fourth octets are spare and shall be coded as zero.
>SIB Types Ext	O		OCTET STRING (SIZE(4))	This IE contains extension of the bitmap SIB Types indicating the positioning SIB types for which the ciphering data set is applicable: — a bit set to 0 indicates that the ciphering data set is not applicable to the corresponding positioning SIB type — a bit set to 1 indicates that the ciphering data set is applicable to the corresponding positioning SIB type The mapping of the bits to the positioning SIB types is as follows: — bit 8 in the first octet maps to positioning SIB Type 1-8 — bit 7 in the first octet maps to positioning SIB Type 2-20 — bit 6 in the first octet maps to positioning SIB Type 2-21 — bit 5 in the first octet maps to positioning SIB Type 2-22 — bit 4 in the first octet maps to positioning SIB Type 2-23 — bit 3 in the first octet maps to positioning SIB Type 2-24 — bit 2 in the first octet maps to positioning SIB Type 2-25 Any unassigned bits are spare and shall be coded as zero. In the absence of this IE, the ciphering data set is not applicable for any of the positioning SIB types mapped by this IE.
>Validity Start time	M		OCTET STRING (SIZE(4))	This IE contains the UTC time when the ciphering data set becomes valid, encoded in the same format as the first four octets of the 64-bit timestamp format as defined in clause 6 of IETF RFC 5905 [16].
>Validity Duration	M		INTEGER (0..65535)	In minutes
>TAIs List	O		OCTET STRING (SIZE (7..97))	This IE contains the TAIs of the tracking areas for which the ciphering data set is applicable. It is encoded as octets 2 to n of the Tracking area identity list IE specified in clause 9.9.3.33 of 3GPP TS 24.301 [17]. If this IE is omitted, the ciphering data set is valid in the entire PLMN.

7.4.40 Ciphering Data Error Report Contents

This parameter contains a ciphering data set ID with the associated outcome of storage attempt at the MME.

Table 7.4.40-1: Ciphering Data Error Report Contents

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Ciphering Data Error Report Contents	M
>Ciphering Set ID	M		INTEGER (0..65535)	This IE contains the list of ciphering set IDs for which the MME is sending an acknowledgement
>Storage outcome	M		ENUMERATED ( Successful, Failed )

7.4.41 High Accuracy Geographical Coordinates

This IE contains the high accuracy geographical coordinates.

Table 7.4.41-1: High Accuracy Geographical Coordinates

IE/Group Name

Presence

Range

IE type and reference

Semantics description

High Accuracy Degrees Of Latitude

INTEGER (

-2³¹..2³¹-1)

The IE value (N) is derived by this formula:

N = 2³¹ X /90

X being the latitude in degree (-90°.. +90°)

High Accuracy Degrees Of Longitude

INTEGER (

-2³¹..2³¹-1)

The IE value (N) is derived by this formula:

N = 2³¹ X /180

X being the longitude in degree (-180°..+180°)

7.4.42 High Accuracy Uncertainty Ellipse

This IE contains the high accuracy uncertainty ellipse of a geographical area, using the range (0..255) for high-accuracy uncertainty code "k", as specified in 3GPP TS 23.032 [6].

Table 7.4.42-1: High Accuracy Uncertainty Ellipse

IE/Group Name	Presence	Range	IE type and reference	Semantics description
High Accuracy Uncertainty semi-major	M		INTEGER (0..255)	The high accuracy uncertainty "r" is derived from the high accuracy uncertainty code "k" by: r = 0.3x(1.02^k-1)
High Accuracy Uncertainty semi-minor	M		INTEGER (0..255)	The high accuracy uncertainty "r" is derived from the high accuracy uncertainty code "k" by: r = 0.3x(1.02^k-1)
Orientation of major axis	M		INTEGER (0..179)	Angle in degrees between the major axis and north

7.4.43 High Accuracy Altitude

Table 7.44.3-1: High Accuracy Altitude

IE/Group Name	Presence	Range	IE type and reference	Semantics description
High Accuracy Altitude	M		INTEGER (-64000..1280000)	The relation between the IE value (N) and the altitude a (in metres) it encodes is described by the following equation: a=N x 2^-7

7.4.44 High Accuracy Extended Uncertainty Ellipse

This IE contains the high accuracy extended uncertainty ellipse of a geographical area, using the range (0..255) for High Accuracy Extended Uncertainty code "k", as specified in 3GPP TS 23.032 [6].

Table 7.4.44-1: High Accuracy Extended Uncertainty Ellipse

IE/Group Name	Presence	Range	IE type and reference	Semantics description
High Accuracy Extended Uncertainty semi-major	M		INTEGER (0..255)	The high accuracy extended uncertainty "r" is derived from the high accuracy extended uncertainty code "k", as specified in 3GPP TS 23.032 [6]
High Accuracy Extended Uncertainty semi-minor	M		INTEGER (0..255)	The high accuracy extended uncertainty "r" is derived from the high accuracy extended uncertainty code "k", as specified in 3GPP TS 23.032 [6]
Orientation of major axis	M		INTEGER (0..179)	Angle in degrees between the major axis and north

7.4.45 High Accuracy Scalable Uncertainty Ellipse

Table 7.4.45-1: High Accuracy Scalable Uncertainty Ellipse

IE/Group Name	Presence	Range	IE type and reference	Semantics description
CHOICE High Accuracy Scalable Uncertainty Ellipse
>High Accuracy Uncertainty Ellipse	M		7.4.42
>High Accuracy Extended Uncertainty Ellipse	M		7.4.44

7.4.46 High Accuracy Scalable Uncertainty Altitude

Table 7.4.46-1: High Accuracy Scalable Uncertainty Altitude

IE/Group Name	Presence	Range	IE type and reference	Semantics description
CHOICE High Accuracy Scalable Uncertainty Altitude
>High Accuracy Uncertainty Altitude	M		INTEGER ( 0..255)	The high accuracy uncertainty altitude "h" expressed in metres is derived from the high accuracy uncertainty code "k", by: h=0.3x(1.02^k-1)
>High Accuracy Extended Uncertainty Altitude	M		INTEGER ( 0..255)	The high accuracy extended uncertainty "r" is derived from the high accuracy extended uncertainty code "k", as specified in 3GPP TS 23.032 [6]

7.4.47 UE Country Determination Indication

This parameter indicates whether the determining of geographical area identified by the country, area within a country or international area where UE is located for PLMN selection verification is required or not.

Table 7.4.47-1: UE Country Determination Indication

IE/Group Name	Presence	Range	IE type and reference	Semantics description
UE Country Determination Indication	O		ENUMERATED (required, not required, …)	Indicates if the determining of geographical area identified by the country, area within a country or international area where UE is located for PLMN selection verification is required or not.

7.4.48 UE Area Indication

This parameter contains a country, area within a country or international area indication where UE is located.

Table 7.4.48-1: UE Area Indication

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Country	O		OCTET STRING	Includes the country or the area of country where the UE is located. This IE contains two-letter ISO 3166 country code in capital ASCII letters, e.g., DE or US. IETF RFC 4776 [18]
International Area Indication	O		ENUMERATED ( Yes, …)	Indicates the UE is located in international area.
NOTE: Either Country or International Area Indication shall be present.

7.5 Message and information element abstract syntax

7.5.1 General

LCS-AP ASN.1 definition conforms to [8] and [9].

The ASN.1 definition specifies the structure and content of LCS-AP messages. LCS-AP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a LCS-AP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids):

– IEs shall be ordered (in an IE container) in the order they appear in object set definitions.

If a LCS-AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error in clause 10 of [7].

7.5.2 Usage of protocol extension mechanism for non-standard use

The protocol extension mechanism for non-standard use may be used:

– for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multi-vendor interoperability.

– by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation.

The extension mechanism shall not be used for basic functionality. Such functionality shall be standardised.

7.5.3 Elementary procedure definitions

— **************************************************************

—

— Elementary Procedure definitions

—

— **************************************************************

LCS-AP-PDU-Descriptions {

itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)

eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-PDU-Descriptions (0)}

DEFINITIONS AUTOMATIC TAGS ::=

BEGIN

— **************************************************************

—

— IE parameter types from other modules.

—

— **************************************************************

IMPORTS

Criticality,

ProcedureCode

FROM LCS-AP-CommonDataTypes

Location-Request,

Location-Response,

Location-Abort-Request,

Connection-Oriented-Information,

Connectionless-Information,

Reset-Request,

Reset-Acknowledge,

Ciphering-Key-Data,

Ciphering-Key-Data-Result

FROM LCS-AP-PDU-Contents

id-Location-Service-Request,

id-Connection-Oriented-Information-Transfer,

id-Connectionless-Information-Transfer,

id-Location-Abort,

id-Reset,

id-Ciphering-Key-Data-Delivery

FROM LCS-AP-Constants;

— **************************************************************

—

— Interface Elementary Procedure Class

—

— **************************************************************

LCS-AP-ELEMENTARY-PROCEDURE ::= CLASS {

&InitiatingMessage ,

&SuccessfulOutcome OPTIONAL,

&UnsuccessfulOutcome OPTIONAL,

&procedureCode ProcedureCode UNIQUE,

&criticality Criticality DEFAULT ignore

}

WITH SYNTAX {

INITIATING MESSAGE &InitiatingMessage

[SUCCESSFUL OUTCOME &SuccessfulOutcome]

[UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome]

PROCEDURE CODE &procedureCode

[CRITICALITY &criticality]

}

— **************************************************************

—

— Interface PDU Definition

—

— **************************************************************

LCS-AP-PDU ::= CHOICE {

initiatingMessage InitiatingMessage,

successfulOutcome SuccessfulOutcome,

unsuccessfulOutcome UnsuccessfulOutcome,

…

}

InitiatingMessage ::= SEQUENCE {

procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}),

criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}),

value LCS-AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode})

}

SuccessfulOutcome ::= SEQUENCE {

procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}),

criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}),

value LCS-AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode})

}

UnsuccessfulOutcome ::= SEQUENCE {

procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}),

criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}),

value LCS-AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode})

}

— **************************************************************

—

— Interface Elementary Procedure List

—

— **************************************************************

LCS-AP-ELEMENTARY-PROCEDURES LCS-AP-ELEMENTARY-PROCEDURE ::= {

LCS-AP-ELEMENTARY-PROCEDURES-CLASS-1 |

LCS-AP-ELEMENTARY-PROCEDURES-CLASS-2 ,

…

}

LCS-AP-ELEMENTARY-PROCEDURES-CLASS-1 LCS-AP-ELEMENTARY-PROCEDURE ::= {

location-Service-Request |

connectionless-Information-Transfer |

location-Abort |

reset |

ciphering-Key-Data-Delivery ,

…

}

LCS-AP-ELEMENTARY-PROCEDURES-CLASS-2 LCS-AP-ELEMENTARY-PROCEDURE ::= {

connection-Oriented-Information-Transfer ,

…

}

— **************************************************************

—

— Interface Elementary Procedures

—

— **************************************************************

location-Service-Request LCS-AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE Location-Request

SUCCESSFUL OUTCOME Location-Response

UNSUCCESSFUL OUTCOME Location-Response

PROCEDURE CODE id-Location-Service-Request

CRITICALITY reject

}

connection-Oriented-Information-Transfer LCS-AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE Connection-Oriented-Information

PROCEDURE CODE id-Connection-Oriented-Information-Transfer

CRITICALITY reject

}

connectionless-Information-Transfer LCS-AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE Connectionless-Information

UNSUCCESSFUL OUTCOME Connectionless-Information

PROCEDURE CODE id-Connectionless-Information-Transfer

CRITICALITY reject

}

location-Abort LCS-AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE Location-Abort-Request

SUCCESSFUL OUTCOME Location-Response

PROCEDURE CODE id-Location-Abort

CRITICALITY reject

}

reset LCS-AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE Reset-Request

SUCCESSFUL OUTCOME Reset-Acknowledge

PROCEDURE CODE id-Reset

CRITICALITY reject

}

ciphering-Key-Data-Delivery LCS-AP-ELEMENTARY-PROCEDURE ::= {

INITIATING MESSAGE Ciphering-Key-Data

SUCCESSFUL OUTCOME Ciphering-Key-Data-Result

UNSUCCESSFUL OUTCOME Ciphering-Key-Data-Result

PROCEDURE CODE id-Ciphering-Key-Data-Delivery

CRITICALITY reject

}

END

7.5.4 PDU definitions

— **************************************************************

—

— PDU definitions for LCS-AP.

—

— **************************************************************

LCS-AP-PDU-Contents {

itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)

eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-PDU-Contents (1)}

DEFINITIONS AUTOMATIC TAGS ::=

BEGIN

— **************************************************************

—

— IE parameter types from other modules.

—

— **************************************************************

IMPORTS

APDU,

Accuracy-Fulfillment-Indicator,

Barometric-Pressure,

Cell-Portion-ID,

Ciphering-Data,

Ciphering-Data-Ack,

Ciphering-Data-Error-Report,

Civic-Address,

Correlation-ID,

Coverage-Level,

E-CGI,

Geographical-Area,

IMSI,

IMEI,

Include-Velocity,

LCS-Cause,

LCS-Client-Type,

LCS-Service-Type-ID,

LCS-Priority,

LCS-QoS,

Location-Type,

MultipleAPDUs,

Network-Element,

Payload-Type,

Positioning-Data,

RAT-Type,

Return-Error-Type,

Return-Error-Cause,

UE-Positioning-Capability,

Velocity-Estimate,

UE-Country-Determination-Indication,

UE-Area-Indication

FROM LCS-AP-IEs

ProtocolExtensionContainer{},

ProtocolIE-Container{},

LCS-AP-PROTOCOL-EXTENSION,

LCS-AP-PROTOCOL-IES

FROM LCS-AP-Containers

id-Accuracy-Fulfillment-Indicator,

id-APDU,

id-Barometric-Pressure,

id-Cell-Portion-ID,

id-Ciphering-Data,

id-Ciphering-Data-Ack,

id-Ciphering-Data-Error-Report,

id-Civic-Address,

id-Correlation-ID,

id-Coverage-Level,

id-Destination-ID,

id-E-UTRAN-Cell-Identifier,

id-Include-Velocity,

id-IMEI,

id-IMSI,

id-LCS-Client-Type,

id-LCS-Priority,

id-LCS-QOS,

id-LCS-Cause,

id-LCS-Service-Type-ID,

id-Location-Estimate,

id-Location-Type,

id-MultipleAPDUs,

id-Payload-Type,

id-Positioning-Data,

id-RAT-Type,

id-Return-Error-Request,

id-Return-Error-Cause,

id-Source-Identity,

id-UE-Positioning-Capability,

id-Velocity-Estimate,

id-UE-Country-Determination-Indication,

id-UE-Area-Indication

FROM LCS-AP-Constants;

— **************************************************************

—

— Location-Request

—

— **************************************************************

Location-Request ::= SEQUENCE {

protocolIEs ProtocolIE-Container { { Location-Request-IEs} },

protocolExtensions ProtocolExtensionContainer { { Location-Request-Extensions} } OPTIONAL,

…

}

Location-Request-IEs LCS-AP-PROTOCOL-IES ::= {

{ ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE mandatory } |

{ ID id-Location-Type CRITICALITY reject TYPE Location-Type PRESENCE mandatory } |

{ ID id-E-UTRAN-Cell-Identifier CRITICALITY ignore TYPE E-CGI PRESENCE mandatory } |

{ ID id-LCS-Client-Type CRITICALITY reject TYPE LCS-Client-Type PRESENCE optional } |

{ ID id-LCS-Priority CRITICALITY reject TYPE LCS-Priority PRESENCE optional } |

{ ID id-LCS-QOS CRITICALITY reject TYPE LCS-QoS PRESENCE optional } |

{ ID id-UE-Positioning-Capability CRITICALITY reject TYPE UE-Positioning-Capability PRESENCE optional } |

{ ID id-Include-Velocity CRITICALITY reject TYPE Include-Velocity PRESENCE optional } |

{ ID id-IMSI CRITICALITY ignore TYPE IMSI PRESENCE optional } |

{ ID id-IMEI CRITICALITY ignore TYPE IMEI PRESENCE optional } |

{ ID id-MultipleAPDUs CRITICALITY reject TYPE MultipleAPDUs PRESENCE optional } |

{ ID id-RAT-Type CRITICALITY ignore TYPE RAT-Type PRESENCE optional } |

{ ID id-Coverage-Level CRITICALITY ignore TYPE Coverage-Level PRESENCE optional},

…

}

Location-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {

{ ID id-LCS-Service-Type-ID CRITICALITY ignore EXTENSION LCS-Service-Type-ID PRESENCE optional } |

{ ID id-UE-Country-Determination-Indication CRITICALITY ignore TYPE UE-Country-Determination-Indication PRESENCE optional},

…

}

— **************************************************************

—

— Location-Response

—

— **************************************************************

Location-Response ::= SEQUENCE {

protocolIEs ProtocolIE-Container { {Location-Response-IEs} },

protocolExtensions ProtocolExtensionContainer { {Location-Response-Extensions} } OPTIONAL,

…

}

Location-Response-IEs LCS-AP-PROTOCOL-IES ::= {

{ ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE mandatory } |

{ ID id-Location-Estimate CRITICALITY reject TYPE Geographical-Area PRESENCE optional } |

{ ID id-Positioning-Data CRITICALITY reject TYPE Positioning-Data PRESENCE optional } |

{ ID id-Velocity-Estimate CRITICALITY reject TYPE Velocity-Estimate PRESENCE optional } |

{ ID id-Accuracy-Fulfillment-Indicator CRITICALITY reject TYPE Accuracy-Fulfillment-Indicator PRESENCE optional } |

{ ID id-LCS-Cause CRITICALITY ignore TYPE LCS-Cause PRESENCE optional } ,

…

}

Location-Response-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {

{ ID id-E-UTRAN-Cell-Identifier CRITICALITY ignore EXTENSION E-CGI PRESENCE optional } |

{ ID id-Cell-Portion-ID CRITICALITY ignore EXTENSION Cell-Portion-ID PRESENCE optional } |

{ ID id-Civic-Address CRITICALITY ignore EXTENSION Civic-Address PRESENCE optional } |

{ ID id-Barometric-Pressure CRITICALITY ignore EXTENSION Barometric-Pressure PRESENCE optional } |

{ ID id-UE-Area-Indication CRITICALITY ignore EXTENSION UE-Area-Indication PRESENCE optional },

…

}

— **************************************************************

—

— Location-Abort

—

— **************************************************************

Location-Abort-Request ::= SEQUENCE {

protocolIEs ProtocolIE-Container { {Location-Abort-Request-IEs} },

protocolExtensions ProtocolExtensionContainer { {Location-Abort-Request-Extensions} } OPTIONAL,

…

}

Location-Abort-Request-IEs LCS-AP-PROTOCOL-IES ::= {

{ ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE mandatory } |

{ ID id-LCS-Cause CRITICALITY ignore TYPE LCS-Cause PRESENCE mandatory } ,

…

}

Location-Abort-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

— **************************************************************

—

— Connection-Oriented-Information

—

— **************************************************************

Connection-Oriented-Information ::= SEQUENCE {

protocolIEs ProtocolIE-Container { {Connection-Oriented-Information-IEs} },

protocolExtensions ProtocolExtensionContainer { {Connection-Oriented-Information-Extensions} } OPTIONAL,

…

}

Connection-Oriented-Information-IEs LCS-AP-PROTOCOL-IES ::= {

{ ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE optional } |

{ ID id-Payload-Type CRITICALITY reject TYPE Payload-Type PRESENCE optional } |

{ ID id-APDU CRITICALITY reject TYPE APDU PRESENCE optional } ,

…

}

Connection-Oriented-Information-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

— **************************************************************

—

— Connectionless-Information

—

— **************************************************************

Connectionless-Information ::= SEQUENCE {

protocolIEs ProtocolIE-Container { {Connectionless-Information-IEs} },

protocolExtensions ProtocolExtensionContainer { {Connectionless-Information-Extensions} } OPTIONAL,

…

}

Connectionless-Information-IEs LCS-AP-PROTOCOL-IES ::= {

{ ID id-Source-Identity CRITICALITY reject TYPE Network-Element PRESENCE mandatory } |

{ ID id-Destination-ID CRITICALITY reject TYPE Network-Element PRESENCE mandatory } |

{ ID id-APDU CRITICALITY reject TYPE APDU PRESENCE mandatory } |

{ ID id-Return-Error-Request CRITICALITY reject TYPE Return-Error-Type PRESENCE optional } |

{ ID id-Return-Error-Cause CRITICALITY ignore TYPE Return-Error-Cause PRESENCE optional } ,

…

}

Connectionless-Information-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

— **************************************************************

—

— Reset-Request

—

— **************************************************************

Reset-Request ::= SEQUENCE {

protocolIEs ProtocolIE-Container { {Reset-Request-IEs} },

protocolExtensions ProtocolExtensionContainer { {Reset-Request-Extensions} } OPTIONAL,

…

}

Reset-Request-IEs LCS-AP-PROTOCOL-IES ::= {

{ ID id-LCS-Cause CRITICALITY ignore TYPE LCS-Cause PRESENCE mandatory } ,

…

}

Reset-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

— **************************************************************

—

— Reset-Acknowledge

—

— **************************************************************

Reset-Acknowledge ::= SEQUENCE {

protocolIEs ProtocolIE-Container { { Reset-Acknowledge-IEs} },

protocolExtensions ProtocolExtensionContainer { { Reset-Acknowledge-Extensions} } OPTIONAL,

…

}

Reset-Acknowledge-IEs LCS-AP-PROTOCOL-IES ::= {

…

}

Reset-Acknowledge-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

— **************************************************************

—

— Ciphering-Key-Data

—

— **************************************************************

Ciphering-Key-Data ::= SEQUENCE {

protocolIEs ProtocolIE-Container { {Ciphering-Key-Data-IEs} },

protocolExtensions ProtocolExtensionContainer { {Ciphering-Key-Data-Extensions} } OPTIONAL,

…

}

Ciphering-Key-Data-IEs LCS-AP-PROTOCOL-IES ::= {

{ ID id-Ciphering-Data CRITICALITY reject TYPE Ciphering-Data PRESENCE mandatory } ,

…

}

Ciphering-Key-Data-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

— **************************************************************

—

— Ciphering-Key-Data-Result

—

— **************************************************************

Ciphering-Key-Data-Result ::= SEQUENCE {

protocolIEs ProtocolIE-Container { {Ciphering-Key-Data-Result-IEs} },

protocolExtensions ProtocolExtensionContainer { {Ciphering-Key-Data-Result-Extensions} } OPTIONAL,

…

}

Ciphering-Key-Data-Result-IEs LCS-AP-PROTOCOL-IES ::= {

{ ID id-Ciphering-Data-Ack CRITICALITY reject TYPE Ciphering-Data-Ack PRESENCE conditional } |

{ ID id-Ciphering-Data-Error-Report CRITICALITY reject TYPE Ciphering-Data-Error-Report PRESENCE conditional } ,

…

}

Ciphering-Key-Data-Result-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

END

7.5.5 Information element definitions

— **************************************************************

—

— Information Element Definitions

—

— **************************************************************

LCS-AP-IEs {

itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)

eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-IEs (2)}

DEFINITIONS AUTOMATIC TAGS ::=

BEGIN

IMPORTS

max-No-Of-Points,

max-Set,

max-GNSS-Set,

max-Add-Pos-Set,

max-Cipher-Set,

id-Additional-PositioningDataSet

FROM LCS-AP-Constants

Criticality,

ProcedureCode,

TriggeringMessage,

ProtocolIE-ID

FROM LCS-AP-CommonDataTypes

ProtocolExtensionContainer{},

LCS-AP-PROTOCOL-EXTENSION

FROM LCS-AP-Containers;

— A

APDU ::= OCTET STRING

Accuracy-Fulfillment-Indicator ::= ENUMERATED {

requested-accuracy-fulfilled,

requested-accuracy-not-fulfilled,

…

}

Additional-PositioningDataSet ::= SEQUENCE(SIZE(1..max-Add-Pos-Set)) OF Additional-PositioningMethodAndUsage

Additional-PositioningMethodAndUsage ::= OCTET STRING (SIZE(1))

Altitude ::= INTEGER (0..65535)

— The valid value for this IE is 0 to 32767.

— Reception of value greater than 32767 shall be mapped to the value 32767.

Altitude-And-Direction ::= SEQUENCE {

direction-Of-Altitude Direction-Of-Altitude,

altitude Altitude,

…

}

Angle ::= INTEGER (0..179)

— B

Barometric-Pressure ::= INTEGER (30000..115000)

Bearing ::= INTEGER (0..359)

— C

C0 ::= BIT STRING (SIZE (1..128))

CellIdentity ::= BIT STRING (SIZE (28))

Cell-Portion-ID ::= INTEGER (0..255,…, 256..4095)

Ciphering-Data ::= SEQUENCE(SIZE(1..max-Cipher-Set)) OF Ciphering-Data-Set

Ciphering-Data-Ack ::= SEQUENCE(SIZE(1..max-Cipher-Set)) OF Ciphering-Set-ID

Ciphering-Data-Error-Report ::= SEQUENCE(SIZE(1..max-Cipher-Set)) OF Ciphering-Data-Error-Report-Contents

Ciphering-Data-Set ::= SEQUENCE {

ciphering-Set-ID Ciphering-Set-ID,

ciphering-Key Ciphering-Key,

c0 C0,

sib-Types SIB-Types,

validity-Start-Time Validity-Start-Time,

validity-Duration Validity-Duration,

tais-List TAIs-List,

…

}

Ciphering-Data-Error-Report-Contents ::= SEQUENCE {

ciphering-Set-ID Ciphering-Set-ID,

storage-Outcome Storage-Outcome,

…

}

Ciphering-Set-ID ::= INTEGER (0..65535)

Ciphering-Key ::= OCTET STRING (SIZE (16))

Civic-Address ::= OCTET STRING

Confidence ::= INTEGER (0..100)

Correlation-ID ::= OCTET STRING (SIZE (4))

Country ::= OCTET STRING

— D

DegreesLatitude ::= INTEGER (0..8388607) — 23 bit field

DegreesLongitude ::= INTEGER (-8388608..8388607) — 24 bit field

Direction-Of-Altitude ::= ENUMERATED {

height,

depth

}

— E

E-CGI ::= SEQUENCE {

pLMNidentity PLMN-ID,

cell-ID CellIdentity,

iE-Extensions ProtocolExtensionContainer { { E-CGI-ExtIEs} } OPTIONAL,

…}

E-CGI-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

Coverage-Level ::= ENUMERATED {

extendedcoverage,

…

}

Ellipsoid-Point-With-Uncertainty-Ellipse ::= SEQUENCE {

geographical-Coordinates Geographical-Coordinates,

uncertainty-Ellipse Uncertainty-Ellipse,

confidence Confidence,

iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Point-With-Uncertainty-Ellipse-ExtIEs} } OPTIONAL,

…}

Ellipsoid-Point-With-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

Ellipsoid-Point-With-Altitude ::= SEQUENCE {

geographical-Coordinates Geographical-Coordinates,

altitude-And-Direction Altitude-And-Direction,

iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Point-With-Altitude-ExtIEs} } OPTIONAL,

…}

Ellipsoid-Point-With-Altitude-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid ::= SEQUENCE {

geographical-Coordinates Geographical-Coordinates,

altitude-And-Direction Altitude-And-Direction,

uncertainty-Ellipse Uncertainty-Ellipse,

uncertainty-Altitude Uncertainty-Altitude,

confidence Confidence,

iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid-ExtIEs} } OPTIONAL,

…}

Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

Ellipsoid-Arc ::= SEQUENCE {

geographical-Coordinates Geographical-Coordinates,

inner-Radius Inner-Radius,

uncertainty-Radius Uncertainty-Code,

offset-Angle Angle,

included-Angle Angle,

confidence Confidence,

iE-Extensions ProtocolExtensionContainer { { Ellipsoid-Arc-ExtIEs} } OPTIONAL,

…

}

Ellipsoid-Arc-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

ENB-ID ::= CHOICE {

macro-eNB-ID Macro-eNB-ID,

home-eNB-ID Home-eNB-ID,

…,

short-macro-eNB-ID Short-Macro-eNB-ID,

long-macro-eNB-ID Long-Macro-eNB-ID

}

E-SMLC-ID ::= INTEGER (0..255)

— F

— G

Geographical-Area ::= CHOICE {

point Point,

point-With-Uncertainty Point-With-Uncertainty,

ellipsoidPoint-With-Uncertainty-Ellipse Ellipsoid-Point-With-Uncertainty-Ellipse,

polygon Polygon,

ellipsoid-Point-With-Altitude Ellipsoid-Point-With-Altitude,

ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid,

ellipsoid-Arc Ellipsoid-Arc,

…,

high-Accuracy-Ellipsoid-Point-With-Uncertainty-Ellipse High-Accuracy-Ellipsoid-Point-With-Uncertainty-Ellipse,

high-Accuracy-Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid High-Accuracy-Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid,

high-Accuracy-Ellipsoid-Point-With-Scalable-Uncertainty-Ellipse High-Accuracy-Ellipsoid-Point-With-Scalable-Uncertainty-Ellipse,

high-Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid High-Accuracy- Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid

}

Geographical-Coordinates ::= SEQUENCE {

latitudeSign LatitudeSign,

degreesLatitude DegreesLatitude,

degreesLongitude DegreesLongitude,

iE-Extensions ProtocolExtensionContainer { {Geographical-Coordinates-ExtIEs} } OPTIONAL,

…

}

Geographical-Coordinates-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

Global-eNB-ID ::= SEQUENCE {

pLMN-ID PLMN-ID,

eNB-ID ENB-ID

}

GNSS-Positioning-Method-And-Usage ::= OCTET STRING (SIZE (1))

GNSS-Positioning-Data-Set ::= SEQUENCE (SIZE (1..max-GNSS-Set)) OF GNSS-Positioning-Method-And-Usage

— H

High-Accuracy-Altitude ::= INTEGER (-64000..1280000)

High-Accuracy-DegreesLatitude ::= INTEGER(-2147483648..2147483647)

High-Accuracy-DegreesLongitude ::= INTEGER(-2147483648..2147483647)

High-Accuracy-Ellipsoid-Point-With-Uncertainty-Ellipse ::= SEQUENCE {

high-Accuracy-Geographical-Coordinates High-Accuracy-Geographical-Coordinates,

high-Accuracy-Uncertainty-Ellipse High-Accuracy-Uncertainty-Ellipse,

confidence Confidence,

iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Uncertainty-Ellipse-ExtIEs} } OPTIONAL,

…}

High-Accuracy-Ellipsoid-Point-With-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

High-Accuracy-Ellipsoid-Point-With-Scalable-Uncertainty-Ellipse ::= SEQUENCE {

high-Accuracy-Geographical-Coordinates High-Accuracy-Geographical-Coordinates,

high-Accuracy-Scalable-Uncertainty-Ellipse High-Accuracy-Scalable-Uncertainty-Ellipse,

confidence Confidence,

iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Scalable-Uncertainty-Ellipse-ExtIEs} } OPTIONAL,

…}

High-Accuracy-Ellipsoid-Point-With-Scalable-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

High-Accuracy-Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid ::= SEQUENCE {

high-Accuracy-Geographical-Coordinates High-Accuracy-Geographical-Coordinates,

high-Accuracy-Altitude High-Accuracy-Altitude,

high-Accuracy-Uncertainty-Ellipse High-Accuracy-Uncertainty-Ellipse,

confidence Confidence,

high-Accuracy-Uncertainty-Altitude High-Accuracy-Uncertainty-Code,

vertical-Confidence Confidence,

iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid-ExtIEs} } OPTIONAL,

…}

High-Accuracy-Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

High-Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid ::= SEQUENCE {

high-Accuracy-Geographical-Coordinates High-Accuracy-Geographical-Coordinates,

high-Accuracy-Altitude High-Accuracy-Altitude,

high-Accuracy-Scalable-Uncertainty-Ellipse High-Accuracy-Scalable-Uncertainty-Ellipse,

confidence Confidence,

high-Accuracy-Scalable-Uncertainty-Altitude High-Accuracy-Scalable-Uncertainty-Altitude,

vertical-Confidence Confidence,

iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid-ExtIEs} } OPTIONAL,

…}

High-Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

High-Accuracy-Geographical-Coordinates ::= SEQUENCE {

high-Accuracy-DegreesLatitude High-Accuracy-DegreesLatitude,

high-Accuracy-DegreesLongitude High-Accuracy-DegreesLongitude,

iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Geographical-Coordinates-ExtIEs} } OPTIONAL,

…

}

High-Accuracy-Geographical-Coordinates-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

High-Accuracy-Uncertainty-Code ::= INTEGER (0..255)

High-Accuracy-Extended-Uncertainty-Code ::= INTEGER (0..255)

High-Accuracy-Uncertainty-Ellipse ::= SEQUENCE {

high-Accuracy-Uncertainty-SemiMajor High-Accuracy-Uncertainty-Code,

high-Accuracy-Uncertainty-SemiMinor High-Accuracy-Uncertainty-Code,

orientation-Major-Axis INTEGER (0..179),

iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Uncertainty-Ellipse-ExtIEs} } OPTIONAL,

…

}

High-Accuracy-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

High-Accuracy-Extended-Uncertainty-Ellipse ::= SEQUENCE {

high-Accuracy-Extended-Uncertainty-SemiMajor High-Accuracy-Extended-Uncertainty-Code,

high-Accuracy-Extended-Uncertainty-SemiMinor High-Accuracy-Extended-Uncertainty-Code,

orientation-Major-Axis INTEGER (0..179),

iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Extended-Uncertainty-Ellipse-ExtIEs} } OPTIONAL,

…

}

High-Accuracy-Extended-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

High-Accuracy-Scalable-Uncertainty-Ellipse ::= CHOICE {

high-Accuracy-Uncertainty-Ellipse High-Accuracy-Uncertainty-Ellipse,

high-Accuracy-Extended-Uncertainty-Ellipse High-Accuracy-Extended-Uncertainty-Ellipse

}

High-Accuracy-Scalable-Uncertainty-Altitude ::= CHOICE {

high-Accuracy-Uncertainty-Altitude High-Accuracy-Uncertainty-Code,

high-Accuracy-Extended-Uncertainty-Altitude High-Accuracy-Extended-Uncertainty-Code

}

Home-eNB-ID ::= BIT STRING (SIZE (28))

Horizontal-Accuracy ::= INTEGER (0..127)

Horizontal-Speed-And-Bearing ::= SEQUENCE {

bearing INTEGER (0..359),

horizontal-Speed INTEGER (0..2047)

}

Horizontal-Velocity ::= SEQUENCE {

horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing,

iE-Extensions ProtocolExtensionContainer { { Horizontal-Velocity-ExtIEs} } OPTIONAL,

…

}

Horizontal-Velocity-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

Horizontal-With-Vertical-Velocity ::= SEQUENCE {

horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing,

vertical-Velocity Vertical-Velocity,

iE-Extensions ProtocolExtensionContainer { { Horizontal-With-Vertical-Velocity-ExtIEs} } OPTIONAL,

…

}

Horizontal-With-Vertical-Velocity-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

Horizontal-Velocity-With-Uncertainty ::= SEQUENCE {

horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing,

uncertainty-Speed INTEGER (0..255),

iE-Extensions ProtocolExtensionContainer { { Horizontal-Velocity-With-Uncertainty-ExtIEs} } OPTIONAL,

…

}

Horizontal-Velocity-With-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

Horizontal-With-Vertical-Velocity-And-Uncertainty ::= SEQUENCE {

horizontal-Speed-And-Bearing Horizontal-Speed-And-Bearing,

vertical-Velocity Vertical-Velocity,

horizontal-Uncertainty-Speed INTEGER (0..255),

vertical-Uncertainty-Speed INTEGER (0..255),

iE-Extensions ProtocolExtensionContainer { { Horizontal-With-Vertical-Velocity-And-Uncertainty-ExtIEs} } OPTIONAL,

…

}

Horizontal-With-Vertical-Velocity-And-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

— I

IMSI ::= OCTET STRING (SIZE (3..8))

IMEI ::= OCTET STRING (SIZE (8))

Include-Velocity ::= ENUMERATED {

requested,

not-Requested,

…

}

Inner-Radius ::= INTEGER (0..65535) — 16 bit field

International-Area-Indication ::= ENUMERATED {

yes,

…

}

— J

— K

— L

LatitudeSign ::= ENUMERATED {

north,

south

}

Location-Type ::= ENUMERATED {

geographic-Information,

assistance-Information,

…,

last-known-location

}

LCS-Cause ::= CHOICE {

radio-Network-Layer Radio-Network-Layer-Cause,

transport-Layer Transport-Layer-Cause,

protocol Protocol-Cause,

misc Misc-Cause

}

LCS-Client-Type ::= ENUMERATED {

emergency-Services,

value-Added-Services,

pLMN-Operator-Services,

lawful-Intercept-Services,

pLMN-Operator-broadcast-Services,

pLMN-Operator-OM,

pLMN-Operator-Anonymous-Statistics,

pLMN-Operator-Target-MS-Service-Support,

…

}

LCS-Priority ::= OCTET STRING (SIZE (1))

LCS-QoS ::= SEQUENCE {

horizontal-Accuracy Horizontal-Accuracy OPTIONAL,

vertical-Requested Vertical-Requested OPTIONAL,

vertical-Accuracy Vertical-Accuracy OPTIONAL,

response-Time Response-Time OPTIONAL,

…

}

LCS-Service-Type-ID ::= INTEGER (0..127)

Long-Macro-eNB-ID ::= BIT STRING (SIZE (21))

— M

Macro-eNB-ID ::= BIT STRING (SIZE (20))

Message-Identifier ::= BIT STRING (SIZE (16))

Misc-Cause ::= ENUMERATED {

processing-Overload,

hardware-Failure,

o-And-M-Intervention,

unspecified,

…,

ciphering-key-data-lost

}

MultipleAPDUs ::= SEQUENCE (SIZE (1.. 3)) OF APDU

— N

Network-Element ::= CHOICE {

global-eNB-ID Global-eNB-ID,

e-SMLC-ID E-SMLC-ID

}

— O

Orientation-Major-Axis ::= INTEGER (0..89)

— P

Payload-Type ::= ENUMERATED {

lPP,

lPPa,

…

}

PLMN-ID ::= TBCD-STRING

Point ::= SEQUENCE {

geographical-Coordinates Geographical-Coordinates,

iE-Extensions ProtocolExtensionContainer { {Point-ExtIEs} } OPTIONAL,

…

}

Point-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

Point-With-Uncertainty ::= SEQUENCE {

geographical-Coordinates Geographical-Coordinates,

uncertainty-Code Uncertainty-Code,

iE-Extensions ProtocolExtensionContainer { {Point-With-Uncertainty-ExtIEs} } OPTIONAL,

…}

Point-With-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

Polygon ::= SEQUENCE (SIZE (1..max-No-Of-Points)) OF Polygon-Point

Polygon-Point ::= SEQUENCE {

geographical-Coordinates Geographical-Coordinates,

iE-Extensions ProtocolExtensionContainer { {Polygon-Point-ExtIEs} } OPTIONAL,

…

}

Polygon-Point-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

…

}

Positioning-Data ::= SEQUENCE {

positioning-Data-Set Positioning-Data-Set OPTIONAL,

gNSS-Positioning-Data-Set GNSS-Positioning-Data-Set OPTIONAL,

iE-Extensions ProtocolExtensionContainer { { Positioning-Data-ExtIEs} } OPTIONAL,

…

}

Positioning-Data-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {

{ ID id-Additional-PositioningDataSet CRITICALITY ignore EXTENSION Additional-PositioningDataSet PRESENCE optional },

…

}

Positioning-Data-Set ::= SEQUENCE (SIZE (1..max-Set)) OF Positioning-Method-And-Usage

Positioning-Method-And-Usage ::= OCTET STRING (SIZE (1))

Protocol-Cause ::= ENUMERATED {

transfer-Syntax-Error,
abstract-Syntax-Error-Reject,
abstract-Syntax-Error-Ignore-And-Notify,
message-Not-Compatible-With-Receiver-State,

semantic-Error,
unspecified,

abstract-Syntax-Error,

…

}

— Q

— R

Radio-Network-Layer-Cause ::= ENUMERATED {

unspecified,

…

}

RAT-Type ::= ENUMERATED {

lte-wb,

nb-iot,

…,

lte-m

}

Response-Time ::= ENUMERATED {

low-Delay(0),

delay-Tolerant(1),

…

}

Return-Error-Type ::= ENUMERATED {

yes,

}

Return-Error-Cause ::= ENUMERATED {

system-Failure,

protocol-Error,

destination-Unknown,

destination-Unreachable,

congestion,

…

}

— S

Short-Macro-eNB-ID ::= BIT STRING (SIZE (18))

SIB-Types ::= OCTET STRING (SIZE (4))

Storage-Outcome ::= ENUMERATED {

successful,

failed

}

— T

TAIs-List ::= OCTET STRING (SIZE (7..97))

TBCD-STRING ::= OCTET STRING (SIZE (3))

Transport-Layer-Cause ::= ENUMERATED {

tranport-Resource-Unavailable,

unspecified,

…

}

— U

Uncertainty-Altitude ::= INTEGER (0..127)

Uncertainty-Code ::= INTEGER (0..127)

Uncertainty-Ellipse ::= SEQUENCE {

uncertainty-SemiMajor Uncertainty-Code,

uncertainty-SemiMinor Uncertainty-Code,

orientation-Major-Axis Orientation-Major-Axis

}

UE-Positioning-Capability ::= SEQUENCE {

lPP BOOLEAN,

…

}

UE-Country-Determination-Indication ::= ENUMERATED {

required,

not-required,

…

}

UE-Area-Indication ::= SEQUENCE {

country Country,

international-area-indication International-Area-Indication

}

— V

Validity-Duration ::= INTEGER (0..65535)

Validity-Start-Time ::= OCTET STRING (SIZE (4))

Velocity-Estimate ::= CHOICE {

horizontal-Velocity Horizontal-Velocity,

horizontal-With-Vertical-Velocity Horizontal-With-Vertical-Velocity,

horizontal-Velocity-With-Uncertainty Horizontal-Velocity-With-Uncertainty,

horizontal-With-Vertical-Velocity-And-Uncertainty Horizontal-With-Vertical-Velocity-And-Uncertainty,

…

}

Vertical-Requested ::= ENUMERATED {

vertical-coordinate-Is-Not-Requested(0),

vertical-coordinate-Is-Requested(1)

}

Vertical-Accuracy ::= INTEGER (0..127)

Vertical-Velocity ::= SEQUENCE {

vertical-Speed INTEGER (0..255),

vertical-Speed-Direction Vertical-Speed-Direction

}

Vertical-Speed-Direction ::= ENUMERATED {

upward,

downward

}

— W

— X

— Y

END

7.5.6 Common definitions

— **************************************************************

—

— Common definitions

—

— **************************************************************

LCS-AP-CommonDataTypes {

itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)

eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-CommonDataTypes (3)}

DEFINITIONS AUTOMATIC TAGS ::=

BEGIN

Criticality ::= ENUMERATED { reject, ignore, notify }

Presence ::= ENUMERATED { optional, conditional, mandatory }

ProcedureCode ::= INTEGER (0..255)

ProtocolExtensionID ::= INTEGER (0..65535)

ProtocolIE-ID ::= INTEGER (0..65535)

TriggeringMessage ::= ENUMERATED {initiating-message, successful-outcome, unsuccessful-outcome, outcome}

END

7.5.7 Constant definitions

— **************************************************************

—

— Constant definitions

—

— **************************************************************

LCS-AP-Constants {

itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)

eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-Constants (4)}

DEFINITIONS AUTOMATIC TAGS ::=

BEGIN

— **************************************************************

—

— Elementary Procedures

—

— **************************************************************

id-Location-Service-Request INTEGER ::= 0

id-Connection-Oriented-Information-Transfer INTEGER ::= 1

id-Connectionless-Information-Transfer INTEGER ::= 2

id-Location-Abort INTEGER ::= 3

id-Reset INTEGER ::= 4

id-Ciphering-Key-Data-Delivery INTEGER ::= 5

— **************************************************************

—

— IEs

—

— **************************************************************

id-Accuracy-Fulfillment-Indicator INTEGER ::= 0

id-APDU INTEGER ::= 1

id-Correlation-ID INTEGER ::= 2

id-Destination-ID INTEGER ::= 3

id-E-UTRAN-Cell-Identifier INTEGER ::= 4

id-Include-Velocity INTEGER ::= 5

id-IMEI INTEGER ::= 6

id-IMSI INTEGER ::= 7

id-LCS-Client-Type INTEGER ::= 8

id-LCS-Priority INTEGER ::= 9

id-LCS-QOS INTEGER ::= 10

id-LCS-Cause INTEGER ::= 11

id-Location-Estimate INTEGER ::= 12

id-Location-Type INTEGER ::= 13

id-MultipleAPDUs INTEGER ::= 14

id-Payload-Type INTEGER ::= 15

id-Positioning-Data INTEGER ::= 16

id-Return-Error-Request INTEGER ::= 17

id-Return-Error-Cause INTEGER ::= 18

id-Source-Identity INTEGER ::= 19

id-UE-Positioning-Capability INTEGER ::= 20

id-Velocity-Estimate INTEGER ::= 21

id-LCS-Service-Type-ID INTEGER ::= 22

id-Cell-Portion-ID INTEGER ::= 23

id-Civic-Address INTEGER ::= 24

id-Barometric-Pressure INTEGER ::= 25

id-Additional-PositioningDataSet INTEGER ::= 26

id-RAT-Type INTEGER ::= 27

id-Ciphering-Data INTEGER ::= 28

id-Ciphering-Data-Ack INTEGER ::= 29

id-Ciphering-Data-Error-Report INTEGER ::= 30

id-Coverage-Level INTEGER ::= 31

id-UE-Country-Determination-Indication INTEGER ::= 32

id-UE-Area-Indication INTEGER ::= 33

— **************************************************************

—

— Extension constants

—

— **************************************************************

—

— Lists

—

— **************************************************************

max-No-Of-Points INTEGER ::= 15

max-Set INTEGER ::= 9

max-GNSS-Set INTEGER ::= 9

max-Add-Pos-Set INTEGER ::= 8

max-Cipher-Set INTEGER ::= 16

maxProtocolExtensions INTEGER ::= 65535

maxProtocolIEs INTEGER ::= 65535

END

7.5.8 Container Definitions

— **************************************************************

—

— Container definitions

—

— **************************************************************

LCS-AP-Containers {

itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)

eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-Containers (5)}

DEFINITIONS AUTOMATIC TAGS ::=

BEGIN

— **************************************************************

—

— IE parameter types from other modules.

—

— **************************************************************

IMPORTS

Criticality,

Presence,

ProtocolExtensionID,

ProtocolIE-ID

FROM LCS-AP-CommonDataTypes

maxProtocolExtensions,

maxProtocolIEs

FROM LCS-AP-Constants;

— **************************************************************

—

— Class Definition for Protocol IEs

—

— **************************************************************

LCS-AP-PROTOCOL-IES ::= CLASS {

&id ProtocolIE-ID UNIQUE,

&criticality Criticality DEFAULT ignore,

&Value,

&presence Presence

}

WITH SYNTAX {

ID &id

CRITICALITY &criticality

TYPE &Value

PRESENCE &presence

}

— **************************************************************

—

— Class Definition for Protocol Extensions

—

— **************************************************************

LCS-AP-PROTOCOL-EXTENSION ::= CLASS {

&id ProtocolExtensionID UNIQUE,

&criticality Criticality DEFAULT ignore,

&Extension,

&presence Presence

}

WITH SYNTAX {

ID &id

CRITICALITY &criticality

EXTENSION &Extension

PRESENCE &presence

}

— **************************************************************

—

— Container for Protocol IEs

—

— **************************************************************

ProtocolIE-Container {LCS-AP-PROTOCOL-IES : IEsSetParam} ::=

SEQUENCE (SIZE (0..maxProtocolIEs)) OF

ProtocolIE-Field {{IEsSetParam}}

ProtocolIE-Field {LCS-AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE {

id LCS-AP-PROTOCOL-IES.&id ({IEsSetParam}),

criticality LCS-AP-PROTOCOL-IES.&criticality ({IEsSetParam}{@id}),

value LCS-AP-PROTOCOL-IES.&Value ({IEsSetParam}{@id})

}

— **************************************************************

—

— Container Lists for Protocol IE Containers

—

— **************************************************************

ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, LCS-AP-PROTOCOL-IES : IEsSetParam} ::=

SEQUENCE (SIZE (lowerBound..upperBound)) OF

ProtocolIE-Container {{IEsSetParam}}

— **************************************************************

—

— Container for Protocol Extensions

—

— **************************************************************

ProtocolExtensionContainer {LCS-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::=

SEQUENCE (SIZE (1..maxProtocolExtensions)) OF

ProtocolExtensionField {{ExtensionSetParam}}

ProtocolExtensionField {LCS-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE {

id LCS-AP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}),

criticality LCS-AP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}),

extensionValue LCS-AP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id})

}

END

7.5.9 Message transfer syntax

LCS-AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ITU-T Recommendation X.691 [12].

7.6 Handling of unknown, unforeseen and erroneous protocol data

Clause 10 of 3GPP TS 36.413 [7] is applicable for the purposes of the present document.