accessTypes

This field specifies the cellular access type(s). This is represented by a bit string, with a one‑value at the bit position means the particular access type is addressed; a zero‑value means not addressed.

carrierFreq

This field specifies the ARFCN applicable for the NB-IoT carrier frequency as defined in TS 36.101 [21, Table 5.7.3-1].

carrierFreqOffset

This field specifies the offset of the NB-IoT channel number to EARFCN as defined in TS 36.101 [21].

CarrierFreqOffsetNB

This field specifies the offset of the NB-IoT channel number to EARFCN as defined in TS 36.101 [21]. Value v-10 means -10, v-9 means -9, and so on.

plmn-Identity

This field identifies the PLMN of the cell as defined in TS 36.331 [12].

cellIdentity

This field defines the identity of the cell within the context of the PLMN as defined in TS 36.331 [12] and TS 25.331 [13]. The size of the bit string allows for the 32-bit extended UTRAN cell ID; in the case the cell ID is shorter, the first bits of the string are set to 0.

plmn-Identity

This field identifies the PLMN of the cell.

locationAreaCode

This field is a fixed length code identifying the location area within a PLMN.

cellIdentity

This field specifies the cell Identifier which is unique within the context of the GERAN location area.

EPDU-ID

This field provides a unique integer ID for the externally defined positioning method. Its value is assigned to the external entity that defines the EPDU. See table External PDU Identifier Definition for a list of external PDU identifiers defined in this version of the specification.

EPDU-Name

This field provides an optional character encoding which can be used to provide a quasi-unique name for an external PDU – e.g., by containing the name of the defining organization and/or the name of the associated public or proprietary standard for the EPDU.

EPDU-Body

The content and encoding of this field are defined externally to LPP.

1

OMA LOC

OMA LPP extensions (LPPe)

OMA-TS-LPPe-V1_0 [20]

periodicSessionID

This field identifies a particular periodic assistance data delivery session and the initiator of the session.

updateCapabilities

This field identifies the capabilities of the sending entity to support an update of periodic assistance data. A bit value set to one indicates a capability is supported and a bit value set to zero indicates a capability is not supported.

posModes

This field specifies the positioning mode(s). This is represented by a bit string, with a one‑value at the bit position means the particular positioning mode is addressed; a zero‑value means not addressed.

SegmentationInfo

noMoreMessages indicates that this is the only or last LPP message segment used to deliver the entire message body.

moreMessagesOnTheWay indicates that this is one of multiple LPP message segments used to deliver the entire message body.

lpp-message-segmentation-req

This field, if present, indicates that the target device is requested to provide its LPP message segmentation capabilities.
If bit 0 is set to value 1, it indicates that the server is able to send segmented LPP messages to the target device; if bit 0 is set to value 0 it indicates that the server is not able to send segmented LPP messages to the target device.

If bit 1 is set to value 1, it indicates that the server is able to receive segmented LPP messages from the target device; if bit 1 is set to value 0 it indicates that the server is not able to receive segmented LPP messages from the target device.

Segmentation

This field is optionally present, need OP, if lpp-message-segmentation-req has been received from the location server with bit 1 (targetToServer) set to value 1. The field shall be omitted if lpp‑message‑segmentation-req has not been received in this location session, or has been received with bit 1 (targetToServer) set to value 0.

segmentationInfo

This field indicates whether this ProvideCapabilities message is one of many segments, as specified in clause 4.3.5.

lpp-message-segmentation

This field, if present, indicates the target device’s LPP message segmentation capabilities.
If bit 0 is set to value 1, it indicates that the target device supports receiving segmented LPP messages; if bit 0 is set to value 0 it indicates that the target device does not support receiving segmented LPP messages.

If bit 1 is set to value 1, it indicates that the target device supports sending segmented LPP messages; if bit 1 is set to value 0 it indicates that the target device does not support sending segmented LPP messages.

EUTRA

The field is mandatory present for E-UTRA or NB-IoT access. The field shall be omitted for non-EUTRA and non-NB-IoT user plane support.

Segmentation

This field is optionally present, need OP, if lpp-message-segmentation-req has been received from the location server with bit 1 (targetToServer) set to value 1. The field shall be omitted if lpp‑message‑segmentation-req has not been received in this location session, or has been received with bit 1 (targetToServer) set to value 0.

PerADreq

The field is mandatory present if the target device requests periodic assistance data delivery. Otherwise it is not present.

NR

The field is mandatory present for NR access. The field shall be omitted for non-NR user plane support.

primaryCellID

This parameter identifies the current primary cell for the target device.

segmentationInfo

This field indicates whether this RequestAssistanceData message is one of many segments, as specified in clause 4.3.5.

periodicAssistanceDataReq

This field indicates a request for periodic assistance data delivery, as specified in clause 5.2.1a.

PerAD

The field is mandatory present in a periodic assistance data delivery session. Otherwise it is not present.

segmentationInfo

This field indicates whether this ProvideAssistanceData message is one of many segments, as specified in clause 4.3.5.

periodicAssistanceData

This field indicates a periodic assistance data delivery, as specified in clauses 5.2.1a and 5.2.2a.

ECID

The field is optionally present, need ON, if E-CID or NR E-CID is requested. Otherwise it is not present.

locationInformationType

This IE indicates whether the server requires a location estimate or measurements. For ‘locationEstimateRequired‘, the target device shall return a location estimate if possible, or indicate a location error if not possible. For ‘locationMeasurementsRequired‘, the target device shall return measurements if possible, or indicate a location error if not possible. For ‘locationEstimatePreferred‘, the target device shall return a location estimate if possible, but may also or instead return measurements for any requested position methods for which a location estimate is not possible. For ‘locationMeasurementsPreferred‘, the target device shall return location measurements if possible, but may also or instead return a location estimate for any requested position methods for which return of location measurements is not possible.

triggeredReporting

This IE indicates that triggered reporting is requested and comprises the following subfields:

– cellChange: If this field is set to TRUE, the target device provides requested location information each time the primary cell has changed.

– reportingDuration: Maximum duration of triggered reporting in seconds. A value of zero is interpreted to mean an unlimited (i.e. "infinite") duration. The target device should continue triggered reporting for the reportingDuration or until an LPP Abort or LPP Error message is received.

The triggeredReporting field should not be included by the location server and shall be ignored by the target device if the periodicalReporting IE or responseTime IE or responseTimeNB IE is included in CommonIEsRequestLocationInformation.

periodicalReporting

This IE indicates that periodic reporting is requested and comprises the following subfields:

– reportingAmount indicates the number of periodic location information reports requested. Enumerated values correspond to 1, 2, 4, 8, 16, 32, 64, or infinite/indefinite number of reports. If the reportingAmount is ‘infinite/indefinite’, the target device shou-ld continue periodic reporting until an LPP Abort message is received. The value ‘ra1‘ shall not be used by a sender.

– reportingInterval indicates the interval between location information reports and the response time requirement for the first location information report. Enumerated values ri0-25, ri0-5, ri1, ri2, ri4, ri8, ri16, ri32, ri64 correspond to reporting intervals of 1, 2, 4, 8, 10, 16, 20, 32, and 64 seconds, respectively. Measurement reports containing no measurements or no location estimate are required when a reportingInterval expires before a target device is able to obtain new measurements or obtain a new location estimate. The value ‘noPeriodicalReporting‘ shall not be used by a sender.

additionalInformation

This IE indicates whether a target device is allowed to return additional information to that requested. If this IE indicates ‘onlyReturnInformationRequested’ then the target device shall not return any additional information to that requested by the server. If this IE indicates ‘mayReturnAdditionalInformation’ then the target device may return additional information to that requested by the server. If a location estimate is returned, any additional information is restricted to that associated with a location estimate (e.g. might include velocity if velocity was not requested but cannot include measurements). If measurements are returned, any additional information is restricted to additional measurements (e.g. might include E-CID measurements if A-GNSS measurements were requested but not E-CID measurements).

qos

This IE indicates the quality of service and comprises a number of sub-fields. In the case of measurements, some of the sub-fields apply to the location estimate that could be obtained by the server from the measurements provided by the target device assuming that the measurements are the only sources of error. Fields are as follows:

– horizontalAccuracy indicates the maximum horizontal error in the location estimate at an indicated confidence level. The ‘accuracy‘ corresponds to the encoded uncertainty as defined in TS 23.032 [15] and ‘confidence‘ corresponds to confidence as defined in TS 23.032 [15].

– verticalCoordinateRequest indicates whether a vertical coordinate is required (TRUE) or not (FALSE)

– verticalAccuracy indicates the maximum vertical error in the location estimate at an indicated confidence level and is only applicable when a vertical coordinate is requested. The ‘accuracy‘ corresponds to the encoded uncertainty altitude as defined in TS 23.032 [15] and ‘confidence‘ corresponds to confidence as defined in TS 23.032 [15].

– responseTime

– time indicates the maximum response time as measured between receipt of the RequestLocationInformation and transmission of a ProvideLocationInformation. If the unit field is absent, this is given as an integer number of seconds between 1 and 128. If the unit field is present with enumerated value ‘ten-seconds‘, the maximum response time is given in units of 10-seconds, between 10 and 1280 seconds. If the unit field is present with enumerated value ‘ten-milli-seconds‘, the maximum response time is given in units of 10-milli-seconds, between 0.01 and 1.28 seconds. If the periodicalReporting IE is included in CommonIEsRequestLocationInformation, this field should not be included by the location server and shall be ignored by the target device (if included).

