11 E-UTRA and NR MBS measurement requirements
37.571-13GPPPart 1: Conformance test specificationRelease 16TSUser Equipment (UE) conformance specification for UE positioning
11.0 General
This clause defines the minimum performance requirements for MBS FDD and TDD E-UTRA UEs, and NR UEs.
The requirements in this clause that apply for NR UE include NG-RAN NR, EN-DC, NE-DC, NG-RAN E-UTRA and NGEN-DC.
Editor’s Note: For NR tests, the initial test conditions apply for NR UE in FR1. For FR2, initial test conditions are FFS.
11.1 MBS Measurement Reporting Delay (Release 13 only)
11.1.1 Test purpose
The purpose of the test is to verify that the MBS measurements meet the measurement time requirements specified in clause 4.2.3 of TS 37.171 [39] in an environment with fading propagation conditions specified in clause 4.8.2.2 (EPA 5 Hz).
11.1.2 Test applicability
This test applies to all types of E-UTRA UE that supports UE-assisted MBS with LPP Release 13 only.
11.1.3 Minimum conformance requirements
The MBS measurement reporting delay (response time) shall be <12000 msec.
The normative reference for this requirement is TS 37.171 [39] clauses 4.2.3 and A.3.1.
11.1.4 Test description
11.1.4.1 Initial conditions
Test environment: normal; see Annex G.
1. Connect SS and MSS to the UE antenna connector or antenna connectors as shown in figures A.6 or A.7.
2. Switch on the UE.
3. Establish a signalling connection according to the generic procedure in TS 36.508 [18] clause 4.5.3 (State 3, Generic RB established) on a channel in the Mid EARFCN range.
11.1.4.2 Test procedure
1. Set the MSS test parameters as specified in clause 11.1.5.
2. The SS shall send a RESET UE POSITIONING STORED INFORMATION message.
3. The SS shall send an LPP REQUEST CAPABILITIES message.
4. The UE shall transmit an LPP PROVIDE CAPABILITIES message indicating the TBS capabilities supported by the UE in the TBS-ProvideCapabilities IE.
5. The SS shall send a LPP REQUEST LOCATION INFORMATION message, including the TBS‑RequestLocationInformation IE. If the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP REQUEST LOCATION INFORMATION message.
6. The UE shall perform and report the code phase measurement for the simulated beacon. If the UE transmits a TBS‑ProvideLocationInformation IE including the transmitterID and codePhase fields for the simulated beacon within the required response time in 11.1.5, then the number of successful tests is increased by one. Otherwise the number of failure tests is increased by one.
7. If the UE message at step 6 includes the ackRequested IE set to TRUE, the SS shall send a LPP acknowledgement message.
8. Repeat steps 1-7 until the confidence level according to Annex D is achieved. For each iteration, at step 1 reselect the PN code assigned to the MBS beacon.
9. Release the signalling connection.
11.1.4.3 Message contents
Table 11.1.4.3-1: RESET UE POSITIONING STORED INFORMATION
Derivation Path: TS 36.509 [11] clause 6.9 |
|||
Information Element |
Value/remark |
Comment |
Condition |
UE Positioning Technology |
0 0 0 0 0 0 1 0 |
MBS |
Table 11.1.4.3-2: LPP RequestCapabilities
Information Element |
Value/remark |
tbs‑RequestCapabilities-r13 |
TRUE |
Table 11.1.4.3-3: LPP RequestLocationInformation
Derivation Path: TS 36.355 [4] clause 6.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
LPP-Message ::= SEQUENCE { |
|||
transactionID SEQUENCE { |
|||
Initiator |
locationServer |
||
transactionNumber |
1 |
||
} |
|||
endTransaction |
FALSE |
||
sequenceNumber |
Not present |
||
acknowledgement |
Not present |
||
lpp-MessageBody CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation-r9 SEQUENCE { |
|||
commonIEsRequestLocationInformation SEQUENCE { |
|||
locationInformationType |
locationMeasurementsRequired |
||
triggeredReporting |
Not present |
||
periodicalReporting |
Not present |
||
additionalInformation |
onlyReturnInformationRequested |
||
qos SEQUENCE { |
|||
horizontalAccuracy |
Not present |
||
verticalCoordinateRequest |
FALSE |
||
verticalAccuracy |
Not present |
||
responseTime SEQUENCE { |
|||
Time |
12 |
||
responseTimeEarlyFix-r12 |
Not present |
||
} |
|||
velocityRequest |
FALSE |
||
} |
|||
Environment |
Not present |
||
locationCoordinateTypes |
Not present |
||
velocityTypes |
Not present |
||
} |
|||
a-gnss-RequestLocationInformation |
Not present |
||
otdoa-RequestLocationInformation |
Not present |
||
ecid-RequestLocationInformation |
Not present |
||
epdu-RequestLocationInformation |
Not present |
||
sensor-RequestLocationInformation-r13 |
Not present |
||
tbs-RequestLocationInformation-r13 SEQUENCE { |
|||
mbsSgnMeasListReq-r13 |
TRUE |
||
} |
|||
wlan-RequestLocationInformation-r13 |
Not present |
||
bt-RequestLocationInformation-r13 |
Not Present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 11.1.4.3-4: LPP ProvideLocationInformation
Derivation Path: TS 36.355 [4] clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
Initiator |
locationServer |
|||
transactionNumber |
1 |
|||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
(0..255) |
|||
Acknowledgement |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation-r9 SEQUENCE { |
||||
commonIEsProvideLocationInformation |
Not present. |
|||
a-gnss-ProvideLocationInformation |
Not present |
|||
otdoa-ProvideLocationInformation |
Not present |
|||
ecid-ProvideLocationInformation |
Not present |
|||
epdu-ProvideLocationInformation |
Not present |
|||
sensor-ProvideLocationInformation-r13 |
Not present |
|||
tbs-ProvideLocationInformation-r13 |
||||
tbs-MeasurementInformation-r13 |
||||
measurementReferenceTime-r13 |
||||
mbs-SgnMeasList-r13 SEQUENCE (SIZE(n)) { |
||||
transmitterID-r13 |
Present |
|||
codePhase-r13 |
Present |
|||
codePhaseRMSError-r13 |
||||
} |
||||
} |
||||
tbs-Error-r13 |
May be present with error reason ‘undefined’ or ‘thereWereNotEnoughMBSBeaconsReceived’ |
|||
} |
||||
wlan-ProvideLocationInformation-r13 |
Not present |
|||
bt-ProvideLocationInformation-r13 |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
11.1.5 Test requirement
The details of the beacon parameters are in Table 11.1.5-1 and Table 11.1.5-2.
Table 11.1.5-1: General test parameters for the beacon to be simulated for the measurement reporting delay test
Parameter |
Unit |
Value |
Comment |
Number of beacons |
Integer |
1 |
Beacon transmitted in any beacon slot, but static for the test, in the MBS beacon transmission period. Other slots contain no simulated beaconsNote 1 |
Centre Frequency |
MHz |
925.977 |
|
RF Channel |
N/A |
EPA 5Hz |
|
MBS Beacon Configuration |
N/A |
TB1 (2 MHz) |
For details see Annex H |
MBS Packet Type |
N/A |
Type 2 |
For details see Annex H |
Beacon PN Code |
Integer |
Chosen for the beacon from the PN code list for TB1 |
For details see Annex HNote 1 |
Transmit power |
dBm |
-30 |
|
Response time |
Seconds |
12 |
Value of Time used in LPP RequestLocationInformation message in Table 11.1.4.3-3 |
Note 1: The slots and PN codes are chosen at random, such that the UE does not and cannot have advanced knowledge of what that slot/PN code might be. |
Table 11.1.5-2: MBS Beacon Payload fields for the beacon to be simulated for the measurement reporting delay test
MBS Tx ID (see Annex H) |
Slot Index (see Annex H) |
All Other fields (see Annex H) |
|
Equal to Slot number |
Equal to Slot number |
min value (bit_value = 0)Note 1 |
|
Note 1: bit_value is the conversion of the binary number represented by the corresponding bits in the payload to decimal. |
The MBS measurement reporting delay (response time) shall be < 12300 msec.
The test tolerances are defined in clauses C.1.4 and C.4.
The rate of successful tests during repeated tests shall be at least 90% with a confidence level of 95%.
11.1A MBS Measurement Reporting Delay (Release 14 Onwards)
11.1A.1 Test purpose
Same as defined in clause 11.1.1
11.1A.2 Test applicability
This test applies to all types of E-UTRA UE that supports UE-assisted MBS with LPP Release 14 onwards.
11.1A.3 Minimum conformance requirements
Same as defined in clause 11.1.3
11.1A.4 Test description
11.1A.4.1 Initial conditions
Same as defined in clause 11.1.4.1
11.1A.4.2 Test procedure
Same as defined in clause 11.1.4.2, except step 4a is introduced and step 5 is modified as follows:
4a. The SS shall send an LPP PROVIDE ASSISTANCE DATA message to provide the MBS assistance data in accordance with TS 37.571-5 [20], and with the values defined therein. If the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP PROVIDE ASSISTANCE DATA message.
5. The SS shall send a LPP REQUEST LOCATION INFORMATION message, including the TBS‑RequestLocationInformation IE.
11.1A.4.3 Message contents
Same as defined in clause 11.1.4.3, with the addition of the LPP Provide Assistance Data.
Table 11.1A.4.3-5: LPP ProvideAssistanceData
Derivation Path: TS 36.355 [4] clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
Initiator |
locationServer |
|||
transactionNumber |
(0..255) |
|||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
Not present |
|||
acknowledgement |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideAssistanceData SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideAssistanceData-r9 SEQUENCE { |
||||
commonIEsProvideAssistanceData |
Not present |
|||
a-gnss-ProvideAssistanceData |
Not present |
|||
otdoa-ProvideAssistanceData |
Not present |
|||
epdu-ProvideAssistanceData |
Not present |
|||
sensor-ProvideAssistanceData-r14 |
Not present |
Rel-14 onwards |
||
tbs-ProvideAssistanceData-r14 SEQUENCE { |
Rel-14 onwards |
|||
tbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb1 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb2 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
} |
||||
} |
||||
tbs-Error-r14 |
Not Present |
|||
} |
||||
} |
||||
wlan-ProvideAssistanceData-r14 |
Not Present |
Rel-14 onwards |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
11.1A.5 Test requirement
Same as defined in clause 11.1.5, with the beacon parameters set according to the assistance data in TS 37.571-5 [20] clause 8.
11.1B MBS Measurement Reporting Delay (NR)
11.1B.1 Test purpose
Same as defined in clause 11.1.1
11.1B.2 Test applicability
This test applies to all types of NR UE that supports UE-assisted MBS with LPP Release 13 onwards.
11.1B.3 Minimum conformance requirements
Same as defined in clause 11.1.3
11.1B.4 Test description
11.1B.4.1 Initial conditions
Same as defined in clause 11.1.4.1, except in the case of NR UE, step 3 is modified as follows:
3. Establish a signalling connection according to the generic procedure in TS 38.508-1 [45] clause 4.5.4.
11.1B.4.2 Test procedure
For NR UE that supports LPP Release 13 only, same as defined in clause 11.1.4.2. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.1A.4.2.
11.1B.4.3 Message contents
For NR UE that supports LPP Release 13 only, same as defined in clause 11.1.4.3. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.1A.4.3.
11.1B.5 Test requirement
For NR UE that supports LPP Release 13 only, same as defined in clause 11.1.5. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.1A.5.
11.2 MBS Sensitivity Measurement Accuracy (Release 13 only)
11.2.1 Test purpose
The purpose of this test is to verify that the MBS Code Phase measurement accuracy is within the specified limits under target sensitivity conditions. This test will verify the requirements in clause 5.2 of TS 37.171 [39] for MBS measurements. The channel type for this test is AWGN, as specified in clause 4.8.2.1.
11.2.2 Test applicability
This test applies to all types of E-UTRA UE that supports UE-assisted MBS with LPP Release 13 only.
11.2.3 Minimum conformance requirements
The MBS code phase measurement accuracy shall fulfil the requirement given in Table 11.2.3-1.
Table 11.2.3-1: Accuracy requirements for sensitivity scenario
Signal Strength (dBm) |
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
-130 |
1.66 × 10-4 |
2.35 × 10-4 |
Note 1: Provided for reference only Note 2: To be used for testing |
The accuracy requirement for the difference of code phase measurements is derived from the requirement for the code phase measurement accuracy, assuming a scaling factor of due to the compounding of two error distributions.
The normative reference for this requirement is TS 37.171 [39] clause 5.2 (Sensitivity) and clause A.4.2.
11.2.4 Test description
11.2.4.1 Initial conditions
Test environment: normal; see Annex G.
1. Connect SS and MSS to the UE antenna connector or antenna connectors as shown in figures A.6 or A.7.
2. Switch on the UE.
3. Establish a signalling connection according to the generic procedure in TS 36.508 [18] clause 4.5.3 (State 3, Generic RB established) on a channel in the Mid EARFCN range.
11.2.4.2 Test procedure
1. Set the MSS test parameters as specified in clause 11.2.5.
2. The SS shall send a RESET UE POSITIONING STORED INFORMATION message.
3. The SS shall send an LPP REQUEST CAPABILITIES message.
4. The UE shall transmit an LPP PROVIDE CAPABILITIES message indicating the TBS capabilities supported by the UE in the TBS-ProvideCapabilities IE.
5. The SS shall send a LPP REQUEST LOCATION INFORMATION message, including the TBS‑RequestLocationInformation IE. If the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP REQUEST LOCATION INFORMATION message.
6. The UE shall perform and report the code phase measurement for each simulated beacon. If the UE transmits a TBS‑ProvideLocationInformation IE including the transmitterID and codePhase field for the two simulated beacons and the difference between codePhase field values for the two beacons meet the corresponding requirements in Table 11.2.5-3, then the number of successful tests is increased by one. Otherwise the number of failure tests is increased by one.
7. If the UE message at step 6 includes the ackRequested IE set to TRUE, the SS shall send a LPP acknowledgement message.
8. Repeat steps 1-7 until the confidence level according to Annex D is achieved. For each iteration, at step 1 reselect the PN code assigned to each MBS beacon.
9. Release the signalling connection.
11.2.4.3 Message contents
Table 11.2.4.3-1: RESET UE POSITIONING STORED INFORMATION
Derivation Path: TS 36.509 [11] clause 6.9 |
|||
Information Element |
Value/remark |
Comment |
Condition |
UE Positioning Technology |
0 0 0 0 0 0 1 0 |
MBS |
Table 11.2.4.3-2: LPP RequestCapabilities
Information Element |
Value/remark |
tbs‑RequestCapabilities-r13 |
TRUE |
Table 11.2.4.3-3: LPP RequestLocationInformation
Derivation Path: TS 36.355 [4] clause 6.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
LPP-Message ::= SEQUENCE { |
|||
transactionID SEQUENCE { |
|||
Initiator |
locationServer |
||
transactionNumber |
1 |
||
} |
|||
endTransaction |
FALSE |
||
sequenceNumber |
Not present |
||
acknowledgement |
Not present |
||
lpp-MessageBody CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation-r9 SEQUENCE { |
|||
commonIEsRequestLocationInformation SEQUENCE { |
|||
locationInformationType |
locationMeasurementsRequired |
||
triggeredReporting |
Not present |
||
periodicalReporting |
Not present |
||
additionalInformation |
onlyReturnInformationRequested |
||
qos SEQUENCE { |
|||
horizontalAccuracy |
Not present |
||
verticalCoordinateRequest |
FALSE |
||
verticalAccuracy |
Not present |
||
responseTime SEQUENCE { |
|||
Time |
12 |
||
responseTimeEarlyFix-r12 |
Not present |
||
} |
|||
velocityRequest |
FALSE |
||
} |
|||
Environment |
Not present |
||
locationCoordinateTypes |
Not present |
||
velocityTypes |
Not present |
||
} |
|||
a-gnss-RequestLocationInformation |
Not present |
||
otdoa-RequestLocationInformation |
Not present |
||
ecid-RequestLocationInformation |
Not present |
||
epdu-RequestLocationInformation |
Not present |
||
sensor-RequestLocationInformation-r13 |
Not present |
||
tbs-RequestLocationInformation-r13 SEQUENCE { |
|||
mbsSgnMeasListReq-r13 |
TRUE |
||
} |
|||
wlan-RequestLocationInformation-r13 |
Not present |
||
bt-RequestLocationInformation-r13 |
Not Present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 11.2.4.3-4: LPP ProvideLocationInformation
Derivation Path: TS 36.355 [4] clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
Initiator |
locationServer |
|||
transactionNumber |
1 |
|||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
(0..255) |
|||
Acknowledgement |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation-r9 SEQUENCE { |
||||
commonIEsProvideLocationInformation |
Not present. |
|||
a-gnss-ProvideLocationInformation |
Not present |
|||
otdoa-ProvideLocationInformation |
Not present |
|||
ecid-ProvideLocationInformation |
Not present |
|||
epdu-ProvideLocationInformation |
Not present |
|||
sensor-ProvideLocationInformation-r13 |
Not present |
|||
tbs-ProvideLocationInformation-r13 |
||||
tbs-MeasurementInformation-r13 |
||||
measurementReferenceTime-r13 |
||||
mbs-SgnMeasList-r13 SEQUENCE (SIZE(n)) { |
||||
transmitterID-r13 |
Present |
|||
codePhase-r13 |
Present |
|||
codePhaseRMSError-r13 |
||||
} |
||||
mbs-SgnMeasList-r13 SEQUENCE (SIZE(n)) { |
||||
transmitterID-r13 |
Present |
|||
codePhase-r13 |
Present |
|||
codePhaseRMSError-r13 |
||||
} |
||||
} |
||||
tbs-Error-r13 |
May be present with error reason ‘undefined’ or ‘thereWereNotEnoughMBSBeaconsReceived’ |
|||
} |
||||
wlan-ProvideLocationInformation-r13 |
Not present |
|||
bt-ProvideLocationInformation-r13 |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
11.2.5 Test requirement
The details of the beacon parameters are in Table 11.2.5-1 and Table 11.2.5-2.
Table 11.2.5-1: General test parameters for the beacons to be simulated for measurement accuracy in Sensitivity test
Parameter |
Unit |
Value |
Comment |
Number of Beacons |
2 |
Beacons transmitted in any two beacon slots in the beacon transmission period, but static for the test. Other slots contain no simulated beaconsNote 1 |
|
Centre Frequency |
MHz |
925.977 |
|
RF Channel |
N/A |
AWGN |
|
MBS Beacon Configuration |
N/A |
TB1 (2 MHz) |
For details see Annex H |
MBS Packet Type |
N/A |
Type 2 |
For details see Annex H\ |
Beacon PN Code |
Integer |
Chosen for each beacon from the PN code list for TB1 |
Each of the 2 beacons uses a different PN code. For details see Annex HNote 1 |
Response time |
Seconds |
12 |
Value of Time used in LPP RequestLocationInformation message in Table 11.2.4.3-3 |
Note 1: The slots and PN codes are chosen at random, such that the UE does not and cannot have advanced knowledge of what that slot/PN code might be. |
Table 11.2.5-2: MBS Beacon Payload fields, code phase delay difference and transmit powers for the beacons to be simulated for measurement accuracy in sensitivity test
MBS Tx ID (See Annex H) |
Slot Index (See Annex H) |
All Other fields (See Annex H) |
Code phase delay difference between beacons (ms) |
Transmit Power (dBm) |
Equal to Slot number |
Equal to Slot number |
min value (bit_value = 0)Note 1 |
0 |
-128 |
Note 1: bit_value is the conversion of the binary number represented by the corresponding bits in the payload to decimal. |
The MBS code phase measurement accuracy shall fulfil the requirements given in Table 11.2.5-3.
Table 11.2.5-3: Accuracy requirements for Sensitivity scenario
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
1.66 × 10-4 |
2.40 × 10-4 |
Note 1: Provided for reference only Note 2: To be used for testing |
The test tolerances are defined in clauses C.1.4 and C.4.
The rate of successful tests during repeated tests shall be at least 90% with a confidence level of 95%.
11.2A MBS Sensitivity Measurement Accuracy (Release 14 Onwards)
11.2A.1 Test purpose
Same as defined in clause 11.2.1
11.2A.2 Test applicability
This test applies to all types of E-UTRA UE that supports UE-assisted MBS with LPP Release 14 onwards.
11.2A.3 Minimum conformance requirements
Same as defined in clause 11.2.3 except that the accuracy requirements are:
Table 11.2A.3-1: Accuracy requirements for sensitivity scenario
MBS Configuration |
Signal Strength (dBm) |
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
TB1 (2 MHz) |
-130 |
1.66 × 10-4 |
2.35 × 10-4 |
TB2 (5 MHz) |
-130 |
6.6 × 10-5 |
9.3 × 10-5 |
Note 1: Provided for reference only Note 2: To be used for testing |
11.2A.4 Test description
11.2A.4.1 Initial conditions
Same as defined in clause 11.2.4.1
11.2A.4.2 Test procedure
Same as defined in clause 11.2.4.2, except step 4a is introduced and step 5 is modified as follows:
4a. The SS shall send an LPP PROVIDE ASSISTANCE DATA message to provide the MBS assistance data in accordance with TS 37.571-5 [20], and with the values defined therein. If the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP PROVIDE ASSISTANCE DATA message.
5. The SS shall send a LPP REQUEST LOCATION INFORMATION message, including the TBS‑RequestLocationInformation IE.
11.2A.4.3 Message contents
Same as defined in clause 11.2.4.3, with the addition of the LPP Provide Assistance Data
Table 11.2A.4.3-5: LPP ProvideAssistanceData
Derivation Path: TS 36.355 [4] clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
Initiator |
locationServer |
|||
transactionNumber |
(0..255) |
|||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
Not present |
|||
acknowledgement |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideAssistanceData SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideAssistanceData-r9 SEQUENCE { |
||||
commonIEsProvideAssistanceData |
Not present |
|||
a-gnss-ProvideAssistanceData |
Not present |
|||
otdoa-ProvideAssistanceData |
Not present |
|||
epdu-ProvideAssistanceData |
Not present |
|||
sensor-ProvideAssistanceData-r14 |
Not present |
Rel-14 onwards |
||
tbs-ProvideAssistanceData-r14 SEQUENCE { |
Rel-14 onwards |
|||
tbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb1 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 2 tb1 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb2 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 2 tb2 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
} |
||||
} |
||||
tbs-Error-r14 |
Not Present |
|||
} |
||||
} |
||||
wlan-ProvideAssistanceData-r14 |
Not Present |
Rel-14 onwards |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
11.2A.5 Test requirement
Same as defined in clause 11.2.5, with the beacon parameters set according to the assistance data in TS 37.571-5 [20] clause 8 and with the measurement accuracy requirement in Table 11.2A.5-1.
Table 11.2A.5-1: Accuracy requirements for Sensitivity scenario
MBS Configuration |
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
TB1 (2 MHz) |
1.66 × 10-4 |
2.40 × 10-4 |
TB2 (5 MHz) |
6.6 × 10-5 |
9.8 × 10-5 |
Note 1: Provided for reference only Note 2: To be used for testing |
11.2B MBS Sensitivity Measurement Accuracy (NR)
11.2B.1 Test purpose
Same as defined in clause 11.2.1
11.2B.2 Test applicability
This test applies to all types of NR UE that supports UE-assisted MBS with LPP Release 13 onwards.
11.2B.3 Minimum conformance requirements
For NR UE that supports LPP Release 13 only, same as defined in clause 11.2.3. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.2A.3
11.2B.4 Test description
11.2B.4.1 Initial conditions
Same as defined in clause 11.2.4.1, except in the case of NR UE, step 3 is modified as follows:
3. Establish a signalling connection according to the generic procedure in TS 38.508-1 [45] clause 4.5.4.
11.2B.4.2 Test procedure
For NR UE that supports LPP Release 13 only, same as defined in clause 11.2.4.2. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.2A.4.2.
11.2B.4.3 Message contents
For NR UE that supports LPP Release 13 only, same as defined in clause 11.2.4.3. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.2A.4.3
11.2B.5 Test requirement
For NR UE that supports LPP Release 13 only, same as defined in clause 11.2.5. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.2A.5
11.3 MBS Nominal Measurement Accuracy (Release 13 only)
11.3.1 Test purpose
The purpose of this test is to verify that the MBS Code Phase measurement accuracy is within the specified limits under ideal conditions. This test will verify the requirements in clauses 5.3 of 37.171 [39] for MBS measurements. The channel type for this test is AWGN, as specified in clause 4.8.2.1.
11.3.2 Test applicability
This test applies to all types of E-UTRA UE that supports UE-assisted MBS with LPP Release 13 only.
11.3.3 Minimum conformance requirements
The MBS code phase measurement accuracy shall fulfil the requirement given in Table 11.3.3-1.
Table 11.3.3-1: Accuracy requirements for Nominal scenario
Signal Strength (dBm) |
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
-30 |
5.0 × 10-5 |
7. 1 × 10-5 |
Note 1: Provided for reference only Note 2: To be used for testing |
The accuracy requirement for the difference of code phase measurements is derived from the requirement for the code phase measurement accuracy, assuming a scaling factor of due to the compounding of two error distributions.
The normative reference for this requirement is TS 37.171 [39] clause 5.3 (Nominal) and clause A.4.2.
11.3.4 Test description
11.3.4.1 Initial conditions
Test environment: normal; see Annex G.
1. Connect SS and MSS to the UE antenna connector or antenna connectors as shown in figures A.6 or A.7.
2. Switch on the UE.
3. Establish a signalling connection according to the generic procedure in TS 36.508 [18] clause 4.5.3 (State 3, Generic RB established) on a channel in the Mid EARFCN range.
11.3.4.2 Test procedure
1. Set the MSS test parameters as specified in clause 11.3.5.
2. The SS shall send a RESET UE POSITIONING STORED INFORMATION message.
3. The SS shall send an LPP REQUEST CAPABILITIES message.
4. The UE shall transmit an LPP PROVIDE CAPABILITIES message indicating the TBS capabilities supported by the UE in the TBS-ProvideCapabilities IE.
5. The SS shall send a LPP REQUEST LOCATION INFORMATION message, including the TBS‑RequestLocationInformation IE. If the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP REQUEST LOCATION INFORMATION message.
6. The UE shall perform and report the code phase measurement for each simulated beacon. If the UE transmits a TBS‑ProvideLocationInformation IE including the transmitterID and codePhase field for the two simulated beacons and the difference between codePhase field values for the two beacons meet the corresponding requirements in Table 11.3.5-3, then the number of successful tests is increased by one. Otherwise the number of failure tests is increased by one.
7. If the UE message at step 6 includes the ackRequested IE set to TRUE, the SS shall send a LPP acknowledgement message.
8. Repeat steps 1-7 until the confidence level according to Annex D is achieved. For each iteration, at step 1 reselect the PN code assigned to each MBS beacon.
9. Release the signalling connection.
11.3.4.3 Message contents
Table 11.3.4.3-1: RESET UE POSITIONING STORED INFORMATION
Derivation Path: TS 36.509 [11] clause 6.9 |
|||
Information Element |
Value/remark |
Comment |
Condition |
UE Positioning Technology |
0 0 0 0 0 0 1 0 |
MBS |
Table 11.3.4.3-2: LPP RequestCapabilities
Information Element |
Value/remark |
tbs‑RequestCapabilities-r13 |
TRUE |
Table 11.3.4.3-3: LPP RequestLocationInformation
Derivation Path: TS 36.355 [4] clause 6.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
LPP-Message ::= SEQUENCE { |
|||
transactionID SEQUENCE { |
|||
Initiator |
locationServer |
||
transactionNumber |
1 |
||
} |
|||
endTransaction |
FALSE |
||
sequenceNumber |
Not present |
||
acknowledgement |
Not present |
||
lpp-MessageBody CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation-r9 SEQUENCE { |
|||
commonIEsRequestLocationInformation SEQUENCE { |
|||
locationInformationType |
locationMeasurementsRequired |
||
triggeredReporting |
Not present |
||
periodicalReporting |
Not present |
||
additionalInformation |
onlyReturnInformationRequested |
||
qos SEQUENCE { |
|||
horizontalAccuracy |
Not present |
||
verticalCoordinateRequest |
FALSE |
||
verticalAccuracy |
Not present |
||
responseTime SEQUENCE { |
|||
Time |
12 |
||
responseTimeEarlyFix-r12 |
Not present |
||
} |
|||
velocityRequest |
FALSE |
||
} |
|||
Environment |
Not present |
||
locationCoordinateTypes |
Not present |
||
velocityTypes |
Not present |
||
} |
|||
a-gnss-RequestLocationInformation |
Not present |
||
otdoa-RequestLocationInformation |
Not present |
||
ecid-RequestLocationInformation |
Not present |
||
epdu-RequestLocationInformation |
Not present |
||
sensor-RequestLocationInformation-r13 |
Not present |
||
tbs-RequestLocationInformation-r13 SEQUENCE { |
|||
mbsSgnMeasListReq-r13 |
TRUE |
||
} |
|||
wlan-RequestLocationInformation-r13 |
Not present |
||
bt-RequestLocationInformation-r13 |
Not Present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 11.3.4.3-4: LPP ProvideLocationInformation
Derivation Path: TS 36.355 [4] clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
Initiator |
locationServer |
|||
transactionNumber |
1 |
|||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
(0..255) |
|||
Acknowledgement |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation-r9 SEQUENCE { |
||||
commonIEsProvideLocationInformation |
Not present. |
|||
a-gnss-ProvideLocationInformation |
Not present |
|||
otdoa-ProvideLocationInformation |
Not present |
|||
ecid-ProvideLocationInformation |
Not present |
|||
epdu-ProvideLocationInformation |
Not present |
|||
sensor-ProvideLocationInformation-r13 |
Not present |
|||
tbs-ProvideLocationInformation-r13 |
||||
tbs-MeasurementInformation-r13 |
||||
measurementReferenceTime-r13 |
||||
mbs-SgnMeasList-r13 SEQUENCE (SIZE(n)) { |
||||
transmitterID-r13 |
Present |
|||
codePhase-r13 |
Present |
|||
codePhaseRMSError-r13 |
||||
} |
||||
mbs-SgnMeasList-r13 SEQUENCE (SIZE(n)) { |
||||
transmitterID-r13 |
Present |
|||
codePhase-r13 |
Present |
|||
codePhaseRMSError-r13 |
||||
} |
||||
} |
||||
tbs-Error-r13 |
May be present with error reason ‘undefined’ or ‘thereWereNotEnoughMBSBeaconsReceived’ |
|||
} |
||||
wlan-ProvideLocationInformation-r13 |
Not present |
|||
bt-ProvideLocationInformation-r13 |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
11.3.5 Test requirement
The details of the beacon parameters are in Table 11.3.5-1 and Table 11.3.5-2.
Table 11.3.5-1: General test parameters for the beacons to be simulated for measurement accuracy in Nominal test
Parameter |
Unit |
Value |
Comment |
Number of Beacons |
2 |
Beacons transmitted in any two beacon slots in the beacon transmission period, but static for the test. Other slots contain no simulated beaconsNote 1 |
|
Centre Frequency |
MHz |
925.977 |
|
RF Channel |
N/A |
AWGN |
|
MBS Beacon Configuration |
N/A |
TB1 (2 MHz) |
For details see Annex H |
MBS Packet Type |
N/A |
Type 2 |
For details see Annex H |
Beacon PN Code |
Integer |
Chosen for each beacon from the PN code list for TB1 |
Each of the 2 beacons uses a different PN code. For details see Annex HNote 1 |
Response time |
Seconds |
12 |
Value of Time used in LPP RequestLocationInformation message in Table 11.3.4.3-3 |
Note 1: The slots and PN codes are chosen at random, such that the UE does not and cannot have advanced knowledge of what that slot/PN code might be. |
Table 11.3.5-2: MBS Beacon Payload fields, code phase delay difference and transmit powers for the beacons to be simulated for measurement accuracy in Nominal test
MBS Tx ID (See Annex H) |
Slot Index (See Annex H) |
All Other fields (See Annex H) |
Code phase delay difference between beacons (ms) |
Transmit Power (dBm) |
Equal to Slot number |
Equal to Slot number |
min value (bit_value = 0)Note 1 |
0 |
-30 |
Note: bit_value is the conversion of the binary number represented by the corresponding bits in the payload to decimal. |
The MBS code phase measurement accuracy shall fulfil the requirements given in Table 11.3.5-3.
Table 11.3.5-3: Accuracy requirements for Nominal scenario
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
5.0 × 10-5 |
7. 6 × 10-5 |
Note 1: Provided for reference only Note 2: To be used for testing |
The test tolerances are defined in clauses C.1.4 and C.4.
The rate of successful tests during repeated tests shall be at least 90% with a confidence level of 95%.
11.3A MBS Nominal Measurement Accuracy (Release 14 Onwards)
11.3A.1 Test purpose
Same as defined in clause 11.3.1
11.3A.2 Test applicability
This test applies to all types of E-UTRA UE supports UE-assisted MBS with LPP Release 14 onwards.
11.3A.3 Minimum conformance requirements
Same as defined in clause 11.3.3 except that the accuracy requirements are:
Table 11.3A.3-1: Accuracy requirements for Nominal scenario
MBS Configuration |
Signal Strength (dBm) |
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
TB1 (2 MHz) |
-30 |
5.0 × 10-5 |
7.1 × 10-5 |
TB2 (5 MHz) |
-30 |
2.0 × 10-5 |
2.8 × 10-5 |
Note 1: Provided for reference only. Note 2: To be used for testing. |
11.3A.4 Test description
11.3A.4.1 Initial conditions
Same as defined in clause 11.3.4.1
11.3A.4.2 Test procedure
Same as defined in clause 11.3.4.2, except step 4a is introduced and step 5 is modified as follows:
4a. The SS shall send an LPP PROVIDE ASSISTANCE DATA message to provide the MBS assistance data in accordance with TS 37.571-5 [20], and with the values defined therein. If the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP PROVIDE ASSISTANCE DATA message.
5. The SS shall send a LPP REQUEST LOCATION INFORMATION message, including the TBS‑RequestLocationInformation IE.
11.3A.4.3 Message contents
Same as defined in clause 11.3.4.3, with the addition of the LPP Provide Assistance Data.
Table 11.3A.4.3-5: LPP ProvideAssistanceData
Derivation Path: TS 36.355 [4] clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
Initiator |
locationServer |
|||
transactionNumber |
(0..255) |
|||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
Not present |
|||
acknowledgement |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideAssistanceData SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideAssistanceData-r9 SEQUENCE { |
||||
commonIEsProvideAssistanceData |
Not present |
|||
a-gnss-ProvideAssistanceData |
Not present |
|||
otdoa-ProvideAssistanceData |
Not present |
|||
epdu-ProvideAssistanceData |
Not present |
|||
sensor-ProvideAssistanceData-r14 |
Not present |
Rel-14 onwards |
||
tbs-ProvideAssistanceData-r14 SEQUENCE { |
Rel-14 onwards |
|||
tbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb1 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 2 tb1 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb2 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 2 tb2 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
} |
||||
} |
||||
tbs-Error-r14 |
Not Present |
|||
} |
||||
} |
||||
wlan-ProvideAssistanceData-r14 |
Not Present |
Rel-14 onwards |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
11.3A.5 Test requirement
Same as defined in clause 11.3.5, with the beacon parameters set according to the assistance data in TS 37.571-5 [20] clause 8 and with the measurement accuracy requirement in Table 11.3A.5-1.
Table 11.3A.5-1: Accuracy requirements for Nominal scenario
MBS Configuration |
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
TB1 (2 MHz) |
5.0 × 10-5 |
7.6 × 10-5 |
TB2 (5 MHz) |
2.0 × 10-5 |
3.3 × 10-5 |
Note 1: Provided for reference only. Note 2: To be used for testing. |
11.3B MBS Nominal Measurement Accuracy (NR)
11.3B.1 Test purpose
Same as defined in clause 11.3.1
11.3B.2 Test applicability
This test applies to all types of NR UE that supports UE-assisted MBS with LPP Release 13 onwards.
11.3B.3 Minimum conformance requirements
For NR UE that supports LPP Release 13 only, same as defined in clause 11.3.3. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.3A.3
11.3B.4 Test description
11.3B.4.1 Initial conditions
Same as defined in clause 11.3.4.1, except in the case of NR UE, step 3 is modified as follows:
3. Establish a signalling connection according to the generic procedure in TS 38.508-1 [45] clause 4.5.4.
11.3B.4.2 Test procedure
For NR UE that supports LPP Release 13 only, same as defined in clause 11.3.4.2. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.3A.4.2
11.3B.4.3 Message contents
For NR UE that supports LPP Release 13 only, same as defined in clause 11.3.4.3. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.3A.4.3
11.3B.5 Test requirement
For NR UE that supports LPP Release 13 only, same as defined in clause 11.3.5. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.3A.5
11.4 MBS Dynamic Range Measurement Accuracy (Release 13 only)
11.4.1 Test purpose
The purpose of this test is to verify that the MBS Code Phase measurement accuracy is within the specified limits under maximum dynamic range conditions. This test will verify the requirements in clauses 5.4 of TS 37.171 [39] for MBS measurements. The channel type for this test is AWGN, as specified in clause 4.8.2.1.
11.4.2 Test applicability
This test applies to all types of E-UTRA UE that supports UE-assisted MBS with LPP Release 13 only.
11.4.3 Minimum conformance requirements
The MBS code phase measurement accuracy shall fulfil the requirements given in Table 11.4.3-1.
Table 11.4.3-1: Accuracy requirements for Dynamic Range scenario
Signal Strength (dBm) |
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
-30 |
5.0 × 10-5 |
7. 1 × 10-5 |
-130 |
1.66 × 10-4 |
2.35 × 10-4 |
Note 1: Provided for reference only Note 2: To be used for testing |
The accuracy requirement for the difference of code phase measurements is derived from the requirement for the code phase measurement accuracy, assuming a scaling factor of due to the compounding of two error distributions.
The normative reference for this requirement is TS 37.171 [39] clause 5.4 (Dynamic Range) and clause A.4.2.
11.4.4 Test description
11.4.4.1 Initial conditions
Test environment: normal; see Annex G.
1. Connect SS and MSS to the UE antenna connector or antenna connectors as shown in figures A.6 or A.7.
2. Switch on the UE.
3. Establish a signalling connection according to the generic procedure in TS 36.508 [18] clause 4.5.3 (State 3, Generic RB established) on a channel in the Mid EARFCN range.
11.4.4.2 Test procedure
1. Set the MSS test parameters as specified in clause 11.4.5.
2. The SS shall send a RESET UE POSITIONING STORED INFORMATION message.
3. The SS shall send an LPP REQUEST CAPABILITIES message.
4. The UE shall transmit an LPP PROVIDE CAPABILITIES message indicating the TBS capabilities supported by the UE in the TBS-ProvideCapabilities IE.
5. The SS shall send a LPP REQUEST LOCATION INFORMATION message, including the TBS‑RequestLocationInformation IE. If the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP REQUEST LOCATION INFORMATION message.
6. The UE shall perform and report the code phase measurement for each simulated beacon. If the UE transmits a TBS‑ProvideLocationInformation IE including the transmitterID and codePhase field for the four simulated beacons and the difference between codePhase field values for the two high power beacons and the difference in the codePhase field values for the two low power beacons meet the corresponding requirements in Table 11.4.5-3, then the number of successful tests is increased by one. Otherwise the number of failure tests is increased by one.
7. If the UE message at step 6 includes the ackRequested IE set to TRUE, the SS shall send a LPP acknowledgement message.
8. Repeat steps 1-7 until the confidence level according to Annex D is achieved. For each iteration, at step 1 reselect the PN code assigned to each MBS beacon.
9. Release the signalling connection.
11.4.4.3 Message contents
Table 11.4.4.3-1: RESET UE POSITIONING STORED INFORMATION
Derivation Path: TS 36.509 [11] clause 6.9 |
|||
Information Element |
Value/remark |
Comment |
Condition |
UE Positioning Technology |
0 0 0 0 0 0 1 0 |
MBS |
Table 11.4.4.3-2: LPP RequestCapabilities
Information Element |
Value/remark |
tbs‑RequestCapabilities-r13 |
TRUE |
Table 11.4.4.3-3: LPP RequestLocationInformation
Derivation Path: TS 36.355 [4] clause 6.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
LPP-Message ::= SEQUENCE { |
|||
transactionID SEQUENCE { |
|||
Initiator |
locationServer |
||
transactionNumber |
1 |
||
} |
|||
endTransaction |
FALSE |
||
sequenceNumber |
Not present |
||
acknowledgement |
Not present |
||
lpp-MessageBody CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation-r9 SEQUENCE { |
|||
commonIEsRequestLocationInformation SEQUENCE { |
|||
locationInformationType |
locationMeasurementsRequired |
||
triggeredReporting |
Not present |
||
periodicalReporting |
Not present |
||
additionalInformation |
onlyReturnInformationRequested |
||
qos SEQUENCE { |
|||
horizontalAccuracy |
Not present |
||
verticalCoordinateRequest |
FALSE |
||
verticalAccuracy |
Not present |
||
responseTime SEQUENCE { |
|||
Time |
12 |
||
responseTimeEarlyFix-r12 |
Not present |
||
} |
|||
velocityRequest |
FALSE |
||
} |
|||
Environment |
Not present |
||
locationCoordinateTypes |
Not present |
||
velocityTypes |
Not present |
||
} |
|||
a-gnss-RequestLocationInformation |
Not present |
||
otdoa-RequestLocationInformation |
Not present |
||
ecid-RequestLocationInformation |
Not present |
||
epdu-RequestLocationInformation |
Not present |
||
sensor-RequestLocationInformation-r13 |
Not present |
||
tbs-RequestLocationInformation-r13 SEQUENCE { |
|||
mbsSgnMeasListReq-r13 |
TRUE |
||
} |
|||
wlan-RequestLocationInformation-r13 |
Not present |
||
bt-RequestLocationInformation-r13 |
Not Present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 11.4.4.3-4: LPP ProvideLocationInformation
Derivation Path: TS 36.355 [4] clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
Initiator |
locationServer |
|||
transactionNumber |
1 |
|||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
(0..255) |
|||
Acknowledgement |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation-r9 SEQUENCE { |
||||
commonIEsProvideLocationInformation |
Not present. |
|||
a-gnss-ProvideLocationInformation |
Not present |
|||
otdoa-ProvideLocationInformation |
Not present |
|||
ecid-ProvideLocationInformation |
Not present |
|||
epdu-ProvideLocationInformation |
Not present |
|||
sensor-ProvideLocationInformation-r13 |
Not present |
|||
tbs-ProvideLocationInformation-r13 |
||||
tbs-MeasurementInformation-r13 |
||||
measurementReferenceTime-r13 |
||||
mbs-SgnMeasList-r13 SEQUENCE (SIZE(n)) { |
||||
transmitterID-r13 |
Present |
|||
codePhase-r13 |
Present |
|||
codePhaseRMSError-r13 |
||||
} |
||||
mbs-SgnMeasList-r13 SEQUENCE (SIZE(n)) { |
||||
transmitterID-r13 |
Present |
|||
codePhase-r13 |
Present |
|||
codePhaseRMSError-r13 |
||||
} |
||||
mbs-SgnMeasList-r13 SEQUENCE (SIZE(n)) { |
||||
transmitterID-r13 |
Present |
|||
codePhase-r13 |
Present |
|||
codePhaseRMSError-r13 |
||||
} |
||||
mbs-SgnMeasList-r13 SEQUENCE (SIZE(n)) { |
||||
transmitterID-r13 |
Present |
|||
codePhase-r13 |
Present |
|||
codePhaseRMSError-r13 |
||||
} |
||||
} |
||||
tbs-Error-r13 |
May be present with error reason ‘undefined’ or ‘thereWereNotEnoughMBSBeaconsReceived’ |
|||
} |
||||
wlan-ProvideLocationInformation-r13 |
Not present |
|||
bt-ProvideLocationInformation-r13 |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
11.4.5 Test requirement
The details of the beacon parameters are in Table 11.4.5-1 and Table 11.4.5-2.
Table 11.4.5-1: General test parameters for the beacons to be simulated for measurement accuracy in Dynamic Range test
Parameter |
Unit |
Value |
Comment |
Number of Beacons |
4 |
Beacons 1 to 4. Transmitted in any four consecutive beacon slots in the beacon transmission period, but static for the test. Other slots contain no simulated beaconsNote 1 |
|
Centre Frequency |
MHz |
925.977 |
|
RF Channel |
N/A |
AWGN |
|
MBS Beacon Configuration |
N/A |
TB1 (2 MHz) |
For details see Annex H |
MBS Packet Type |
N/A |
Type 2 |
For details see Annex H |
Beacon PN Code |
Integer |
Chosen for each beacon from the PN code list for TB1 |
Each of the 4 beacons uses a different PN code. For details see Annex HNote 1 |
Response time |
Seconds |
12 |
Value of Time used in LPP RequestLocationInformation message in Table 11.4.4.3-3 |
Note 1: The slots and PN codes are chosen at random, such that the UE does not and cannot have advanced knowledge of what that slot/PN code might be. |
Table 11.4.5-2: MBS Beacon Payload fields, code phase delay difference and transmit powers for the beacons to be simulated for measurement accuracy in Dynamic Range test
Beacon |
MBS Tx ID (See Annex H) |
Slot Index (See Annex H) |
All Other fields (See Annex H) |
Code phase delay difference between beacons (ms) |
Transmit Power (dBm) |
1 |
Equal to Slot number |
Equal to Slot number |
min value (bit_value = 0)Note 1 |
Beacon 1 to beacon 3: 0 Note 2 |
-30 (high power) |
2 |
Equal to Slot number |
Equal to Slot number |
min value (bit_value = 0)Note 1 |
Beacon 2 to beacon 4: 0 Note 2 |
-128 (low power) |
3 |
Equal to Slot number |
Equal to Slot number |
min value (bit_value = 0)Note 1 |
Beacon 1 to beacon 3: 0 Note 2 |
-30 (high power) |
4 |
Equal to Slot number |
Equal to Slot number |
min value (bit_value = 0)Note 1 |
Beacon 2 to beacon 4: 0 Note 2 |
-128 (low power) |
Note 1: bit_value is the conversion of the binary number represented by the corresponding bits in the payload to decimal. Note 2: The code phase delay difference between beacon 1 and 3 and beacon 2 and 4 shall be set to some non-zero value. |
The MBS code phase measurement accuracy shall fulfil the requirements given in Table 11.4.5-3.
Table 11.4.5-3: Accuracy requirements for Dynamic Range scenario
Beacon Signal Strength |
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
High Power (-30 dBm) |
5.0 × 10-5 |
7. 6 × 10-5 |
Low Power (-130 dBm) |
1.66 × 10-4 |
2.40 × 10-4 |
Note 1: Provided for reference only Note 2: To be used for testing |
The test tolerances are defined in clauses C.1.4 and C.4.
The rate of successful tests during repeated tests shall be at least 90% with a confidence level of 95%.
11.4A MBS Dynamic Range Measurement Accuracy (Release 14 Onwards)
11.4A.1 Test purpose
Same as defined in clause 11.4.1
11.4A.2 Test applicability
This test applies to all types of E-UTRA UE that supports UE-assisted MBS with LPP Release 14 onwards.
11.4A.3 Minimum conformance requirements
Same as defined in clause 11.4.3 except that the accuracy requirements are:
Table 11.4A.3-1: Accuracy requirements for Dynamic Range scenario
MBS Configuration |
Signal Strength (dBm) |
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
TB1 (2 MHz) |
-30 |
5.0 × 10-5 |
7.1 × 10-5 |
-130 |
1.66 × 10-4 |
2.35 × 10-4 |
|
TB2 (5 MHz) |
-30 |
2.0 × 10-5 |
2.8 × 10-5 |
-130 |
6.6 × 10-5 |
9.3 × 10-5 |
|
Note 1: Provided for reference only. Note 2: To be used for testing. |
11.4A.4 Test description
11.4A.4.1 Initial conditions
Same as defined in clause 11.4.4.1
11.4A.4.2 Test procedure
Same as defined in clause 11.4.4.2, except step 4a is introduced and step 5 is modified as follows:
4a. The SS shall send an LPP PROVIDE ASSISTANCE DATA message to provide the MBS assistance data in accordance with TS 37.571-5 [20], and with the values defined therein. If the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP PROVIDE ASSISTANCE DATA message.
5. The SS shall send a LPP REQUEST LOCATION INFORMATION message, including the TBS‑RequestLocationInformation IE.
11.4A.4.3 Message contents
Same as defined in clause 11.4.4.3, with the addition of the LPP Provide Assistance Data.
Table 11.4A.4.3-5: LPP ProvideAssistanceData
Derivation Path: TS 36.355 [4] clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
Initiator |
locationServer |
|||
transactionNumber |
(0..255) |
|||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
Not present |
|||
acknowledgement |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideAssistanceData SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideAssistanceData-r9 SEQUENCE { |
||||
commonIEsProvideAssistanceData |
Not present |
|||
a-gnss-ProvideAssistanceData |
Not present |
|||
otdoa-ProvideAssistanceData |
Not present |
|||
epdu-ProvideAssistanceData |
Not present |
|||
sensor-ProvideAssistanceData-r14 |
Not present |
Rel-14 onwards |
||
tbs-ProvideAssistanceData-r14 SEQUENCE { |
Rel-14 onwards |
|||
tbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb1 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 2 tb1 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 3 tb1 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 4 tb1 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb2 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 2 tb2 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 3 tb2 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 4 tb2 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
} |
||||
} |
||||
tbs-Error-r14 |
Not Present |
|||
} |
||||
} |
||||
wlan-ProvideAssistanceData-r14 |
Not Present |
Rel-14 onwards |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
11.4A.5 Test requirement
Same as defined in clause 11.4.5, with the beacon parameters set according to the assistance data in TS 37.571-5 [20] clause 8 and with the measurement accuracy requirementsin Table 114A.5-1.
Table 11.4A.5-1: Accuracy requirements for Dynamic Range scenario
MBS Configuration |
Beacon Signal Strength |
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
TB1 (2 MHz) |
High Power (-30 dBm) |
5.0 × 10-5 |
7.6 × 10-5 |
Low Power (-130 dBm) |
1.66 × 10-4 |
2.40 × 10-4 |
|
TB2 (5 MHz) |
High Power (-30 dBm) |
2.0 × 10-5 |
3.3 × 10-5 |
Low Power (-130 dBm) |
6.6 × 10-5 |
9.8 × 10-5 |
|
Note 1: Provided for reference only Note 2: To be used for testing |
11.4B MBS Dynamic Range Measurement Accuracy (NR)
11.4B.1 Test purpose
Same as defined in clause 11.4.1
11.4B.2 Test applicability
This test applies to all types of NR UE that supports UE-assisted MBS with LPP Release 13 onwards.
11.4B.3 Minimum conformance requirements
For NR UE that supports LPP Release 13 only, same as defined in clause 11.4.3. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.4A.3
11.4B.4 Test description
11.4B.4.1 Initial conditions
Same as defined in clause 11.4.4.1, except in the case of NR UE, step 3 is modified as follows:
3. Establish a signalling connection according to the generic procedure in TS 38.508-1 [45] clause 4.5.4.
11.4B.4.2 Test procedure
For NR UE that supports LPP Release 13 only, same as defined in clause 11.4.4.2. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.4A.4.2
11.4B.4.3 Message contents
For NR UE that supports LPP Release 13 only, same as defined in clause 11.4.4.3. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.4A.4.3
11.4B.5 Test requirement
For NR UE that supports LPP Release 13 only, same as defined in clause 11.4.5. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.4A.5
11.5 MBS Measurement Accuracy in Multipath (Release 13 only)
11.5.1 Test purpose
The purpose of this test is to verify that the MBS Code Phase measurement accuracy is within the specified limits in a multipath environment. This test will verify the requirements in clause 5.5 of TS 37.171 [39] for MBS measurements. The channel type for the test is EPA 5 Hz, as specified in clause 4.8.2.2.
11.5.2 Test applicability
This test applies to all types of E-UTRA UE that supports UE-assisted MBS with LPP Release 13 only.
11.5.3 Minimum conformance requirements
The MBS code phase measurement accuracy shall fulfil the requirements in Table 11.5.3-1.
Table 11.5.3-1: Accuracy requirements for Multipath scenario
Direct Path Signal Strength (dBm) |
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
-30 |
1.66 × 10-4 |
2.35 × 10-4 |
Note 1: Provided for reference only Note 2: To be used for testing |
The accuracy requirement for the difference of code phase measurements is derived from the requirement for the code phase measurement accuracy, assuming a scaling factor of due to the compounding of two error distributions.
The normative reference for this requirement is TS 37.171 [39] clause 5.5 (Multipath) and clause A.4.3.
11.5.4 Test description
11.5.4.1 Initial conditions
Test environment: normal; see Annex G.
1. Connect SS and MSS to the UE antenna connector or antenna connectors as shown in figures A.6 or A.7.
2. Switch on the UE.
3. Establish a signalling connection according to the generic procedure in TS 36.508 [18] clause 4.5.3 (State 3, Generic RB established) on a channel in the Mid EARFCN range.
11.5.4.2 Test procedure
1. Set the MSS test parameters as specified in clause 11.5.5.
2. The SS shall send a RESET UE POSITIONING STORED INFORMATION message.
3. The SS shall send an LPP REQUEST CAPABILITIES message.
4. The UE shall transmit an LPP PROVID CAPABILITIES message indicating the TBS capabilities supported by the UE in the TBS-ProvideCapabilities IE.
5. The SS shall send a LPP REQUEST LOCATION INFORMATION message, including the TBS‑RequestLocationInformation. If the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP REQUEST LOCATION INFORMATION message.
6. The UE shall perform and report the code phase measurement for each simulated beacon. If the UE transmits a TBS‑ProvideLocationInformation IE including the transmitterID and codePhase field for the two simulated and the difference between codePhase field values for the two beacons meets the requirement in Table 11.5.5-3, then the number of successful tests is increased by one. Otherwise the number of failure tests is increased by one.
7. If the UE message at step 6 includes the ackRequested IE set to TRUE, the SS shall send a LPP acknowledgement message.
8. Repeat steps 1-7 until the confidence level according to Annex D is achieved. For each iteration, at step 1 reselect the PN code assigned to each MBS beacon.
9. Release the signalling connection.
11.5.4.3 Message contents
Table 11.5.4.3-1: RESET UE POSITIONING STORED INFORMATION
Derivation Path: TS 36.509 [11] clause 6.9 |
|||
Information Element |
Value/remark |
Comment |
Condition |
UE Positioning Technology |
0 0 0 0 0 0 1 0 |
MBS |
Table 11.5.4.3-2: LPP Request Capabilities
Information Element |
Value/remark |
tbs‑RequestCapabilities-r13 |
TRUE |
Table 11.5.4.3-3: LPP RequestLocationInformation
Derivation Path: TS 36.355 [4] clause 6.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
LPP-Message ::= SEQUENCE { |
|||
transactionID SEQUENCE { |
|||
Initiator |
locationServer |
||
transactionNumber |
1 |
||
} |
|||
endTransaction |
FALSE |
||
sequenceNumber |
Not present |
||
acknowledgement |
Not present |
||
lpp-MessageBody CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation-r9 SEQUENCE { |
|||
commonIEsRequestLocationInformation SEQUENCE { |
|||
locationInformationType |
locationMeasurementsRequired |
||
triggeredReporting |
Not present |
||
periodicalReporting |
Not present |
||
additionalInformation |
onlyReturnInformationRequested |
||
qos SEQUENCE { |
|||
horizontalAccuracy |
Not present |
||
verticalCoordinateRequest |
FALSE |
||
verticalAccuracy |
Not present |
||
responseTime SEQUENCE { |
|||
Time |
12 |
||
responseTimeEarlyFix-r12 |
Not present |
||
} |
|||
velocityRequest |
FALSE |
||
} |
|||
Environment |
Not present |
||
locationCoordinateTypes |
Not present |
||
velocityTypes |
Not present |
||
} |
|||
a-gnss-RequestLocationInformation |
Not present |
||
otdoa-RequestLocationInformation |
Not present |
||
ecid-RequestLocationInformation |
Not present |
||
epdu-RequestLocationInformation |
Not present |
||
sensor-RequestLocationInformation-r13 |
Not present |
||
tbs-RequestLocationInformation-r13 SEQUENCE { |
|||
mbsSgnMeasListReq-r13 |
TRUE |
||
} |
|||
wlan-RequestLocationInformation-r13 |
Not present |
||
bt-RequestLocationInformation-r13 |
Not Present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 11.5.4.3-4: LPP ProvideLocationInformation
Derivation Path: TS 36.355 [4] clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
Initiator |
locationServer |
|||
transactionNumber |
1 |
|||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
(0..255) |
|||
Acknowledgement |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation-r9 SEQUENCE { |
||||
commonIEsProvideLocationInformation |
Not present. |
|||
a-gnss-ProvideLocationInformation |
Not present |
|||
otdoa-ProvideLocationInformation |
Not present |
|||
ecid-ProvideLocationInformation |
Not present |
|||
epdu-ProvideLocationInformation |
Not present |
|||
sensor-ProvideLocationInformation-r13 |
Not present |
|||
tbs-ProvideLocationInformation-r13 |
||||
tbs-MeasurementInformation-r13 |
||||
measurementReferenceTime-r13 |
||||
mbs-SgnMeasList-r13 SEQUENCE (SIZE(n)) { |
||||
transmitterID-r13 |
Present |
|||
codePhase-r13 |
Present |
|||
codePhaseRMSError-r13 |
||||
} |
||||
mbs-SgnMeasList-r13 SEQUENCE (SIZE(n)) { |
||||
transmitterID-r13 |
Present |
|||
codePhase-r13 |
Present |
|||
codePhaseRMSError-r13 |
||||
} |
||||
} |
||||
tbs-Error-r13 |
May be present with error reason ‘undefined’ or ‘thereWereNotEnoughMBSBeaconsReceived’ |
|||
} |
||||
wlan-ProvideLocationInformation-r13 |
Not present |
|||
bt-ProvideLocationInformation-r13 |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
11.5.5 Test requirement
The details of the beacon parameters are in Table 11.5.5-1 and Table 11.5.5-2.
Table 11.5.5-1: General test parameters for the beacons to be simulated for measurement accuracy in Multipath test
Parameter |
Unit |
Value |
Comment |
Number of beacons |
Integer |
2 |
Beacons transmitted in the any two beacon slots in the beacon transmission period, but static for the test. Other slots contain no simulated beacons.Note 1 |
Centre Frequency |
MHz |
925.977 |
|
RF Channel |
N/A |
EPA 5 Hz |
|
MBS Beacon Configuration |
N/A |
TB1 (2 MHz) |
For details see Annex H |
MBS Packet Type |
N/A |
Type 2 |
For details see Annex H |
Beacon PN Code |
Integer |
Chosen for each beacon from the PN code list for TB1 |
Each of the 2 beacons uses a different PN code For details see Annex HNote 1 |
Response time |
Seconds |
12 |
Value of Time used in LPP RequestLocationInformation message in Table 11.5.4.3-3 |
Note 1: The slots and PN codes are chosen at random, such that the UE does not and cannot have advanced knowledge of what that slot/PN code might be. |
Table 11.5.5-2: MBS Beacon Payload fields, and code phase delay difference and transmit powers for the beacons to be simulated for measurement accuracy in Multipath test
MBS Tx ID (See Annex H) |
Slot Index (See Annex H) |
All Other fields (See Annex H) |
Code phase delay difference between beacons (ms) |
Transmit Power (dBm) |
Equal to Slot number |
Equal to Slot number |
min value (bit_value = 0)Note 1 |
0 |
-30 |
Note 1: bit_value is the conversion of the binary number represented by the corresponding bits in the payload to decimal. |
The MBS code phase measurement accuracy shall fulfil the requirements in Table 11.5.5-3.
Table 11.5.5-3: Accuracy requirements for Multipath scenario
Code phase measurement accuracy (ms)Note 1 |
Accuracy requirement for the difference of code phase measurements (ms)Note 2 |
1.66 × 10-4 |
2.40 × 10-4 |
Note 1: Provided for reference only Note 2: To be used for testing |
The test tolerances are defined in clauses C.1.4 and C.4.
The rate of successful tests during repeated tests shall be at least 90% with a confidence level of 95%.
11.5A MBS Measurement Accuracy in Multipath (Release 14 Onwards)
11.5A.1 Test purpose
Same as defined in clause 11.5.1
11.5A.2 Test applicability
This test applies to all types of E-UTRA UE that supports UE-assisted MBS with LPP Release 14 onwards.
11.5A.3 Minimum conformance requirements
Same as defined in clause 11.5.3
11.5A.4 Test description
11.5A.4.1 Initial conditions
Same as defined in clause 11.5.4.1
11.5A.4.2 Test procedure
Same as defined in clause 11.5.4.2, except step 4a is introduced and step 5 is modified as follows:
4a. The SS shall send an LPP PROVIDE ASSISTANCE DATA message to provide the MBS assistance data in accordance with TS 37.571-5 [20], and with the values defined therein. If the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP PROVIDE ASSISTANCE DATA message.
5. The SS shall send a LPP REQUEST LOCATION INFORMATION message, including the TBS RequestLocationInformation.
11.5A.4.3 Message contents
Same as defined in clause 11.5.4.3, with the addition of the LPP Provide Assistance Data.
Table 11.5A.4.3-5: LPP ProvideAssistanceData
Derivation Path: TS 36.355 [4] clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
Initiator |
locationServer |
|||
transactionNumber |
(0..255) |
|||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
Not present |
|||
acknowledgement |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideAssistanceData SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideAssistanceData-r9 SEQUENCE { |
||||
commonIEsProvideAssistanceData |
Not present |
|||
a-gnss-ProvideAssistanceData |
Not present |
|||
otdoa-ProvideAssistanceData |
Not present |
|||
epdu-ProvideAssistanceData |
Not present |
|||
sensor-ProvideAssistanceData-r14 |
Not present |
Rel-14 onwards |
||
tbs-ProvideAssistanceData-r14 SEQUENCE { |
Rel-14 onwards |
|||
tbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb1 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 2 tb1 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb2 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 2 tb2 |
|||
mbs-AlmanacAssistance-r14 |
Not Present |
|||
mbs-AcquisitionAssistance-r14 |
As defined in TS 37.571-5 [20], clause 8 |
|||
} |
||||
} |
||||
} |
||||
tbs-Error-r14 |
Not Present |
|||
} |
||||
} |
||||
wlan-ProvideAssistanceData-r14 |
Not Present |
Rel-14 onwards |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
11.5A.5 Test requirement
Same as defined in clause 11.5.5, with the beacon parameters set according to the assistance data in TS 37.571-5 [20] clause 8.
11.5B MBS Measurement Accuracy in Multipath (NR)
11.5B.1 Test purpose
Same as defined in clause 11.5.1.
11.5B.2 Test applicability
This test applies to all types of NR UE that supports UE-assisted MBS with LPP Release 13 onwards.
11.5B.3 Minimum conformance requirements
Same as defined in clause 11.5.3.
11.5B.4 Test description
11.5B.4.1 Initial conditions
For NR UE that supports LPP Release 13 only, same as defined in clause 11.5.4.1. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.5A.4.1.
11.5B.4.2 Test procedure
For NR UE that supports LPP Release 13 only, same as defined in clause 11.5.4.2. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.5A.4.2.
11.5B.4.3 Message contents
For NR UE that supports LPP Release 13 only, same as defined in clause 11.5.4.3. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.5A.4.3.
11.5B.5 Test requirement
For NR UE that supports LPP Release 13 only, same as defined in clause 11.5.5. For NR UE that supports LPP Release 14 onwards, same as defined in clause 11.5A.5.