7.3.5 LPP Abort

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

7.3.5.1 E-SMLC initiated Abort

7.3.5.1.1 Test Purpose (TP)

(1)

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

ensure that {
when { UE receives a LPP Abort message carrying the transaction ID of an on-going procedure }

then { UE aborts the on-going procedure }

}

7.3.5.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.355, clause 5.5.3.

[TS 36.355, clause 5.5.3]

Upon receiving an Abort message, a device shall:

1> abort any ongoing procedure associated with the transaction ID indicated in the message.

7.3.5.1.3 Test description

7.3.5.1.3.1 Pre-test conditions

System Simulator:

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

– Sub-test 5: Cell 1 as specified in 5.2.2.

UE:

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

Preamble:

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

Related PICS/PIXIT Statements:

–

7.3.5.1.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.5.1.3.2-0 below:

Table 7.3.5.1.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

8

Void

9

Void

10

Void

11

UE supporting WLAN (Rel-13 only)

12

UE supporting MBS (Rel-13 only)

13

UE supporting Bluetooth

15

UE supporting GNSS(1)

16

UE supporting MBS (Rel-14 onwards)

17

UE supporting WLAN (Rel-14 onwards)

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

Note that this test case does not include a sub-test for the case where ECID or Sensor is supported by the UE as the behaviour required cannot be guaranteed in these cases.

Table 7.3.5.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

00

The SS sends a RESET UE POSITIONING STORED INFORMATION message.

<–

RESET UE POSITIONING STORED INFORMATION

–

–

0

The SS sends a LPP message of type Request Capabilities.

<–

DLInformationTransfer

(LPP REQUEST CAPABILITIES)

–

–

0a

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

–>

ULInformationTransfer

(LPP PROVIDE CAPABILITIES)

–

–

0b

IF

the UE LPP message at step 0a includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

–

–

0c

IF NOT

Sub-test 11 or 12 or 13

THEN

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

<–

DLInformationTransfer

(LPP PROVIDE ASSISTANCE DATA)

1

The SS sends a LPP message of type Request Location Information including a transaction ID.

<–

DLInformationTransfer

(LPP REQUEST LOCATION INFORMATION)

–

–

2

Immediately after step 1, the SS sends a LPP message of type Abort using the same transaction ID chosen in step 1.

<–

DLInformationTransfer

(LPP ABORT)

–

–

3

The SS waits for 10 seconds to ensure the UE does not send a LPP message of type Provide Location Information with the same transaction ID as in step 1.

1

P

7.3.5.1.3.3 Specific message contents

Table 7.3.5.1.3.3-0: RESET UE POSITIONING STORED INFORMATION (step 00, Table 7.3.5.1.3.2-1)

Derivation Path: 36.509 clause 6.9

Information Element

Value/remark

Comment

Condition

UE Positioning Technology

Sub-tests 15: 0 0 0 0 0 0 0 0

Sub-test 5: 0 0 0 0 0 0 0 1

Sub-test 11, 17: 0 0 0 0 0 0 1 1

Sub-tests 12, 16: 0 0 0 0 0 0 1 0

Sub-test 13: 0 0 0 0 0 1 0 0

Sub-tests 15: AGNSS

Sub-test 5: OTDOA

Sub-test 11, 17: WLAN

Sub-tests 12, 16: MBS

Sub-test 13: Bluetooth