– responseTimeEarlyFix indicates the maximum response time as measured between receipt of the RequestLocationInformation and transmission of a ProvideLocationInformation containing early location measurements or an early location estimate. If the unit field is absent, this is given as an integer number of seconds between 1 and 128. If the unit field is present with enumerated value ‘ten-seconds‘, the maximum response time is given in units of 10-seconds, between 10 and 1280 seconds. If the unit field is present with enumerated value ‘ten-milli-seconds‘, the maximum response time is given in units of 10-milli-seconds, between 0.01 and 1.28 seconds. When this IE is included, a target should send a ProvideLocationInformation (or more than one ProvideLocationInformation if location information will not fit into a single message) containing early location information according to the responseTimeEarlyFix IE and a subsequent ProvideLocationInformation (or more than one ProvideLocationInformation if location information will not fit into a single message) containing final location information according to the time IE. A target shall omit sending a ProvideLocationInformation if the early location information is not available at the expiration of the time value in the responseTimeEarlyFix IE. A server should set the responseTimeEarlyFix IE to a value less than that for the time IE. A target shall ignore the responseTimeEarlyFix IE if its value is not less than that for the time IE.

– unit indicates the unit of the time and responseTimeEarlyFix fields. Enumerated value ‘ten-seconds‘ corresponds to a resolution of 10 seconds. Enumerated value ‘ten-milli-seconds‘ corresponds to a resolution of 0.01 seconds. If this field is absent, the unit/resolution is 1 second. Enumerated value ‘ten-milli-seconds‘ is only applicable for NR E-CID Positioning, NR DL-TDOA Positioning, NR DL-AoD Positioning, and NR Multi-RTT Positioning. If the enumerated value ‘ten-milli-seconds‘ is included for methods others than NR E-CID Positioning, NR DL-TDOA Positioning, NR DL-AoD Positioning, and NR Multi-RTT Positioning the target device shall ignore the unit field.

– velocityRequest indicates whether velocity (or measurements related to velocity) is requested (TRUE) or not (FALSE).

– responseTimeNB
If the periodicalReporting IE or responseTime IE is included in CommonIEsRequestLocationInformation, this field should not be included by the location server and shall be ignored by the target device (if included).

– timeNB indicates the maximum response time as measured between receipt of the RequestLocationInformation and transmission of a ProvideLocationInformation. If the unitNB field is absent, this is given as an integer number of seconds between 1 and 512. If the unitNB field is present, the maximum response time is given in units of 10-seconds, between 10 and 5120 seconds.

– responseTimeEarlyFixNB indicates the maximum response time as measured between receipt of the RequestLocationInformation and transmission of a ProvideLocationInformation containing early location measurements or an early location estimate. If the unitNB field is absent, this is given as an integer number of seconds between 1 and 512. If the unitNB field is present, the maximum response time is given in units of 10-seconds, between 10 and 5120 seconds. When this IE is included, a target should send a ProvideLocationInformation (or more than one ProvideLocationInformation if location information will not fit into a single message) containing early location information according to the responseTimeEarlyFixNB IE and a subsequent ProvideLocationInformation (or more than one ProvideLocationInformation if location information will not fit into a single message) containing final location information according to the timeNB IE. A target shall omit sending a ProvideLocationInformation if the early location information is not available at the expiration of the time value in the responseTimeEarlyFixNB IE. A server should set the responseTimeEarlyFixNB IE to a value less than that for the timeNB IE. A target shall ignore the responseTimeEarlyFixNB IE if its value is not less than that for the timeNB IE.

– unitNB indicates the unit of the timeNB and responseTimeEarlyFixNB fields. Enumerated value ‘ten-second‘ corresponds to a resolution of 10 seconds. If this field is absent, the unit/resolution is 1 second.

– horizontalAccuracyExt indicates the maximum horizontal error in the location estimate at an indicated confidence level. The ‘accuracyExt‘ corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [15] and ‘confidence’ corresponds to confidence as defined in TS 23.032 [15]. This field should not be included by the location server and shall be ignored by the target device if the horizontalAccuracy field is included in QoS.

– verticalAccuracyExt indicates the maximum vertical error in the location estimate at an indicated confidence level and is only applicable when a vertical coordinate is requested. The ‘accuracyExt‘ corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [15] and ‘confidence‘ corresponds to confidence as defined in TS 23.032 [15]. This field should not be included by the location server and shall be ignored by the target device if the verticalAccuracy field is included in QoS.

All QoS requirements shall be obtained by the target device to the degree possible but it is permitted to return a response that does not fulfill all QoS requirements if some were not attainable. The single exception is time and timeNB which shall always be fulfilled – even if that means not fulfilling other QoS requirements.

A target device supporting NB-IoT access shall support the responseTimeNB IE.

A target device supporting HA GNSS shall support the HorizontalAccuracyExt, VerticalAccuracyEx, and unit fields with enumerated value ‘ten-seconds‘.

A target device supporting NB-IoT access and HA GNSS shall support the unitNB field.

environment

This field provides the target device with information about expected multipath and non line of sight (NLOS) in the current area. The following values are defined:

– badArea: possibly heavy multipath and NLOS conditions (e.g. bad urban or urban).

– notBadArea: no or light multipath and usually LOS conditions (e.g. suburban or rural).

– mixedArea: environment that is mixed or not defined.

If this field is absent, a default value of ‘mixedArea’ applies.

locationCoordinateTypes

This field provides a list of the types of location estimate that the target device may return when a location estimate is obtained by the target.

velocityTypes

This fields provides a list of the types of velocity estimate that the target device may return when a velocity estimate is obtained by the target.

messageSizeLimitNB

This field provides an octet limit on the amount of location information a target device can return.

– measurementLimit indicates the maximum amount of location information the target device should return in response to the RequestLocationInformation message received from the location server.
The limit applies to the overall size of the LPP message at LPP level (LPP Provide Location Information), and is specified in steps of 100 octets. The message size limit is then given by the value provided in measurementLimit times 100 octets.

segmentationInfo

This field indicates whether this RequestLocationInformation message is one of many segments, as specified in clause 4.3.5

scheduledLocationTime

This field indicates that the target device is requested to obtain location measurements or location estimate valid at the scheduledLocationTime T and comprises the following subfields:

– utcTime provides T in UTC in the form of YYMMDDhhmmssZ.

– gnssTime provides T in GNSS system time of the GNSS indicated by gnss-TimeID.

– gnss-TOD-msec specifies the GNSS TOD in 1-milli-second resolution rounded down to the nearest millisecond unit.

– networkTime provides T in E-UTRA or NR network time.

– lte-PhysCellId, lte-ArfcnEUTRA, lte-CellGlobalId identifies the reference cell (E-UTRA) that is used for the network time.

– lte-systemFrameNumber specifies the system frame number in E-UTRA.

– nr-PhysCellID, nr-ARFCN , nr-CellGlobalID identifies the reference cell (NR) that is used for the network time.

– nr-SFN specifies the system frame number in NR.

– nr-Slot specifies the slot number in NR for the indicated subcarrier spacing (SCS). The total NR network time is given by nr-SFN + nr-Slot.

– relativeTime provides T in seconds from current time, where current time is defined as the time the CommonIEsRequestLocationInformation was received.

NOTE 1: A location estimate returned to an LCS Client, AF or UE for a scheduled location time can be treated by the LCS Client, AF or UE as an estimate of the location of the UE at the scheduled location time (see TS 23.273 [42]).

NOTE 2: If this field is present, at least one of utcTime, gnssTime, networkTime, or relativeTime shall be present.

targetIntegrityRisk

This field indicates the TIR for which the PL is requested. The TIR is calculated by P=10^-0.1n [hour^-1] where n is the value of targetIntegrityRisk and the range is 10^-1 to 10^-9 per hour.

Segmentation

This field is optionally present, need OP, if lpp-message-segmentation-req has been received from the location server with bit 1 (targetToServer) set to value 1. The field shall be omitted if lpp‑message‑segmentation-req has not been received in this location session, or has been received with bit 1 (targetToServer) set to value 0.

locationEstimate

This field provides a location estimate using one of the geographic shapes defined in TS 23.032 [15]. Coding of the values of the various fields internal to each geographic shape follow the rules in TS 23.032 [15]. The conditions for including this field are defined for the locationInformationType field in a Request Location Information message.

velocityEstimate

This field provides a velocity estimate using one of the velocity shapes defined in TS 23.032 [15]. Coding of the values of the various fields internal to each velocity shape follow the rules in TS 23.032 [15].

locationError

This field shall be included if and only if a location estimate and measurements are not included in the LPP PDU. The field includes information concerning the reason for the lack of location information. The LocationFailureCause ‘periodicLocationMeasurementsNotAvailable‘ shall be used by the target device if periodic location reporting was requested, but no measurements or location estimate are available when the reportingInterval expired.

earlyFixReport

This field shall be included if and only if the ProvideLocationInformation message contains early location measurements or an early location estimate. The target device shall set the values of this field as follows:

– noMoreMessages: This is the only or last ProvideLocationInformation message used to deliver the entire set of early location information.

– moreMessagesOnTheWay: This is one of multiple ProvideLocationInformation messages used to deliver the entire set of early location information (if early location information will not fit into a single message).

If this field is included, the IE SegmentationInfo shall not be included.

locationSource

This field provides the source positioning technology for the location estimate.

