7.3.4 LPP Positioning Procedures

37.571-23GPPPart 2: Protocol conformanceRelease 16TSUser Equipment (UE) conformance specification for UE positioning

7.3.4.1 E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE-Based

7.3.4.1.1 Test Purpose (TP)

(1)

with { a NAS signalling connection for EPC-NI-LR session existing }

ensure that {

when { UE receives assistance data and a location request for UE-based }

then { UE sends a PROVIDE LOCATION INFORMATION message containing a location estimate }

}

7.3.4.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.355, clause 5.2.4, 5.3.3 and 5.3.4.

[TS 36.355, clause 5.2.4]

Upon receiving a ProvideAssistanceData message, the target device shall:

1> for each positioning method contained in the message:

2> deliver the related assistance data to upper layers.

[TS 36.355, clause 5.3.3]

Upon receiving a RequestLocationInformation message, the target device shall:

1> if the requested information is compatible with the target device capabilities and configuration:

2> include the requested information in a ProvideLocationInformation message;

2> set the IE LPP-TransactionID in the response to the same value as the IE LPP-TransactionID in the received message;

2> deliver the ProvideLocationInformation message to lower layers for transmission.

1> otherwise:

[…]

[TS 36.355, clause 5.3.4]

When triggered to transmit ProvideLocationInformation message, the target device shall:

1> for each positioning method contained in the message:

2> set the corresponding IE to include the available location information;

1> deliver the response to lower layers for transmission.

7.3.4.1.3 Test description

7.3.4.1.3.1 Pre-test conditions

System Simulator:

– Cell 1.

– Satellite signals (sub-test case 15): As specified in 5.2.1.

– MBS signals (Sub-test 16): As specified in 5.2.4 .

– WLAN signals (Sub-test 17): as specified in 5.2.5.

UE:

– The UE shall begin the test with no assistance data stored.

Preamble:

– The UE is in state Generic RB Established (state 3) according to 3GPP 36.508 [8].

Related PICS/PIXIT Statements:

7.3.4.1.3.2 Test procedure sequence

This test case includes sub-test cases dependent on the the positioning method(s) supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 7.3.4.1.3.2-0 below:

Table 7.3.4.1.3.2-0: Sub-test case numbers

Sub-Test Case Number

Supported Positioning Methods

1

Void

2

Void

3

Void

4

Void

8

Void

9

Void

10

Void

15

UE supporting GNSS(1)

16

UE supporting MBS (Rel-14 onwards)

17

UE supporting WLAN (Rel-14 onwards)

18

UE supporting Sensor (Rel-14 onwards)

NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE

Table 7.3.4.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The stored assistance data in the UE are cleared.

<–

RESET UE POSITIONING STORED INFORMATION

1a

The SS sends a LPP message of type Request Capabilities.

<–

DLInformationTransfer

(LPP REQUEST CAPABILITIES)

1b

The UE sends a LPP message of type Provide Capabilities including the UE positioning capabilities.

–>

ULInformationTransfer

(LPP PROVIDE CAPABILITIES)

1c

IF

the UE LPP message at step 1b includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

2

The SS sends a LPP message of type Provide Assistance Data.

<–

DLInformationTransfer

(LPP PROVIDE ASSISTANCE DATA)

3

The SS sends a LPP message of type Request Location Information including a request for a location estimate.

<–

DLInformationTransfer

(LPP REQUEST LOCATION INFORMATION)

4

The UE sends a LPP message of type Provide Location Information including a location estimate.

–>

ULInformationTransfer

(LPP PROVIDE LOCATION INFORMATION)

1

P

4a

IF

the UE LPP message at step 4 includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

7.3.4.1.3.3 Specific message contents

Table 7.3.4.1.3.3-1: RESET UE POSITIONING STORED INFORMATION (step 1, Table 7.3.4.1.3.2-1)

Derivation Path: 36.509 clause 6.9

Information Element

Value/remark

Comment

Condition

UE Positioning Technology

Sub-test 15: 0 0 0 0 0 0 0 0

Sub-test 16: 0 0 0 0 0 0 1 0

Sub-test 17: 0 0 0 0 0 0 1 1

Sub-test 18: 0 0 0 0 0 1 0 1

Sub-test 15: GNSS

Sub-test 16: MBS

Sub-test 17: WLAN

Sub-test 18: Sensor

Table 7.3.4.1.3.3-2: DLInformationTransfer (steps 1a, 1c, 2, 3 and 4a, Table 7.3.4.1.3.2-1)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

DLInformationTransfer ::= SEQUENCE {

rrc-TransactionIdentifier

criticalExtensions CHOICE {

c1 CHOICE {

dlInformationTransfer-r8 SEQUENCE {

dedicatedInfoType CHOICE {

dedicatedInfoNAS OCTET STRING

Set according to Table 7.3.4.1.3.3-3

DOWNLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.3.4.1.3.3-3: DOWNLINK GENERIC NAS TRANSPORT (steps 1a, 1c, 2, 3 and 4a, Table 7.3.4.1.3.2‑1)

Derivation Path: 24.301 Table 8.2.31.1

Information Element

Value/remark

Comment

Condition

Protocol discriminator

0111

EPS mobility management messages

Security header type

0000

Plain NAS message

Downlink generic NAS transport message identity

01101000

Downlink generic NAS transport

Generic message container type

00000001

LTE Positioning Protocol (LPP) message container

Generic message container

Step 1a:

Set according to Table 7.3.4.1.3.3-3a

LPP Request Capabilities.

Step 2:

Set according to Table 7.3.4.1.3.3-4

LPP Provide Assistance Data

Step 3:

Set according to Table 7.3.4.1.3.3-5

LPP Request Location Information

Steps 1c and 4a:

Set according to Table 7.3.4.1.3.3-9

LPP Acknowledgement

Additional information

Present

Routing Identifier/

Correlation ID

Table 7.3.4.1.3.3-3a: LPP Request Capabilities (step 1a, Table 7.3.4.1.3.2-1)

Derivation Path: Table 5.4-1

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-1

Table 7.3.4.1.3.3-4: LPP Provide Assistance data (step 2, Table 7.3.4.1.3.2-1)

Derivation Path: Table 5.4-2

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-2 with the following exceptions:

transactionID SEQUENCE {

initiator

locationServer

transactionNumber

(0..255)

}

Table 7.3.4.1.3.3-5: LPP Request Location Information (step 3, Table 7.3.4.1.3.2-1)

Derivation Path: Table 5.4-3

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-3 with the following exceptions:

locationInformationType

locationEstimateRequired

Table 7.3.4.1.3.3-6: ULInformationTransfer (steps 1b and 4, Table 7.3.4.1.3.2-1)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

ULInformationTransfer ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ulInformationTransfer-r8 SEQUENCE {

dedicatedInfoType CHOICE {

dedicatedInfoNAS OCTET STRING

Set according to Table 7.3.4.1.3.3-7

UPLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.3.4.1.3.3-7: UPLINK GENERIC NAS TRANSPORT (steps 1b and 4, Table 7.3.4.1.3.2-1)

Derivation Path: 24.301 Table 8.2.32.1

Information Element

Value/remark

Comment

Condition

Protocol discriminator

0111

EPS mobilitymanagement messages

Security header type

0000

Plain NAS message

Uplink generic NAS transport message identity

01101001

Uplink generic NAS transport

Generic message container type

00000001

LTE Positioning Protocol (LPP) message container

Generic message container

Step 1b:

Set according to Table

7.3.4.1.3.3-7a

LPP Provide Capabilities

Step 4:

Set according to Table

7.3.4.1.3.3-8

LPP Provide Location Information

Additional information

Present

The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 1a or 3 Table 7.3.4.1.3.2‑1)

Table 7.3.4.1.3.3-7a: LPP Provide Capabilities. (step 1b, Table 7.3.4.1.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

locationServer

transactionNumber

(0..255)

Contains the same value as the corresponding field in the LPP Request Capabilities message in step 1a, Table 7.3.4.1.3.2-1.

}

endTransaction

TRUE

sequenceNumber

(0..255)

acknowledgement SEQUENCE {

Present, or not present

ackRequested

TRUE

ackIndicator

Not present

}

lpp-MessageBody CHOICE {

c1 CHOICE {

provideCapabilities SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

provideCapabilities-r9 SEQUENCE {

commonIEsProvideCapabilities

Dependent on UE capabilities

Rel-14 onwards

a-gnss-ProvideCapabilities

Dependent on UE capabilities

otdoa-ProvideCapabilities

Dependent on UE capabilities

ecid-ProvideCapabilities

Dependent on UE capabilities

epdu-ProvideCapabilities

Not present

sensor-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

tbs-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

wlan-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

bt-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

}

}

}

}

}

}

Table 7.3.4.1.3.3-8: LPP Provide Location Information (step 4, Table 7.3.4.1.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

locationServer

transactionNumber

(0..255)

Contains the same value as the corresponding field in LPP Request Location Information message in step 3, Table 7.3.4.1.3.1-1

}

endTransaction

TRUE

sequenceNumber

(0..255)

acknowledgement SEQUENCE {

Present, or not present

ackRequested

TRUE

ackIndicator

Not present

}

lpp-MessageBody CHOICE {

c1 CHOICE {

provideLocationInformation SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

provideLocationInformation-r9

SEQUENCE {

commonIEsProvideLocationInformation

SEQUENCE {

Present

locationEstimate

Present.

Any value acceptable

velocityEstimate

Not present

locationError

Not present

earlyFixReport-r12

Not present

Rel-12 onwards

}

a-gnss-ProvideLocationInformation

SEQUENCE {

Present for sub-test 15

gnss-SignalMeasurementInformation

Not present

gnss-LocationInformation

SEQUENCE {

Present

measurementReferenceTime

Any value acceptable

agnss-List

Any value acceptable

}

gnss-Error

Not present

}

otdoa-ProvideLocationInformation

Not present

ecid-ProvideLocationInformation

Not present

epdu-ProvideLocationInformation

Not present

sensor-ProvideLocationInformation-r13

SEQUENCE {

Present for sub-test 18

Rel-13 onwards

sensor-MeasurementInformation-r13

Present. Any value acceptable

sensor-Error-r13

Not present

}

tbs-ProvideLocationInformation-r13

SEQUENCE {

Present for sub-test 16

Rel-13 onwards

tbs-MeasurementInformation-r13

SEQUENCE {

Present

Rel-13 onwards

measurementReferenceTime-r13

Any value acceptable

mbs-SgnMeasList-r13

Any value acceptable

}

tbs-Error-r13

Not present

Rel-13 onwards

}

wlan-ProvideLocationInformation-r13

SEQUENCE {

Present for sub-test 17

Rel-13 onwards

wlan-MeasurementInformation-r13

Present. Any value acceptable

wlan-Error-r13

Not present

}

bt-ProvideLocationInformation-r13

Not present

Rel-13 onwards

}

}

}

}

}

}

