U.S. patent application number 14/912587 was filed with the patent office on 2016-07-14 for devices and methods for sending or receiving assistance data.
The applicant listed for this patent is INTEL IP CORPORATION. Invention is credited to Hyung-Nam CHOI, Michael HORVAT, Kenan N. ISA.
Application Number | 20160205651 14/912587 |
Document ID | / |
Family ID | 52667889 |
Filed Date | 2016-07-14 |
United States Patent
Application |
20160205651 |
Kind Code |
A1 |
ISA; Kenan N. ; et
al. |
July 14, 2016 |
DEVICES AND METHODS FOR SENDING OR RECEIVING ASSISTANCE DATA
Abstract
A device for use in a mobile communication user equipment, UE,
includes processing circuitry to: receive cell data pertaining to a
plurality of assistance data cells, and receive offset information,
wherein the offset information describes respective LTE frame
offsets between an assistance data reference cell and each of a
plurality of neighbour cells. A location server to provide
positioning assistance data to a user equipment, UE, comprises
processing circuitry to: determine offset information describing
respective LTE frame time offsets between an assistance data
reference cell and each of a plurality of neighbour cells.
Inventors: |
ISA; Kenan N.; (Duisburg,
DE) ; HORVAT; Michael; (Munich, DE) ; CHOI;
Hyung-Nam; (Hamburg, DE) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
INTEL IP CORPORATION |
Santa Clara |
CA |
US |
|
|
Family ID: |
52667889 |
Appl. No.: |
14/912587 |
Filed: |
September 12, 2014 |
PCT Filed: |
September 12, 2014 |
PCT NO: |
PCT/US14/55513 |
371 Date: |
February 17, 2016 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61879014 |
Sep 17, 2013 |
|
|
|
Current U.S.
Class: |
455/456.1 |
Current CPC
Class: |
H04J 13/0048 20130101;
G01S 5/0236 20130101; H04W 28/12 20130101; H04W 72/042 20130101;
H04W 72/0446 20130101; H04W 64/00 20130101; H04W 36/04 20130101;
H04L 1/1893 20130101; H04L 5/003 20130101; H04J 3/02 20130101; H04W
4/70 20180201; H04L 5/14 20130101; H04W 24/10 20130101; H04L 5/0048
20130101; H04W 76/28 20180201; H04W 72/0466 20130101; H04L 5/0051
20130101; H04W 28/0247 20130101; H04B 7/2643 20130101; H04W 4/14
20130101; H04W 28/0268 20130101; H04W 28/0236 20130101; H04L
27/2601 20130101; H04W 28/0242 20130101; H04W 36/0083 20130101 |
International
Class: |
H04W 64/00 20060101
H04W064/00; G01S 5/02 20060101 G01S005/02 |
Claims
1. A device for use in a mobile communication user equipment, UE,
the device comprising processing circuitry to: receive cell data
pertaining to a plurality of assistance data cells, and receive
offset information, wherein the plurality of assistance data cells
includes an assistance data reference cell and a plurality of
neighbour cells, the cell data includes: (i) information to
describe timings of positioning reference signals, PRSs, of the
assistance data reference cell, and (ii) neighbour information, the
neighbour information to describe timings, relative to the
assistance data reference cell, of positioning reference signals,
PRSs, of the plurality of neighbour cells, and wherein the offset
information describes respective LTE frame offsets between the
assistance data reference cell and each of the neighbour cells.
2. The device of claim 1, wherein a serving cell of the UE is the
assistance data reference cell or one of the plurality of neighbour
cells.
3. The device of claim 2, wherein the processing circuitry is
further to determine a time window relative to a serving cell
timing for measuring a PRS receive timing of an assistance data
cell other than the serving cell based on the cell data and the
offset information.
4. The device of claim 3, wherein: the serving cell is different
from the assistance data reference cell; and the neighbour cell has
PRS muting enabled.
5. The device of claim 1, wherein: when the UE has one or more
serving cells, and none of the serving cells is configured to
transmit positioning reference signals, the processing circuitry is
further to determine a time window for measuring a PRS receive
timing of an assistance data cell that is not one of the serving
cells based on the neighbour information and the offset
information.
6. The device of claim 2, wherein when the serving cell belongs to
a first carrier frequency, and the reference cell and at least one
of the other assistance data cells belong to a second carrier
frequency different from the first carrier frequency, the
processing circuitry is further to perform inter-frequency RSTD
measurements on the second carrier frequency based on the cell data
and the offset information.
7. The device of claim 1, wherein the offset information is to be
received in an information element that replaces or updates an
information element specified within 3GPP TS 36.355.
8. The device of claim 7, wherein the cell data and offset
information are received in the same information element.
9. The device of claim 7, wherein the replaced or updated
information element is an OTDOA-NeighbourCellInfoElement or the
offset information replaces prs-SubframeOffset in the
OTDOA-NeighbourCellInfoElement.
10. The device of claim 1, wherein the processing circuitry is
further to: perform RSTD measurements using received PRSs of at
least some of the assistance data cells; and generate a report
based on the RSTD measurements, the report indicating the RSTD
measurements relative to an RSTD reference cell, wherein the RSTD
reference cell is different from a serving cell of the UE.
11. The device of claim 1, wherein the processing circuitry is to
receive assistance data, and either: the assistance data including
the cell data and the offset information, or the assistance data
includes the cell data, and the offset information is to be
received separately from the assistance data.
12. The device of claim 1, wherein the device is a user equipment
further comprising one or more of: a screen, a speaker, a
touchscreen, a keyboard, an antenna array including a plurality of
antennas, a graphics processor, an application processor.
13. A location server for use in a communication system, the device
to provide positioning assistance data to a user equipment, UE, the
device comprising processing circuitry to: determine information
describing an assistance data reference cell; determine cell data,
the cell data to describe relative transmit timings of positioning
reference signals between a plurality of neighbour cells; determine
offset information describing respective LTE frame time offsets
between the assistance data reference cell and each of the
neighbour cells; and sending to the UE data including the
information describing the assistance data reference cell, the cell
data, and the offset information; wherein the assistance data
includes at least the information describing the assistance data
reference cell and the cell data.
14. The location server of claim 13, wherein the assistance data
reference cell is not a serving cell of the UE.
15. The location server of claim 13, wherein: the plurality of
neighbour cells and the assistance data reference cell are
assistance data cells; a serving cell of the UE is one of the
assistance data cells, and the serving cell of the UE belongs to a
first carrier frequency; at least one of the assistance data cells
other than the serving cell belong to a second carrier
frequency.
16. A method performed by a user equipment, UE, the method
comprising: receiving Observed Time of Difference Of Arrival,
OTDOA, assistance data, the OTDOA assistance data including data
indicative of timings of positioning reference signals, PRSs, for a
plurality of neighbour cells, the timings indicated relative to a
timing of an assistance data reference cell, wherein receiving
OTDOA assistance data includes receiving offset information, the
offset information indicative of respective LTE frame offsets
between the assistance data reference cell and the plurality of
neighbour cells.
17. The method of claim 16, further comprising determining a time
window for measuring a PRS receive timing of an assistance data
cell based on the data indicative of timings of PRSs and the offset
information, wherein wherein the assistance data cell is the
assistance data reference cell or a neighbour cell of the plurality
of neighbour cells.
18. The method of claim 16, further comprising: performing RSTD
measurements of one or more cells, the one or more cells selected
from the neighbour cells and the assistance data reference cell;
and sending a report of the RSTD measurements, the report
indicating the RSTD measurements relative to an RSTD reference
cell, the RSTD reference cell selected from the one or more
cells.
19. The method of claim 18, wherein the RSTD reference cell is
different from a serving cell of the UE.
20. A method performed by a location server, the method comprising:
receiving from a user equipment, UE, a request for Observed Time of
Difference Of Arrival, OTDOA, assistance data; generating the OTDOA
assistance data; and sending the generated OTDOA assistance data to
the UE, wherein the OTDOA assistance data includes offset
information describing LTE frame offsets between the assistance
data reference cell and the plurality of neighbour cells.
21. The method of claim 20, further comprising: selecting the
assistance data reference cell, wherein the assistance data
reference cell is selected to be different from a serving cell of
the UE.
22-25. (canceled)
Description
TECHNICAL FIELD
[0001] Embodiments described herein generally relate to location
servers and user equipment, more particularly, embodiments relate
to location servers for sending assistance data relating to
positioning reference signals and user equipment for receiving the
assistance data.
BACKGROUND
[0002] Various positioning techniques have been developed for
determining a location of a user equipment (UE). Among these
techniques is the observed time difference of arrival (OTDOA)
method. According to this method, a UE measures the time of arrival
of the downlink (DL) signals from the base stations of several
surrounding cells and reports these measurements (or quantities
derived from these) back to the network. The location entity in the
network then applies triangulation techniques based on the
measurements in order to estimate the UE's position. The precision
of the method may be improved by using further OTDOA measurements
to other nearby base stations to fine tune the location estimate.
The precision and reliability of OTDOA-based methods increase with
increased availability of measurement data, especially when the UE
can measure more than just 2 or 3 surrounding base stations. The
LTE Positioning Protocol (LPP) in 3GPP TS 36.355 specifies an
implementation of an OTDOA method.
BRIEF DESCRIPTION OF THE DRAWINGS
[0003] FIG. 1 illustrates a system for performing OTDOA
positioning.
[0004] FIG. 2 illustrates limitations of the system described in
3GPP TS 36.355.
[0005] FIG. 3 illustrates a location server.
[0006] FIG. 4 illustrates effects of providing offset
information.
[0007] FIG. 5 illustrates an example of offset information.
[0008] FIG. 6 illustrates a method of receiving assistance data
performed by a user equipment according to some embodiments.
[0009] FIG. 7 illustrates a method of sending assistance data
performed by a location server according to some embodiments.
[0010] FIG. 8 illustrates a system according to some
embodiments.
[0011] FIG. 9 illustrates an embodiment of a mobile device.
DESCRIPTION OF EMBODIMENTS
[0012] FIG. 1 illustrates a system 100 for performing OTDOA
positioning. The system includes a UE 110, which may be any
suitable target device for OTDOA positioning, and a location server
120. In order to perform an OTDOA measurement, the location server
120 provides assistance data 125 to the UE 110.
[0013] The UE 110 measures the timing of receipt, by the UE, of
positioning reference signals (PRSs) 135a-c from a plurality of
references sources 130a-c. The positioning reference signal sources
may be eNodeBs (eNBs) that have PRS configured, for example. The
measurements by the UE may include Reference Signal Time Difference
(RSTD) measurements.
[0014] The UE 110 reports the measured timings, or data derived
from the timings, to the location server 120 in measurement data
115.
[0015] The location server 120 may use the received measurement
data 115 to determine a location of the UE 110 using triangulation
techniques and knowledge of the locations of the reference sources
130a-c.
[0016] Communication between the UE 110 and the location server 120
(e.g. assistance data 125 and measurements 115) may be performed
using one or more LPP sessions.
[0017] The assistance data 125 provides the UE 110 with
configuration parameters of the reference sources 130a-c.
[0018] 3GPP TS 36.355 release 9 requires that the UE 110 receive
the assistance data 125 though the serving cell (primary cell,
Pcell). However, in 3GPP TS 36.355 release 10, it is possible for
the UE 110 to receive OTDOA assistance data through any serving
cell (primary cell or secondary cell, Scell), if the UE 110
supports carrier aggregation.
[0019] TS 36.355, section 6.5.1.1 includes a note that the location
server should include in the assistance data at least one cell for
which the System Frame Number (SFN) can be obtained by the target
device, e.g. the serving cell, either as the assistance data
reference cell or in the neighbor cell list. Otherwise the target
device will be unable to perform the OTDOA measurement and the
positioning operation will fail.
[0020] Typically, SFN is obtained by the UE 110 from Physical
Broadcast Channel (PBCH) detection (i.e. the master information
block (MIB) detection), which is usually carried out only for the
UE's serving cell(s). A UE 110 could be arranged to decode the PBCH
to obtain SFN for a cell other than a serving cell for e.g. the
assistance data reference cell. However, this is complex and would
require a further timing synchronization to this cell by the UE
while processing throughput on the serving cell. Further, the
minimum SINR for PRS is specified to be -13dB in 3GPP TS 36.133. In
contrast, for PBCH the minimum SINR is specified to be -6.1dB in
3GPP TS 36.101. Since the actual serving cell is typically
connected with the UE for actual data throughput due to having the
highest SINR among the identified cells, it is questionable whether
or not the other identified cells, which have a lower SINR than the
serving cell, would have a strong enough signal for PBCH
detection.
[0021] The present inventors have realized that, where the
assistance data reference cell is not a serving cell, the reference
sources 130a-c that are useable for OTDOA measurement may be more
limited, and in some cases, it may be impossible to perform OTDOA
measurement.
[0022] FIG. 2 illustrates some limitations of the system as
described in TS 36.355, release 10 (this also applies to relase 9,
assuming a sigle serving cell=Pcell). The UE receives assistance
data 115 that is providing information on an OTDOA assistance data
reference cell, R, and on a plurality of OTDOA assistance data
neighbor cells, N1, . . . , NK.
[0023] According to LPP, the assistance data includes the
information shown in Table 1. The neighbor cells correspond to
reference sources 130a-c that may have PRS that are detectable by
the UE.
TABLE-US-00001 Assistance data Assistance data Assistance Data
neighbour neighbour Reference Cell (R) Cell 1 (N1) Cell K (NK)
physCellId physCellId physCellId cellGlobalId cellGlobalId
cellGlobalId earfcn earfcn earfcn cpLength cpLength cpLength
prsInfo prsInfo prsInfo antennaPortConfig antennaPortConfig
antennaPortConfig slotNumberOffset slotNumberOffset
prs-SubframeOffset prs-SubframeOffset expectedRSTD expectedRSTD
expectedRSTD- expectedRSTD- Uncertainty Uncertainty
[0024] The UE 110 is frame and time synchronized to the serving
cell and so the UE 110 has information 215 for the serving cell,
including for example, SFN, physCellId, cellGlobalId, earfcn,
cpLength, antennaPortConfig.
[0025] Herein the term assistance data cells refers to cells in the
group consisting of the assistance data reference cell and the
assistance data neighbor cells.
[0026] Question 220 of FIG. 2 asks if the serving cell is one of
the assistance data cells. When the answer to question 220 is "No"
OTDOA measurements are not possible (result 225). In this case, the
frame timing of the positioning cells (i.e. assistance data
neighbor cells) are not known, since they are not related to the
SFN of the serving cell. This is contrary to the requirement of TS
36.355, 6.5.1.1, which states "[t]he location server should include
at least one cell for which the SFN can be obtained by the target
device, e.g. the serving cell, in the assistance data, either as
the assistance data reference cell or in the neighbor cell list.
Otherwise the target device will be unable to perform the OTDOA
measurement and the positioning operation will fail."
[0027] Where the answer to question 220 is "yes", question 230 of
FIG. 2 asks if the serving cell has PRS configured. If the answer
to this question is "no", RSTD measurements are not possible, as it
is not possible for the UE to determine the PRS timing of the
positioning cells (result 235).
[0028] Where the answer to questions 220 and 230 are "Yes",
question 240 asks if the serving cell is the reference cell. If the
answer to this question is "no", RSTD measurements may be
performed, but only for cells with PRS muting not configured. RSTD
measurements are not possible for positioning cells that have PRS
muting configured (result 245).
[0029] If the answer is "yes" to each of questions 220, 230 and
240, RSTD measurements may be performed for positioning cells with
or without PRS muting configured. However, when the UE reports the
RSTD measurement data 115 to the location server 120, the serving
cell must be used as the reference cell, which reduces flexibility
and possible performance improvement (result 250).
[0030] The following provides more detail regarding results 235,
245 and 250. In an arrangement where the serving cell does not
transmit PRS, it is not possible to perform RSTD measurements
(result 235). To enable the UE to detect the PRS from the
assistance data neighbour cells, the assistance data according to
TS 36.355 includes a parameter, prs-SubframeOffset, for each of the
neighbor cells. This field specifies the offset between the first
PRS subframe in the assistance data reference cell on the reference
carrier frequency layer and the first PRS subframe in the closest
subsequent PRS positioning occasion of this cell on the other
carrier frequency layer. The value is given in number of full
sub-frames. If the ARFCN is not the same as for the assistance data
reference cell and the field is not present but PRS are available
on this cell, the receiver shall consider the PRS subframe offset
for this cell to be 0. This is, by definition, a timing difference
between positioning reference symbols, and when positioning
reference symbols are not transmitted there is no such offset. In
this case (result 235), the UE cannot use prs-SubframeOffset to
find the PRS timings for assistance data cells, since it relates to
the case where PRS is not configured for the serving cell, and so
prs-SubframeOffset is not defined between the serving cell and
other cells in the assistance data. Accordingly, it is impossible
for UE to make RSTD measurements using PRS.
[0031] In relation to result 245 of FIG. 2, for PRS muting of
assistance data cells TS 36.355 provides the muting patterns of
respective assistance data cells to the UE within the assistance
data. The PRS muting configuration is defined by a periodic PRS
muting sequence with periodicity T.sub.REP where T.sub.REP, counted
in the number of PRS positioning occasions, can be 2, 4, 8, or 16,
which is also the length of the selected bit string that represents
this PRS muting sequence. If a bit in the PRS muting sequence is
set to "0", then the PRS is muted in the corresponding PRS
positioning occasion. The first bit of the PRS muting sequence
corresponds to the first PRS positioning occasion that starts after
the beginning of the assistance data reference cell SFN=0. However,
where the UE does not know the current SFN of the assistance data
reference cell, such as when the assistance data reference cell is
not the serving cell, the muting pattern timing is unknown for all
assistance data neighbor cells. TS 36.355 states that when the SFN
of the assistance data reference cell is not known to the UE and
prs-MutingInfo is provided for a cell in the
OTDOA-NeighbourCellInfoList Information Element (IE), the UE may
assume no PRS is transmitted by that cell. Accordingly, it is not
possible to use neighbor cells with muting configured for RSTD
measurements when the assistance data reference cell is different
from the serving cell.
[0032] In some cases, it may not be possible to ensure that the
assistance data reference cell is the serving cell. For example,
when a handover occurs just after assistance data has been sent to
a UE. Due to the above stated reasons, RSTD measurement performance
degradation may result if the UE does not have information about
the assistance data reference cell SFN.
[0033] In another example, RSTD measurements may not be possible is
when all positioning cells with PRS configuration are on the same
frequency, f2, and the actual serving cell is on frequency f1. In
this case, the link between the actual serving cell SFN and the
frame timings of the positioning cells is not available to the UE.
This case corresponds to the UE performing inter-frequency RSTD
measurements only. This is specified in 3GPP TS 36.133, Table
8.1.2.6.1-1. In this table, column 1 corresponds to f2 only and
column 2 corresponds to f1 and f2. However, it is not possible to
apply column 1 (f2 only) inter-frequency only RSTD measurements.
The is because the UE is obliged to report the systemFrameNumber
field in the OTDOA-SignalMeasurementInformation IE specified in
3GPP TS 36.355, section 6.5.1.5, and it is therefore not possible
to have an RSTD reference cell different from the serving cell,
since the UE knows SFN only for the serving cell. This can be a
performance limitation for the RSTD measurements on frequencies
different from the frequency of the serving cell.
[0034] Another example scenario is the case of a UE 110 connected
to a pico or femto cell as the serving cell, where the UE receives
OTDOA assistance data only containing macro cells (e.g. only these
cells transmit the PRSs).
[0035] The cause of these limitations is described in more detail
in the following. 3GPP 36.211 Table 6.10.4.3-1 defines PRS subframe
configuration according to the following table
TABLE-US-00002 PRS configuration PRS periodicity PRS subframe
offset Index I.sub.PRS T.sub.PRS (subframes) .DELTA..sub.PRS
(subframes) 0-159 160 I.sub.PRS 160-479 320 I.sub.PRS - 160
480-1119 640 I.sub.PRS - 480 1120-2399 1280 I.sub.PRS - 1120
[0036] Here, T.sub.PRS is the PRS transmission period of the
corresponding cell (prsInfo.prs-ConfigurationIndex.Tprs).
.DELTA..sub.PRS specifies when PRS is transmitted by the
corresponding cell (prsInfo.prs-ConfigurationIndex.Dprs). If
T.sub.PRS and .DELTA..sub.PRS are known, the LTE frame number,
n.sub.f, and the LTE subframe number, n.sub.sf, corresponding to
the first subframe of the PRS can be calculated using (given in
3GPP 36.211 Section 6.10.4.3):
(10.times.n.sub.f+[n.sub.s/2]-.DELTA..sub.PRS)modT.sub.PRS=0. Where
n.sub.s is the slot number and the subframe number,
n.sub.sf=Int(n.sub.s/2).
[0037] The LTE frame number for a given cell, n.sub.f, can take
values from 0 to 1023, and corresponds to the SFN of that cell, and
n.sub.sf is the LTE subframe number within the corresponding LTE
frame, with each frame including 10 subframes numbered 0 to 9.
[0038] For example, if T.sub.PRS=160 and .DELTA..sub.PRS=5, the
corresponding cell transmits PRS within the subframes given in the
following table:
TABLE-US-00003 n.sub.f 0 16 32 48 64 . . . 1008 0 . . . n.sub.sf 5
5 5 5 5 . . . 5 5 . . .
[0039] Where n.sub.f takes consecutive values between 0 and 1023
before returning to 0, and for each value of n.sub.f, n.sub.s takes
values between 0 and 9, consecutively.
TABLE-US-00004 n.sub.f 0 0 0 . . . 0 1 1 1 . . . 1 2 2 . . . 1023
1023 1023 . . . 1023 0 0 . . . n.sub.s 0 1 2 . . . 9 0 1 2 . . . 9
0 1 . . . 0 1 2 . . . 9 0 1 . . .
[0040] If T.sub.PRS and .DELTA..sub.PRS are provided, the UE can
identify PRS timing provided n.sub.f and n.sub.s are known for the
particular cell at a particular moment. However, in an asynchronous
network, each cell has independent n.sub.f and n.sub.s values at
any given moment. Accordingly, where assistance data provides only
T.sub.PRS and .DELTA..sub.PRS, the UE may only make full use of
this data if it also knows the timings of that cell (i.e. its
n.sub.f and n.sub.s values).
[0041] This issue of not being able to identify the PRS timings of
cells is not present for synchronous networks, but since the
synchronous network condition is not signaled within the assistance
data, the UE must assume that the network is asynchronous. In order
to address this issue, TS 36.355 includes in the assistance data
prs-SubframeOffset, for each neighbour cell. This is the offset
(the number of whole subframes between the first PRS subframe of
the assistance data reference cell and the next closest subsequent
PRS subframe of the corresponding neighbour cell. However, where
the frame timing of the reference cell is not known,
prs-SubframeOffset does not provide sufficient information to
determine the frame timings for other neighbour cells.
[0042] Embodiments of the invention may eliminate or ameliorate one
or more of the above problems.
[0043] FIG. 3 shows an example of a location server 120 according
to some embodiments. The location server 120 includes a
communication section 310 for communicating with a network, a data
base 320 for storing information on cells, including the reference
cell and neighbor cells, and assistance data preparation section
330. The assistance data preparation section obtains information
from the database 320 and prepares assistance data for sending to
the UE via the communication section 310 and the network. The
assistance data preparation section 330 includes frame number
offset determining section 340. The frame number offset determining
section 340 determines respective frame offsets between the
assistance data reference cell and each of the neighbouring cells
of the assistance data, and includes the result of this
determination in the assistance data to be transmitted to the UE
110.
[0044] According to some embodiments, the assistance data may
include offset information indicating the result of the
determination by the frame number offset determining section 340,
e.g. in the form of an OTDOA parameter. According to some
embodiments, the OTDOA parameter may be defined as:
[0045] frameNumberOffset: This parameter specifies the SFN number
offset at the transmitter between this cell and the assistance data
reference cell.
[0046] The offset information may be included in the
OTDOA-NeighbourCellInfoList information element. For example, the
frameNumberOffset parameter may be provided in addition to the
parameters of the information element
OTDOA-NeighbourCellInfoElement, or an existing parameter in
OTDOA-NeighbourCellInfoElement information element may be
redefined. For example, the parameter prs-SubframeOffset may be
replaced with frameNumberOffset, or a corresponding parameter.
prs-SubframeOffset is defined in 3GPP TS 36.355, section 6.5.1.2,
IE OTDOA-NeighbourCellInfoList. This parameter specifies the offset
between the first PRS subframe in the assistance data reference
cell on the reference carrier frequency layer and the first PRS
subframe in the closest subsequent PRS positioning occasion of this
cell on the other carrier frequency layer.
[0047] In some embodiments, the offset information may be provided
in a separate information element from the
OTDOA-NeighbourCellInfoList IE.
[0048] In some embodiments, the offset information may be provided
separately from the assistance data.
[0049] In some embodiments, the database 320 may be external to the
location server 120, and the location server 120 may receive
information on neighboring cells via the communication section 310,
for example.
[0050] In some examples, the location server 120 may be further
arranged to receive RSTD measurements from the UE 110 via the
communication section 310, and may further include a location
calculating section (not shown) for determining an approximate
position of the UE based on the received RSTD measurements.
[0051] The various sections of the location server 120 may be
implemented in hardware, software and/or firmware. The sections of
the location server 120 may share some or all of their hardware.
The location server 120 may include one or more processors, storage
media, etc. to implement the various sections described above.
[0052] FIG. 4 shows the questions and results of FIG. 2, but
indicates how the results may differ when offset information is
provided to the UE. In particular, the results 235, 245 and 250 may
change when offset information 410 is provided.
[0053] Where PRS is not configured for the serving cell (question
230), the offset information 410 makes it possible to perform
PRS-based RSTD measurements 430. With the offset information, the
SFN of the assistance data reference cells can be determined by the
UE, prs-ConfigurationIndex can then be used for the neighbor cells
to identify the positioning occasions for the neighbour cells.
Therefore, the offset information allows PRS-based RSTD
measurements even when the serving cell (PCell or SCell) does not
have PRS configured.
[0054] When the serving cell is not the assistance data reference
cell (question 240), the offset information 410 makes it possible
to perform RSTD measurements for neighbour cells with PRS muting
enabled, since the offset information enables the UE 110 to
determine the SFN for the assistance data reference cell using the
serving cell SFN, and so the UE can determine the starting time of
the muting pattern for each assistance data cell.
[0055] When the assistance data reference cell is the serving cell
(question 240), the offset information allows the UE to calculate
the frame timing for any of the neighbour cells for which offset
information is provided, and so any of these neighbour cells may be
used as the RSTD reference cell when the UE 110 reports the RSTD
measurements to the location sever 120. This allows the UE to
freely select the RSTD reference cell, such that the RSTD reference
cell may be selected from a frequency that has the most reliable
RSTD results. In contrast, forcing the RSTD reference cell to be
the serving cell, for example, can degrade the RSTD measurement
results. Instead, for example, if only measurements on frequency f2
have been performed (with the serving cell on frequency f1),
selecting an inter-frequency cell as RSTD reference cell will
provide better RSTD measurement performance.
[0056] The offset information enables the UE 110 to determine the
timing relation between all of the assistance data cells, and the
UE 110 can determine PRS timings for assistance data cells from the
PRS configuration information provided within the assistance data.
The form of the offset information is not particularly limited.
[0057] As described above, the offset information allows a frame
relation to be calculated between the OTDOA positioning assistance
data reference cell and the serving cell, without requiring further
PBCH (MIB) detection. In addition, the offset information allows
the removal of ambiguity in the frame relation among the
positioning cells.
[0058] FIG. 5 shows an example of a frame number offset in
accordance with some embodiments. In the example of FIG. 5, the
frameNumberOffset is defined as the (integer) number of frames of
the assistance data reference cell between the start of a
particular frame (e.g. SFN=0) of the assistance data reference cell
and a start of the corresponding frame in a particular neighbour
cell.
[0059] According to TS 36.355, the assistance data includes a
slotNumberOffset field. This is intended for CRS-based RSTD
measurements, and is not required for PRS-based measurements.
However, slotNumberOffset may be used in conjunction with the
frameNumberOffset field, described above, to calculate n.sub.f and
n.sub.sf values for the corresponding neighbour cell, using the
values of n.sub.f and n.sub.fs of the serving cell. The field
frameNumberOffset gives the difference between n.sub.f of the two
cells. The field slotNumberOffset is the difference between n.sub.s
of the two cells, and the subframe number can be determined from
the relation n.sub.sf=Int(n.sub.s/2).
[0060] According to some embodiments, a UE 110 is arranged to
receive assistance data from a location server 120. The assistance
data may include a neighbour cell list that describes timings,
relative to an assistance data reference cell, of positioning
reference signals (PRSs) of a plurality of neighbour cells. The
assistance data may also include information on the assistance data
reference cell, such as timing information. The assistance data
reference cell and neighbour cells are collectively referred to
herein as assistance data cells. The information on the assistance
data reference cell and the neighbour information is referred to
collectively herein as positioning assistance data. The assistance
data may also include offset information describing respective
frame offsets between the assistance data reference cell and each
of the neighbour cells. In some embodiments the offset information
may be included in the neighbour cell list.
[0061] The assistance data cells may include a serving cell of the
UE. The serving cell may be the assistance data reference cell, or
the serving cell may be one of the assistance data neighbour
cells.
[0062] The UE 110 may be arranged to determine a time window for
measuring the PRS receive timing relative to serving cell timing
for an assistance data cell other than the serving cell based on
the assistance data and/including the offset information. The UE
110 may be arranged to perform RSTD measurements based on the
assistance data and/including the offset information.
[0063] As described above, the UE 110 may be able to determine the
time window for measuring the PRS of the neighbour cell even when
the serving cell of the UE 110 is different from the assistance
data reference cell and the neighbour cell has PRS muting
enabled.
[0064] As described above, UE 110 may be able to determine the time
window for measuring the PRS of the neighbour cell even when the
serving cell (or any of the serving cells, when there are multiple
serving cells) is not configured to provide PRS.
[0065] As described above, the UE 110 may be able to determine the
time window for measuring the PRS of the assistance data cell even
when the serving cell belongs to a first carrier frequency and all
other assistance data cells including the reference cell belong to
a second carrier frequency.
[0066] The following provides some examples of embodiments of the
invention applied to particular scenarios.
[0067] In the first example, the assistance data reference cell is
not the serving cell, and a neighbour cell has muting
configured.
TABLE-US-00005 Assistance Data Reference Cell (adrc) earfcnRef = 1
T.sub.PRS = 320 .DELTA..sub.PRS = 0 mutingPattern = 11
TABLE-US-00006 Serving cell (sc) and neighbour cell 1 (nc1) Earfcn
= T.sub.PRS = mutingPattern = prs-SubframeOffset = 1 320 11 0
.DELTA..sub.PRS = slotNumberOffset = frameNumberOffset = 0 0 0
neighbour cell 2 (nc2) Earfcn = T.sub.PRS = mutingPattern =
prs-SubframeOffset = 1 320 0100 0 .DELTA..sub.PRS =
slotNumberOffset = frameNumberOffset = 0 0 0
[0068] In this example, if the frameNumberOffset field is not
provided, SFN of the assistance data reference cell is not known at
the UE, and so it is not possible to find the starting position for
neighbour cell 2, which has mutingPattern=0100. According to TS
36.355, when the SFN of the assistance data reference cell is not
known to the UE and prs-MutingInfo is provided for a cell in the
OTDOA-NeighbourCellInfoList IE, the UE may assume no PRS is
transmitted by that cell. Thus, the UE cannot perform PRS
measurements for neighbour cell 2.
[0069] In contrast, if frameNumberOffset is provided in the
assistance data, the UE can determine n.sub.f(adrc) and
n.sub.sf(adrc) from n.sub.f(sc), n.sub.sf(sc),
frameNumberOffset(sc) and slotNumberOffset(sc), where adrc and sc
indicates that the corresponding parameter belongs to the
assistance data reference cell and serving cell, respectively.
[0070] With frameNumberOffset provided for the neighbor cell 1
(serving cell), the UE is able to calculate the frame number and
subframe number of the assistance data reference cell, then the
starting position of the mutingPattern of neighbour cell 2 becomes
known, and the UE can perform RSTD measurements for neighbour cell
2.
[0071] In the second example, the serving cell is not the
assistance data reference cell, and the serving cell does not
transmit PRS.
TABLE-US-00007 Assistance Data Reference Cell (adrc) earfcnRef = 1
T.sub.PRS = 320 .DELTA..sub.PRS = 0 mutingPattern = 11
TABLE-US-00008 Serving cell (sc) and neighbour cell 1 (nc1) Earfcn
= T.sub.PRS = mutingPattern = prs-SubframeOffset = 1 Undefined
Undefined 0 .DELTA..sub.PRS = slotNumberOffset = frameNumberOffset
= Undefined 0 0
TABLE-US-00009 neighbour cell 2 (nc2) Earfcn = T.sub.PRS =
mutingPattern = prs-SubframeOffset = 1 320 0100 0 .DELTA..sub.PRS =
slotNumberOffset = frameNumberOffset = 0 0 0
[0072] In this example, T.sub.PRS and .DELTA..sub.PRS are not
configured for the serving cell, as the serving cell is not
transmitting PRS. Accordingly, in the absence of frameNumberOffset,
the UE is not able to determine PRS for any of the assistance data
cells; assistance data reference cell and neighbour cell 2, in this
example. However, if frameNumberOffset is provided, the UE can
calculate n.sub.f(adrc) and n.sub.sf(adrc) from n.sub.f(sc),
n.sub.sf(sc), frameNumberOffset(ncl) and slotNumberOffset(ncl)
where ncl indicates that the corresponding parameter belongs to the
assistance data neighbor cell 1.
[0073] From these values and T.sub.PRS(adrc) and .DELTA..sub.PRS
(adrc), all PRS timings for assistance data reference cells can be
determined by the UE 110. The PRS timing of neighbour cell 2 can be
determined based on the PRS timing of the assistance data reference
cell. Thus, even though the serving cell does not transmit PRS, the
UE 110 is able to perform RSTD measurements.
[0074] FIG. 6 illustrates a method 600 performed by a UE 110
according to some embodiments. The method 600 starts at 610. At
620, OTDOA assistance data is received by the UE 110. Receiving
OTDOA assistance data includes (i) receiving 630 data indicative of
timings of PRSs for a plurality of neighbour cells, and (ii)
receiving 640 offset information. The offset information indicative
of respective LTE frame offsets between the assistance data
reference cell and the plurality of neighbour cells. The method
terminates at 650, although other actions may be performed as part
of the method, or a subsequent method may begin after 650.
[0075] In some embodiments, the method may include additional
steps, such as determining a time window for measuring a PRS
receive timing of an assistance data cell based on the data
indicative of timings of PRSs and the offset information. The
method may also include performing RSTD measurements and sending a
report of the RSTD measurements, where the RSTD measurements are
given relative to an RSTD reference cell. In some embodiments, the
RSTD reference cell may be different from a serving cell of the
UE.
[0076] FIG. 7 illustrates a method 700 performed by a location
server 120 according to some embodiments. The method 700 begins at
710. At 720 the location server 120 receives a request for
assistance data. The request may originate from a UE, and may
arrive at the location server via a communication network, which
may include wired and/or wireless components. In response to the
request 720, the location server generates 730 assistance data. The
assistance data includes OTDOA parameters describing LTE frame
relations between a plurality of neighbour cells and an assistance
data reference cell, and offset information describing LTE frame
offsets between the assistance data reference cell and the
plurality of neighbour cells. At 740 the location server sends the
assistance data in response to the request 720. The assistance data
may be sent to the UE via the communication system. The method is
shown terminating at 750, although other operations may be
performed in addition to those shown, or another method may begin
when the method 700 terminates.
[0077] In some embodiments, the method 700 may also include
selecting the assistance data reference cell, where the assistance
data reference cell is selected to be different from a serving cell
of the UE.
[0078] The UE 110 and location server 120 described herein may be
implemented using any suitable hardware and/or software. FIG. 8
illustrates an example system 1000 according to some embodiments.
System 1000 includes one or more processor(s) 1040, system control
logic 1020 coupled with at least one of the processor(s) 1040,
system memory 1010 coupled with system control logic 1020,
non-volatile memory (NVM)/storage 1030 coupled with system control
logic 1020, and a network interface 1060 coupled with system
control logic 1020. The system control logic 1020 may also be
coupled to Input/Output devices 1050.
[0079] Processor(s) 1040 may include one or more single-core or
multi-core processors. Processor(s) 1040 may include any
combination of general-purpose processors and dedicated processors
(e.g., graphics processors, application processors, baseband
processors, etc.). Processors 1040 may be operable to carry out the
above described methods, using suitable instructions or programs
(i.e. operate via use of processor, or other logic, instructions).
The instructions may be stored in system memory 1010, as system
memory portion (OTDOA Logic) 1015, or additionally or alternatively
may be stored in (NVM)/storage 1030, as NVM instruction portion
(OTDOA Logic) 1035.
[0080] OTDOA logic 1015 and/or 1035 may include a logic to cause a
processor 1040 to receive offset information and/or extract offset
information from PRS assistance data, as described above. OTDOA
logic 1015 and/or 1035 may also include logic to perform other
OTDOA actions, as described above.
[0081] OTDOA logic 1015 and/or 1035 may include logic to cause a
processor 1040 to determine offset information, as described above.
OTDOA logic 1015 and/or 1035 may also include logic to perform
other OTDOA actions, as described above, such as determining
neighbour data, preparing assistance data based on offset
information and neighbour data and sending the assistance data to a
UE.
[0082] Processors(s) 1040 may be configured to execute the
embodiments of FIGS. 1 to 7 in accordance with various
embodiments.
[0083] System control logic 1020 for one embodiment may include any
suitable interface controllers to provide for any suitable
interface to at least one of the processor(s) 1040 and/or to any
suitable device or component in communication with system control
logic 1020.
[0084] System control logic 1020 for one embodiment may include one
or more memory controller(s) to provide an interface to system
memory 1010. System memory 1010 may be used to load and store data
and/or instructions, for example, for system 1000. System memory
1010 for one embodiment may include any suitable volatile memory,
such as suitable dynamic random access memory (DRAM), for
example.
[0085] NVM/storage 1030 may include one or more tangible,
non-transitory computer-readable media used to store data and/or
instructions, for example. NVM/storage 1030 may include any
suitable non-volatile memory, such as flash memory, for example,
and/or may include any suitable non-volatile storage device(s),
such as one or more hard disk drive(s) (HDD(s)), one or more
compact disk (CD) drive(s), and/or one or more digital versatile
disk (DVD) drive(s), for example.
[0086] The NVM/storage 1030 may include a storage resource
physically part of a device on which the system 1000 is installed
or it may be accessible by, but not necessarily a part of, the
device. For example, the NVM/storage 1030 may be accessed over a
network via the network interface 1060.
[0087] System memory 1010 and NVM/storage 1030 may respectively
include, in particular, temporal and persistent copies of, for
example, the OTDOA logic 1015 and 1035, respectively. OTDOA logic
1015 and 1035 may include instructions that when executed by at
least one of the processor(s) 1040 result in the system 1000
implementing a one or more of methods 600 and/or 700, or the
method(s) of any other embodiment, as described herein. In some
embodiments, instructions 1015 and 1035, or hardware, firmware,
and/or software components thereof, may additionally/alternatively
be located in the system control logic 1020, the network interface
1060, and/or the processor(s) 1040.
[0088] Network interface 1060 may have a transceiver module 1065 to
provide a radio interface for system 1000 to communicate over one
or more network(s) (e.g. wireless communication network) and/or
with any other suitable device. The transceiver 1065 may perform
the various communicating, transmitting and receiving described in
the various embodiments, and may include a transmitter section and
a receiver section. In various embodiments, the transceiver 1065
may be integrated with other components of system 1000. For
example, the transceiver 1065 may include a processor of the
processor(s) 1040, memory of the system memory 1010, and
NVM/Storage of NVM/Storage 1030. Network interface 1060 may include
any suitable hardware and/or firmware. Network interface 1060 may
be operatively coupled to a plurality of antennas to provide a
multiple input, multiple output radio interface. Network interface
1060 for one embodiment may include, for example, a network
adapter, a wireless network adapter, a telephone modem, and/or a
wireless modem. For example, where system 1000 is a location
server, network interface 1060 may include an Ethernet interface,
an S1-MME interface and/or an S1-U interface.
[0089] For one embodiment, at least one of the processor(s) 1040
may be packaged together with logic for one or more controller(s)
of system control logic 1020. For one embodiment, at least one of
the processor(s) 1040 may be packaged together with logic for one
or more controllers of system control logic 1020 to form a System
in Package (SiP). For one embodiment, at least one of the
processor(s) 1040 may be integrated on the same die with logic for
one or more controller(s) of system control logic 1020. For one
embodiment, at least one of the processor(s) 1040 may be integrated
on the same die with logic for one or more controller(s) of system
control logic 1020 to form a System on Chip (SoC). Each of the
processors 1040 may include an input 1040a for receiving data and
an output 1040b for outputting data.
[0090] In various embodiments, the I/O devices 1050 may include
user interfaces designed to enable user interaction with the system
1000, peripheral component interfaces designed to enable peripheral
component interaction with the system 1000, and/or sensors designed
to determine environmental conditions and/or location information
related to the system 1000.
[0091] FIG. 9 shows an embodiment in which the system 1000
implements a UE 110 in the specific form of a mobile device
1100.
[0092] In various embodiments, the user interfaces could include,
but are not limited to, a display 1140 (e.g., a liquid crystal
display, a touch screen display, etc.), a speaker 1130, a
microphone 1190, one or more cameras 1180 (e.g., a still camera
and/or a video camera), a flashlight (e.g., a light emitting diode
flash), and a keyboard 1170.
[0093] In various embodiments, the peripheral component interfaces
may include, but are not limited to, a non-volatile memory port, an
audio jack, and a power supply interface. In various embodiments,
the sensors may include, but are not limited to, a gyro sensor, an
accelerometer, a proximity sensor, an ambient light sensor, and a
positioning unit. The positioning unit may also be part of, or
interact with, the network interface 1060 to communicate with
components of a positioning network, e.g., a global positioning
system (GPS) satellite. In various embodiments, the system 1100 may
be a mobile computing device such as, but not limited to, a laptop
computing device, a tablet computing device, a netbook, a mobile
phone, etc. In various embodiments, system 1100 may have more or
less components, and/or different architectures.
[0094] As used herein, "processing circuitry to/configured
to/arranged to" perform a function comprises at least one of
"hardware configured to", "software configured to" and a
"combination of hardware and software configured to" perform that
function.
[0095] In embodiments, the implemented wireless network may be a
3rd Generation Partnership Project's long term evolution (LTE)
advanced wireless communication standard, which may include, but is
not limited to releases 8, 9, 10, 11 and 12, or later, of the
3GPP's LTE-A standards.
[0096] Although embodiments of the invention are not limited in
this regard, the terms "plurality" and "a plurality" as used herein
may include, for example, "multiple" or "two or more." The terms
"plurality" or "a plurality" may be used herein to describe two or
more components, devices, elements, units, parameters, and the
like. For example, "a plurality of devices" may include two or more
devices.
[0097] Where operations are described as multiple discrete
operations, this is for the purpose of explaining the illustrative
embodiments; however, the order of description should not be
construed as to imply that these operations are necessarily order
dependent. In particular, these operations need not be performed in
the order of presentation. The terms "comprising," "having," and
"including" are synonymous, unless the context dictates otherwise.
The phrase "A/B" means "A or B". The phrase "A and/or B" means
"(A), (B), or (A and B)". The phrase "at least one of A, B and C"
means "(A), (B), (C), (A and B), (A and C), (B and C) or (A, B and
C)". The phrase "(A) B" means "(B) or (A B)", that is, A is
optional.
[0098] Unless contrary to physical possibility, the inventors
envision the methods described herein: (i) may be performed in any
sequence and/or in any combination; and (ii) the components of
respective embodiments may be combined in any manner.
[0099] Although there have been described example embodiments of
this novel invention, many variations and modifications are
possible without departing from the scope of the invention.
Accordingly the inventive embodiments are not limited by the
specific disclosure above, but rather only by the scope of the
appended claims and their legal equivalents.
[0100] Various embodiments can be realized according to the
following clauses:
[0101] 1. A device for use in a mobile communication user
equipment, UE, the device comprising processing circuitry to:
[0102] receive cell data pertaining to a plurality of assistance
data cells, and receive offset information, wherein [0103] the
plurality of assistance data cells includes an assistance data
reference cell and a plurality of neighbour cells, [0104] the cell
data includes: [0105] (i) information to describe timings of
positioning reference signals, PRSs, of the assistance data
reference cell, and [0106] (ii) neighbour information, the
neighbour information to describe timings, relative to the
assistance data reference cell, of positioning reference signals,
PRSs, of the plurality of neighbour cells, and wherein
[0107] The offset information describes respective LTE frame
offsets between the assistance data reference cell and each of the
neighbour cells.
[0108] 2. The device of clause 1, wherein a serving cell of the UE
is the assistance data reference cell or one of the plurality of
neighbour cells.
[0109] 3. The device of clause 2, wherein the processing circuitry
is further to determine a time window relative to a serving cell
timing for measuring a PRS receive timing of an assistance data
cell other than the serving cell based on the cell data and the
offset information.
[0110] 4. The device of clause 3, wherein: the serving cell is
different from the assistance data reference cell; and the
neighbour cell has PRS muting enabled.
[0111] 5. The device of clause 1, wherein: when the UE has one or
more serving cells, and none of the serving cells is configured to
transmit positioning reference signals, the processing circuitry is
further to determine a time window for measuring a PRS receive
timing of an assistance data cell that is not one of the serving
cells based on the neighbour information and the offset
information.
[0112] 6. The device of clause 2, wherein when the serving cell
belongs to a first carrier frequency, and the reference cell and at
least one of the other assistance data cells belong to a second
carrier frequency different from the first carrier frequency, the
processing circuitry is further to perform inter-frequency RSTD
measurements on the second carrier frequency based on the cell data
and the offset information.
[0113] 7. The device of any preceding clause, wherein the offset
information is to be received in an information element that
replaces or updates an information element specified within 3GPP TS
36.355.
[0114] 8. The device of clause 7, wherein the cell data and offset
information are received in the same information element.
[0115] 9. The device of clause 7 or clause 8, wherein the replaced
or updated information element is an OTDOA-NeighbourCellInfoElement
or the offset information replaces prs-SubframeOffset in the
OTDOA-NeighbourCellInfoElement.
[0116] 10. The device of any preceding clause, wherein the
processing circuitry is further to: [0117] perform RSTD
measurements using received PRSs of at least some of the assistance
data cells; and [0118] generate a report based on the RSTD
measurements, the report indicating the RSTD measurements relative
to an RSTD reference cell, wherein the RSTD reference cell is
different from a serving cell of the UE.
[0119] 11. The device of any preceding clause, wherein the
processing circuitry is to receive assistance data, and either:
[0120] the assistance data including the cell data and the offset
information, or [0121] the assistance data includes the cell data,
and the offset information is to be received separately from the
assistance data.
[0122] 12. A user equipment comprising: [0123] the device of any
preceding clause; and [0124] further comprising one or more of: a
screen, a speaker, a touchscreen, a keyboard, an antenna array
including a plurality of antennas, a graphics processor, an
application processor.
[0125] 13. A location server for use in a communication system, the
device to provide positioning assistance data to a user equipment,
UE, the device comprising processing circuitry to: [0126] determine
information describing an assistance data reference cell; [0127]
determine cell data, the cell data to describe relative transmit
timings of positioning reference signals between a plurality of
neighbour cells; [0128] determine offset information describing
respective LTE frame time offsets between the assistance data
reference cell and each of the neighbour cells; and [0129] sending
to the UE data including the information describing the assistance
data reference cell, the cell data, and the offset information;
[0130] wherein the assistance data includes at least the
information describing the assistance data reference cell and the
cell data.
[0131] 14. The location server of clause 13, wherein the assistance
data reference cell is not a serving cell of the UE.
[0132] 15. The location server of clause 13, wherein: [0133] the
plurality of neighbour cells and the assistance data reference cell
are assistance data cells; [0134] a serving cell of the UE is one
of the assistance data cells, and the serving cell of the UE
belongs to a first carrier frequency; [0135] at least one of the
assistance data cells other than the serving cell belong to a
second carrier frequency.
[0136] 16. A method performed by a user equipment, UE, the method
comprising: [0137] receiving Observed Time of Difference Of
Arrival, OTDOA, assistance data, the OTDOA assistance data
including data indicative of timings of positioning reference
signals, PRSs, for a plurality of neighbour cells, the timings
indicated relative to a timing of an assistance data reference
cell, wherein [0138] receiving OTDOA assistance data includes
receiving offset information, the offset information indicative of
respective LTE frame offsets between the assistance data reference
cell and the plurality of neighbour cells.
[0139] 17. The method of clause 16, further comprising determining
a time window for measuring a PRS receive timing of an assistance
data cell based on the data indicative of timings of PRSs and the
offset information, wherein [0140] wherein the assistance data cell
is the assistance data reference cell or a neighbour cell of the
plurality of neighbour cells.
[0141] 18. The method of clause 16 or clause 17, further
comprising: [0142] performing RSTD measurements of one or more
cells, the one or more cells selected from the neighbour cells and
the assistance data reference cell; and [0143] sending a report of
the RSTD measurements, the report indicating the RSTD measurements
relative to an RSTD reference cell, the RSTD reference cell
selected from the one or more cells.
[0144] 19. The method of clause 18, wherein the RSTD reference cell
is different from a serving cell of the UE.
[0145] 20. A method performed by a location server, the method
comprising: [0146] receiving from a user equipment, UE, a request
for Observed Time of Difference Of Arrival, OTDOA, assistance data;
[0147] generating the OTDOA assistance data; and [0148] sending the
generated OTDOA assistance data to the UE, wherein [0149] the OTDOA
assistance data includes offset information describing LTE frame
offsets between the assistance data reference cell and the
plurality of neighbour cells.
[0150] 21. The method of clause 20, further comprising: [0151]
selecting the assistance data reference cell, wherein the
assistance data reference cell is selected to be different from a
serving cell of the UE.
[0152] 22. A user equipment, UE, comprising: [0153] means to
receive OTDOA assistance data; [0154] means to extract, from the
OTDOA assistance data, cell data and offset information, wherein
[0155] the cell data includes information on an assistance data
reference cell and neighbour information, the neighbour information
to describe timings, relative to the assistance data reference
cell, of positioning reference signals, PRSs, of a plurality of
neighbour cells; and [0156] the offset information to describe
respective LTE frame offsets between the assistance data reference
cell and each of the neighbour cells.
[0157] 23. A location server comprising: [0158] means to determine
OTDOA assistance data for a user equipment, UE; [0159] means to
send the OTDOA assistance data to the UE, wherein [0160] the OTDOA
assistance data includes information on an assistance data
reference cell and neighbour data, the neighbour data to describe
relative timings of positioning reference signals between a
plurality of neighbour cells, and [0161] the OTDOA assistance data
includes offset information describing respective LTE frame time
offsets between the assistance data reference cell and each of the
neighbour cells.
[0162] 24. A computer program that when executed by a computer
causes the computer system to perform the method of any one of
clauses 13 to 21 or to perform as the device of any one of clauses
1 to 12, 22 or 23.
[0163] 25. A non-transitory storage machine-readable storage medium
having stored thereon instructions that, when executed by a
computer, cause the computer to perform the method of any one of
clauses 13 to 21, or operate as the apparatus of any one of clauses
1 to 12, 22 or 23.
[0164] 26. A User Equipment, UE, substantially as described herein
with reference to the drawings.
[0165] 27. A location server substantially as described herein with
reference to the drawings.
[0166] 28. A method substantially as described herein with
reference to the drawings.
* * * * *