NOTE 1: In this version of the specification, the entry ‘tbs’ is used only for TBS positioning based on MBS signals.

NOTE 2: The entry ‘sensor’ is used only for positioning technology that uses barometric pressure sensor. The entry ‘motion-sensor’ is used for positioning technology that uses sensor(s) to detect displacement and movement, e.g. accelerometers, gyros, magnetometers.

locationTimestamp

This field provides the UTC time when the location estimate is valid and should take the form of YYMMDDhhmmssZ.

segmentationInfo

This field indicates whether this ProvideLocationInformation message is one of many segments, as specified in clause 4.3.5

integrityInfo

This field provides the integrity result for the locationEstimate.

– horizontalProtectionLevel provides the HPL for the locationEstimate along the semi-major axis of the error ellipse. Scale factor 0.01 metre; range 0 – 500 metres.

– verticalProtectionLevel provides the VPL for the locationEstimate. Scale factor 0.01 metre; range 0 – 500 metres.

– achievableTargetIntegrityRisk indicates the achievable TIR for which the HPL and VPL are provided. The achievable TIR is given by P=10^-0.1n [hour^-1] where n is the value of achievableTargetIntegrityRisk and the range is 10^-1 to 10^-9 per hour. If this field is absent, the achievable TIR is the same as the targetIntegrityRisk in CommonIEsRequestLocationInformation.

AzElFine

The field is mandatory present if the angles where this IE is used are provided with 0.1 degrees resolution; otherwise it is not present.

alpha

This field specifies the bearing angle α for the translation of the LCS to a GCS as defined in TR 38.901 [44].

Scale factor 1 degree; range 0 to 359 degrees.

alpha-fine

This field provides finer granularity for the alpha.

The total bearing angle α is given by alpha + alpha-fine.

Scale factor 0.1 degrees; range 0 to 0.9 degrees.

beta

This field specifies the downtilt angle β for the translation of the LCS to a GCS as defined in TR 38.901 [44].

Scale factor 1 degree; range 0 to 359 degrees.

beta-fine

This field provides finer granularity for the beta.

The total downtilt angle β is given by beta + beta-fine.

Scale factor 0.1 degrees; range 0 to 0.9 degrees.

gamma

This field specifies the slant angle γ for the translation of the LCS to a GCS as defined in TR 38.901 [44].

Scale factor 1 degree; range 0 to 359 degrees.

gamma-fine

This field provides finer granularity for the gamma.

The total slant angle γ is given by gamma + gamma-fine.

Scale factor 0.1 degrees; range 0 to 0.9 degrees.

nr-RelativeTimeDifference

This field specifies the additional detected path timing relative to the detected path timing of the reference resource. The mapping of reported values and measured quantity value is defined in TS 38.133 [46] clause 10.1.23.3.3 and 10.1.25.3.3. A positive value indicates that the particular path is later in time than the detected path of the reference; a negative value indicates that the particular path is earlier in time than the detected path of the reference.

nr-PathQuality

This field specifies the target device′s best estimate of the quality of the detected timing of the additional path.

nr-DL-PRS-RSRPP

This field specifies the DL PRS reference signal received path power (DL PRS-RSRPP) of the NR-AdditionalPath reported, as defined in TS 38.215 [36]. The mapping of the quantity is defined as in TS 38.133 [46].

nr-DL-PRS-ReferenceInfo

This field specifies the IDs of the assistance data reference TRP.

nr-DL-PRS-AssistanceDataList

This field specifies the DL-PRS resources for each frequency layer.

nr-SSB-Config

This field specifies the SSB configuration of the TRPs.

nr-DL-PRS-PositioningFrequencyLayer

This field specifies the Positioning Frequency Layer for the nr-DL-PRS-AssistanceDataPerFreq field.

nr-DL-PRS-AssistanceDataPerFreq

This field specifies the DL-PRS Resources for the TRPs within the Positioning Frequency Layer.

dl-PRS-ID

This field is used along with a DL-PRS Resource Set ID and a DL-PRS Resource ID to uniquely identify a DL-PRS Resource, and is associated with a single TRP.

nr-PhysCellID

This field specifies the physical cell identity of the TRP. When the field prs-OnlyTP is included, this field is not included.

nr-CellGlobalID

This field specifies the NCGI, the globally unique identity of a cell in NR, as defined in TS 38.331 [35]. When the field prs-OnlyTP is included, this field is not included.

nr-ARFCN

This field specifies the NR-ARFCN of the TRP’s CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID. When the field prs-OnlyTP is included, this field is not included.

nr-DL-PRS-SFN0-Offset

This field specifies the time offset of the SFN#0 slot#0 for the given TRP with respect to SFN#0 slot#0 of the assistance data reference TRP and comprises the following subfields:

– sfn-Offset specifies the SFN offset at the TRP antenna location between the assistance data reference TRP and this neighbour TRP.

The offset corresponds to the number of full radio frames counted from the beginning of a radio frame #0 of the assistance data reference TRP to the beginning of the closest subsequent radio frame #0 of this neighbour TRP.

– integerSubframeOffset specifies the frame boundary offset at the TRP antenna location between the assistance data reference TRP and this neighbour TRP counted in full subframes.

The offset is counted from the beginning of a subframe #0 of the assistance data reference TRP to the beginning of the closest subsequent subframe #0 of this neighbour TRP, rounded down to multiples of subframes.

nr-DL-PRS-ExpectedRSTD

This field indicates the RSTD value that the target device is expected to measure between this TRP and the assistance data reference TRP. The nr-DL-PRS-ExpectedRSTD field takes into account the expected propagation time difference as well as transmit time difference of PRS positioning occasions between the two TRPs. The resolution is 4×T_s, with T_s=1/(15000*2048) seconds.

nr-DL-PRS-ExpectedRSTD-Uncertainty

This field indicates the uncertainty in nr-DL-PRS-ExpectedRSTD value. The uncertainty is related to the location server′s a‑priori estimate of the target device location. The nr-DL-PRS-ExpectedRSTD and nr-DL-PRS-ExpectedRSTD-Uncertainty together define the search window for the target device.

The resolution R is

– T_s if all PRS resources are in frequency range 2,

– 4×T_s otherwise,

with T_s=1/(15000*2048) seconds.

The target device may assume that the beginning of the subframe for the PRS of this TRP is received within the search window of size

– [-nr-DL-PRS-ExpectedRSTD-Uncertainty×R ; nr-DL-PRS-ExpectedRSTD-Uncertainty×R] centred at T_REF+1 millisecond×N+nr-DL-PRS-ExpectedRSTD×4×T_s,

where T_REF is the reception time of the beginning of the subframe for the PRS of the assistance data reference TRP at the target device antenna connector, and N can be calculated based on

– nr-DL-PRS-SFN0-Offset

– dl-PRS-Periodicity-and-ResourceSetSlotOffset

– dl-PRS-ResourceSlotOffset.

nr-DL-PRS-Info

This field specifies the PRS configuration of the TRP.

dl-PRS-SubcarrierSpacing

This field specifies the subcarrier spacing of the DL-PRS Resource. 15, 30, 60 kHz for FR1; 60, 120 kHz for FR2. All DL-PRS Resources and DL-PRS Resource Sets in the same Positioning Frequency layer have the same value of dl-PRS-SubcarrierSpacing.

dl-PRS-ResourceBandwidth

This field specifies the number of PRBs allocated for the DL-PRS Resource (allocated DL-PRS bandwidth) in multiples of 4 PRBs. All DL-PRS Resources of the DL-PRS Resource Set have the same bandwidth. All DL-PRS Resource Sets belonging to the same Positioning Frequency Layer have the same value of DL-PRS Bandwidth and Start PRB.

Integer value 1 corresponds to 24 PRBs, value 2 corresponds to 28 PRBs, value 3 corresponds to 32 PRBs and so on.

dl-PRS-StartPRB

This field specifies the start PRB index defined as offset with respect to reference DL-PRS Point A for the Positioning Frequency Layer. All DL-PRS Resources Sets belonging to the same Positioning Frequency Layer have the same value of dl-PRS-StartPRB.

dl-PRS-PointA

This field specifies the absolute frequency of the reference resource block for the DL-PRS. Its lowest subcarrier is also known as DL-PRS Point A. A single DL-PRS Point A for DL-PRS Resource allocation is provided per Positioning Frequency Layer. All DL-PRS Resources belonging to the same DL-PRS Resource Set have the same DL-PRS Point A.

dl-PRS-CombSizeN

This field specifies the Resource Element spacing in each symbol of the DL-PRS Resource. All DL-PRS Resource Sets belonging to the same Positioning Frequency Layer have the same value of comb size N.

dl-PRS-CyclicPrefix

This field specifies the Cyclic Prefix length of the DL-PRS Resource. All DL-PRS Resources Sets belonging to the same Positioning Frequency Layer have the same value of dl-PRS-CyclicPrefix.

prs-OnlyTP

This field, if present, indicates that the NR-DL-PRS-AssistanceData is provided for a PRS-only TP. Whether the field is present or absent should be the same for all the NR-DL-PRS-AssistanceData of all the PRS transmitted under the same TP.

The target device shall not assume that any other signals or physical channels are present for the TRP other than DL-PRS.

nr-DL-PRS-ExpectedAoD-or-AoA

This field specifies the expected AoD or AoA in the Global Coordinate System (GCS) at the target device location together with uncertainty.