Table 7.3.4.1.3.3-9: LPP Acknowledgement (steps 1c and 4a, Table 7.3.4.1.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID

Not present

endTransaction

TRUE

sequenceNumber

Not present

acknowledgement SEQUENCE {

ackRequested

FALSE

ackIndicator

(0..255)

Contains the same value of the sequenceNumber field in step 1b or 4, Table 7.3.4.1.3.2-1.

}

lpp-MessageBody

Not present.

}

7.3.4.2 E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE‑Assisted

7.3.4.2.1 Test Purpose (TP)

(1)

with { a NAS signalling connection for EPC-NI-LR session existing }

ensure that {
when { UE receives assistance data and a location request for UE-assisted }

then { UE sends a PROVIDE LOCATION INFORMATION message containing location measurements }

}

7.3.4.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.355, clause 5.2.4, 5.3.3 and 5.3.4.

[TS 36.355, clause 5.2.4]

Upon receiving a ProvideAssistanceData message, the target device shall:

1> for each positioning method contained in the message:

2> deliver the related assistance data to upper layers.

[TS 36.355, clause 5.3.3]

Upon receiving a RequestLocationInformation message, the target device shall:

1> if the requested information is compatible with the target device capabilities and configuration:

2> include the requested information in a ProvideLocationInformation message;

2> set the IE LPP-TransactionID in the response to the same value as the IE LPP-TransactionID in the received message;

2> deliver the ProvideLocationInformation message to lower layers for transmission.

1> otherwise:

[…]

[TS 36.355, clause 5.3.4]

When triggered to transmit ProvideLocationInformation message, the target device shall:

1> for each positioning method contained in the message:

2> set the corresponding IE to include the available location information;

1> deliver the response to lower layers for transmission.

7.3.4.2.3 Test description

7.3.4.2.3.1 Pre-test conditions

System Simulator:

– Sub-tests 11, 12, 13, 14, 15, 16, 17, 18: Cell 1.

– Sub-test 5 and 7: Cells 1 and 2, as specified in 5.2.2.

– Sub-tests 6 FDD, 6 TDD: Cells 1 and 2, as specified in 5.2.3.

– Satellite signals (Sub-test 15): As specified in 5.2.1.

– WLAN signals (Sub-test 11, 17): as specified in 5.2.5.

– MBS signals (Sub-tests 12, 16): as specified in 5.2.4

– Bluetooth signals (Sub-test 13): as specified in 5.2.6.

UE:

– The UE shall begin the test with no assistance data stored.

Preamble:

– The UE is in state Generic RB Established (state 3) according to 3GPP 36.508 [8].

Related PICS/PIXIT Statements:

7.3.4.2.3.2 Test procedure sequence

This test case includes sub-test cases dependent on the positioning method(s) supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 7.3.4.2.3.2-0 below:

Table 7.3.4.2.3.2-0: Sub-test case numbers

Sub-Test Case Number

Supported Positioning Methods

1

Void

2

Void

3

Void

4

Void

5

UE supporting OTDOA

6 FDD

UE supporting ECID (FDD)

6 TDD

UE supporting ECID (TDD)

7

UE supporting GNSS(1) and OTDOA

8

Void

9

Void

10

Void

11

UE supporting WLAN (Rel-13 only)

12

UE supporting MBS (Rel-13 only)

13

UE supporting Bluetooth

14

UE supporting Sensor (Rel-13 only)

15

UE supporting GNSS(1)

16

UE supporting MBS (Rel-14 onwards)

17

UE supporting WLAN (Rel-14 onwards)

18

UE supporting Sensor (Rel-14 onwards)

NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE

Table 7.3.4.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

IF

sub-test 7 or 15 or 16 or 17 or 18
THEN

The stored assistance data in the UE are cleared.

<–

RESET UE POSITIONING STORED INFORMATION

1a

IF

Sub-test 5 or 7

THEN

The stored OTDOA assistance data in the UE are cleared.

<–

RESET UE POSITIONING STORED INFORMATION

1b

The SS sends a LPP message of type Request Capabilities.

<–

DLInformationTransfer

(LPP REQUEST CAPABILITIES)

1c

The UE sends a LPP message of type Provide Capabilities including the UE positioning capabilities.

–>

ULInformationTransfer

(LPP PROVIDE CAPABILITIES)

1d

IF

the UE LPP message at step 1c includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

2

IF NOT
sub-test 6 FDD or 6 TDD or 11 or 12 or 13 or 14

THEN

The SS sends a LPP message of type Provide Assistance Data.

<–

DLInformationTransfer

(LPP PROVIDE ASSISTANCE DATA)

3

The SS sends a LPP message of type Request Location Information including a request for location measurements.

<–

DLInformationTransfer

(LPP REQUEST LOCATION INFORMATION)

Steps 4a1-4a2 and 4b1-4b4 represent alternative UE behaviours depending on the UE implementation

4a1 (Note 1)

All sub-tests:

The UE sends a LPP message of type Provide Location Information including location measurements.

–>

ULInformationTransfer

(LPP PROVIDE LOCATION INFORMATION)

1

P

4a2

IF

the UE LPP message at step 4 a1 includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

4b1 (Note 2)

IF sub-test 7

THEN

The UE sends a LPP message of type Provide Location Information including "early fix" location measurements.

–>

ULInformationTransfer