Table 7.3.5.1.3.3-1: DLInformationTransfer (steps 0, 0b, 0c, 1 and 2, Table 7.3.5.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.5.1.3.3-2

DOWNLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.3.5.1.3.3-2: DOWNLINK GENERIC NAS TRANSPORT (steps 0, 0b, 0c, 1 and 2, Table 7.3.5.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 0:

Set according to Table 7.3.5.1.3.3-2a

LPP Request Capabilities.

Step 0b:

Set according to Table 7.3.5.1.3.3-2b

LPP Acknowledgement

Step 0c:

Set according to Table 7.3.5.1.3.3-2c

LPP Provide Assistance Data

Step 1:

Set according to Table 7.3.5.1.3.3-3

LPP Request Location Information

Step 2:

Set according to Table 7.3.5.1.3.3-4

LPP Abort

Additional information

Present

Routing Identifier/

Correlation ID

Table 7.3.5.1.3.3-2a: LPP Request Capabilities (step 0, Table 7.3.5.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.5.1.3.3-2b: LPP Acknowledgement (step 0b, Table 7.3.5.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 0a, Table 7.3.5.1.3.2‑1.

}

lpp-MessageBody

Not present.

}

Table 7.3.5.1.3.3-2c: LPP Provide Assistance Data (step 0c, Table 7.3.5.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)

}

OTDOA-NeighbourCellInfoList ::= SEQUENCE (SIZE(1)) OF SEQUENCE {

Sub-test 5

SEQUENCE (SIZE(18)) OF SEQUENCE {

Sequence contains 18 instances of the following data.

physCellId

Refer to Sequence data values in Table 7.3.5.1.3.3-2d

cellGlobalId

For values of cellidentity refer to Sequence data values in Table 7.3.5.1.3.3-2d

earfcn

Not present

Same as for the reference cell

cpLength

Not present

Same as for the reference cell

prsInfo

Not present

Same as for the reference cell

antennaPortConfig

Not present

Same as for the reference cell

slotNumberOffset

Not present

Same as for the reference cell

prs-SubframeOffset

Not present

Same as for the reference cell

expectedRSTD

Refer to Sequence data values in Table 7.3.5.1.3.3-2d

expectedRSTD-Uncertainty

Refer to Sequence data values in Table 7.3.5.1.3.3-2d

earfcn-v9a0

Not present

Same as for the reference cell

tpId-r14

Not present

Transmission Points not used

Rel-14 onwards

prs-only-tp-r14

Not present

Not required

Rel-14 onwards

cpLengthCRS-r14

Not present

Not required

Rel-14 onwards

sameMBSFNconfigNeighbour-r14

TRUE

Same as for the reference cell

Rel-14 onwards

dlBandwidth-r14

Not present

Same as for the reference cell and PRS frequency hopping not used

Rel-14 onwards

addPRSconfigNeighbour-r14

Not present

No additional PRS configuration(s)

Rel-14 onwards

}

}

Table 7.3.5.1.3.3-2d: Sequence data values for 18 instances of sequence for Table 7.3.5.1.3.3-2c

Cell

Value physCellId

Value cellidentity (E-UTRAN Cell Identity)

Value expectedRSTD

Value expectedRSTD-Uncertainty

Comment

Value eNB ID

Value Cell Identity

Cell 2

2

‘0000 0000 0000 0000 0001’B

‘0000 0010’B

8192

10

As defined for Cell 2 in 36.508 [8]

Cell 4

4

‘0000 0000 0000 0000 0011’B

‘0000 0100’B

8192

10

As defined for Cell 4 in 36.508 [8]

Dummy cell

1

‘0000 0000 0000 0000 0001’B

‘0000 0001’B

8253

51

Dummy cell

3

‘0000 0000 0000 0000 0010’B

‘0000 0011’B

8211

51

Dummy cell

6

‘0000 0000 0000 0000 0100’B

‘0000 0110’B

8221

51

Dummy cell

7

‘0000 0000 0000 0000 0110’B

‘0000 0111’B

8192

51

Dummy cell

8

‘0000 0000 0000 0000 0010’B

‘0000 1000’B

8233

51

Dummy cell

9

‘0000 0000 0000 0000 0100’B

‘0000 1001’B

8161

51

Dummy cell

10

‘0000 0000 0000 0000 0101’B

‘0000 1010’B

8226

51

Dummy cell

11

‘0000 0000 0000 0000 0110’B

‘0000 1011’B

8232

51

Dummy cell

16

‘0000 0000 0000 0000 0010’B

‘0001 0000’B

8223

51

Dummy cell

111

‘0000 0000 0000 0000 1100’B

‘0110 1111’B

8236

51

Dummy cell

118

‘0000 0000 0000 0000 1111’B

‘0111 0110’B

8223

51

Dummy cell

119

‘0000 0000 0000 0000 1110’B

‘0111 0111’B

8221

51

Dummy cell

120

‘0000 0000 0000 0000 1111’B

‘0111 1000’B

8223

51

Dummy cell

122

‘0000 0000 0000 0000 1010’B

‘0111 1010’B

8243

51

Dummy cell

125

‘0000 0000 0000 0000 1011’B

‘0111 1101’B

8253

51

Dummy cell

126

‘0000 0000 0000 0000 1100’B

‘0111 1110’B

8257

51

Table 7.3.5.1.3.3-3: LPP Request Location Information (step 1, Table 7.3.5.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:

transactionID SEQUENCE {

initiator

locationServer

transactionNumber

0

}

locationInformationType

locationEstimateRequired

In case of "UE-based" Location method supported by the UE

locationMeasurementsRequired

In case of "UE-assisted" Location method supported by the UE

time

10

Table 7.3.5.1.3.3-4: LPP Abort (step 2, Table 7.3.5.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

}

endTransaction

TRUE

sequenceNumber

Not present.

acknowledgement

Not present

lpp-MessageBody CHOICE {

c1 CHOICE {

abort SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

abort-r9 SEQUENCE {

commonIEsAbort SEQUENCE {

abortCause

networkAbort

}

epdu-Abort

Not present

}

}

}

}

}

}

}

Table 7.3.5.1.3.3-5: ULInformationTransfer (step 0a, Table 7.3.5.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.5.1.3.3-6

UPLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.3.5.1.3.3-6: UPLINK GENERIC NAS TRANSPORT (step 0a, Table 7.3.5.1.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

Set according to Table 7.3.5.1.3.3-7

LPP Provide Capabilities

Additional information

Present

The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 0 Table 7.3.5.1.3.2-1)

Table 7.3.5.1.3.3-7: LPP Provide Capabilities. (step 0a, Table 7.3.5.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 0, Table 7.3.5.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

}

}

}

}

}

}