– expectedDL-AzimuthAoD: This field specifies the expected azimuth angle of departure.
Scale factor 1 degree; range 0 to 359 degrees.

– expectedDL-AzimuthAoD-Unc: This field specifies the (single-sided) uncertainty of the expected azimuth angle of departure. If this field is absent, it indicates maximum uncertainty (60 degrees).
Scale factor 1 degree; range 0 to 60 degrees.

– expectedDL-ZenithAoD: This field specifies the expected elevation angle of departure.
Scale factor 1 degree; range 0 to 180 degrees.

– expectedDL-ZenithAoD-Unc: This field specifies the (single-sided) uncertainty of the expected elevation angle of departure. If this field is absent, it indicates maximum uncertainty (30 degrees).
Scale factor 1 degree; range 0 to 30 degrees.

– expectedDL-AzimuthAoA: This field specifies the expected azimuth angle of arrival.
Scale factor 1 degree; range 0 to 359 degrees.

– expectedDL-AzimuthAoA-Unc: This field specifies the (single-sided) uncertainty of the expected azimuth angle of arrival. If this field is absent, it indicates maximum uncertainty (60 degrees).
Scale factor 1 degree; range 0 to 60 degrees.

– expectedDL-ZenithAoA: This field specifies the expected elevation angle of arrival.
Scale factor 1 degree; range 0 to 180 degrees.

– expectedDL-ZenithAoA-Unc: This field specifies the (single-sided) uncertainty of the expected elevation angle of arrival. If this field is absent, it indicates maximum uncertainty (30 degrees).
Scale factor 1 degree; range 0 to 30 degrees.

dl-PRS-ID

This field specifies the DL-PRS ID of the TRP for which the LOS/NLOS Information is provided.

nr-PhysCellID

This field specifies the physical Cell-ID of the TRP for which the LOS/NLOS Information is provided, as defined in TS 38.331 [35].

nr-CellGlobalID

This field specifies the NCGI, the globally unique identity of a cell in NR, of the TRP for which the LOS/NLOS Information is provided, as defined in TS 38.331 [35].

nr-ARFCN

This field specifies the NR-ARFCN of the TRP’s CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID.

nr-los-nlos-indicator

This field provides the expected likelihood of a LOS propagation path from a TRP to the target device (choice perTrp) or for all DL-PRS Resources of the TRP (choice perResource).

Rep

The field is mandatory present, if dl-PRS-ResourceRepetitionFactor is present. Otherwise it is not present.

NotSame

The field is optionally present, need OP. If the field is absent, the indicated nr-DL-PRS-PrioResourceID belongs to the same DL-PRS Resource Set as the nr-DL-PRS-ResourceID.

nr-DL-PRS-ResourceSetID

This field specifies the DL-PRS Resource Set ID, which is used to identify the DL-PRS Resource Set of the TRP across all the frequency layers.

dl-PRS-Periodicity-and-ResourceSetSlotOffset

This field specifies the periodicity of DL-PRS allocation in slots configured per DL-PRS Resource Set and the slot offset with respect to SFN #0 slot #0 for a TRP where the DL-PRS Resource Set is configured (i.e. slot where the first DL-PRS Resource of DL-PRS Resource Set occurs).

dl-PRS-ResourceRepetitionFactor

This field specifies how many times each DL-PRS Resource is repeated for a single instance of the DL-PRS Resource Set. It is applied to all resources of the DL-PRS Resource Set. Enumerated values n2, n4, n6, n8, n16, n32 correspond to 2, 4, 6, 8, 16, 32 resource repetitions, respectively. If this field is absent, the value for dl-PRS-ResourceRepetitionFactor is 1 (i.e., no resource repetition).

dl-PRS-ResourceTimeGap

This field specifies the offset in units of slots between two repeated instances of a DL-PRS Resource corresponding to the same DL-PRS Resource ID within a single instance of the DL-PRS Resource Set. The time duration spanned by one DL-PRS Resource Set containing repeated DL-PRS Resources should not exceed DL-PRS-Periodicity.

dl-PRS-NumSymbols

This field specifies the number of symbols per DL-PRS Resource within a slot.

dl-PRS-MutingOption1

This field specifies the DL-PRS muting configuration of the TRP for the Option-1 muting, as specified in TS 38.214 [45], and comprises the following sub-fields:

– dl-prs-MutingBitRepetitionFactor indicates the number of consecutive instances of the DL-PRS Resource Set corresponding to a single bit of the nr-option1-muting bit map. Enumerated values n1, n2, n4, n8 correspond to 1, 2, 4, 8 consecutive instances, respectively. If this sub-field is absent, the value for dl-prs-MutingBitRepetitionFactor is n1.

– nr-option1-muting defines a bitmap of the time locations where the DL-PRS Resource is transmitted (value ‘1’) or not (value ‘0’) for a DL-PRS Resource Set, as specified in TS 38.214 [45].

If this field is absent, Option-1 muting is not in use for the TRP.

dl-PRS-MutingOption2

This field specifies the DL-PRS muting configuration of the TRP for the Option-2 muting, as specified in TS 38.214 [45], and comprises the following sub-fields:

– nr-option2-muting defines a bitmap of the time locations where the DL-PRS Resource is transmitted (value ‘1’) or not (value ‘0’). Each bit of the bitmap corresponds to a single repetition of the DL-PRS Resource within an instance of a DL-PRS Resource Set, as specified in TS 38.214 [45]. The size of this bitmap should be the same as the value for dl-PRS-ResourceRepetitionFactor.

If this field is absent, Option-2 muting is not in use for the TRP.

dl-PRS-ResourcePower

This field specifies the average EPRE of the resources elements that carry the PRS in dBm that is used for PRS transmission. The UE assumes constant EPRE is used for all REs of a given DL-PRS resource.

dl-PRS-SequenceID

This field specifies the sequence Id used to initialize c_init value used in pseudo random generator TS 38.211 [41], clause 5.2.1 for generation of DL-PRS sequence for transmission on a given DL-PRS Resource.

dl-PRS-CombSizeN-AndReOffset

This field specifies the Resource Element spacing in each symbol of the DL-PRS Resource and the Resource Element (RE) offset in the frequency domain for the first symbol in a DL-PRS Resource. All DL-PRS Resource Sets belonging to the same Positioning Frequency Layer have the same value of comb size. The relative RE offsets of following symbols are defined relative to the RE Offset in the frequency domain of the first symbol in the DL-PRS Resource according to TS 38.211 [41]. The comb size configuration should be aligned with the comb size configuration for the frequency layer.

dl-PRS-ResourceSlotOffset

This field specifies the starting slot of the DL-PRS Resource with respect to the corresponding DL-PRS-Resource Set Slot Offset.

dl-PRS-ResourceSymbolOffset

This field specifies the starting symbol of the DL-PRS Resource within a slot determined by dl-PRS-ResourceSlotOffset.

dl-PRS-QCL-Info

This field specifies the QCL indication with other DL reference signals for serving and neighbouring cells and comprises the following subfields:

– ssb indicates the SSB information for QCL source and comprises the following sub-fields:

– pci specifies the physical cell ID of the cell with the SSB that is configured as the source reference signal for the DL-PRS. The UE obtains the SSB configuration for the SSB configured as source reference signal for the DL-PRS by indexing to the field nr-SSB-Config with this physical cell identity.

– ssb-Index indicates the index for the SSB configured as the source reference signal for the DL-PRS.

– rs-Type indicates the QCL type.

– dl-PRS indicates the PRS information for QCL source reference signal and comprises the followings sub-fields:

– qcl-DL-PRS-ResourceID specifies DL-PRS Resource ID of the DL-PRS resource used as the source reference signal.

– qcl-DL-PRS-ResourceSetID indicates the DL-PRS Resource Set ID of the DL-PRS Resource Set used as the source reference signal.

dl-PRS-ResourcePrioritySubset

This field provides a subset of DL-PRS Resources, which is associated with nr-DL-PRS-ResourceID for the purpose of prioritization of DL-AoD reporting, as specified in TS 38.214 [45].

NOTE: This field is only applicable to DL-AoD positioning method and should be ignored for DL-TDOA and Multi-RTT positioning.

maxSupportedFreqLayers

Indicates the maximum number of positioning frequency layers supported by UE.

simulLTE-NR-PRS

Indicates whether the UE supports parallel processing of LTE PRS and NR PRS.

dummy

This field is not used in the specification. If received it shall be ignored by the receiver.

supportedBandwidthPRS

Indicates the maximum number of DL-PRS bandwidth in MHz, which is supported and reported by UE.

dl-PRS-BufferType

Indicates DL-PRS buffering capability. Value type1 indicates sub-slot/symbol level buffering and value type2 indicates slot level buffering.

durationOfPRS-Processing

Indicates the duration N of DL-PRS symbols in units of ms a UE can process every T ms assuming maximum DL-PRS bandwidth provided in supportedBandwidthPRS and comprises the following subfields:

– durationOfPRS-ProcessingSymbols: This field specifies the values for N. Enumerated values indicate 0.125, 0.25, 0.5, 1, 2, 4, 8, 12, 16, 20, 25, 30, 35, 40, 45, 50 ms.

– durationOfPRS-ProcessingSymbolsInEveryTms: This field specifies the values for T. Enumerated values indicate 8, 16, 20, 30, 40, 80, 160, 320, 640, 1280 ms.

See NOTE.

maxNumOfDL-PRS-ResProcessedPerSlot