(LPP PROVIDE LOCATION INFORMATION)

4b2

IF

the UE LPP message at step 4b1 includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

4b3

The UE sends a LPP message of type Provide Location Information including location measurements.

–>

ULInformationTransfer

(LPP PROVIDE LOCATION INFORMATION)

1

P

4b4

IF

the UE LPP message at step 4b3 includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

Note 1: This alternative is applicable to all releases of LPP and may be followed even in the case of sub-test 7 and LPP release 12 onwards.

Note 2: This alternative is applicable only to LPP release 12 onwards.

7.3.4.2.3.3 Specific message contents

Table 7.3.4.2.3.3-1: RESET UE POSITIONING STORED INFORMATION (step 1, Table 7.3.4.2.3.2-1)

Derivation Path: 36.509 clause 6.9

Information Element

Value/remark

Comment

Condition

UE Positioning Technology

Sub-tests 7, 15: 0 0 0 0 0 0 0 0

Sub-test 16: 0 0 0 0 0 0 1 0

Sub-test 17: 0 0 0 0 0 0 1 1

Sub-test 18: 0 0 0 0 0 1 0 1

Sub-tests 7, 15: GNSS

Sub-test 16: MBS

Sub-test 17: WLAN

Sub-test 18: Sensor

Table 7.3.4.2.3.3-2: RESET UE POSITIONING STORED INFORMATION (step 1a, Table 7.3.4.2.3.2-1)

Derivation Path: 36.509 clause 6.9

Information Element

Value/remark

Comment

Condition

UE Positioning Technology

0 0 0 0 0 0 0 1

OTDOA

Table 7.3.4.2.3.3-3: DLInformationTransfer (steps 1b, 1d, 2, 3, 4a2, 4b2 and 4b4, Table 7.3.4.2.3.2-1)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

DLInformationTransfer ::= SEQUENCE {

rrc-TransactionIdentifier

criticalExtensions CHOICE {

c1 CHOICE {

dlInformationTransfer-r8 SEQUENCE {

dedicatedInfoType CHOICE {

dedicatedInfoNAS OCTET STRING

Set according to Table 7.3.4.2.3.3-4

DOWNLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.3.4.2.3.3-4: DOWNLINK GENERIC NAS TRANSPORT (steps 1b, 1d, 2, 3, 4a2, 4b2 and 4b4, Table 7.3.4.2.3.2‑1)

Derivation Path: 24.301 Table 8.2.31.1

Information Element

Value/remark

Comment

Condition

Protocol discriminator

0111

EPS mobility management messages

Security header type

0000

Plain NAS message

Downlink generic NAS transport message identity

01101000

Downlink generic NAS transport

Generic message container type

00000001

LTE Positioning Protocol (LPP) message container

Generic message container

Step 1b:

Set according to Table 7.3.4.2.3.3-4a

LPP Request Capabilities.

Step 2:

Set according to Table 7.3.4.2.3.3-5

LPP Provide Assistance Data

Step 3:

Set according to Table 7.3.4.2.3.3-6

LPP Request Location Information

Steps 1d, 4a2, 4b2 and 4b4:

Set according to Table 7.3.4.2.3.3-10

LPP Acknowledgement

Additional information

Present

Routing Identifier/

Correlation ID

Table 7.3.4.2.3.3-4a: LPP Request Capabilities (step 1b, Table 7.3.4.2.3.2‑1)

Derivation Path: Table 5.4-1

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-1

Table 7.3.4.2.3.3-5: LPP Provide Assistance data (step 2, Table 7.3.4.2.3.2-1)

Derivation Path: Table 5.4-2

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-2 with the following exceptions:

transactionID SEQUENCE {

initiator

locationServer

transactionNumber

(0..255)

}

Table 7.3.4.2.3.3-6: LPP Request Location Information (step 3, Table 7.3.4.2.3.2-1)

Derivation Path: Table 5.4-3

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-3 with the following exceptions:

locationInformationType

locationMeasurementsRequired

qos SEQUENCE {

horizontalAccuracy

Not present

verticalCoordinateRequest

FALSE

verticalAccuracy

Not present

responseTime SEQUENCE {

time

32

responseTimeEarlyFix-r12

Sub-tests 5, 6 FDD, 6 TDD, 11, 12, 13, 14, 15, 16, 17, 18: not present

Sub-test 7: 10

Rel-12 onwards

}

velocityRequest

FALSE

}

a-gnss-RequestLocationInformation

Set according to Table 7.3.4.2.3.3-11

Table 7.3.4.2.3.3-7: ULInformationTransfer (steps 1c, 4 a1, 4b1 and 4b3, Table 7.3.4.2.3.2-1)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

ULInformationTransfer ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ulInformationTransfer-r8 SEQUENCE {

dedicatedInfoType CHOICE {

dedicatedInfoNAS OCTET STRING

Set according to Table 7.3.4.2.3.3-8

UPLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.3.4.2.3.3-8: UPLINK GENERIC NAS TRANSPORT (steps 1c, 4 a1, 4b1 and 4b3, Table 7.3.4.2.3.2-1)

Derivation Path: 24.301 Table 8.2.32.1

Information Element

Value/remark

Comment

Condition

Protocol discriminator

0111

EPS mobility management messages

Security header type

0000

Plain NAS message

Uplink generic NAS transport message identity

01101001

Uplink generic NAS transport

Generic message container type

00000001

LTE Positioning Protocol (LPP) message container

Generic message container

Step 1c:

Set according to Table

7.3.4.2.3.3-8a

LPP Provide Capabilities

Steps 4 a1, 4b1 and 4b3:

Set according to Table

7.3.4.2.3.3-9

LPP Provide Location Information

Additional information

Present

The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 1b or 3 Table 7.3.4.2.3.2-1)

Table 7.3.4.2.3.3-8a: LPP Provide Capabilities. (step 1c, Table 7.3.4.2.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

locationServer

transactionNumber

(0..255)

Contains the same value as the corresponding field in the LPP Request Capabilities message in step 1b, Table 7.3.4.2.3.2-1

}

endTransaction

TRUE

sequenceNumber

(0..255)

acknowledgement SEQUENCE {

Present, or not present

ackRequested

TRUE

ackIndicator

Not present

}

lpp-MessageBody CHOICE {

c1 CHOICE {

provideCapabilities SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

provideCapabilities-r9 SEQUENCE {

commonIEsProvideCapabilities

Dependent on UE capabilities

Rel-14 onwards

a-gnss-ProvideCapabilities

Dependent on UE capabilities

otdoa-ProvideCapabilities

Dependent on UE capabilities

ecid-ProvideCapabilities SEQUENCE{

Dependent on UE capabilities

ueRxTxSupTDD-r13

Present (TRUE) for sub-test 6 TDD

Rel-13 onwards

}

epdu-ProvideCapabilities

Not present

sensor-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

tbs-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

wlan-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

bt-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

}

}

}

}

}

}

Table 7.3.4.2.3.3-9: LPP Provide Location Information (steps 4 a1, 4b1 and 4b3, Table 7.3.4.2.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

locationServer

transactionNumber

(0..255)

Contains the same value as the corresponding field in LPP Request Location Information message in step 3, Table 7.3.4.2.3.1-1

}

endTransaction

Step 4a1, 4b3: TRUE

Step 4b1: FALSE

sequenceNumber

(0..255)

acknowledgement SEQUENCE {

Present, or not present

ackRequested

TRUE

ackIndicator

Not present

}

lpp-MessageBody CHOICE {

c1 CHOICE {

provideLocationInformation SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

provideLocationInformation-r9 SEQUENCE {

commonIEsProvideLocationInformation SEQUENCE {

Step 4a1, 4b3: May be present

Step 4b1: Present

locationEstimate

Not present

velocityEstimate

Not present

locationError

Not present

earlyFixReport-r12

Step 4a1, 4b3: Not present

Rel-12 onwards

Step 4b1: Any value acceptable

}

a-gnss-ProvideLocationInformation SEQUENCE {

Step 4a1: Present for sub-tests 7, 15

Step 4b1, 4b3: May be present

One of a-gnss-ProvideLocationInformation or otdoa-ProvideLocationInformation shall be present

gnss-SignalMeasurementInformation SEQUENCE {

Present

measurementReferenceTime

Present. Any value acceptable

gnss-MeasurementList SEQUENCE (SIZE(1..n)) OF SEQUENCE {

Present. SIZE n is the number of GNSSs supported by the UE, one instance for each GNSS supported by the UE

gnss-ID

Present

gnss-SgnMeasList

Present, one instance for each frequency within the GNSS supported by the UE. Any value acceptable

}

}

}

gnss-LocationInformation

Not present

gnss-Error

Not present

}

otdoa-ProvideLocationInformation

SEQUENCE {

Step 4a1: Present for sub-tests 5, 7

Step 4b1, 4b3: May be present

One of a-gnss-ProvideLocationInformation or otdoa-ProvideLocationInformation shall be present

otdoa-SignalMeasurementInformation

Present. Any value acceptable

otdoa-Error

May be present

}

ecid-ProvideLocationInformation

SEQUENCE {

Present for sub-test 6 FDD, 6 TDD.

ecid-SignalMeasurementInformation

Present. Any value acceptable

ecid-Error

Not present

}

epdu-ProvideLocationInformation

Not present

sensor-ProvideLocationInformation-r13

SEQUENCE {

Present for sub-test 14, 18

Rel-13 onwards

sensor-MeasurementInformation-r13

Present. Any value acceptable

sensor-Error-r13

May be present

}

tbs-ProvideLocationInformation-r13

SEQUENCE {

Present for sub-tests 12, 16

Rel-13 onwards

tbs-MeasurementInformation-r13

SEQUENCE {

Present

measurementReferenceTime-r13

Any value acceptable

mbs-SgnMeasList-r13

Any value acceptable

}

tbs-Error-r13

Not present

}

wlan-ProvideLocationInformation-r13

SEQUENCE {

Present for sub-test 11, 17

Rel-13 onwards

wlan-MeasurementInformation-r13

Present. Any value acceptable

wlan-Error-r13

May be present

}

bt-ProvideLocationInformation-r13

SEQUENCE {

Present for sub-test 13

Rel-13 onwards

bt-MeasurementInformation-r13

Present. Any value acceptable

bt-Error-r13

May be present

}

}

}

}

}

}

}

}

