7.5 RRC Protocol Procedures

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

7.5.1 Inter-frequency RSTD measurement indication

7.5.1.1 Test Purpose (TP)

(1)

with { a NAS signalling connection existing }

ensure that {

when { the UE receives OTDOA assistance data including inter-frequency cells together with

a location request for OTDOA }

then { the UE initiates the RRC Inter-frequency RSTD measurement procedure to indicate

“start”.}

}

(2)

with { a NAS signalling connection existing }

ensure that {

when { the UE stops reporting inter-frequency RSTD measurements }

then { the UE initiates the RRC Inter-frequency RSTD measurement procedure to indicate

“stop”. }

}

7.5.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.355 clauses 6.5.1.2, 6.5.1.5, and TS 36.331 clauses 5.5.7.2, 5.7.7.3.

[TS 36.355, clause 6.5.1.2]

If inter-frequency neighbour cells are included in OTDOA-NeighbourCellInfoList, where an inter-frequency is a E-UTRA frequency which is different from the E-UTRA serving cell frequency, the LPP layer shall inform lower layers to start performing inter-frequency RSTD measurements for these neighbour cells and also provide to lower layers the information about these neighbour cells, e.g. EARFCN and PRS positioning occasion information.

[TS 36.355, clause 6.5.1.5]

If the target device stops reporting inter-frequency RSTD measurements, where the inter-frequency RSTD measurement is an OTDOA RSTD measurement with at least one cell on a frequency different from the serving cell frequency, the LPP layer shall inform lower layers that inter-frequency RSTD measurements are stopped.

[TS 36.331, clause 5.5.7.2]

The UE shall:

1> if and only if upper layers indicate to start performing inter-frequency RSTD measurements; and the UE requires measurement gaps for these measurements while measurement gaps are either not configured or not sufficient:

2> initiate the procedure to indicate start;

NOTE 1: The UE verifies the measurement gap situation only upon receiving the indication from upper layers. If at this point in time sufficient gaps are available, the UE does not initiate the procedure. Unless it receives a new indication from upper layers, the UE is only allowed to further repeat the procedure in the same PCell once per frequency if the provided measurement gaps are insufficient.

1> if and only if upper layers indicate to stop performing inter-frequency RSTD measurements:

2> initiate the procedure to indicate stop;

NOTE 2: The UE may initiate the procedure to indicate stop even if it did not previously initiate the procedure to indicate start.

[TS 36.331, clause 5.5.7.3]

The UE shall set the contents of InterFreqRSTDMeasurementIndication message as follows:

1> set the rstd-InterFreqIndication as follows:

2> if the procedure is initiated to indicate start of inter-frequency RSTD measurements:

3> set the rstd-InterFreqInfoList according to the information received from upper layers;

2> else if the procedure is initiated to indicate stop of inter-frequency RSTD measurements:

3> set the rstd-InterFreqIndication to the value stop;

1> submit the InterFreqRSTDMeasurementIndication message to lower layers for transmission, upon which the procedure ends;

7.5.1.3 Test description

7.5.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 as specified in 5.2.2.

UE:

Preamble:

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

Related PICS/PIXIT Statements:

– Support for inter-frequency RSTD measurements that require measurement gaps for these measurements.

7.5.1.3.2 Test procedure sequence

Table 7.5.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The stored OTDOA 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)

EXCEPTION: In parallel to the events described in Steps 2 to 6, the steps specified in Table 7.5.1.3.2-2 take place

2

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

<–

DLInformationTransfer

(LPP PROVIDE ASSISTANCE DATA)

3-5

Void

6

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

<–

DLInformationTransfer

(LPP REQUEST LOCATION INFORMATION)

EXCEPTION: In parallel with the events described in Steps 7 to 10, the steps specified in Table 7.5.1.3.2-3 take place.

7

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

–>

ULInformationTransfer

(LPP PROVIDE LOCATION INFORMATION)

7a

IF

the UE LPP message at step 7 includes an acknowledgment request

THEN

SS sends a LPP Acknowledgement response.

<–

DLInformationTransfer

(LPP ACKNOWLEDGEMENT)

8-10

Void

Table 7.5.1.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits an RRC InterFreqRSTDMeasurementIndication message to indicate “start”

–>

InterFreqRSTDMeasurementIndication

1

P

2

The SS transmits an RRCConnectionReconfiguration message to set up the measurement gap configuration

<–

RRCConnectionReconfiguration

3

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the set up of the measurement gap configuration

–>

RRCConnectionReconfigurationComplete

Table 7.5.1.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits an RRC InterFreqRSTDMeasurementIndication message to indicate “stop”

–>

InterFreqRSTDMeasurementIndication

2

P

2

The SS transmits an RRCConnectionReconfiguration message to release the measurement gap configuration

<–

RRCConnectionReconfiguration

3

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the release of the measurement gap configuration

–>

RRCConnectionReconfigurationComplete

7.5.1.3.3 Specific message contents

For the default message content as specified in subclause 5.4, the values for sub-test 5 are used.