Indicates the maximum number of DL-PRS resources that UE can process in a slot. SCS: 15 kHz, 30 kHz, 60 kHz are applicable for FR1 bands. SCS: 60 kHz, 120 kHz are applicable for FR2 bands.

supportedDL-PRS-ProcessingSamples-RRC-CONNECTED

Indicates the UE capability for support of measurements based on measuring M=1 or M=2 (instances) of a DL-PRS Resource Set. The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList. Otherwise, the UE does not include this field.

NOTE: This feature is supported for both UE-assisted and UE based positioning.

prs-ProcessingWindowType1A

Indicates the supported DL-PRS processing types subject to the UE determining that DL-PRS to be higher priority for DL-PRS measurement outside MG and in a DL-PRS Processing Window.

Type 1A refers to the determination of prioritization between DL-PRS and other DL signals/channels in all OFDM symbols within the PRS Processing Window. The DL signals/channels from all DL CCs (per UE) are affected across LTE and NR. Enumerated value indicates supported priority handing options of DL-PRS:

– option1: UE indicates support of two priority states.

– State 1: DL-PRS is higher priority than all PDCCH/PDSCH/CSI-RS

– State 2: DL-PRS is lower priority than all PDCCH/PDSCH/CSI-RS

– option2: UE indicates support of three priority states

– State 1: DL-PRS is higher priority than all PDCCH/PDSCH/CSI-RS

– State 2: DL-PRS is lower priority than PDCCH and URLLC PDSCH and higher priority than other PDSCH/CSI-RS

Note: The URLLC channel corresponds a dynamically scheduled PDSCH whose PUCCH resource for carrying ACK/NAK is marked as high-priority.

– State 3: DL-PRS is lower priority than all PDCCH/PDSCH/CSI-RS

– option3: UE indicates support of single priority state

– State 1: DL-PRS is higher priority than all PDCCH/PDSCH/CSI-RS

The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList. Otherwise, the UE does not include this field.

NOTE: Within a PRS processing window, UE measurement is inside the active DL BWP with PRS having the same numerology as the active DL BWP.

prs-ProcessingWindowType1B

Indicates the supported DL-PRS processing types subject to the UE determining that DL-PRS to be higher priority for DL-PRS measurement outside MG and in a DL-PRS Processing Window.

Type 1B refers to the determination of prioritization between DL-PRS and other DL signals/channels in all OFDM symbols within the PRS processing window. The DL signals/channels from a certain band are affected. Enumerated value indicates supported priority handing options of DL-PRS (see prs-ProcessingWindowType1A).

The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList. Otherwise, the UE does not include this field.

NOTE: Within a PRS processing window, UE measurement is inside the active DL BWP with PRS having the same numerology as the active DL BWP.

prs-ProcessingWindowType2

Indicates the supported DL-PRS processing types subject to the UE determining that DL-PRS to be higher priority for DL-PRS measurement outside MG and in a DL-PRS Processing Window.

Type 2 refers to the determination of prioritization between DL-PRS and other DL signals/channels only in DL-PRS symbols within the PRS processing window. Enumerated value indicates supported priority handing options of DL-PRS (see prs-ProcessingWindowType1A).

The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList. Otherwise, the UE does not include this field.

NOTE: Within a PRS processing window, UE measurement is inside the active DL BWP with PRS having the same numerology as the active DL BWP.

prs-ProcessingCapabilityOutsideMGinPPW

Indicates the DL-PRS Processing Capability outside MG and comprises the following subfields:

– prsProcessingType: Indicates the DL-PRS Processing Window Type for which the prs-ProcessingCapabilityOutsideMGinPPW are provided.

– ppw-dl-PRS-BufferType: Indicates DL-PRS buffering capability. Value ‘type1′ indicates sub-slot/symbol level buffering and value ‘type2′ indicates slot level buffering.

– ppw-durationOfPRS-Processing1: Indicates the duration of DL-PRS symbols N in units of ms a UE can process every T ms assuming maximum DL-PRS bandwidth provided in ppw-maxNumOfDL-Bandwidth and comprises the following subfields:

– ppw-durationOfPRS-ProcessingSymbolsN: This field specifies the values for N. Enumerated values indicate 0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50 ms.

– ppw-durationOfPRS-ProcessingSymbolsT: This field specifies the values for T. Enumerated values indicate 1, 2, 4, 8, 16, 20, 30, 40, 80, 160, 320, 640, 1280 ms.

– ppw-durationOfPRS-Processing2: Indicates the duration of DL-PRS symbols N2 in units of ms a UE can process inT2 ms assuming maximum DL-PRS bandwidth provided in ppw-maxNumOfDL-Bandwidth and comprises the following subfields:

– ppw-durationOfPRS-ProcessingSymbolsN2: This field specifies the values for N2. Enumerated values indicate 0.125, 0.25, 0.5, 1, 2, 3, 4, 5, 6, 8, 12 ms.

– ppw-durationOfPRS-ProcessingSymbolsT2: This field specifies the values for T2. Enumerated values indicate 4, 5, 6, 8 ms.

– ppw-maxNumOfDL-PRS-ResProcessedPerSlot: Indicates the maximum number of DL-PRS resources that UE can process in a slot. SCS: 15 kHz, 30 kHz, 60 kHz are applicable for FR1 bands. SCS: 60 kHz, 120 kHz are applicable for FR2 bands.

– ppw-maxNumOfDL-Bandwidth: Indicates the maximum number of DL PRS bandwidth in MHz, which is supported and reported by UE for PRS measurement outside MG within the PPW.

The UE can include this field only if the UE supports one of prs-ProcessingWindowType1A, prs-ProcessingWindowType1B and prs-ProcessingWindowType2. Otherwise, the UE does not include this field.

NOTE: A UE that supports one of prs-ProcessingWindowType1, prs-ProcessingWindowType1B or prs-ProcessingWindowType2 defined in TS 38.331 [35] shall always support ppw-dl-PRS-BufferType, ppw-durationOfPRS-Processing1, ppw-durationOfPRS-Processing2, ppw-maxNumOfDL-PRS-ResProcessedPerSlot, and ppw-maxNumOfDL-BandwidthFR1 or ppw-maxNumOfDL-BandwidthFR2.

dl-PRS-BufferType-RRC-Inactive

Indicates DL-PRS buffering capability in RRC_INACTIVE state. Value ‘type1′ indicates sub-slot/symbol level buffering and value ‘type2′ indicates slot level buffering.

durationOfPRS-Processing-RRC-Inactive

Indicates the duration N of DL-PRS symbols in units of ms a UE can process every T ms in RRC_INACTIVE state assuming maximum DL-PRS bandwidth provided in supportedBandwidthPRS and comprises the following subfields:

– durationOfPRS-ProcessingSymbols: This field specifies the values for N. Enumerated values indicate 0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50 ms.

– durationOfPRS-ProcessingSymbolsInEveryTms: This field specifies the values for T. Enumerated values indicate 8, 16, 20, 30, 40, 80, 160, 320, 640, 1280 ms.

See NOTE.

maxNumOfDL-PRS-ResProcessedPerSlot-RRC-Inactive

Indicates the maximum number of DL-PRS resources a UE can process in a slot in RRC_INACTIVE state. SCS: 15 kHz, 30 kHz, 60 kHz are applicable for FR1 bands. SCS: 60 kHz, 120 kHz are applicable for FR2 bands.

supportedLowerRxBeamSweepingFactor-FR2

Indicates support of the lower Rx beam sweeping factor than 8 for FR2. Enumerated value indicates the number of Rx beam sweeping factors supported.

supportedDL-PRS-ProcessingSamples-RRC-Inactive

Indicates the UE capability for support of measurements based on measuring M=1 or M=2 samples (instances) of a DL-PRS Resource Set in RRC_INACTIVE state. The UE can include this field only if the UE supports prs-ProcessingRRC-Inactive defined in TS 38.331 [35]. Otherwise, the UE does not include this field.

ssb-FromNeighCellAsQCL

Indicates the support of SSB from neighbour cell as QCL source of a DL-PRS. UE supporting this feature also support reusing SSB measurement from RRM for receiving PRS.

Note: It refers to Type-C for FR1 and Type-C & Type-D support for FR2.

prs-FromServNeighCellAsQCL

Indicates the support of DL-PRS from serving/neighbour cell as QCL source of a DL-PRS.

Note 1: It refers to Type-D support for FR2.

Note 2: A PRS from a PRS-only TP is treated as PRS from a non-serving cell.

maxNrOfPosLayer

Indicates the maximum number of supported positioning frequency layers.

dl-PRS-ResourcesBandCombinationList

Provides the capabilities of DL-PRS Resources for the indicated band combination in bandList. This field is provided for all band combinations for which the target device supports DL-PRS.

maxNrOfDL-PRS-ResourcesPerResourceSet

Indicates the maximum number of DL-PRS Resources per DL-PRS Resource Set. Value 16, 32, 64 are only applicable to FR2 bands. Value 1 is not applicable for DL-AoD.

maxNrOfDL-PRS-ResourcesPerPositioningFrequencylayer

Indicates the maximum number of DL-PRS resources per positioning frequency layer. Value 6 is only applicable to FR1 bands.

maxNrOfDL-PRS-ResourcesAcrossAllFL-TRP-ResourceSet

Indicates the maximum number of DL-PRS Resources supported by UE across all frequency layers, TRPs and DL-PRS Resource Sets.