Table 7.3.4.2.3.3-10: LPP Acknowledgement (steps 1d, 4a2, 4b2 and 4b4, Table 7.3.4.2.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID

Not present

endTransaction

TRUE

sequenceNumber

Not present

acknowledgement SEQUENCE {

ackRequested

FALSE

ackIndicator

(0..255)

Contains the same value of the sequenceNumber field in step 1c or 4 a1 or 4b1 or 4b3, Table 7.3.4.2.3.2-1

}

lpp-MessageBody

Not present.

}

Table 7.3.4.2.3.3-11: A-GNSS Request Location Information (step 3, Table 7.3.4.2.3.2-1)

Derivation Path: Table 5.4-4

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-4 with the following exceptions:

multiFreqMeasReq

TRUE, if UE supports multi frequency GNSS

MultiFreqAGNSS

Condition

Description

MultiFreqAGNSS

The UE supports at least one of pc_A_GPS_L2C, pc_A_GPS_L5, pc_QZSS_QZS_L1C, pc_QZSS_QZS_L2C, pc_QZSS_QZS_L5, pc_GLONASS_G2, pc_GLONASS_G3, pc_GALILEO_E5a, pc_GALILEO_E5b, pc_GALILEO_E6, pc_GALILEO_E5aE5b or pc_BDS_B1C

7.3.4.3 E-SMLC Initiated Position Measurement without assistance data: UE‑Based

7.3.4.3.1 Test Purpose (TP)

(1)

with { a NAS signalling connection for EPC-NI-LR session existing }

ensure that {
when { UE has no assistance data stored and receives a location request for UE-based and the UE
requires assistance data in order to fulfill the location request }

then { UE sends a REQUEST ASSISTANCE DATA message followed by a PROVIDE LOCATION INFORMATION
message containing a location estimate }

}

7.3.4.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.355, clause 5.2.3, 5.2.4, 5.3.3 and 5.3.4.

[TS 36.355, clause 5.2.3]

When triggered to transmit a RequestAssistanceData message, the target device shall:

1> set the IEs for the positioning-method-specific request for assistance data to request the data indicated by upper layers.

[TS 36.355, clause 5.2.4]

Upon receiving a ProvideAssistanceData message, the target device shall:

1> for each positioning method contained in the message:

2> deliver the related assistance data to upper layers.

[TS 36.355, clause 5.3.3]

Upon receiving a RequestLocationInformation message, the target device shall:

1> if the requested information is compatible with the target device capabilities and configuration:

2> include the requested information in a ProvideLocationInformation message;

2> set the IE LPP-TransactionID in the response to the same value as the IE LPP-TransactionID in the received message;

2> deliver the ProvideLocationInformation message to lower layers for transmission.

1> otherwise:

[…]

[TS 36.355, clause 5.3.4]

When triggered to transmit ProvideLocationInformation message, the target device shall:

1> for each positioning method contained in the message:

2> set the corresponding IE to include the available location information;

1> deliver the response to lower layers for transmission.

7.3.4.3.3 Test description

7.3.4.3.3.1 Pre-test conditions

System Simulator:

– Cell 1.

– Satellite signals (sub-test 15): As specified in 5.2.1.

– MBS signals (sub-test 16): As specified in 5.2.4.

– WLAN signals (Sub-test 17): as specified in 5.2.5.

UE:

– The UE shall begin the test with no assistance data stored.

Preamble:

– The UE is in state Generic RB Established (state 3) according to 3GPP 36.508 [8].

Related PICS/PIXIT Statements:

– Method of triggering an LPP Request Assistance Data message.

7.3.4.3.3.2 Test procedure sequence

This test case includes sub-test cases dependent on the the positioning method(s) supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 7.3.4.3.3.2-0 below:

Table 7.3.4.3.3.2-0: Sub-test case numbers

Sub-Test Case Number

Supported Positioning Methods

1

Void

2

Void

3

Void

4

Void

8

Void

9

Void

10

Void

15

UE supporting GNSS(1)

16

UE supporting MBS (Rel-14 onwards)

17

UE supporting WLAN (Rel-14 onwards)

18

UE supporting Sensor (Rel-14 onwards)

NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE

Table 7.3.4.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The stored assistance data in the UE are cleared.

<–

RESET UE POSITIONING STORED INFORMATION

1a

The SS sends a LPP message of type Request Capabilities.

<–

DLInformationTransfer

(LPP REQUEST CAPABILITIES)

1b

The UE sends a LPP message of type Provide Capabilities including the UE positioning capabilities.

–>

ULInformationTransfer

(LPP PROVIDE CAPABILITIES)

1c

IF

the UE LPP message at step 1b includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

2

The SS sends a LPP message of type Request Location Information including a request for a location estimate.

<–

DLInformationTransfer

(LPP REQUEST LOCATION INFORMATION)

3

The UE sends a LPP message of type Request Assistance Data including a request for assistance data.
NOTE: This requires a method of triggering an Request Assistance Data message.

–>

ULInformationTransfer

(LPP REQUEST ASSISTANCE DATA)

1

P

4

The SS sends a LPP message of type Provide Assistance Data.

<–

DLInformationTransfer

(LPP PROVIDE ASSISTANCE DATA)

5

The UE sends a LPP message of type Provide Location Information including a location estimate.

–>

ULInformationTransfer

(LPP PROVIDE LOCATION INFORMATION)

1

P

5a

IF

the UE LPP message at step 5 includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

7.3.4.3.3.3 Specific message contents

Table 7.3.4.3.3.3-1: RESET UE POSITIONING STORED INFORMATION (step 1, Table 7.3.4.3.3.2-1)

Derivation Path: 36.509 clause 6.9

Information Element

Value/remark

Comment

Condition

UE Positioning Technology

Sub-test 15: 0 0 0 0 0 0 0 0

Sub-test 16: 0 0 0 0 0 0 1 0

Sub-test 17: 0 0 0 0 0 0 1 1