Table 7.5.1.3.3-1: RESET UE POSITIONING STORED INFORMATION (step 1, Table 7.5.1.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.5.1.3.3-2: DLInformationTransfer (steps 1a, 1c, 2, 6 and 7a, Table 7.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.5.1.3.3-3

DOWNLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.5.1.3.3-3: DOWNLINK GENERIC NAS TRANSPORT (steps 1a, 1c, 2, 6 and 7a, Table 7.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 1a:

Set according to Table 7.5.1.3.3-3a

LPP Request Capabilities.

Step 2:

Set according to Table 7.5.1.3.3-4

LPP Provide Assistance Data

Step 6:

Set according to Table 7.5.1.3.3-8

LPP Request Location Information

Steps 1c and 7a:

Set according to Table 7.5.1.3.3-12

LPP Acknowledgement

Additional information

Present

Routing Identifier/

Correlation ID

Table 7.5.1.3.3-3a: LPP Request Capabilities (step 1a, Table 7.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.5.1.3.3-4: LPP Provide Assistance data (step 2, Table 7.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-ProvideAssistanceData SEQUENCE {

otdoa-NeighbourCellInfo

Set according to Table 7.5.1.3.3-5.

}

Table 7.5.1.3.3-5: OTDOA-NeighbourCellInfoList (step 2, Table 7.5.1.3.2-1)

Derivation Path: 36.355 clause 6.5.1.2

Information Element

Value/remark

Comment

Condition

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

SEQUENCE (SIZE(1)) OF SEQUENCE {

Cell 3

physCellId

3

cellGlobalId SEQUENCE {

mcc

As defined for Cell 3 in 36.508 [8]

mnc

As defined for Cell 3 in 36.508 [8]

cellidentity

As defined for Cell 3 in 36.508 [8]

}

earfcn

For E-UTRA band < 65: as defined for Cell 3 in 36.508 [8]

For E-UTRA band > 64:

not present

cpLength

Not present

Same as for the reference cell

prsInfo SEQUENCE {

prs-Bandwidth

PRS are transmitted over the used system bandwidth (see subclause 5.2.2)

prs-ConfigurationIndex

12

numDL-Frames

sf-1

prs-MutingInfo-r9

Not present

PRS muting is not used.

prsID-r14

Not present

PRS-ID not used

Rel-14 onwards

add-numDL-Frames-r14

Not present

Not required

Rel-14 onwards

prsOccGroupLen-r14

Not present

No PRS occasion group configured

Rel-14 onwards

prsHoppingInfo-r14

Not present

PRS frequency hopping not used

Rel-14 onwards

}

antennaPortConfig

Not present

Same as for the reference cell

slotNumberOffset

Not present

Slot timing is the same as for reference cell

prs-SubframeOffset

10

expectedRSTD

8192

Value 0

expectedRSTD-Uncertainty

10

About 1 s

earfcn-v9a0

For E-UTRA band < 65:

not present

For E-UTRA Band > 64:

as defined for Cell 3 in 36.508 [8]

tpId-r14

Not present

Transmission Points not used

Rel-14 onwards

prs-only-tp-r14

Not present

Not required

Rel-14 onwards

cpLengthCRS-r14

Normal

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

}

SEQUENCE (SIZE(1)) OF SEQUENCE {

Cell 6

Assumes that earfcn for Cell 6 is different from earfcn for Cell 3.

physCellId

6

cellGlobalId SEQUENCE {

mcc

As defined for Cell 6 in 36.508 [8]

mnc

As defined for Cell 6 in 36.508 [8]

cellidentity

As defined for Cell 6 in 36.508 [8]

}

earfcn

For E-UTRA band < 65:
as defined for Cell 6 in 36.508 [8]

For E-UTRA band > 64:

not present

cpLength

Not present

Same as for the reference cell

prsInfo SEQUENCE {

prs-Bandwidth

PRS are transmitted over the used system bandwidth (see subclause 5.2.2)

prs-ConfigurationIndex

12

numDL-Frames

sf-1

prs-MutingInfo-r9

Not present

PRS muting is not used.

prsID-r14

Not present

PRS-ID not used

Rel-14 onwards

add-numDL-Frames-r14

Not present

Not required

Rel-14 onwards

prsOccGroupLen-r14

Not present

No PRS occasion group configured

Rel-14 onwards

prsHoppingInfo-r14

Not present

PRS frequency hopping not used

Rel-14 onwards

}

antennaPortConfig

Not present

Same as for the reference cell

slotNumberOffset

Not present

Slot timing is the same as for reference cell

prs-SubframeOffset

10

expectedRSTD

8192

Value 0

expectedRSTD-Uncertainty

10

About 1 s

earfcn-v9a0

For E-UTRA band < 65: not present

For E-UTRA band > 64:

as defined for Cell 6 in 36.508 [8]

tpId-r14

Not present

Transmission Points not used

Rel-14 onwards

prs-only-tp-r14

Not present

Not required

Rel-14 onwards

cpLengthCRS-r14

Normal

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.5.1.3.3-6: RRC InterFreqRSTDMeasurementIndication (step 1, Table 7.5.1.3.2-2)

Derivation Path: 36.331, clause 6.2.2

Information Element

Value/remark

Comment

Condition

InterFreqRSTDMeasurementIndication-r10 ::= SEQUENCE{

criticalExtensions CHOICE {

c1 CHOICE {

interFreqRSTDMeasurementIndication-r10

SEQUENCE {

rstd-InterFreqIndication-r10 CHOICE {

start SEQUENCE {

rstd-InterFreqInfoList-r10 SEQUENCE {

2 entries

carrierFreq-r10[1]

For E-UTRA band < 65: as defined for Cell 3 in 36.508 [8]

For E-UTRA band > 64: 65535

measPRS-Offset-r10[1]

(0..39)

carrierFreq-v1090[1]

For E-UTRA band < 65: not present

For E-UTRA band > 64: as defined for Cell 3 in 36.508 [8]

carrierFreq-r10[2]

For E-UTRA band < 65: as defined for Cell 6 in 36.508 [8]

For E-UTRA band > 64: 65535

measPRS-Offset-r10[2]

(0..39)

carrierFreq-v1090[2]

For E-UTRA band < 65:

Not present

For E-UTRA band > 64: as defined for Cell 6 in 36.508 [8]

}

}

}

lateNonCriticalExtension OCTET STRING

Not present

nonCriticalExtension SEQUENCE {}

Not present

}

criticalExtensionsFuture SEQUENCE {}

Not present

}

}

}

Table 7.5.1.3.3-7: RRCConnectionReconfiguration (step 2, Table 7.5.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

As defined in 36.508, Table 4.6.1-8 with the following exceptions:

measConfig ::= SEQUENCE {

measGapConfig CHOICE {

setup SEQUENCE {

gapOffset CHOICE {

gp0

Value of measPRS-Offset-r10 as provided by the UE in Table 7.5.1.3.3-6.

}

}

}

}

Table 7.5.1.3.3-8: LPP Request Location Information (step 6, Table 7.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:

locationInformationType

locationMeasurementsRequired

time

10

Table 7.5.1.3.3-9: ULInformationTransfer (steps 1b and 7, Table 7.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.5.1.3.3-10

UPLINK GENERIC NAS TRANSPORT

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 7.5.1.3.3-10: UPLINK GENERIC NAS TRANSPORT (steps 1b and 7, Table 7.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

Step 1b:

Set according to Table

7.5.1.3.3-10a

LPP Provide Capabilities

Step 7:

Set according to Table

7.5.1.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 1a or 6 Table 7.5.1.3.2-1)

Table 7.5.1.3.3-10a: LPP Provide Capabilities. (step 1b, Table 7.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 1a, Table 7.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

}

}

}

}

}

}

Table 7.5.1.3.3-11: LPP Provide Location Information (step 7, Table 7.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 LPP Request Location Information message in step 6, Table 7.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 {

provideLocationInformation SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

provideLocationInformation-r9

SEQUENCE {

commonIEsProvideLocationInformation

May be present. Any value acceptable

a-gnss-ProvideLocationInformation

Not present

otdoa-ProvideLocationInformation

May be present. Any value acceptable

ecid-ProvideLocationInformation

Not present

epdu-ProvideLocationInformation

Not present

sensor-ProvideLocationInformation-r13

Not present

Rel-13 onwards

tbs-ProvideLocationInformation-r13

Not present

Rel-13 onwards

wlan-ProvideLocationInformation-r13

Not present

Rel-13 onwards

bt-ProvideLocationInformation-r13

Not present

Rel-13 onwards

}

}

}

}

}

}

Table 7.5.1.3.3-12: LPP Acknowledgement (steps 1c and 7a, Table 7.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 1b or 7, Table 7.5.1.3.2-1

}

lpp-MessageBody

Not present.

}

Table 7.5.1.3.3-13: RRC InterFreqRSTDMeasurementIndication (step 1, Table 7.5.1.3.2-3)

Derivation Path: 36.331, clause 6.2.2

Information Element

Value/remark

Comment

Condition

InterFreqRSTDMeasurementIndication-r10 ::= SEQUENCE{

criticalExtensions CHOICE {

c1 CHOICE {

interFreqRSTDMeasurementIndication-r10

SEQUENCE {

rstd-InterFreqIndication-r10 CHOICE {

stop

NULL

}

lateNonCriticalExtension OCTET STRING

Not present

nonCriticalExtension SEQUENCE {}

Not present

}

criticalExtensionsFuture SEQUENCE {}

Not present

}

}

}

Table 7.5.1.3.3-14: RRCConnectionReconfiguration (step 2, Table 7.5.1.3.2-3)

Derivation Path: 36.508, Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

As defined in 36.508, Table 4.6.1-8 with the following exceptions:

measConfig ::= SEQUENCE {

measGapConfig CHOICE {

release

NULL

}

}

7.5.2 Void