fr1-Only: This is applicable for FR1 only band combinations;

fr2-Only: This is applicable for FR2 only band combinations;

fr1-FR2Mix: This is applicable for band combinations containing FR1 and FR2 bands. fr1 means for FR1 in FR1/FR2 mixed operation, and fr2 means for FR2 in FR1/FR2 mixed operation.

dl-PRS-ID

This field specifies the DL-PRS ID of the TRP for which the TRP Tx TEG information is provided.

nr-PhysCellID

This field specifies the physical Cell-ID of the TRP for which the TRP Tx TEG information is provided, as defined in TS 38.331 [35].

nr-CellGlobalID

This field specifies the NCGI, the globally unique identity of a cell in NR, of the TRP for which the TRP Tx TEG information is provided, as defined in TS 38.331 [35].

nr-ARFCN

This field specifies the NR-ARFCN of the TRP’s CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID.

dl-PRS-TEG-InfoSet

This field specifies the TRP Tx TEG ID associated with the transmissions of each DL-PRS Resource of the TRP. The dl-prs-trp-Tx-TEG-ID in dl-PRS-TEG-InfoSet is associated with the nr-DL-PRS-ResourceID of NR-DL-PRS-Info using the same structure and order.

nr-TRP-TxTEG-TimingErrorMargin

This field specifies the timing error margin value for all the TRP Tx TEGs contained within one NR-DL-PRS-TRP-TEG-InfoPerTRP.

dl-prs-configuration-id

This field provides an identity for the On-Demand-DL-PRS-Configuration.

nr-DL-PRS-PositioningFrequencyLayer

This field, together with nr-DL-PRS-Info, provides the On-demand DL-PRS Configuration information.

Only the following fields in IE NR-DL-PRS-PositioningFrequencyLayer are applicable:

dl-PRS-ResourceBandwidth, dl-PRS-CombSizeN.

The target device shall ignore the remaining fields in IE NR-DL-PRS-PositioningFrequencyLayer.

nr-DL-PRS-Info

This field, together with nr-DL-PRS-PositioningFrequencyLayer, provides the On-demand DL-PRS Configuration information. Only the following fields in IE NR-DL-PRS-Info are applicable:

DL-PRS periodicity in dl-PRS-Periodicity-and-ResourceSetSlotOffset, dl-PRS-ResourceRepetitionFactor, dl-PRS-NumSymbols, comb-size in dl-PRS-CombSizeN-AndReOffset, dl-PRS-QCL-Info.

The target device shall ignore the remaining fields in IE NR-DL-PRS-Info.

dl-prs-FrequencyRangeReq

This field specifies the frequency range for which the on-demand DL-PRS is requested.

dl-prs-ResourceSetPeriodicityReq

This field specifies the requested periodicity of the DL-PRS Resource Set in slots. The periodicity depends on the subcarrier spacing (SCS) and takes values

slots, where for SCS of 15, 30, 60 and 120 kHz respectively. μ refers to the target devices current primary cell.

dl-prs-ResourceBandwidthReq

This field specifies the requested number of PRBs allocated for the DL-PRS Resource (allocated DL-PRS bandwidth) in multiples of 4 PRBs. Integer value 1 corresponds to 24 PRBs, value 2 corresponds to 28 PRBs, value 3 corresponds to 32 PRBs and so on.

dl-prs-ResourceRepetitionFactorReq

This field specifies the requested DL-PRS Resource repetition. Enumerated values n2, n4, n6, n8, n16, n32 correspond to 2, 4, 6, 8, 16, 32 resource repetitions, respectively.

dl-prs-NumSymbolsReq

This field specifies the requested number of symbols per DL-PRS Resource within a slot.

dl-prs-CombSizeN-Req

This field specifies the requested Resource Element spacing in each symbol of the DL-PRS Resource.

dl-prs-QCL-InformationReqTRPlist

This field specifies the recommended or requested QCL indication with other DL reference signals.

– dl-PRS-ID indicates the DL-PRS ID of the TRP for which the QCL information is recommended.

– nr-PhysCellID indicates the physical Cell-ID of the TRP for which the QCL information is recommended, as defined in TS 38.331 [35].

– nr-CellGlobalID indicates the NCGI, the globally unique identity of a cell in NR, of the TRP for which the QCL information is recommended, as defined in TS 38.331 [35].

– nr-ARFCN indicates the NR-ARFCN of the TRP’s CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID.

– dl-prs-QCL-InformationReqSet indicates the recommended QCL information per DL-PRS Resource Set.

– nr-DL-PRS-ResourceSetID indicates the DL-PRS Resource Set ID for which the QCL information is recommended.

– dl-prs-QCL-InformationReq

– dl-prs-QCL-InfoRecPerResourceSet indicates a single recommended QCL source for the DL-PRS Resource Set.

– dl-prs-QCL-Info-requested indicates that the UE requests to provide the QCL information in the assistance data.

– dl-prs-QCL-InfoRecPerResource indicates a list of recommended QCL sources for the DL-PRS Resource Set. If this field is present, the dl-prs-QCL-InformationReg shall be ignored by the receiver.

dl-prs-StartTime-and-Duration

This field specifies the requested start time and duration for the on-demand DL-PRS and comprises the following subfields:

– dl-prs-start-time specifies the desired start time for the requested DL-PRS. It indicates the time in seconds from the time the IE NR-On-Demand-DL-PRS-Request was received.

– dl-prs-duration specifies the desired duration of the requested DL-PRS. The desired duration is the sum of the seconds, minutes, hours fields. If this field is included, at least one of the seconds, minutes, hours fields shall be present.

nr-on-demand-DL-PRS-Information

This field specifies the on-demand DL-PRS configuration information requested by the target device.

NOTE: If the network provided predefined on-demand DL-PRS configurations (NR-On-Demand-DL-PRS-Configurations), the target device can only request explicit parameters (nr-on-demand-DL-PRS-Information) within the scope of those configurations.

dl-prs-configuration-id-PrefList

This field specifies the on-demand DL-PRS configuration associated with DL-PRS-Configuration-ID in IE NR-On-Demand-DL-PRS-Configurations the target device wishes to obtain in the order of preference. The first DL-PRS-Configuration-ID in the list is the most preferred configuration, the second DL-PRS-Configuration-ID the second most preferred, etc.

nr-on-demand-DL-PRS-InformationSup

This field, if present, indicates that the target device supports the IE NR-On-Demand-DL-PRS-Information in IE NR-On-Demand-DL-PRS-Request.

nr-on-demand-DL-PRS-ConfigurationsSup

This field, if present, specifies that the target device supports the dl-prs-configuration-id-PrefList in IE NR-On-Demand-DL-PRS-Request.

nr-SelectedDL-PRS-FrequencyLayerIndex

This field indicates the frequency layer provided in IE NR-DL-PRS-AssistanceData. Value 0 corresponds to the first frequency layer provided in nr-DL-PRS-AssistanceDataList in IE NR-DL-PRS-AssistanceData, value 1 to the second frequency layer in nr-DL-PRS-AssistanceDataList, and so on.

nr-SelectedDL-PRS-IndexListPerFreq

This field provides the list of addressed TRPs of the selected frequency layer. If this field is absent, all DL-PRS Resources of all TRPs of the indicated frequency layer are addressed.

nr-SelectedTRP-Index

This field indicates the addressed TRP of the selected frequency layer. Value 0 corresponds to the first entry in nr-DL-PRS-AssistanceDataPerFreq provided in IE NR-DL-PRS-AssistanceData, value 1 corresponds to the second entry in nr-DL-PRS-AssistanceDataPerFreq, and so on.

dl-SelectedPRS-ResourceSetIndexList

This field provides the list of addressed DL-PRS Resource Sets of the selected TRPs of the selected frequency layer. If this field is absent, all DL-PRS Resource Sets and Resources of the indicated TRP are addressed.

nr-DL-SelectedPRS-ResourceSetIndex

This field indicates the addressed DL-PRS Resource Set of the selected TRP of the selected frequency layer. Value 0 corresponds to the first entry in nr-DL-PRS-ResourceSetList in IE NR-DL-PRS-Info provided in IE NR-DL-PRS-AssistanceData. Value 1 corresponds to the second entry in the nr-DL-PRS-ResourceSetList in IE NR-DL-PRS-Info.

dl-SelectedPRS-ResourceIndexList

This field provides the list of addressed DL-PRS Resources of the selected DL-PRS Resource Set of the selected TRP of the selected frequency layer. If this field is absent, all DL-PRS Resources of the indicated DL-PRS Resource Set are addressed.

nr-dl-SelectedPRS-ResourceIdIndex

This field indicates the addressed DL-PRS Resource of the selected DL-PRS Resource Set of the TRP of the selected frequency layer. Value 0 corresponds to the first entry in dl-PRS-ResourceList in IE NR-DL-PRS-Info provided in IE NR-DL-PRS-AssistanceData. Value 1 corresponds to the second entry in the dl-PRS-ResourceList in IE NR-DL-PRS-Info, and so on.

nr-ARFCN

This field specifies the ARFCN of the first RE of SSB’s RB#10.

ss-PBCH-BlockPower

Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [48], clause 7.

halfFrameIndex

Indicates the 5 msec offset of the SSB within a 10 msec system frame.

ssb-periodicity

The SSB periodicity in ms for the rate matching purpose.

ssb-PositionsInBurst

Indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213 [48], clause 4.1. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted.