Sub-test 18: 0 0 0 0 0 1 0 1

Sub-test 15: GNSS

Sub-test 16: MBS Sub-test 17: WLAN

Sub-test 18: Sensor

Table 7.3.4.3.3.3-2: DLInformationTransfer (steps 1a, 1c, 2, 4 and 5a, Table 7.3.4.3.3.2-1)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

DLInformationTransfer ::= SEQUENCE {

rrc-TransactionIdentifier

criticalExtensions CHOICE {

c1 CHOICE {

dlInformationTransfer-r8 SEQUENCE {

dedicatedInfoType CHOICE {

dedicatedInfoNAS OCTET STRING

Set according to Table 7.3.4.3.3.3-3

DOWNLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.3.4.3.3.3-3: DOWNLINK GENERIC NAS TRANSPORT (steps 1a, 1c, 2, 4 and 5a, Table 7.3.4.3.3.2‑1)

Derivation Path: 24.301 Table 8.2.31.1

Information Element

Value/remark

Comment

Condition

Protocol discriminator

0111

EPS mobility management messages

Security header type

0000

Plain NAS message

Downlink generic NAS transport message identity

01101000

Downlink generic NAS transport

Generic message container type

00000001

LTE Positioning Protocol (LPP) message container

Generic message container

Step 1a:

Set according to Table 7.3.4.3.3.3-3a

LPP Request Capabilities.

Step 2:

Set according to Table 7.3.4.3.3.3-4

LPP Request Location Information

Step 4:

Set according to Table 7.3.4.3.3.3-9

LPP Provide Assistance Data

Steps 1c and 5a:

Set according to Table 7.3.4.3.3.3-11

LPP Acknowledgement

Additional information

Present

Routing Identifier/

Correlation ID

Table 7.3.4.3.3.3-3a: LPP Request Capabilities (step 1a, Table 7.3.4.3.3.2‑1)

Derivation Path: Table 5.4-1

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-1

Table 7.3.4.3.3.3-4: LPP Request Location Information (step 2, Table 7.3.4.3.3.2-1)

Derivation Path: Table 5.4-3

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-3 with the following exceptions:

locationInformationType

locationEstimateRequired

a-gnss-RequestLocationInformation

Set according to Table 7.3.4.3.3.3-5

Sub-test 15

sensor-RequestLocationInformation-r14

Set according to Table 7.3.4.3.3.3-5B

Rel-14 onwards

Sub-test 18

tbs-RequestLocationInformation-r13

Set according to Table 7.3.4.3.3.3-5A

Rel-13 onwards

Sub-test 16

wlan-RequestLocationInformation-r14

Set according to Table 7.3.4.3.3.3-5C

Rel-14 onwards

Sub-test 17

Table 7.3.4.3.3.3-5: A-GNSS Request Location Information (step 2, Table 7.3.4.3.3.2-1)

Derivation Path: Table 5.4-4

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-4 with the following exceptions:

assistanceAvailability

TRUE

Table 7.3.4.3.3.3-5A: TBS Request Location Information (step 2, Table 7.3.4.3.3.2-1)

Derivation Path: Table 5.4-7

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-7 with the following exceptions:

mbsSgnMeasListReq-r13

FALSE (UE-based MBS)

Rel-13 onwards

mbsAssistanceAvailability-r14

TRUE

Rel-14 onwards

Table 7.3.4.3.3.3-5B: Sensor Request Location Information (step 2, Table 7.3.4.3.3.2-1)

Derivation Path: Table 5.4-10

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-10 with the following exceptions:

uncompensatedBarometricPressureReq-r13

FALSE (UE-based Sensor)

Rel-13 onwards

assistanceAvailability-r14

TRUE

Rel-14 onwards

Table 7.3.4.3.3.3-5C: WLAN Request Location Information (step 2, Table 7.3.4.3.3.2-1)

Derivation Path: Table 5.4-8

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-8 with the following exceptions:

requestedMeasurements-r13

bit 0 = 0 (rssi) (UE-based WLAN)

bit 1 = 0 (rtt) (UE-based WLAN)

Rel-13 onwards

assistanceAvailability-r14

TRUE

Rel-14 onwards

Table 7.3.4.3.3.3-6: ULInformationTransfer (steps 1b, 3 and 5, Table 7.3.4.3.3.2-1)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

ULInformationTransfer ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ulInformationTransfer-r8 SEQUENCE {

dedicatedInfoType CHOICE {

dedicatedInfoNAS OCTET STRING

Set according to Table 7.3.4.3.3.3-7

UPLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.3.4.3.3.3-7: UPLINK GENERIC NAS TRANSPORT (steps 1b, 3 and 5, Table 7.3.4.3.3.2-1)

Derivation Path: 24.301 Table 8.2.32.1

Information Element

Value/remark

Comment

Condition

Protocol discriminator

0111

EPS mobility management messages

Security header type

0000

Plain NAS message

Uplink generic NAS transport message identity

01101001

Uplink generic NAS transport

Generic message container type

00000001

LTE Positioning Protocol (LPP) message container

Generic message container

Step 1b:

Set according to Table

7.3.4.3.3.3-7a

LPP Provide Capabilities

Step 3:

Set according to Table

7.3.4.3.3.3-8

LPP Request Assistance Data

Step 5:

Set according to Table

7.3.4.3.3.3-10

LPP Provide Location Information

Additional information

Present

The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 1a or 2 or 4 Table 7.3.4.3.3.2-1)

Table 7.3.4.3.3.3-7a: LPP Provide Capabilities. (step 1b, Table 7.3.4.3.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

locationServer

transactionNumber

(0..255)

Contains the same value as the corresponding field in the LPP Request Capabilities message in step 1a, Table 7.3.4.3.3.2-1

}

endTransaction

TRUE

sequenceNumber

(0..255)

acknowledgement SEQUENCE {

Present, or not present

ackRequested

TRUE

ackIndicator

Not present

}

lpp-MessageBody CHOICE {

c1 CHOICE {

provideCapabilities SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

provideCapabilities-r9 SEQUENCE {

commonIEsProvideCapabilities

Dependent on UE capabilities

Rel-14 onwards

a-gnss-ProvideCapabilities

Dependent on UE capabilities

otdoa-ProvideCapabilities

Dependent on UE capabilities

ecid-ProvideCapabilities

Dependent on UE capabilities

epdu-ProvideCapabilities

Not present

sensor-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

tbs-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

wlan-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

bt-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

}

}

}

}

}

}

Table 7.3.4.3.3.3-8: LPP Request Assistance Data (step 3, Table 7.3.4.3.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

targetDevice

transactionNumber

(0..255)

}

endTransaction

FALSE

sequenceNumber

(0..255)

acknowledgement SEQUENCE {

Present or not present

ackRequested

TRUE

ackIndicator

Not present

}

lpp-MessageBody CHOICE {

c1 CHOICE {

requestAssistanceData SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

requestAssistanceData-r9 SEQUENCE {

commonIEsRequestAssistanceData

Present or not present

a-gnss-RequestAssistanceData

Present for sub-test 15

otdoa-RequestAssistanceData

Not present

epdu-RequestAssistanceData

Not present

sensor-RequestAssistanceData-r14

Present for sub-test 18

Rel-14 onwards

tbs-RequestAssistanceData-r14

Present for sub-test 16

wlan-RequestAssistanceData-r14

Present for sub-test 17

Rel-14 onwards

}

}

}

}

}

}

Table 7.3.4.3.3.3-9: LPP Provide Assistance Data (step 4, Table 7.3.4.3.3.2-1)

Derivation Path: Table 5.4-2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

targetDevice

transactionNumber

(0..255)

Contains the same value as the corresponding field in the LPP Request Assistance Data message in step 3 Table 7.3.4.3.3.2-1

}

endTransaction

TRUE

sequenceNumber

Not present

acknowledgement SEQUENCE {

Present if acknowledgement field is included by the UE at step 3, Table 7.3.4.3.3.2-1.

ackRequested

FALSE

ackIndicator

(0..255)

Contains the same value as the sequenceNumber in step 3, Table 7.3.4.3.3.2-1

}

