5 Default Conditions for E-UTRAN
37.571-23GPPPart 2: Protocol conformanceRelease 16TSUser Equipment (UE) conformance specification for UE positioning
5.1 LCS Sub-Test Cases
Some test cases defined in clause 7 may include several 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 5.1-1. The applicable sub-tests for each test case are specified in the test procedure sequence clause of each test case. If no sub-tests are defined for a specific test case it means that this particular test case is not dependent on a specific positioning method.
Table 5.1-1: Sub-Test Case Numbers for E-UTRA
Sub-Test Case Number |
Supported Positioning Methods |
1 |
Void |
2 |
Void |
3 |
Void |
4 |
Void |
5 |
UE supporting OTDOA |
6 FDD |
UE supporting ECID (FDD) |
6 TDD |
UE supporting ECID (TDD) |
7 |
UE supporting GNSS(1) and OTDOA |
8 |
Void |
9 |
Void |
10 |
Void |
11 |
UE supporting WLAN (Rel-13 only) |
12 |
UE supporting MBS(2) (Rel-13 only) |
13 |
UE supporting Bluetooth |
14 |
UE supporting Sensor (Rel-13 only) |
15 |
UE supporting GNSS(1) |
16 |
UE supporting MBS(2) (Rel-14 onwards) |
17 |
UE supporting WLAN (Rel-14 onwards) |
18 |
UE supporting Sensor (Rel-14 onwards) |
23 |
UE supporting MBS(2) (Rel-15 onwards) |
24 |
UE supporting Sensor (Rel-15 onwards) |
25 |
UE supporting GNSS(1) (Rel-15 onwards) |
NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE NOTE 2: Metropolitan Beacon System (MBS) is a specific type of Terrestrial Beacon System (TBS) [29] |
5.2 Default signal conditions
5.2.1 Simulated GNSS environment
During A-GNSS signalling tests, where required the SS shall generate all UE supported satellite signals. Where required the SS shall provide assistance data dependent on UE capabilities defined in subclause 5.4.1.1 and consistent with the satellite signals generated during these tests if satellite signals are also required.
The levels of the simulated satellites shall be at -125 dBm ± 6 dBm.
GNSS scenarios together with associated assistance data are defined in TS 37.571-5 [12].
The accuracy of the GNSS time in the provided assistance data shall be within ± 2 seconds relative to the GNSS time in the system simulator. In the case that assistance data is required but satellite signals are not required then this clause does not apply.
5.2.2 Simulated OTDOA environment
For OTDOA signalling test cases a multi cell environment with Cell 1 and Cell 2 (where required) is used, as defined in 3GPP TS 36.508 [8].
All cells transmit PRS according to the PRS configuration provided in the OTDOA assistance data defined in subclause 5.4.1.2. The positioning subframes are low-interference subframes, i.e. contain no PDSCH transmissions.
Normal propagation condition is used for all cells. Cell 1 is the serving cell and Cell 2 (where required) is a neighbour cell.
Where two cells are required, the two Cells 1 and 2 shall be synchronized, and the timing offset (the RSTD) between the cells, referenced to the UE’s antenna input, shall be set equal to the expectedRSTD value provided in the OTDOA assistance data, as defined in subclause 5.4.1.2.
The E-UTRA frequency to be tested and other default conditions are as specified for signalling test cases in 3GPP TS 36.508 [8].
5.2.3 Simulated ECID environment
For ECID signalling test cases a multi cell environment with Cell 1 and Cell 2 is used, as defined in 3GPP TS 36.508 [8].
Normal propagation condition is used for all cells. Cell 1 is the serving cell and Cell 2 is a neighbour cell.
The E-UTRA frequency to be tested and other default conditions are as specified for signalling test cases in 3GPP TS 36.508 [8].
Note: If the only ECID measurement supported by the UE is the UE Rx-Tx Time Difference Measurement, Cell 2 does not need to be simulated (see also table 5.4-6).
5.2.4 Simulated MBS environment
During MBS signalling tests, where required, the SS shall generate the UE supported MBS signals as defined in the MBS scenarios defined in TS 37.571-5 [12].
5.2.5 Simulated WLAN environment
During WLAN signalling tests, where required, the SS shall generate the UE supported WLAN signals as defined in the WLAN scenarios defined in TS 37.571-5 [12].
5.2.6 Simulated Bluetooth environment
During Bluetooth signalling tests, where required, the SS shall generate the UE supported Bluetooth signals as defined in the Bluetooth scenarios defined in TS 37.571-5 [12].
5.2.7 Simulated Sensor environment
During Sensor signalling tests there is no simulated sensor environment.
5.3 Default RRC and NAS message and information elements contents
The default values of common RRC and NAS messages and information elements are used as defined in 3GPP
TS 36.508 [8] with the following exceptions.
– ATTACH ACCEPT
Table 5.3-1: ATTACH ACCEPT
Derivation Path: 36.508 Table 4.7.2-1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
EPS network feature support |
Set according to Table 5.3-2 |
Table 5.3-2: EPS network feature support
Derivation Path: 24.301 clause 9.9.3.12A |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
IMS voice over PS session indicator (IMS VoPS) (octet 3, bit 1) |
1 |
IMS voice over PS session in S1 mode supported |
||
Emergency bearer services indicator (EMC BS) (octet 3, bit 2) |
1 |
emergency bearer services in S1 mode supported |
||
Location services indicator in EPC (EPC-LCS) (octet 3, bit 3) |
1 |
location services via EPC supported |
||
Location services indicator in CS (CS-LCS) (octet 3, bit 4 to 5) |
01 |
location services via CS domain not supported |
||
octet 3, bit 6 to 8 |
000 |
spare |
5.4 Default LPP message and information elements contents
This clause contains the default values of LPP messages and information elements used, unless indicated otherwise in specific clauses of this specification.
– LPP REQUEST CAPABILITIES
Table 5.4-1: RequestCapabilities
Derivation Path: 36.355 clause 6.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
LPP-Message ::= SEQUENCE { |
|||
transactionID SEQUENCE { |
|||
Initiator |
locationServer |
||
transactionNumber |
(0..255) |
||
} |
|||
endTransaction |
FALSE |
||
sequenceNumber |
Not present |
||
acknowledgement |
Not present |
||
lpp-MessageBody CHOICE { |
|||
c1 CHOICE { |
|||
requestCapabilities SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
requestCapabilities-r9 SEQUENCE { |
|||
commonIEsRequestCapabilities SEQUENCE { |
Present |
Rel-14 onwards |
|
lpp-message-segmentation-req-r14 |
00 |
Server is not able to send segmented LPP messages. Server is not able to receive segmented LPP messages. Rel-14 onwards |
|
} |
|||
a-gnss-RequestCapabilities SEQUENCE { |
|||
gnss-SupportListReq |
TRUE |
||
assistanceDataSupportListReq |
TRUE |
||
locationVelocityTypesReq |
TRUE |
||
} |
|||
otdoa-RequestCapabilities SEQUENCE { |
Present |
||
} |
|||
ecid-RequestCapabilities SEQUENCE { |
Present |
||
} |
|||
epdu-RequestCapabilities |
Not present |
||
sensor-RequestCapabilities-r13 SEQUENCE { |
Present |
Rel-13 onwards |
|
} |
|||
tbs-RequestCapabilities-r13 SEQUENCE { |
Present |
Rel-13 onwards |
|
} |
|||
wlan-RequestCapabilities-r13 SEQUENCE { |
Present |
Rel-13 onwards |
|
} |
|||
bt-RequestCapabilities-r13 SEQUENCE { |
Present |
Rel-13 onwards |
|
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
– LPP PROVIDE ASSISTANCE DATA
Table 5.4-2: ProvideAssistanceData
Derivation Path: 36.355 clause 6.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
LPP-Message ::= SEQUENCE { |
|||
transactionID SEQUENCE { |
Dependent on test case. |
||
initiator |
|||
transactionNumber |
|||
} |
|||
endTransaction |
TRUE |
||
sequenceNumber |
Not present |
||
acknowledgement |
Not present |
||
lpp-MessageBody CHOICE { |
|||
c1 CHOICE { |
|||
provideAssistanceData SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
provideAssistanceData-r9 SEQUENCE { |
|||
commonIEsProvideAssistanceData |
Not present |
||
a-gnss-ProvideAssistanceData SEQUENCE { |
Sub-tests 7 and 15 only; and as defined in Table 5.4.1.1-1. |
||
gnss-CommonAssistData SEQUENCE { |
|||
gnss-ReferenceTime |
As defined in 37.571-5 [12] |
||
gnss-ReferenceLocation |
As defined in 37.571-5 [12] |
||
gnss-IonosphericModel |
As defined in 37.571-5 [12] |
||
gnss-EarthOrientationParameters |
Not present |
||
} |
|||
gnss-GenericAssistData(SIZE(1..4))OF{ |
SIZE is dependent on the number of GNSSs supported by the UE. If one GNSS supported by the UE, SIZE = 1 If two GNSSs supported by the UE, SIZE = 2 If three GNSSs supported by the UE, SIZE = 3 If four GNSSs supported by the UE, SIZE = 4 |
||
gnss-ID |
For each GNSS supported by the UE. |
||
sbas-ID |
Not present |
||
gnss-TimeModels |
As defined in 37.571-5 [12] |
||
gnss-DifferentialCorrections |
Not present |
||
gnss-NavigationModel |
As defined in 37.571-5 [12] |
||
gnss-RealTimeIntegrity |
Not present |
||
gnss-DataBitAssistance |
Not present |
||
gnss-AcquisitionAssistance |
As defined in 37.571-5 [12] |
||
gnss-Almanac |
As defined in 37.571-5 [12] |
||
gnss-UTC-Model |
As defined in 37.571-5 [12] |
||
gnss-AuxiliaryInformation |
As defined in 37.571-5 [12] |
||
} |
|||
gnss-Error |
Not present |
||
} |
|||
otdoa-ProvideAssistanceData SEQUENCE { |
Sub-test 5 and 7 only |
||
otdoa-ReferenceCellInfo |
As defined in Table 5.4.1.2-1 |
||
otdoa-NeighbourCellInfo |
As defined in Table 5.4.1.2-2 |
||
otdoa-Error |
Not present |
||
} |
|||
epdu-Provide-AssistanceData |
Not present |
||
sensor-ProvideAssistanceData-r14 SEQUENCE { |
Rel-14 onwards |
Sub-test 18 only as defined in clause 5.4.1.5 |
|
sensor-AssistanceDataList-r14 |
As defined in Table 5.4.1.5-2 |
||
sensor-Error-r14 |
Not present |
||
} |
|||
tbs-ProvideAssistanceData-r14 SEQUENCE { |
Rel-14 onwards |
Sub-test 16 only as defined in clause 5.4.1.3 |
|
tbs-AssistanceDataList-r14 SEQUENCE { |
|||
mbs-AssistanceDataList-r14 SEQUENCE (SIZE(1..n)) OF SEQUENCE{ |
|||
mbs-AlmanacAssistance-r14 |
As defined in Table 5.4.1.3-2 |
||
mbs-AcquisitonAssistance-r14 |
As defined in Table 5.4.1.3-2 |
||
} |
|||
} |
|||
tbs-Error-r14 |
Not present |
||
} |
|||
wlan-ProvideAssistanceData-r14 SEQUENCE { |
Rel-14 onwards |
Sub-test 17 only as defined in clause 5.4.1.4 |
|
wlan-DataSet-r14 |
As defined in Table 5.4.1.4-2 |
||
wlan-Error-r14 |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
– LPP REQUEST LOCATION INFORMATION
Table 5.4-3: RequestLocationInformation
Derivation Path: 36.355 clause 6.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
LPP-Message ::= SEQUENCE { |
|||
transactionID SEQUENCE { |
|||
initiator |
locationServer |
||
transactionNumber |
(0..255) |
||
} |
|||
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 |
Dependent on test case |
||
triggeredReporting |
Not present |
||
periodicalReporting |
Not present |
||
additionalInformation |
onlyReturnInformationRequested |
||
qos SEQUENCE { |
|||
horizontalAccuracy |
Not present |
||
verticalCoordinateRequest |
FALSE |
||
verticalAccuracy |
Not present |
||
responseTime SEQUENCE { |
|||
time |
32 |
||
responseTimeEarlyFix-r12 |
Not present |
Rel-12 onwards |
|
} |
|||
velocityRequest |
FALSE |
||
} |
|||
environment |
Not present |
||
locationCoordinateTypes |
Not present |
||
velocityTypes |
Not present |
||
} |
|||
a-gnss-RequestLocationInformation |
As defined in Table 5.4-4 |
Sub-tests 7 and 15 |
|
otdoa-RequestLocationInformation |
As defined in Table 5.4-5 |
Sub-test 5 and 7 |
|
ecid-RequestLocationInformation |
As defined in Table 5.4-6 |
Sub-test 6 |
|
epdu-RequestLocationInformation |
Not Present |
||
sensor-RequestLocationInformation-r13 |
As defined in Table 5.4-10 |
Rel-13 onwards |
Sub-test 14, 18 |
tbs-RequestLocationInformation-r13 |
As defined in Table 5.4-7 |
Rel-13 onwards |
Sub-tests 12, 16 |
wlan-RequestLocationInformation-r13 |
As defined in Table 5.4-8 |
Rel-13 onwards |
Sub-test 11, 17 |
bt-RequestLocationInformation-r13 |
As defined in Table 5.4-9 |
Rel-13 onwards |
Sub-test 13 |
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
– A-GNSS REQUEST LOCATION INFORMATION
Table 5.4-4: A-GNSS-RequestLocationInformation
Derivation Path: 36.355 clause 6.5.2.7 |
|||
Information Element |
Value/remark |
Comment |
Condition |
A-GNSS-RequestLocationInformation ::= SEQUENCE { |
|||
gnss-PositioningInstructions SEQUENCE { |
|||
gnss-Methods |
Dependent on the GNSS(s) supported by the UE. If GPS supported bit 0 = 1 If Galileo supported bit 3 = 1 If GLONASS supported bit 4 = 1 If BDS supported bit 5 = 1 |
GNSS-ID-Bitmap |
|
fineTimeAssistanceMeasReq |
FALSE |
||
adrMeasReq |
FALSE |
||
multiFreqMeasReq |
FALSE |
||
assistanceAvailability |
FALSE |
||
} |
|||
} |
– OTDOA REQUEST LOCATION INFORMATION
Table 5.4-5: OTDOA-RequestLocationInformation
Derivation Path: 36.355 clause 6.5.1.6 |
|||
Information Element |
Value/remark |
Comment |
Condition |
OTDOA-RequestLocationInformation ::= SEQUENCE { |
|||
assistanceAvailability |
FALSE |
||
multipathRSTD-r14 |
Not present |
Rel-14 onwards |
|
maxNoOfRSTDmeas-r14 |
Not present |
Rel-14 onwards |
|
} |
– ECID REQUEST LOCATION INFORMATION
Table 5.4-6: ECID-RequestLocationInformation
Derivation Path: 36.355 clause 6.5.3.3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
ECID-RequestLocationInformation ::= SEQUENCE { |
|||
requestedMeasurements |
All measurements supported by the UE |
||
} |
– TBS REQUEST LOCATION INFORMATION
Table 5.4-7: TBS-RequestLocationInformation
Derivation Path: 36.355 clause 6.5.4.3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
TBS-RequestLocationInformation-r13 ::= SEQUENCE { |
|||
mbsSgnMeasListReq-r13 |
TRUE (UE-Assisted MBS) |
Rel-13 onwards |
|
mbsAssistanceAvailability-r14 |
FALSE |
Rel-14 onwards |
|
mbsRequestedMeasurements-r14 |
Not present |
Rel-14 onwards |
|
} |
– WLAN REQUEST LOCATION INFORMATION
Table 5.4-8: WLAN-RequestLocationInformation
Derivation Path: 36.355 clause 6.5.6.3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
WLAN-RequestLocationInformation-r13 ::= SEQUENCE { |
|||
requestedMeasurements-r13 |
bit 0 = 1 (rssi) (UE-Assisted WLAN) bit 1 = 1 (rtt) (UE-Assisted WLAN) |
Rel-13 onwards |
|
assistanceAvailability-r14 |
FALSE |
Rel-14 onwards |
|
} |
– BT REQUEST LOCATION INFORMATION
Table 5.4-9: BT-RequestLocationInformation
Derivation Path: 36.355 clause 6.5.7.3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
BT-RequestLocationInformation-r13 ::= SEQUENCE { |
|||
requestedMeasurements-r13 |
bit 0 = 1 (rssi) (UE-Assisted BT) |
Rel-13 onwards |
|
} |
– SENSOR REQUEST LOCATION INFORMATION
Table 5.4-10: Sensor-RequestLocationInformation
Derivation Path: 36.355 clause 6.5.5.3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
Sensor-RequestLocationInformation-r13 ::= SEQUENCE { |
|||
uncompensatedBarometricPressureReq-r13 |
TRUE (UE-Assisted Sensor) |
Rel-13 onwards |
|
assistanceAvailability-r14 |
FALSE |
Rel-14 onwards |
|
} |
5.4.1 Default assistance data information elements
5.4.1.1 GNSS Assistance Data Elements
Table 5.4.1.1-1 defines the GNSS assistance data elements which shall be provided to the UE in the tests in LPP Provide Assistance Data messages in the absence of a corresponding LPP Request Assistance Data message. The GNSS assistance data provided depends on the mode being used in the test case, the assistance data supported by the UE and the GNSSs supported by the UE. GNSS assistance data IEs not supported by the UE shall not be sent. GNSS assistance data IEs supported by the UE but not listed in Table 5.4.1.1-1 shall not be sent. The content of the assistance data elements is defined in 37.571-5 [12] clause 7.
Table 5.4.1.1-1: GNSS assistance data to be provided to the UE
GNSS Assistance Data IE supported by UE |
Mode used in test case |
||
UE-based |
UE-assisted, GNSS-AcquisitionAssistance supported by UE |
UE-assisted, GNSS-AcquisitionAssistance not supported by UE |
|
GNSS-Reference Time |
Yes |
Yes |
Yes |
GNSS-ReferenceLocation |
Yes |
No |
Yes |
GNSS-IonosphericModel |
Yes |
No |
No |
GNSS-TimeModelList |
Yes(1) |
No |
Yes(1) |
GNSS-NavigationModel |
Yes |
No |
Yes |
GNSS-AcquisitionAssistance |
No |
Yes |
No |
GNSS-Almanac |
No |
No |
Yes |
GNSS-UTC-Model |
Yes(3) |
Yes(3) |
Yes(3) |
GNSS-AuxiliaryInformation |
Yes(2) |
Yes(2) |
Yes(2) |
NOTE 1: Only if more than one GNSS supported by the UE. NOTE 2: Only if GLONASS supported by the UE, and/or if the UE supports multiple signals per GNSS, and/or if BDS B1C signal type supported by the UE. NOTE 3: Only if GLONASS and at least one other GNSS supported by the UE. |
5.4.1.2 OTDOA Assistance Data Elements
This subclause defines the OTDOA assistance data elements which shall be provided to the UE in the tests in LPP Provide Assistance Data messages.
– OTDOA REFERENCE CELL INFO
Table 5.4.1.2-1: OTDOA-ReferenceCellInfo
Derivation Path: 36.355 clause 6.5.1.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
OTDOA-ReferenceCellInfo ::= SEQUENCE { |
Cell 1 |
||
physCellId |
0 |
||
cellGlobalId SEQUENCE { |
|||
mcc |
As defined for Cell 1 in 36.508 [8] |
||
mnc |
As defined for Cell 1 in 36.508 [8] |
||
cellidentity |
As defined for E-UTRAN Cell Identifier for Cell 1 in 36.508 [8] |
||
} |
|||
earfcnRef |
Not present |
Same as the serving cell |
|
antennaPortConfig |
Not present |
Same as the serving cell |
|
cpLength |
Normal |
||
prsInfo SEQUENCE { |
|||
prs-Bandwidth |
PRS are transmitted over the used system bandwidth (see subclause 5.2.2) |
||
prs-ConfigurationIndex |
FDD: 2 TDD: 4 |
||
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 |
} |
|||
earfcnRef-v9a0 |
Not present |
Same as the serving cell |
|
tpId-r14 |
Not present |
Transmission Points not used |
Rel-14 onwards |
cpLengthCRS-r14 |
Normal |
Rel-14 onwards |
|
sameMBSFNconfigRef-r14 |
TRUE |
Same as the serving cell |
Rel-14 onwards |
dlBandwidth-r14 |
Not present |
Same as the serving cell and PRS frequency hopping not used |
Rel-14 onwards |
addPRSconfigRef-r14 |
Not present |
No additional PRS configuration(s) |
Rel-14 onwards |
} |
– OTDOA NEIGHBOUR CELL INFO LIST
Table 5.4.1.2-2: OTDOA-NeighbourCellInfoList
Derivation Path: 36.355 clause 6.5.1.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
OTDOA-NeighbourCellInfoList ::= SEQUENCE (SIZE(1)) OF SEQUENCE { |
|||
SEQUENCE (SIZE(2)) OF SEQUENCE { |
Cell 2 |
||
physCellId |
2 |
||
cellGlobalId SEQUENCE { |
|||
mcc |
As defined for Cell 2 in 36.508 [8] |
||
mnc |
As defined for Cell 2 in 36.508 [8] |
||
cellidentity |
As defined for E-UTRAN Cell Identifier for Cell 2 in 36.508 [8] |
||
} |
|||
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 |
Slot timing is the same as for reference cell |
|
prs-SubframeOffset |
Not present |
||
expectedRSTD |
8192 |
Value 0 |
|
expectedRSTD-Uncertainty |
10 |
About 1 s |
|
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 |
} |
|||
SEQUENCE { |
Cell 4 |
||
physCellId |
4 |
||
cellGlobalId SEQUENCE { |
|||
mcc |
As defined for Cell 4 in 36.508 [8] |
||
mnc |
As defined for Cell 4 in 36.508 [8] |
||
cellidentity |
As defined for E-UTRAN Cell Identifier for Cell 4 in 36.508 [8] |
||
} |
|||
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 |
Slot timing is the same as for reference cell |
|
prs-SubframeOffset |
Not present |
||
expectedRSTD |
8192 |
Value 0 |
|
expectedRSTD-Uncertainty |
10 |
About 1 s |
|
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 |
} |
|||
} |
5.4.1.3 MBS Assistance Data Elements
Tables 5.4.1.3-1 and 5.4.1.3-2 define the MBS assistance data elements which shall be provided to the UE in sub-test 16 via LPP Provide Assistance Data messages in the absence of a corresponding LPP Request Assistance Data message.
Table 5.4.1.3-1 defines the MBS assistance data IEs that conditionally depend on the mode being used in the test case and on the assistance data supported by the UE.
Table 5.4.1.3-2 defines the content of the TBS-AssistantDataList.
Table 5.4.1.3-1: MBS assistance data IEs to be conditionally provided to the UE
MBS Assistance Data IE supported by UE |
Mode used in test case |
|
UE-based, MBS (Release 14 onwards) |
UE-assisted, MBS (Release 14 onwards) |
|
mbs-AlmanacAssistance-r14 |
Yes |
No |
mbs-AcquisitionAssistance-r14 |
Yes |
Yes |
Table 5.4.1.3-2: Content of TBS-AssistanceDataList
Derivation Path: TS 36.355 [4] clause 6.5.4 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
tbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataList-r14 SEQUENCE { |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb1 |
|||
mbs-AlmanacAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
mbs-AcquisitionAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 2 tb1 |
|||
mbs-AlmanacAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
mbs-AcquisitionAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 3 tb1 |
|||
mbs-AlmanacAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
mbs-AcquisitionAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 4 tb1 |
|||
mbs-AlmanacAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
mbs-AcquisitionAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 1 tb2 |
|||
mbs-AlmanacAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
mbs-AcquisitionAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 2 tb2 |
|||
mbs-AlmanacAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
mbs-AcquisitionAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 3 tb2 |
|||
mbs-AlmanacAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
mbs-AcquisitionAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
} |
||||
mbs-AssistanceDataElement-r14 SEQUENCE { |
Beacon 4 tb2 |
|||
mbs-AlmanacAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
mbs-AcquisitionAssistance-r14 |
According to Table 5.4.1.3-1 and as defined in TS 37.571-5 [12], clause 8 |
|||
} |
||||
} |
||||
} |
5.4.1.4 WLAN Assistance Data Elements
Tables 5.4.1.4-1 and 5.4.1.4-2 define the WLAN assistance data elements which shall be provided to the UE in sub-test 17 via LPP Provide Assistance Data messages in the absence of a corresponding LPP Request Assistance Data message.
Table 5.4.1.4-1 defines the WLAN assistance data IE that conditionally depends on the mode being used in the test case and on the assistance data supported by the UE.
Table 5.4.1.4-2 defines the content of the WLAN-DataSet.
Table 5.4.1.4-1: WLAN assistance data IE to be conditionally provided to the UE
WLAN assistance data IE supported by UE |
Mode used in test case |
|
UE-based, WLAN (Release 14 onwards) |
UE-assisted, WLAN (Release 14 onwards) |
|
wlan-AP-Location-r14 (WLAN AP location information) |
Yes |
No |
Table 5.4.1.4-2: Content of WLAN-DataSet
Derivation Path: TS 36.355 [4] clause 6.5.6.8 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
wlan-DataSet-r14::= SEQUENCE (SIZE (1)) OF SEQUENCE { |
Rel-14 onwards |
|||
SEQUENCE (SIZE (4)) OF SEQUENCE.{ |
||||
WLAN-AP-Data-r14 SEQUENCE { |
WLAN AP 1 |
|||
wlan-AP-Identifier-r14 |
As defined in TS 37.571-5 [12], clause 9 |
|||
wlan-AP-Location-r14 |
According to Table 5.4.1.4-1 and as defined in TS 37.571-5 [12], clause 9 |
|||
} |
||||
WLAN-AP-Data-r14 SEQUENCE { |
WLAN AP 2 |
|||
wlan-AP-Identifier-r14 |
As defined in TS 37.571-5 [12], clause 9 |
|||
wlan-AP-Location-r14 |
According to Table 5.4.1.4-1 and as defined in TS 37.571-5 [12], clause 9 |
|||
} |
||||
WLAN-AP-Data-r14 SEQUENCE { |
WLAN AP 3 |
|||
wlan-AP-Identifier-r14 |
As defined in TS 37.571-5 [12], clause 9 |
|||
wlan-AP-Location-r14 |
According to Table 5.4.1.4-1 and as defined in TS 37.571-5 [12], clause 9 |
|||
} |
||||
WLAN-AP-Data-r14 SEQUENCE { |
WLAN AP 4 |
|||
wlan-AP-Identifier-r14 |
As defined in TS 37.571-5 [12], clause 9 |
|||
wlan-AP-Location-r14 |
According to Table 5.4.1.4-1 and as defined in TS 37.571-5 [12], clause 9 |
|||
} |
||||
supportedChannels-11a-r14 |
As defined in TS 37.571-5 [12], clause 9 |
|||
supportedChannels-11bg-r14 |
As defined in TS 37.571-5 [12], clause 9 |
|||
} |
||||
} |
5.4.1.5 Sensor Assistance Data Elements
Tables 5.4.1.5-1 and 5.4.1.5-2 define the Sensor assistance data elements which shall be provided to the UE in sub-test 18 via LPP Provide Assistance Data messages in the absence of a corresponding LPP Request Assistance Data message.
Table 5.4.1.5-1 defines the Sensor assistance data IE that conditionally depends on the mode being used in the test case.
Table 5.4.1.5-2 defines the content of the Sensor-AssistanceDataList.
Table 5.4.1.5-1: Sensor assistance data IE to be conditionally provided to the UE
Sensor assistance data to be provided to the UE |
Mode used in test case |
|
UE-based, Sensor (Release 14 onwards) |
UE-assisted, Sensor (Release 14 onwards) |
|
sensor-AssistanceDataList-r14 |
Yes |
No |
Table 5.4.1.5-2: Content of Sensor-AssistanceDataList
Derivation Path: TS 36.355 [4] clause 6.5.5.8 |
|||||||
Information Element |
Value/remark |
Comment |
Condition |
||||
Sensor-AssistanceDataList-r14::= SEQUENCE { |
According to Table 5.4.1.5-1 |
Rel-14 onwards |
|||||
refPressure-r14 |
0 |
101325 Pa |
|||||
refPosition-r14 |
As defined in TS 37.571-5 [12], clause 6.1.3.4, GNSS-ReferenceLocation |
As used in GNSS sub-tests |
|||||
refTemperature-r14 |
20 |
293K |
|||||
period-v1520 |
Not present |
||||||
area-v1520 |
Not present |
||||||
} |