ssb-SubcarrierSpacing

Subcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable.

sfn-SSB-Offset

Indicates the 10 msec system frame offset of the SSB within the SSB periodicity. Value 0 indicates that the SSB is transmitted in the first system frame; 1 indicates that the SSB is transmitted in the second system frame and so on. This field shall be configured according to the field ssb-Periodicity and the indicated system frame shall not exceed the configured SSB periodicity.

dl-PRS-ID

This field specifies the DL-PRS ID of the TRP for which the nr-SFN is applicable.

nr-PhysCellID

This field specifies the physical cell identity of the associated TRP, as defined in TS 38.331 [35].

nr-CellGlobalID

This field specifies the NCGI, the globally unique identity of a cell in NR, of the associated TRP, as defined in TS 38.331 [35].

nr-ARFCN

This field specifies the ARFCN of the TRP’s CD-SSB (as defined in TS 38.300 [47]) corresponding to nr-PhysCellID associated with the dl-PRS-ID.

nr-SFN

This field specifies the NR system frame number for the time stamp.

nr-Slot

This field specifies the NR slot number within the NR system frame number indicated by nr-SFN for the time stamp.

timingQualityValue

This field provides an estimate of uncertainty of the timing value for which the IE NR-TimingQuality is provided in units of metres.

timingQualityResolution

This field provides the resolution used in the timingQualityValue field. Enumerated values mdot1, m1, m10, m30 correspond to 0.1, 1, 10, 30 metres, respectively.

Az

The field is mandatory present if the field elevation is absent; otherwise it is optionally present, need ON.

AzOpt

The field is optionally present, need ON, when azimuth is present; otherwise it is not present.

El

The field is mandatory present if the field azimuth is absent; otherwise it is optionally present, need ON.

ElOpt

The field is optionally present, need ON, when elevation is present; otherwise it is not present.

NotSameAsPrev

The field is mandatory present in the first entry of the NR-TRP-LocationInfoPerFreqLayer list; otherwise it is optionally present, need OP.

nr-UE-RxTEG-ID-MaxSupport

Indicates the maximum number of UE-RxTEGs, which is supported and reported by the UE. This field is applicable for UE assisted DL-TDOA and Multi-RTT positioning. The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList and any of maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer, maxNrOfTRP-AcrossFreqs, maxNrOfPosLayer, maxNrOfDL-PRS-ResourcesPerResourceSet and maxNrOfDL-PRS-ResourcesPerPositioningFrequencylayer. Otherwise, the UE does not include this field.

NOTE: A single value is reported when both Multi-RTT and DL-TDOA are supported.

nr-UE-TxTEG-ID-MaxSupport

Indicates the maximum number of UE-TxTEGs, which is supported and reported by the UE. This field is applicable for Multi-RTT and UL-TDOA positioning. For UL-TDOA, the UE can include this field only if the UE supports supportedSRS-PosResources defined in TS 38.331 [35]. For Multi-RTT, the UE can include this field only if the UE supports maxNrOfDL-PRS-ResourcesPerResourceSet, maxNrOfDL-PRS-ResourcesPerPositioningFrequencylayer and supportedSRS-PosResources defined in TS 38.331 [35]. Otherwise, the UE does not include this field.

nr-UE-RxTxTEG-ID-MaxSupport

Indicates the maximum number of UE-RxTxTEGs, which is supported and reported by the UE. This field is applicable for Multi-RTT positioning. The UE can include this field only if the UE supports maxNrOfDL-PRS-ResourcesPerResourceSet, maxNrOfDL-PRS-ResourcesPerPositioningFrequencylayer and supportedSRS-PosResources defined in TS 38.331 [35]. Otherwise, the UE does not include this field.

measureSameDL-PRS-ResourceWithDifferentRxTEGs

Indicates the maximum number of different UE-RxTEGs that a UE can support to measure the same DL-PRS Resource of a TRP. This field is applicable for UE assisted DL-TDOA and Multi-RTT positioning. The UE can include this field only if the UE supports nr-UE-RxTEG-ID-MaxSupport. Otherwise, the UE does not include this field.

measureSameDL-PRS-ResourceWithDifferentRxTEGsSimul

Indicates the maximum number of UE Rx TEGs for measuring the same DL-PRS Resource simultaneously. This field is applicable for UE assisted DL-TDOA and Multi-RTT positioning. The UE can include this field only if the UE supports measureSameDL-PRS-ResourceWithDifferentRxTEGs. Otherwise, the UE does not include this field.

srs-PosResourceConfigCA-BandList

This field indicates the number of SRS for positioning resources supported by the target device. The target device includes this field for each band for the current configured CA band combination. The capability signalling comprises the following parameters.

– freqBandIndicatorNR indicates the current configured NR band of the target device.

– maxNumberSRS-PosResourceSetsPerBWP indicates the maximum number of SRS Resource Sets for positioning supported by the target device per BWP. Enumerated values n1, n2, n4, n8, n12, n16 correspond to 1, 2, 4, 8, 12, 16 SRS Resource Sets for positioning, respectively.

– maxNumberSRS-PosResourcesPerBWP indicates the maximum number of periodic, semi-persistent, and aperiodic SRS Resources for positioning supported by the target device per BWP. Enumerated values n1, n2, n4, n8, n16, n32, n64 correspond to 1, 2, 4, 8, 16, 32, 64 SRS Resources for positioning, respectively.

– maxNumberPeriodicSRS-PosResourcesPerBWP indicates the maximum number of periodic SRS Resources for positioning supported by the target device per BWP. Enumerated values n1, n2, n4, n8, n16, n32, n64 correspond to 1, 2, 4, 8, 16, 32, 64 periodic SRS Resources for positioning, respectively.

– maxNumberAP-SRS-PosResourcesPerBWP indicates the maximum number of aperiodic SRS Resources for positioning supported by the target device per BWP. Enumerated values n1, n2, n4, n8, n16, n32, n64 correspond to 1, 2, 4, 8, 16, 32, 64 aperiodic SRS Resources for positioning, respectively.

– maxNumberSP-SRS-PosResourcesPerBWP indicates the maximum number of semi-persistent SRS Resources for positioning supported by the target device per BWP. Enumerated values n1, n2, n4, n8, n16, n32, n64 correspond to 1, 2, 4, 8, 16, 32, 64 semi-persistent SRS Resources for positioning, respectively.

maxNumberSRS-PosPathLossEstimateAllServingCells

Indicates the maximum number of pathloss estimates that the UE can simultaneously maintain for all the SRS resource sets for positioning across all cells in addition to the up to four pathloss estimates that the UE maintains per serving cell for the PUSCH/PUCCH/SRS transmissions. The UE shall include this field if the UE supports any of olpc-SRS-PosBasedOnPRS-Serving, olpc-SRS-PosBasedOnSSB-Neigh and olpc-SRS-PosBasedOnPRS-Neigh. Otherwise, the UE does not include this field.

maxNumberSRS-PosSpatialRelationsAllServingCells

indicates the maximum number of maintained spatial relations for all the SRS resource sets for positioning across all serving cells in addition to the spatial relations maintained spatial relations per serving cell for the PUSCH/PUCCH/SRS transmissions. It is only applied for FR2. The UE can include this field only if the UE supports any of spatialRelation-SRS-PosBasedOnSSB-Serving, spatialRelation-SRS-PosBasedOnCSI-RS-Serving, spatialRelation-SRS-PosBasedOnPRS-Serving, spatialRelation-SRS-PosBasedOnSSB-Neigh or spatialRelation-SRS-PosBasedOnPRS-Neigh. Otherwise, the UE does not include this field.

olpc-SRS-Pos

Indicates whether the UE supports open-loop power control for SRS for positioning. The capability signalling comprises the following parameters.

– olpc-SRS-PosBasedOnPRS-Serving indicates whether the UE supports OLPC for SRS for positioning based on PRS from the serving cell in the same band. The UE can include this field only if the UE supports NR-DL-PRS-ProcessingCapability and srs-PosResources TS38.331 [35] Otherwise, the UE does not include this field.

– olpc-SRS-PosBasedOnSSB-Neigh indicates whether the UE supports OLPC for SRS for positioning based on SSB from the neighbouring cell in the same band. The UE can include this field only if the UE supports srs-PosResources TS 38.331 [35]. Otherwise, the UE does not include this field.

– olpc-SRS-PosBasedOnPRS-Neigh indicates whether the UE supports OLPC for SRS for positioning based on PRS from the neighbouring cell in the same band. The UE can include this field only if the UE supports olpc-SRS-PosBasedOnPRS-Serving. Otherwise, the UE does not include this field.

Note: A PRS from a PRS-only TP is treated as PRS from a non-serving cell.

– maxNumberPathLossEstimatePerServing indicates the maximum number of pathloss estimates that the UE can simultaneously maintain for all the SRS resource sets for positioning per serving cell in addition to the up to four pathloss estimates that the UE maintains per serving cell for the PUSCH/PUCCH/SRS transmissions. The UE shall include this field if the UE supports any of olpc-SRS-PosBasedOnPRS-Serving, olpc-SRS-PosBasedOnSSB-Neigh and olpc-SRS-PosBasedOnPRS-Neigh. Otherwise, the UE does not include this field.

spatialRelationsSRS-Pos

Indicates whether the UE supports spatial relations for SRS for positioning. It is only applicable for FR2. The capability signalling comprises the following parameters.