lpp-MessageBody CHOICE {

c1 CHOICE {

provideAssistanceData SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

provideAssistanceData-r9 SEQUENCE {

a-gnss-ProvideAssistanceData

The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.3.3.2‑1 which are available according to TS 37.571-5 [12].

sensor-ProvideAssistanceData-r14

The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.3.3.2-1 which are available according to subclause 5.4.1.5.

Rel-14 onwards

tbs-ProvideAssistanceData-r14

The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.3.3.2-1 which are available according to subclause 5.4.1.3.

Rel-14 onwards

wlan-ProvideAssistanceData-r14

The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.3.3.2-1 which are available according to subclause 5.4.1.4.

Rel-14 onwards

}

}

}

}

}

}

Table 7.3.4.3.3.3-10: LPP Provide Location Information (step 5, Table 7.3.4.3.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

locationServer

transactionNumber

(0..255)

Contains the same value as the corresponding field in LPP Request Location Information message in step 2, Table 7.3.4.3.3.1-1

}

endTransaction

TRUE

sequenceNumber

(0..255)

acknowledgement SEQUENCE {

Present, or not present

ackRequested

TRUE

ackIndicator

Not present

}

lpp-MessageBody CHOICE {

c1 CHOICE {

provideLocationInformation SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

provideLocationInformation-r9

SEQUENCE {

commonIEsProvideLocationInformation
SEQUENCE {

Present

locationEstimate

Present.

Any value acceptable

velocityEstimate

Not present

locationError

Not present

earlyFixReport-r12

Not present

Rel-12 onwards

}

a-gnss-ProvideLocationInformation
SEQUENCE {

Present for sub-test 15

gnss-SignalMeasurementInformation

Not present

gnss-LocationInformation
SEQUENCE {

Present

measurementReferenceTime

Any value acceptable

agnss-List

Any value acceptable

}

gnss-Error

Not present

}

otdoa-ProvideLocationInformation

Not present

ecid-ProvideLocationInformation

Not present

epdu-ProvideLocationInformation

Not present

sensor-ProvideLocationInformation-r13

Present for sub-test 18

Rel-13 onwards

tbs-ProvideLocationInformation-r13

Present for sub-test 16

Rel-13 onwards

wlan-ProvideLocationInformation-r13

Present for sub-test 17

Rel-13 onwards

bt-ProvideLocationInformation-r13

Not present

Rel-13 onwards

}

}

}

}

}

}

Table 7.3.4.3.3.3-11: LPP Acknowledgement (steps 1c and 5a, Table 7.3.4.3.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID

Not present

endTransaction

TRUE

sequenceNumber

Not present

acknowledgement SEQUENCE {

ackRequested

FALSE

ackIndicator

(0..255)

Contains the same value of the sequenceNumber field in step 1b or 5, Table 7.3.4.3.3.2-1.

}

lpp-MessageBody

Not present.

}

7.3.4.4 E-SMLC Initiated Position Measurement without assistance data: UE‑Assisted

7.3.4.4.1 Test Purpose (TP)

(1)

with { a NAS signalling connection for EPC-NI-LR session existing }

ensure that {
when { UE has no assistance data stored and receives a location request for UE-assisted and the
UE requires assistance data in order to fulfill the location request }

then { UE sends a REQUEST ASSISTANCE DATA message followed by a PROVIDE LOCATION INFORMATION
message containing location measurements }

}

7.3.4.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.355, clause 5.2.3, 5.2.4, 5.3.3 and 5.3.4.

[TS 36.355, clause 5.2.3]

When triggered to transmit a RequestAssistanceData message, the target device shall:

1> set the IEs for the positioning-method-specific request for assistance data to request the data indicated by upper layers.

[TS 36.355, clause 5.2.4]

Upon receiving a ProvideAssistanceData message, the target device shall:

1> for each positioning method contained in the message:

2> deliver the related assistance data to upper layers.

[TS 36.355, clause 5.3.3]

Upon receiving a RequestLocationInformation message, the target device shall:

1> if the requested information is compatible with the target device capabilities and configuration:

2> include the requested information in a ProvideLocationInformation message;

2> set the IE LPP-TransactionID in the response to the same value as the IE LPP-TransactionID in the received message;

2> deliver the ProvideLocationInformation message to lower layers for transmission.

1> otherwise:

[…]

[TS 36.355, clause 5.3.4]

When triggered to transmit ProvideLocationInformation message, the target device shall:

1> for each positioning method contained in the message:

2> set the corresponding IE to include the available location information;

1> deliver the response to lower layers for transmission.

7.3.4.4.3 Test description

7.3.4.4.3.1 Pre-test conditions

System Simulator:

– Sub-tests 15, 16, 17, 18: Cell 1.

– Sub-test 5 and 7: Cells 1 and 2, as specified in 5.2.2.

– Satellite signals (Sub-test 15): As specified in 5.2.1.

– MBS signals (Sub-test 16): As specified in 5.2.4 .

– WLAN signals (Sub-test 17): As specified in 5.2.5 .

UE:

– The UE shall begin the test with no assistance data stored.

Preamble:

– The UE is in state Generic RB Established (state 3) according to 3GPP 36.508 [8].

Related PICS/PIXIT Statements:

– Method of triggering an LPP Request Assistance Data message.

7.3.4.4.3.2 Test procedure sequence

This test case includes sub-test cases dependent on the positioning method(s) supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 7.3.4.4.3.2-0 below:

Table 7.3.4.4.3.2-0: Sub-test case numbers

Sub-Test Case Number

Supported Positioning Methods

1

Void

2

Void

3

Void

4

Void

5

UE supporting OTDOA

7

UE supporting GNSS(1) and OTDOA

8

Void

9

Void

10

Void

15

UE supporting GNSS(1)

16

UE supporting MBS (Rel-14 onwards)

17

UE supporting WLAN (Rel-14 onwards)

18

UE supporting Sensor (Rel-14 onwards)

NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE

Table 7.3.4.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

IF

sub-test 7 or 15 or 16 or 17 or 18
THEN

The stored assistance data in the UE are cleared.

<–

RESET UE POSITIONING STORED INFORMATION

1a

IF

Sub-test 5 or 7

THEN

The stored OTDOA assistance data in the UE are cleared.

<–

RESET UE POSITIONING STORED INFORMATION

1b

The SS sends a LPP message of type Request Capabilities.

<–

DLInformationTransfer

(LPP REQUEST CAPABILITIES)

1c

The UE sends a LPP message of type Provide Capabilities including the UE positioning capabilities.

–>

ULInformationTransfer

(LPP PROVIDE CAPABILITIES)

1d

IF

the UE LPP message at step 1c includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

2

The SS sends a LPP message of type Request Location Information including a request for location measurements.

<–

DLInformationTransfer

(LPP REQUEST LOCATION INFORMATION)

3

The UE sends a LPP message of type Request Assistance.NOTE: This requires a method of triggering a Request Assistance Data message.

–>

ULInformationTransfer

(LPP REQUEST ASSISTANCE DATA)

1

P

4

The SS sends a LPP message of type Provide Assistance Data.

<–

DLInformationTransfer

(LPP PROVIDE ASSISTANCE DATA)

4a

IF sub-test 7 THEN the UE may send a second LPP message of type Request Assistance Data including a request for GNSS assistance data or OTDOA assistance data.

–>

ULInformationTransfer

(LPP REQUEST ASSISTANCE DATA)

1

P

4b

IF in step 4a the UE sends a second LPP message of type Request Assistance Data THEN the SS sends a LPP message of type Provide Assistance Data.

<–

DLInformationTransfer

(LPP PROVIDE ASSISTANCE DATA)

Steps 5a1-5a2 and 5b1-5b4 represent alternative UE behaviours depending on the UE implementation

5a1 (Note 1)

All sub-tests:

The UE sends a LPP message of type Provide Location Information including location measurements.

–>

ULInformationTransfer

(LPP PROVIDE LOCATION INFORMATION)

1

P

5a2

IF

the UE LPP message at step 5a1 includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

5b1 (Note 2)

IF sub-test 7

THEN

The UE sends a LPP message of type Provide Location Information including "early fix" location measurements.

–>

ULInformationTransfer

(LPP PROVIDE LOCATION INFORMATION)

5b2

IF

the UE LPP message at step 5b1 includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

5b3

The UE sends a LPP message of type Provide Location Information including location measurements.

–>

ULInformationTransfer

(LPP PROVIDE LOCATION INFORMATION)

1

P

5b4

IF

the UE LPP message at step 5b3 includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

Note 1: This alternative is applicable to all releases of LPP and may be followed even in the case of sub-test 7 and LPP release 12 onwards.

Note 2: This alternative is applicable only to LPP release 12 onwards.

7.3.4.4.3.3 Specific message contents

Table 7.3.4.4.3.3-1: RESET UE POSITIONING STORED INFORMATION (step 1, Table 7.3.4.4.3.2-1)

Derivation Path: 36.509 clause 6.9

Information Element

Value/remark

Comment

Condition

UE Positioning Technology

Sub-tests 7, 15: 0 0 0 0 0 0 0 0

Sub-test 16: 0 0 0 0 0 0 1 0

Sub-test 17: 0 0 0 0 0 0 1 1

Sub-test 18: 0 0 0 0 0 1 0 1

Sub-tests 7, 15: GNSS

Sub-test 16: MBS

Sub-test 17: WLAN

Sub-test 18: Sensor

Table 7.3.4.4.3.3-2: RESET UE POSITIONING STORED INFORMATION (step 1a, Table 7.3.4.4.3.2-1)

Derivation Path: 36.509 clause 6.9

Information Element

Value/remark

Comment

Condition

UE Positioning Technology

0 0 0 0 0 0 0 1

OTDOA

Table 7.3.4.4.3.3-3: DLInformationTransfer (steps 1b, 1d, 2, 4, 4b, 5a2, 5b2 and 5b4, Table 7.3.4.4.3.2-1)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

DLInformationTransfer ::= SEQUENCE {

rrc-TransactionIdentifier

criticalExtensions CHOICE {

c1 CHOICE {

dlInformationTransfer-r8 SEQUENCE {

dedicatedInfoType CHOICE {

dedicatedInfoNAS OCTET STRING

Set according to Table 7.3.4.4.3.3-4

DOWNLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.3.4.4.3.3-4: DOWNLINK GENERIC NAS TRANSPORT (steps 1b, 1d, 2, 4, 4b, 5a2, 5b2 and 5b4, Table 7.3.4.4.3.2‑1)

Derivation Path: 24.301 Table 8.2.31.1

Information Element

Value/remark

Comment

Condition

Protocol discriminator

EPS mobility management messages

Security header type

0000

Plain NAS message

Downlink generic NAS transport message identity

01101000

Downlink generic NAS transport

Generic message container type

00000001

LTE Positioning Protocol (LPP) message container

Generic message container

Step 1b:

Set according to Table 7.3.4.4.3.3-4a

LPP Request Capabilities

Step 2:

Set according to Table 7.3.4.4.3.3-5

LPP Request Location Information

Steps 4 and 4b:

Set according to Table 7.3.4.4.3.3-10

LPP Provide Assistance Data

Steps 1d, 5a2, 5b2 and 5b4:

Set according to Table 7.3.4.4.3.3-12

LPP Acknowledgement

Additional information

Present

Routing Identifier/

Correlation ID

Table 7.3.4.4.3.3-4a: LPP Request Capabilities (step 1b, Table 7.3.4.4.3.2-1)

Derivation Path: Table 5.4-1

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-1

Table 7.3.4.4.3.3-5: LPP Request Location Information (step 2, Table 7.3.4.4.3.2-1)

Derivation Path: Table 5.4-3

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-3 with the following exceptions:

locationInformationType

locationMeasurementsRequired

a-gnss-RequestLocationInformation

Set according to Table 7.3.4.4.3.3-6

Sub-tests 7, 15

otdoa-RequestLocationInformation

Set according to Table 7.3.4.4.3.3-6a

Sub-test 5, 7

qos SEQUENCE {

horizontalAccuracy

Not present

verticalCoordinateRequest

FALSE

verticalAccuracy

Not present

responseTime SEQUENCE {

time

32

responseTimeEarlyFix-r12

Sub-tests 5, 15, 16: not present

Sub-test 7: 10

Rel-12 onwards

}

velocityRequest

FALSE

}

sensor-RequestLocationInformation-r14

Set according to Table 7.3.4.4.3.3-6c

Rel-14 onwards

Sub-test 18

tbs-RequestLocationInformation-r13

Set according to Table 7.3.4.4.3.3-6b

Rel-13 onwards

Sub-test 16

wlan-RequestLocationInformation-r14

Set according to Table 7.3.4.4.3.3-6d

Rel-14 onwards

Sub-test 17

Table 7.3.4.4.3.3-6: A-GNSS Request Location Information (step 2, Table 7.3.4.4.3.2-1)

Derivation Path: Table 5.4-4

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-4 with the following exceptions:

assistanceAvailability

TRUE

multiFreqMeasReq

TRUE, if UE supports multi frequency GNSS

MultiFreqAGNSS

Condition

Description

MultiFreqAGNSS

The UE supports at least one of pc_A_GPS_L2C, pc_A_GPS_L5, pc_QZSS_QZS_L1C, pc_QZSS_QZS_L2C, pc_QZSS_QZS_L5, pc_GLONASS_G2, pc_GLONASS_G3, pc_GALILEO_E5a, pc_GALILEO_E5b, pc_GALILEO_E6, pc_GALILEO_E5aE5b or pc_BDS_B1C

Table 7.3.4.4.3.3-6a: OTDOA Request Location Information (step 2, Table 7.3.4.4.3.2-1)

Derivation Path: Table 5.4-5

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-5 with the following exceptions:

assistanceAvailability

TRUE

Table 7.3.4.4.3.3-6b: TBS Request Location Information (step 2, Table 7.3.4.4.3.2-1)

Derivation Path: Table 5.4-7

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-7 with the following exceptions:

mbsAssistanceAvailability-r14

TRUE

Rel-14 onwards

Table 7.3.4.4.3.3-6c: Sensor Request Location Information (step 2, Table 7.3.4.4.3.2-1)

Derivation Path: Table 5.4-10

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-10 with the following exceptions:

assistanceAvailability-r14

TRUE

Rel-14 onwards

Table 7.3.4.4.3.3-6d: WLAN Request Location Information (step 2, Table 7.3.4.4.3.2-1)

Derivation Path: Table 5.4-8

Information Element

Value/remark

Comment

Condition

As defined in Table 5.4-8 with the following exceptions:

assistanceAvailability-r14

TRUE

Rel-14 onwards

Table 7.3.4.4.3.3-7: ULInformationTransfer (steps 1c, 3, 4a, 5a1, 5b1 and 5b3, Table 7.3.4.4.3.2-1)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

ULInformationTransfer ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ulInformationTransfer-r8 SEQUENCE {

dedicatedInfoType CHOICE {

dedicatedInfoNAS OCTET STRING

Set according to Table 7.3.4.4.3.3-8

UPLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.3.4.4.3.3-8: UPLINK GENERIC NAS TRANSPORT (steps 1c, 3, 4a, 5a1, 5b1 and 5b3, Table 7.3.4.4.3.2-1)

Derivation Path: 24.301 Table 8.2.32.1

Information Element

Value/remark

Comment

Condition

Protocol discriminator

0111

EPS mobility management messages

Security header type

0000

Plain NAS message

Uplink generic NAS transport message identity

01101001

Uplink generic NAS transport

Generic message container type

00000001

LTE Positioning Protocol (LPP) message container

Generic message container

Step 1c:

Set according to Table

7.3.4.4.3.3-8a

LPP Provide Capabilities

Steps 3 and 4a:

Set according to Table

7.3.4.4.3.3-9

LPP Request Assistance Data

Steps 5a1, 5b1 and 5b3:

Set according to Table

7.3.4.4.3.3-11

LPP Provide Location Information

Additional information

Present

The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 1b, 2 or 4 Table 7.3.4.4.3.2-1)

Table 7.3.4.4.3.3-8a: LPP Provide Capabilities. (step 1c, Table 7.3.4.4.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

locationServer

transactionNumber

(0..255)

Contains the same value as the corresponding field in the LPP Request Capabilities message in step 1b, Table 7.3.4.4.3.2-1

}

endTransaction

TRUE

sequenceNumber

(0..255)

acknowledgement SEQUENCE {

Present, or not present

ackRequested

TRUE

ackIndicator

Not present

}

lpp-MessageBody CHOICE {

c1 CHOICE {

provideCapabilities SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

provideCapabilities-r9 SEQUENCE {

commonIEsProvideCapabilities

Dependent on UE capabilities

Rel-14 onwards

a-gnss-ProvideCapabilities

Dependent on UE capabilities

otdoa-ProvideCapabilities

Dependent on UE capabilities

ecid-ProvideCapabilities

Dependent on UE capabilities

epdu-ProvideCapabilities

Not present

sensor-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

tbs-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

wlan-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

bt-ProvideCapabilities-r13

Dependent on UE capabilities

Rel-13 onwards

}

}

}

}

}

}

Table 7.3.4.4.3.3-9: LPP Request Assistance Data (steps 3 and 4a, Table 7.3.4.4.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

targetDevice

transactionNumber

(0..255)

}

endTransaction

FALSE

sequenceNumber

(0..255)

acknowledgement SEQUENCE {

Present or not present

ackRequested

TRUE

ackIndicator

Not present

}

lpp-MessageBody CHOICE {

c1 CHOICE {

requestAssistanceData SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

requestAssistanceData-r9 SEQUENCE {

commonIEsRequestAssistanceData

Present or not present

a-gnss-RequestAssistanceData

Present for sub-tests 7, 15

For sub-test 7, in case the UE sends two separate LPP Request Assistance Data messages in steps 3 and 4a then one contains a-gnss-RequestAssistanceData and the other contains otdoa-RequestAssistanceData

otdoa-RequestAssistanceData

Present for sub-test 5,7

For sub-test 7, in case the UE sends two separate LPP Request Assistance Data messages in steps 3 and 4a then one contains a-gnss-RequestAssistanceData and the other contains otdoa-RequestAssistanceData

epdu-RequestAssistanceData

Not present

sensor-RequestAssistanceData-r14

Present for sub-test 18

Rel-14 onwards

tbs-RequestAssistanceData-r14

Present for sub-test 16

Release 14 onwards

wlan-RequestAssistanceData-r14

Present for sub-test 17

Rel-14 onwards

}

}

}

}

}

}