– spatialRelation-SRS-PosBasedOnSSB-Serving indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the serving cell in the same band. The UE can include this field only if the UE supports srs-PosResources TS 38.331 [35]. Otherwise, the UE does not include this field.

– spatialRelation-SRS-PosBasedOnCSI-RS-Serving indicates whether the UE supports spatial relation for SRS for positioning based on CSI-RS from the serving cell in the same band. The UE can include this field only if the UE supports spatialRelation-SRS-PosBasedOnSSB-Serving. Otherwise, the UE does not include this field.

– spatialRelation-SRS-PosBasedOnPRS-Serving indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the serving cell in the same band. The UE can include this field only if the UE supports any of DL-PRS Resources for DL-AoD, DL-PRS Resources for DL-TDOA or DL-PRS Resources for Multi-RTT, or srs-PosResources TS 38.331 [35]. Otherwise, the UE does not include this field.

– spatialRelation-SRS-PosBasedOnSRS indicates whether the UE supports spatial relation for SRS for positioning based on SRS in the same band. The UE can include this field only if the UE supports srs-PosResources TS 38.331 [35]. Otherwise, the UE does not include this field.

– spatialRelation-SRS-PosBasedOnSSB-Neigh indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the neighbouring cell in the same band. The UE can include this field only if the UE supports spatialRelation-SRS-PosBasedOnSSB-Serving. Otherwise, the UE does not include this field.

– spatialRelation-SRS-PosBasedOnPRS-Neigh indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the neighbouring cell in the same band. The UE can include this field only if the UE supports spatialRelation-SRS-PosBasedOnPRS-Serving. Otherwise, the UE does not include this field.

Note: A PRS from a PRS-only TP is treated as PRS from a non-serving cell.

posSRS-RRC-Inactive-InInitialUL-BWP

Indicates whether the UE supports positioning SRS transmission in RRC_INACTIVE state for initial UL BWP.

– maxNumOfSRSposResourceSets indicates the maximum number of SRS Resource Sets for positioning supported by the UE.

– maxNumOfPeriodicAndSemiPeristentSRSposResources indicates the maximum number of periodic and semi-persistent SRS Resources for positioning supported by the UE.

– maxNumOfPeriodicAndSemiPeristentSRSposResourcesPerSlot indicates the maximum number of periodic and semi-persistent SRS Resources for positioning per slot supported by the UE.

– maxNumOfPeriodicSRSposResources indicates the maximum number of periodic SRS Resources for positioning supported by the UE.

– maxNumOfPeriodicSRSposResourcesPerSlot indicates the maximum number of periodic SRS Resources for positioning per slot supported by the UE.

– maxNumOfSemiPersistentSRSposResources indicates the maximum number of semi-persistent SRS Resources for positioning supported by the UE. The UE can include this field only if the UE supports posSRS-RRC-Inactive-InInitialUL-BWP. Otherwise, the UE does not include this field.

– maxNumOfSemiPersistentSRSposResourcesPerSlot indicates the maximum number of semi-persistent SRS Resources for positioning per slot supported by the UE. The UE can include this field only if the UE supports posSRS-RRC-Inactive-InInitialUL-BWP. Otherwise, the UE does not include this field.

posSRS-RRC-Inactive-OutsideInitialUL-BWP

Indicates whether the UE supports positioning SRS transmission in RRC_INACTIVE state outside initial UL BWP. The UE can include this field only if the UE supports posSRS-RRC-Inactive-InInitialUL-BWP. Otherwise, the UE does not include this field.

– maxSRSposBandwidthForEachSCS-withinCC-FR1 indicates the maximum SRS bandwidth supported for each SCS that UE supports within a single CC for FR1.

– maxSRSposBandwidthForEachSCS-withinCC-FR2 indicates the maximum SRS bandwidth supported for each SCS that UE supports within a single CC for FR2.

– maxNumOfSRSposResourceSets indicates the maximum number of SRS Resource Sets for positioning supported by the UE.

– maxNumOfPeriodicSRSposResources indicates the maximum number of periodic SRS Resources for positioning supported by the UE.

– maxNumOfPeriodicSRSposResourcesPerSlot indicates the maximum number of periodic SRS Resources for positioning per slot supported by the UE.

– differentNumerologyBetweenSRSposAndInitialBWP indicates whether different numerology between the SRS and the initial UL BWP is supported by the UE. If the field is absent, the UE only supports same numerology between the SRS and the initial UL BWP.

– srsPosWithoutRestrictionOnBWP indicates whether SRS operation without restriction on the BW is supported by the UE; BW of the SRS may not include BW of the CORESET#0 and SSB. If the field is absent, the UE supports only SRS BW that include the BW of the CORESET #0 and SSB.

– maxNumOfPeriodicAndSemiPeristentSRSposResources indicates the maximum number of periodic and semi-persistent SRS Resources for positioning supported by the UE.

– maxNumOfPeriodicAndSemiPeristentSRSposResourcesPerSlot indicates the maximum number of periodic and semi-persistent SRS Resources for positioning per slot supported by the UE.

– differentCenterFreqBetweenSRSposAndInitialBWP indicates whether different center frequenecy between the SRS for positioning and the initial UL BWP is supported by the UE. If the field is absent, the UE only supports same center frequency between the SRS for positioning and initial UL BWP.

– maxNumOfSemiPersistentSRSposResources indicates the maximum number of semi-persistent SRS Resources for positioning supported by the UE. The UE can include this field only if the UE supports posSRS-RRC-Inactive-InInitialUL-BWP. Otherwise, the UE does not include this field.

– maxNumOfSemiPersistentSRSposResourcesPerSlot indicates the maximum number of semi-persistent SRS Resources for positioning per slot supported by the UE. The UE can include this field only if the UE supports posSRS-RRC-Inactive-InInitialUL-BWP. Otherwise, the UE does not include this field.

– switchingTimeSRS-TX-OtherTX indicates the switching time between SRS Tx and other Tx in initial UL BWP or Rx in initial DL-BWP.

olpc-SRS-PosRRC-Inactive

Indicates whether the UE supports open-loop power control for SRS for positioning in RRC_INACTIVE state. The UE can include this field only if the UE supports posSRS-RRC-Inactive-InInitialUL-BWP. Otherwise, the UE does not include this field.

spatialRelationsSRS-PosRRC-Inactive

Indicates whether the UE supports spatial relations for SRS for positioning in RRC_INACTIVE state on FR2. The UE can include this field only if the UE supports posSRS-RRC-Inactive-InInitialUL-BWP. Otherwise, the UE does not include this field.

milli-arc-second-units

This field provides the units and scale factor for the delta-latitude and delta-longitude fields. Enumerated values mas0-03, mas0-3, mas3, and mas30, correspond to 0.03, 0.3, 3, and 30 milliarcseconds, respectively.

height-units

This field provides the units and scale factor for the delta-height field. Enumerated values mm, cm, and m correspond to 10^-3 metre, 10^-2 metre, and 1 metres, respectively.

delta-latitude

This field specifies the delta value in latitude of the desired location, defined as "desired location" minus "reference point location" and comprises the following sub-fields:

– delta-Latitude specifies the delta value in latitude in the unit provided in milli-arc-second-units field.

– coarse-delta-Latitude specifies the delta value in latitude in 1024 times the size of the unit provided in milli-arc‑second‑units field and with the same sign as in the delta-Latitude field. If this field is absent, the value for coarse-delta-Latitude is zero.

I.e., the full delta-latitude is given by:

(delta-Latitude × milli-arc-second-units) ± (coarse-delta-Latitude × 1024 × milli-arc-second-units) [milli-arc-seconds]

delta-longitude

This field specifies the delta value in longitude of the desired location, defined as "desired location" minus "reference point location" and comprises the following sub-fields:

– delta-Longitude specifies the delta value in longitude in the unit provided in milli-arc-second-units field.

– coarse-delta-Longitude specifies the delta value in longitude in 1024 times the size of the unit provided in milli-arc‑second‑units field and with the same sign as in the delta-Longitude field. If this field is absent, the value for coarse-delta-Longitude is zero.

I.e., the full delta-longitude is given by:

(delta-Longitude × milli-arc-second-units) ± (coarse-delta-Latitude × 1024 × milli-arc-second-units) [milli-arc-seconds]

delta-height

This field specifies the delta value in ellipsoidal height of the desired location, defined as "desired location" minus "reference point location" and comprises the following sub-fields:

– delta-Height specifies the delta value in ellipsoidal height in the unit provided in height-units field.

– coarse-delta-Height specifies the delta value in ellipsoidal height in 1024 times the size of the unit provided in height-units field and with the same sign as in the delta-Height field. If this field is absent, the value for coarse-delta-Height is zero.

I.e., the full delta-height is given by:

(delta-Height × height-units) ± (coarse-delta-Height × 1024 × height-units) [metres]

locationUNC

This field specifies the uncertainty of the location coordinates and comprises the following sub-fields:

– horizontalUncertainty indicates the horizontal uncertainty of the ARP latitude/longitude. The ′horizontalUncertainty′ corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [15] and ′horizontalConfidence′ corresponds to confidence as defined in TS 23.032 [15].

– verticalUncertainty indicates the vertical uncertainty of the ARP altitude. The ‘verticalUncertainty‘ corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [15] and ‘verticalConfidence‘ corresponds to confidence as defined in TS 23.032 [15].

If this field is absent, the uncertainty is the same as for the associated reference point location.