Table 7.3.4.4.3.3-10: LPP Provide Assistance Data (steps 4 and 4b, Table 7.3.4.4.3.2-1)

Derivation Path: Table 5.4-2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

targetDevice

transactionNumber

(0..255)

Contains the same value as the corresponding field in the LPP Request Assistance Data message in step 3 or 4a Table 7.3.4.4.3.2-1.

}

endTransaction

TRUE

sequenceNumber

Not present

acknowledgement SEQUENCE {

Present if acknowledgement field is included by the UE at step 3 or 4a, Table 7.3.4.4.3.2-1.

ackRequested

FALSE

ackIndicator

(0..255)

Contains the same value as the sequenceNumber in step 3 or 4a, Table 7.3.4.4.3.2-1.

}

lpp-MessageBody CHOICE {

c1 CHOICE {

provideAssistanceData SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

provideAssistanceData-r9 SEQUENCE {

a-gnss-ProvideAssistanceData

The SS provides the assistance data requested by the UE at step 3 or 4a, Table 7.3.4.4.3.2‑1 which are available according to TS 37.571-5 [12].

For sub-test 7, in case the UE sends two separate LPP Request Assistance Data messages in steps 3 and 4a then the SS sends two seperate LPP Provide Assistance Data messages in steps 4 and 4b each containing the relevant assistance data.

Sub-tests 7, 15

otdoa-ProvideAssistanceData

The SS provides the assistance data requested by the UE at step 3 or 4a, Table 7.3.4.4.3.2-1 according to subclause 5.4.1.2.

For sub-test 7, in case the UE sends two separate LPP Request Assistance Data messages in steps 3 and 4a then the SS sends two seperate LPP Provide Assistance Data messages in steps 4 and 4b each containing the relevant assistance data.

Sub-tests 5,7

sensor-ProvideAssistanceData-r14

The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.4.3.2-1 which are available according to subclause 5.4.1.5.

Release 14 onwards

Sub-test 18

tbs-ProvideAssistanceData-r14

The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.4.3.2-1 which are available according to subclause 5.4.1.3.

Release 14 onwards

Sub-test 16

wlan-ProvideAssistanceData-r14

The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.4.3.2-1 which are available according to subclause 5.4.1.4.

Release 14 onwards

Sub-test 17

}

}

}

}

}

}

Table 7.3.4.4.3.3-11: LPP Provide Location Information (steps 5a1, 5b1 and 5b3, Table 7.3.4.4.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID SEQUENCE {

initiator

locationServer

transactionNumber

(0..255)

Contains the same value as the corresponding field in LPP Request Location Information message in step 2, Table 7.3.4.4.3.1-1

}

endTransaction

Step 5a1, 5b3: TRUE

Step 5b1: FALSE

sequenceNumber

(0..255)

acknowledgement SEQUENCE {

Present, or not present

ackRequested

TRUE

ackIndicator

Not present

}

lpp-MessageBody CHOICE {

c1 CHOICE {

provideLocationInformation SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

provideLocationInformation-r9 SEQUENCE {

commonIEsProvideLocationInformation SEQUENCE {

Step 5a1, 5b3: May be present

Step 5b1: Present

locationEstimate

Not present

velocityEstimate

Not present

locationError

Not present

earlyFixReport-r12

Step 5a1, 5b3: Not present

Rel-12 onwards

Step 5b1: Any value acceptable

}

a-gnss-ProvideLocationInformation SEQUENCE {

Step 5a1: Present for sub-tests 7, 15

Step 5b1, 5b3: May be present

One of a-gnss-ProvideLocationInformation or otdoa-ProvideLocationInformation shall be present

gnss-SignalMeasurementInformation SEQUENCE {

Present

measurementReferenceTime

Present. Any value acceptable

gnss-MeasurementList SEQUENCE (SIZE(1..n)) OF SEQUENCE {

Present. SIZE n is the number of GNSSs supported by the UE, one instance for each GNSS supported by the UE

gnss-ID

Present

gnss-SgnMeasList

Present, one instance for each frequency within the GNSS supported by the UE. Any value acceptable

}

}

}

gnss-LocationInformation

Not present

gnss-Error

Not present

}

otdoa-ProvideLocationInformation

SEQUENCE {

Step 5a1: Present for sub-tests 5, 7

Step 5b1, 5b3: May be present

One of a-gnss-ProvideLocationInformation or otdoa-ProvideLocationInformation shall be present

otdoa-SignalMeasurementInformation

Present. Any value acceptable

otdoa-Error

May be present

}

ecid-ProvideLocationInformation

Not present

epdu-ProvideLocationInformation

Not present

sensor-ProvideLocationInformation-r13

Present for sub-test 18

Rel-13 onwards

tbs-ProvideLocationInformation-r13

Present for sub-test 16

Rel-13 onwards

wlan-ProvideLocationInformation-r13

Present for sub-test 17

Rel-13 onwards

bt-ProvideLocationInformation-r13

Not present

Rel-13 onwards

}

}

}

}

}

}

}

Table 7.3.4.4.3.3-12: LPP Acknowledgement (steps 1d, 5a2, 5b2 and 5b4, Table 7.3.4.4.3.2-1)

Derivation Path: 36.355 clause 6.2

Information Element

Value/remark

Comment

Condition

LPP-Message ::= SEQUENCE {

transactionID

Not present

endTransaction

TRUE

sequenceNumber

Not present

acknowledgement SEQUENCE {

ackRequested

FALSE

ackIndicator

(0..255)

Contains the same value of the sequenceNumber field in step 1c or 5a1 or 5b1 or 5b3, Table 7.3.4.4.3.2-1.

}

lpp-MessageBody

Not present.

}