Note: Descriptions are shown in the official language in which they were submitted.
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
HANDOVER LATENCY REDUCTION
BACKGROUND
[0001] As used herein, terms such as "user equipment" ("UE"), "mobile
station" ("MS"),
"user agent" ("UA"), "user device," and "user node" might in some cases refer
to mobile
devices such as mobile telephones, personal digital assistants, handheld or
laptop
computers, and similar devices that have telecommunications capabilities. Such
terms
can also refer to any hardware or software component (alone or in combination)
that can
terminate a communication session for a user. Such a component might also
include one
or more associated removable memory modules, such as but not limited to a
Universal
Integrated Circuit Card (UICC) that includes a Subscriber Identity Module
(SIM)
application, a Universal Subscriber Identity Module (USIM) application, or a
Removable
User Identity Module (R-UIM) application. Alternatively, such a component
might consist
of a device itself without such a module. In other cases, terms such as "UE"
and the like
might refer to devices that have similar capabilities but that are not
transportable, such as
desktop computers, set-top boxes, or network appliances.
[0002] As telecommunications technology has evolved, more advanced network
access equipment has been introduced that can provide services that were not
previously
possible. This network access equipment might include systems and devices that
are
improvements of the equivalent equipment in a traditional wireless
telecommunications
system. Specifications regarding such advanced or next generation equipment
may be
included in evolving wireless communications standards, such as Long-Term
Evolution
(LTE) and LTE-Advanced (LTE-A). For example, an LTE or LTE-A system might be
an
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and include an
Evolved
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
Node B (or eNB), a wireless access point, a relay node, or a similar component
rather
than a traditional base station. As used herein, the term "eNB" may refer to
"eNBs" but
may also include any of these systems. These components may also be referred
to as
an access node. The terms "eNB" and "access node" may be synonymous in some
embodiments,
BRIEF DESCRIPTION OF THE DRAWINGS
[0003] Reference is now made to the following description, taken in
connection with
the accompanying drawings, wherein like reference numerals may represent like
parts.
[0004] Figure 1 is a schematic diagram of a radio access network that
allows a UE to
communicate with other network components and/or devices, according to an
embodiment of the present disclosure.
[0005] Figure 2 is an example of the definition for prach-Configlndex in
3GPP TS
36.211 V9.2.0, according to an embodiment of the present disclosure.
[0006] Figure 3 is a flow diagram illustrating handover of a UE to E-UTRA,
according
to an embodiment of the present disclosure.
[0007] Figure 4 illustrates a random access procedure for handover to E-
UTRA by
decoding the E-UTRA PBCH in order to determine the two least significant bits
of the E-
UTRA System Frame Number, according to an embodiment of the present
disclosure.
[0008] Figure 5 is a flowchart illustrating a UE's procedure to determine
the E-UTRA
radio frame to perform random access, synchronization indicators, and polarity
determination for PRACH during inter-RAT handover, according to an embodiment
of the
present disclosure.
2
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
[0009] Figure 6 is a flowchart illustrating an exemplary UE procedure
during inter-RAT
handover to determine the E-UTRA radio frame to perform random access,
including a
timing offset indication for the PRACH configuration, according to an
embodiment of the
present disclosure.
[0010] Figure 7 illustrates a processor and related components suitable for
implementing the several embodiments of the present disclosure.
DETAILED DESCRIPTION
[0011] It should be understood at the outset that although illustrative
implementations
of one or more embodiments of the present disclosure are provided below, the
disclosed
systems and/or methods may be implemented using any number of techniques. The
disclosure should in no way be limited to the illustrative implementations,
drawings, and
techniques illustrated below, including the exemplary designs and
implementations
illustrated and described herein, but may be modified within the scope of the
appended
claims along with their full scope of equivalents.
[0012] As used throughout the specification, claims, and Figures, the
following
acronyms have the following definitions. Unless stated otherwise, all terms
are defined
by and follow the standards set forth by the Third Generation Partnership
Program
(3GPP) technical specifications or by the OMA (Open Mobile Alliance).
[0013] "COMA" is defined as "Code Division Multiple Access."
[0014] "CR" is defined as "Change Request."
[0015] " D L" is defined as "DownLink."
[0016] "EDGE" is defined as "Enhanced Data rates for GSM Evolution."
[0017] "E-UTRA" is defined as "Evolved Universal Terrestrial Radio Access."
3
CA 02808232 2013-02-13
WO 2012/020107
PCT/EP2011/063884
[0018] "FDD" is defined as "Frequency Division Duplexing."
[0019] "GERAN" is defined as "GSM EDGE Radio Access Network."
[0020] "GSM" is defined as "Global System for Mobile
communications."
[0021] "HO" is defined as "Handover."
[0022] "HRPD" is defined as "High Rate Packet Data."
[0023] "1E" is defined as "Information Element."
:
" [0024] "LSB" is defined as "Least Significant Bit."
[0025] "LTE" is defined as "Long Term Evolution."
[0026] "MIB" is defined as "Master Information Block."
[0027] "PBCH" is defined as "Physical Broadcast Channel."
[0028] "PRACH" is defined as "Physical Random Access Channel."
[0029] "PSS" is defined as "Primary Synchronization Signal."
[0030] "RA" is defined as "Random Access."
[0031] "RACH" is defined as "Random Access Channel."
[0032] "RAN" is defined as "Radio Access Network."
[0033] "RAT" is defined as "Radio Access Technology."
[0034] "RRC" is defined as "Radio Resource Control."
[0035] "SFN" is defined as "System Frame Number."
[0036] "sss" is defined as "Secondary Synchronization Signal."
[0037] "TDD" is defined as "Time Division Duplexing."
[0038] "TDMA" is defined as "Time Division Multiple Access."
[0039] "UL" is defined as "UpLink."
[0040] "UTRA" is defined as "Universal Terrestrial Radio Access."
4
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
[0041] The
term "may," as used herein, can contemplate embodiments in which an
object or technique is either required, or possible but not required. Thus,
for example,
while the term "may" might be used, in some embodiments the term "may" could
be
replaced by the term "shall" or "must."
[0042] In
one embodiment, the term "frame polarity" is defined as whether the radio
frame has an even or odd SFN (that is, the radio frame has a mod 2 alignment).
However, the embodiments specifically contemplate different alignments. For
example,
the embodiments described herein apply equally well to radio frames with other
alignments, such as mod 4, mod 8, or any other radio frame alignment. Thus, as
used
herein, the term "polarity" is defined as including both mod 2 radio frame
alignment and
other radio frame alignments, including but not limited to mod 4 and mod 8.
[0043] The
embodiments described herein relate to mechanisms to reduce the latency
for a "Handover-to-E-UTRA" procedure, i.e., handover from a source cell with
another
RAT to a target E-UTRA cell. In addition, mechanisms are described to reduce
the
latency for intra-E-UTRA handover, i.e., the source and target cells are both
E-UTRA
cells, when the source and target cells are not synchronized.
[0044] In
particular, signaling may be provided to allow a UE to determine whether the
source and target cells of the handover are synchronized, and/or to determine
a relative
polarity of SFNs in the source and target cells. In an embodiment, both
determinations
may be made based on information received in a single indicator received from
the
source cell.
Still further, if the source and target cells (in a synchronized or
unsynchronized system) can determine the timing offset relative to one
another, then
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
parameters derived from the offset can be signaled to the UE so that the UE
can
determine the target cell frame polarity from the current time value of the
source cell.
[0045] Stated differently, the embodiments relate to inter-RAT handover of
a UE to an
E-UTRAN. If the E-UTRAN PRACH configuration is not the same in all subframes,
it may
be beneficial for the UE to obtain the MIB from the E-UTRAN cell before the UE
can
perform a random access procedure. Obtaining the MIB may add latency to the
handover thereby increasing the interruption time. This latency may occur even
if the two
networks involved in the handover are synchronized, because there is no
mechanism to
inform the UE that the networks are synchronized or to convey information
about the
timing relationship between the networks. Thus, the embodiments provide
mechanisms
to signal to the UE whether or not the networks are synchronized. These
mechanisms
also convey to the UE sufficient timing information so that the UE can perform
a random
access procedure in the E-UTRAN without obtaining the MIB. Multiple
embodiments are
described below.
[0046] Figure 1 is a schematic diagram of a radio access network that
allows a UE to
communicate with other network components and/or devices according to an
embodiment of the disclosure. In particular, Figure 1 illustrates an
embodiment of a RAN
100 that allows a UE to communicate with other network components and/or
devices.
The RAN 100 may be an LTE or LTE-A system, e.g., as described in 3GPP. For
example, an LTE or LTE-A system might include an Evolved Universal Terrestrial
Radio
Access Network (E-UTRAN) Evolved Node B (or eNB), a wireless access point, or
a
similar component. Figure 1 is exemplary and may have other components or
arrangements in other embodiments. In an embodiment, the RAN 100 may comprise
at
6
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
least one access device 110 and at least one UE 120, which may be both located
within a
cell 130. The RAN 100 may also comprise or may be coupled to a network 140.
[0047] As described above, the term "access device" refers to any component
of the
wireless network, such as a traditional base station, a wireless access point,
or an LTE or
LTE-A Evolved Node B or eNB, that creates a geographical area of reception and
transmission coverage allowing a UE 120 or a relay node (not shown) to access
or
communicate with other components in a telecommunications system, such as a
second
UE 120. In this document, the terms "access node" and "access device" may be
used
interchangeably. An access node may include various combinations of hardware
and/or
software.
[0048] The access device 110 may communicate with any UE 120 within the same
cell 130, via a direct link, such as in a UTRAN. The cell 130 may be a
geographical area
1
of reception and transmission coverage. For instance, the direct link may be a
point-to-
point link established between the access device 110 and the UE 120 and used
to
transmit and receive signals between the two. Alternatively, the access
devices 110 may
communicate with any UE 120 in the same cell 130 over shared links, such as in
an E-
UTRAN. For instance, the shared links may comprise an uplink shared channel
and a
downlink shared channel. Additionally, the access device 110 may communicate
with
other components or devices in order to access a network 140 that might use
network
protocols or technologies similar to or different from those used by the RAN
100. In an
embodiment, the UEs 120 may move about between different cells 130 and their
communications may be handed over between the different cells 130, where the
UEs 120
may communicate with different access devices 110.
7
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
[0049] The network 140 may be a wireless network, a wired network, or a
combination
of any wired or wireless networks. The networks may include a Wireless LAN
(WLAN)
network, an Ethernet based network, an Internet Protocol (IP) based network, a
Digital
Subscriber Line (DSL) network, an Optical communications network, and/or any
other
wireless or wired networks that may be used to exchange communications/data
with the
UE 120. The communications/data may comprise voice and/or video calls, emails,
text/media messages (e.g. using Short Message Service (SMS) or Multimedia
Messaging
Service (MMS)), IP data, and/or any other data.
[0050] General description of E-UTRA PRACH configuration
[0051] In E-UTRA system, the eNB configures PRACH configuration for a UE
through
a PRACH-Config Information Element. The PRACH-Config Information Element may
be
defined in 3GPP TS 36.331 V9.3.0 as the following:
ASN 1START
PRACH-ConfigSIB ::= SEQUENCE {
rootSeguencelndex INTEGER (0..837),
prach-Configlnfo PRAC H-Config Info
PRACH-Config ::= SEQUENCE {
rootSeguencelndex INTEGER (0..837),
prach-ConfigInfo P RACH-Config I nfo
OPTIONAL -
- Need ON
8
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
PRACH-ConfigInfo ::= SEQUENCE {
prach-Configlndex INTEGER (0..63),
highSpeedFlag BOOLEAN,
zeroCorrelationZoneConfig INTEGER (0..15),
prach-FreqOffset INTEGER (0..94)
[0052] Within the above PRACH-Config Information Element, prach-ConfigIndex
is
used to define the preamble format, the radio frames, and the subframe numbers
that
may be used to transmit preambles. Figure 2 is an example of the definition
for prach-
ConfigIndex in 3GPP TS 36.211 V9.2Ø In this example, PRACH resources may be
configured either on every radio frame or only on the even-numbered radio
frames. If the
E-UTRA cell configures PRACH to be transmitted only on radio frames with even
SFNs,
then it may be desirable for the UE to know whether the current SFN is even or
odd
before it can transmit on PRACH to access the system.
[0053] Similarly, if the E-UTRA cell configures the PRACH to be transmitted
only on
odd SFNs (which may be the case for a TDD system), then it may also be
desirable for
the UE to know whether the current SFN is even or odd before the UE can
transmit on
the PRACH to access the system.
[0054] Inter-RAT HO to E-UTRA
[0055] Figure 3 is a flow diagram illustrating handover of a UE 300 to an E-
UTRAN
302 from a network having a RAT other than E-UTRA, according to an embodiment
of the
9
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
present disclosure. The procedure shown in Figure 3 may be implemented by a
processor using instructions stored on a medium, such as the processor and
media
shown in Figure 7.
[0056] In an embodiment, the E-UTRAN 302 may transmit an
RRCConnectionReconfiguration message 304 to the UE 300, possibly via another
RAN.
In turn, the UE transmits an RRCConnectionReconfigurationComplete message 306
to
the E-UTRAN. The process terminates thereafter.
[0057] The handover to E-UTRAN procedure shown in Figure 3 may be used when
the network hands over the UE from another RAT to E-UTRA. As described in 3GPP
TS
36.331 V9.3.0, the RAN using another RAT initiates the handover-to-E-UTRA
procedure,
in accordance with the specifications applicable for the other RAT. This
initiation may be
performed by sending the RRCConnectionReconfiguration message via the RAT from
which the inter-RAT handover is performed. Figure 3 shows the signaling flow
for the
handover-to-E-UTRA procedure.
[0058] However, in the case where the target E-UTRA cell configures PRACH
to be
transmitted only on radio frames with even SFNs or only on radio frames with
odd SFNs,
it may be desirable for the UE to know whether the current SFN is even or odd
before it
can access the target E-UTRA cell after handover. Otherwise, the UE might not
be able
to access the target E-UTRA cell or might only be able to access the target E-
UTRA cell
after an additional delay. The embodiments described herein relate to
addressing these
and other issues.
[0059] Based on current E-UTRA specifications, when PRACH resources are not
provisioned in every radio frame, the UE may assume the source and target
radio frames
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
are synchronized at the SFN level within the E-UTRAN. SFN synchronization
implies that
radio frames from the source and target cells are aligned within less than
half a radio
frame length, as observed at the UE. Thus, the UE might not have to wait to
attempt
decoding the PBCH to determine the polarity of the SFN before transmitting on
PRACH.
However, current specifications do not address the case for inter-RAT
handovers.
[0060] Figure 4 illustrates a random access procedure for handover to E-
UTRA by
decoding the E-UTRA PBCH in order to determine the two least significant bits
of the E-
UTRA System Frame Number, according to an embodiment of the present
disclosure.
The procedure shown in Figure 4 may be implemented by a processor using
instructions
stored on a medium, such as the processor and media shown in Figure 7.
[0061] The handover procedure to an E-UTRAN begins at block 400. The UE
obtains
the PSS and SSS (block 402). The UE then determines if the PRACH configuration
is the
same in all radio frames (block 404). If the determination in block 404 is
"yes," then the
UE performs the random access (block 406). The process terminates thereafter.
If the
determination to block 404 is "no," then the UE obtains the MIB by decoding
the PBCH
(block 408). The UE then performs the random access in an appropriate frame
(block
410). The process terminates thereafter.
[0062] This procedure allows a UE to determine the frame polarity (even or
odd) of the
target E-UTRA system and transmit on PRACH. However, the PBCH TTI is a 40ms
interval, which leads to increased handover latency and interruption time. The
embodiments described herein address and decrease this handover latency.
[0063] In an embodiment, a system may exhibit one or more the following
properties:
(a) the random access opportunities are not the same in all radio frames, (b)
zero or more
11
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
cells are synchronized and zero or more are unsynchronized, (c) reading the
SFN of the
target cell takes longer than gaining timing synchronization to the target
cell, and (d) there
is a desire to minimize HO latency and interruption time. In such a system, a
signaling
mechanism (1) may be needed or desired to inform the UE whether a handover is
(un)synchronized and/or (2) may be needed or desired to signal the parameters
to
determine a timing offset and/or relative relationship of the SFNs between the
source and
target cells. Furthermore, in such a system a mechanism may be needed or
desired to
determine when to access the target cell based on the timing of the source
cell without
waiting to read the SFN of the target cell.
[0064]
Regarding the signaling mechanism, the synchronized or unsynchronized state
of the cells can be (a) sent within the message that instructs the UE to
perform the
handover or (b) broadcast in system information by the serving cell stating
whether it is
synchronized to its neighbors. For (b) several bits may be required if some or
all the
neighbors of the serving cell are not synchronized. For example, the signaling
could take
one or more of several different forms. For example, the signaling could be
(1) a list of all
synchronized neighbors that could be signaled, with unlisted neighbors assumed
to be
unsynchronized. In
another example, the signaling could be (2) a list of all
unsynchronized neighbors that could be signaled, with unlisted neighbors
assumed to be
synchronized. In another example, the signaling could be (3) a list of
synchronization
states of other radio access technologies. In another example, the signaling
could be (4)
a list of synchronization states per frequency (and optionally per radio
access
technology). In another example, the signaling could be (5) a range of cell
identities
(optionally per frequency and/or per radio access technology) that are
synchronized, with
12
CA 02808232 2013-02-13
WO 2012/020107
PCT/EP2011/063884
other neighbors assumed to be unsynchronized. In another example, the
signaling could
be (6) a range of cell identities (optionally per frequency and/or per radio
access
technology) that are unsynchronized, with other neighbors assumed to be
synchronized.
In another example, the signaling could be (7) any other encoding that
distinguishes the
group of synchronized neighbors from the group of unsynchronized neighbors.
[0065] If the source cell and target cell are synchronized, a
mechanism may be
, needed or desired to determine the timing and/or relative
relationship of the SFN of the
target from the source. The mechanism could take one of several different
forms. In an
embodiment, the mechanism might be (a) expressed in procedural text of the
standard.
In another embodiment, the mechanism might be (b) expressed in field
descriptions of the
standard. Parameters used to calculate the timing offset may be signaled in
the
handover message, or the relationship could be specified in the handover
message.
[0066] For handovers between unsynchronized cells, if the cells
are able to determine
their timing offset at the time of the handover, then the parameters used to
calculate the
timing offset could be signaled in the handover message, and hence the UE can
determine when to access the target cell without waiting to read the SFN from
the target
cell.
[0067] Specific solutions related to E-UTRA
[0068] If the source and target RANs are synchronized, one of
several mechanisms
may be used for the UE to determine the frame polarity of the target E-UTRA
cell based
on system timing and/or frame number of the source RANs. Frame polarity may be
defined as whether the radio frame has an even or odd SFN. Determining frame
polarity
allows the UE to transmit on the PRACH before decoding the PBCH.
13
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
[0069] If the source and target RANs are unsynchronized, one of several
mechanisms
may be used for the UE to determine the frame polarity of the target E-UTRA
cell and to
transmit on the PRACH before decoding the PBCH. This solution also may apply
to intra-
E-UTRA handover if the source and target cells are not synchronized.
[0070] Figure 5 is a flowchart illustrating a UE's procedure to determine
the E-UTRA
radio frame to perform random access, synchronization indicators, and polarity
determination for PRACH during inter-RAT handover, according to an embodiment
of the
present disclosure. The procedure shown in Figure 5 may be implemented by a
processor using instructions stored on a medium, such as the processor and
media
shown in Figure 7.
[0071] The process begins as the UE begins a handover procedure to an E-UTRAN
(block 500). The UE obtains the PSS and SSS (block 502). The UE determines
whether
the PRACH config is the same in all frames (block 504). If "yes," then the UE
performs
the RA (block 506). The process terminates thereafter.
[0072] If "no", then the UE determines whether the RANs are synchronized
(block
508). If "yes", then the UE determines the SFN polarity (block 510). The UE
then
performs the RA in the appropriate radio frame (block 512). The process
terminates
thereafter.
[0073] Returning to block 508, if the RANs are not synchronized, then the
UE obtains
the MIB (block 514). The UE then performs the RA in the appropriate radio
frame (block
516). The process terminates thereafter.
[0074] Synchronization indicator
14
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
[0075] A synchronization indicator may be used to indicate whether the
source RAN is
synchronized with the target E-UTRA cell for handover purposes. The
synchronization
indicator can be transmitted either in a dedicated message like a handover
command or
in a broadcast message in the source system.
[0076] Synchronization indicator in handover Command to E-UTRA
[0077] One embodiment is to add the synchronization indicator as part of
RRCConnectionReconfiguration message that is sent to the UE during the
handover-to-
E-UTRA procedure. The synchronization indicator indicates whether the source
cell and
target cell are synchronized. The following information element (1E) is an
example of
adding the synchronization flag as the synchronization indicator in the IE
MobilityControl] nfo, which is transmitted within
RRCConnectionReconfiguration, with
changes shown in italics and underlined.
ASN1START
MobilityControl! nfo ::= SEQUENCE {
targetPhysCellId PhysCellId,
carrierFreq CarrierFreqEUTRA
OPTIONAL, Cond
HO-toEUTRA
carrierBandwidth CarrierBandwidthEUTRA
OPTIONAL, -- Cond HO-
toEUTRA
additionalSpectrumEmission AdditionalSpectrumEmission
OPTIONAL, -- Cond
HO-toEUTRA
t30.4 ENUMERATED{
ms50, ms100, ms150, ms200, ms500, ms1000,
ms2000, spare1},
newUE-Identity C-RNTI,
CA 02808232 2013-02-13
WO 2012/020107
PCT/EP2011/063884
radioResourceConfigCommon RadioResourceConfigCommon,
rach-ConfigDedicated RACH-Config Dedicated
OPTIONAL, -- Need
OP
synchronisedInterRalHo BOOLEAN
OPTIONAL, -
Cond SyncHo
CarrierBandwidthEUTRA ::= SEQUENCE {
dl-Bandwidth ENUMERATED {
n6, n15, n25, n50, n75, n100, sparel 0,
spare9, spare8, spare7, spare6, spare5,
spare4, spare3, spare2, spare1},
ul-Bandwidth ENUMERATED {
n6, n15, n25, n50, n75, n100, spare10,
spare9, spare8, spare7, spare6, spare5,
spare4, spare3, spare2, spare1} OPTIONAL --
Need OP
1
CarrierFreqEUTRA SEQUENCE {
dl-CarrierFreq ARFCN-ValueEUTRA,
ul-CarrierFreq ARFCN-ValueEUTRA
OPTIONAL Cond
FDD
}
ASN1STOP
16
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
[0078] Table 1 below shows exemplary MobilityControlinfo field descriptions
for an IE
according to an embodiment of the present disclosure. Table 1 is for the 1E
described
above, with changes in the table shown in italics and underlined.
MobilityControllnfo field descriptions
t304
Timer T304 as described in section 7.3. ms50 corresponds with 50 ms, ms100
corresponds with 100 ms
and so on.
di-Bandwidth
Parameter: Downlink bandwidth, see TS 36.101 [42].
of-Bandwidth
Parameter: Uplink bandwidth, see TS 36.101 [42, table 5.6-11 For TDD, the
parameter is absent and it is
equal to downlink bandwidth. If absent for FDD, apply the same value as
applies for the downlink
bandwidth.
rach-ConfigDedicated
The dedicated random access parameters. If absent the UE applies contention
based random access as
specified in TS 36.321 [6].
carrierBandwidth
Provides the parameters Downlink bandwidth, and Uplink bandwidth, see TS
36.101 [421.
synchronisedInterRatHo
_ TRUE if the source cell is synchronised with the tar et E-UTRA cell. FALSE
otherwise
Conditional presence J Explanation
FDD The field is mandatory with default value (the default
duplex distance defined for
the concerned band, as specified in TS 36.101 [42]) in case of "FDD";
otherwise
the field is not present.
HO-toEUTRA The field is mandatory present in case of inter-RAT
handover to E-UTRA;
otherwise the field is optionally present, need ON.
SyncHo The field is present for synchronised inter-RAT handover to
E-UTRA: otherwise
i it is not present
Table 1
[0079] Alternatively, the synchronization indicator may be added as an
optional field.
Below is an example of a MobilityControlInfo IE for this embodiment, with
changes in
italics and underlined:
ASN1START
MobilityControlinfo ::= SEQUENCE {
17
CA 02808232 2013-02-13
WO 2012/020107
PCT/EP2011/063884
targetPhysCellId PhysCellId,
carrierFreg CarrierFregEUTRA
OPTIONAL, -- Cond
HO-toEUTRA
carrierBandwidth CarrierBandwidthEUTRA
OPTIONAL, -- Cond HO-
toEUTRA
additionalSpectrumEmission AdditionalSpectrum Emission
OPTIONAL, -- Cond
HO-toEUTRA
t304 ENUMERATED {
g
ms50, ms100, ms150, ms200, ms500, ms1000,
ms2000, sparel},
newUE-Identity C-RNTI,
radioResourceConfigCornmon RadioResourceConfigCommon,
rach-ConfigDedicated RACH-Config Dedicated
OPTIONAL, -- Need
OP
=.=,
synchronisedInterRatHo ENUMERATED (TRUE ) OPTIONAL
-- Cond
SyncHo
1
CarrierBandwidthEUTRA ::= SEQUENCE {
dl-Bandwidth ENUMERATED {
n6, n15, n25, n50, n75, n100, spare10,
spare9, spare8, spare7, spare6, spare5,
spare4, spare3, spare2, sparel},
ul-Bandwidth ENUMERATED {
n6, n15, n25, n50, n75, n100, sparel 0,
spare9, spare8, spare7, spare6, spare5,
18
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
spare4, spare3, spare2, sparel) OPTIONAL --
Need OP
CarrierFreqEUTRA ::= SEQUENCE {
di-CarrierFreq ARFCN-ValueEUTRA,
ul-CarrierFreq ARFCN-ValueEUTRA OPTIONAL -- Cond
FDD
ASN1 STOP
[0080] Table 2 below shows exemplary MobilityControlInfo field descriptions
for an IE
according to an embodiment of the present disclosure. Table 2 is for the IE
described
above, with changes in the table shown in italics and underlined.
19
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
MobilityControlinfo field descriptions
t304
Timer T304 as described in section 7.3. ms50 corresponds with 50 ms, ms100
corresponds with 100 ms
and so on.
di-Bandwidth
Parameter: Downlink bandwidth, see TS 36.101 [42].
ul-Bandwidth
Parameter: Uplink bandwidth, see TS 36.101 [42, table 5.6-1]. For TDD, the
parameter is absent and it is
equal to downlink bandwidth. If absent for FDD, apply the same value as
applies for the downlink
bandwidth.
rach-ConfigDedicated
The dedicated random access parameters. If absent the UE applies contention
based random access as
specified in TS 36.321 [6].
carrierBandwidth
Provides the parameters Downlink bandwidth, and Uplink bandwidth, see TS
36.101 [42].
synchronisedinterRatHo
Indicates that the source cell is synchronised with the tartlet E-UTRA
Conditional presence Explanation
FDD The field is mandatory with default value (the default
duplex distance defined for
the concerned band, as specified in TS 36.101 [42]) in case of "FDD";
otherwise
the field is not present.
HO-toEUTRA The field is mandatory present in case of inter-RAT
handover to E-UTRA;
otherwise the field is optionally present, need ON.
SyncHo The field is present for synchronised inter-RAT handoyer to
E-UTRA: otherwise
it is not present
Table 2
[0081] Synchronization indicator in broadcast system information messaoe
transmitted
in source RAN
[0082] Another embodiment may be to add the synchronization indicator in
broadcast
system information in the source cell to indicate whether the source cell is
synchronized
to the target E-UTRA network. This indicator may be added to UTRA, CDMA2000,
and
GERAN system information broadcasts. In addition, an indicator list may be
broadcast,
which includes the synchronization indicators for different neighbor E-UTRA
cells.
[0083] For example, a synchronizedHO BOOLEAN may be added to the broadcast
system information. If the synchronizedHO BOOLEAN is set to TRUE (or if the
optional
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
enumerated (TRUE) field is present), the neighbor E-UTRA cells listed in the
broadcast
system information are cells that are synchronized with the current cell.
Other non-listed
E-UTRA neighbor cells are considered not synchronized with the current cell.
[0084] However, if synchronizedHO BOOLEAN is set to FALSE (or if the
optional
enumerated (FALSE) field is present), the neighbor E-UTRA cells listed in the
broadcast
system information are cells that are not synchronized with the current cell.
Other non-
listed E-UTRA neighbor cells are considered synchronized with the current
cell. In
another embodiment, if synchronizedHO BOOLEAN is set to FALSE (or if the
optional
enumerated (FALSE) field is present), then all neighbor E-UTRA cells
(regardless of
whether or not they are listed in the broadcast system information) are cells
that are not
synchronized with the current cell.
[0086] In another embodiment, synchronizedHO BOOLEAN is not included in the
broadcast system information. Only neighbor E-UTRA cells listed in the
broadcast
system may be cells synchronized with the current cell. In yet another
embodiment, only
neighbor E-UTRA cells listed in the broadcast system may be cells that are not
synchronized with the current cell.
[0086] Mechanisms to determine the polarity of E-UTRA SFN when the source
cell
and target E-UTRA cell are synchronized
[0087] If the source cell and target E-UTRA cell are synchronized, the UE
can
determine the polarity of the target E-UTRA cell SFN based on the system
timing and/or
frame number in the source RAT. A mechanism for determining the polarity of a
target E-
UTRA cell SFN when a source cell is UTRA will now be described. In an UTRA
system,
the frame length may be 10ms, which may be the same as the radio frame length
in the
21
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
E-UTRA system. The UTRA frame number may be 12 bits and the E-UTRA SFN may be
bits. The frame numbers do not need to be the same, but the least-significant
bit
(LSB) is specified to be identical. Thus, if the LSB of the source UTRA frame
number is
0, the UE may interpret the LSB as corresponding to an even-numbered radio
frame in
the target E-UTRA cell.
[0088] If the LSB of the source UTRA frame number is 1, the UE may
interpret it as
corresponding to an odd-numbered radio frame of the target E-UTRA cell.
Alternatively,
the source and target cells could be specified to be aligned with the opposite
polarity of
the LSB. The following is an example of a CR in TS36.211 which may be used to
describe the changes in the specifications for the matching polarity
alternative. Changes
are shown in italics and underlined.
5.7.1 Time and frequency structure
For frame structure type 1 with preamble format 0-3, there is at most one
random access resource per
subframe. Table 5.7.1-2 lists the preamble formats according to Table 5.7.1-1
and the subframes in
which random access preamble transmission is allowed for a given configuration
in frame structure type
1. The parameter prach-Configurationlndex is given by higher layers. The start
of the random access
preamble shall be aligned with the start of the corresponding uplink subframe
at the UE assuming
NTA = where NTA is defined in section 8.1. For PRACH configuration 0, 1, 2,
15, 16, 17, '18, 31, 32,
33, 34, 47, 48, 49, 50 and 63 the UE may for intra-EUTRA handover purposes
assume an absolute
value of the relative time difference between radio frame i in the current
cell and the target cell of less
than 153600 -15. For inter-RAT handover to EUTRA, for PRACH configuration O.
1, 2, 15, 16, 17, 18,
31, 32, 33, 34, 47, 48, 49, 50 and 63, and if the target E-UTRA cell is
synchronized with the source
UTRA cell for handover purposes, the UE may assume an absolute value of the
relative time difference
between the start of an odd (or even) radio frame in the current UTRA cell and
the start of an odd (or
even) radio frame in the target EUTRA cell of less than 153600 T5 The first
physical resource block
22
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
RA
nPRB allocated to the PRACH opportunity considered for preamble format 0, 1, 2
and 3 is defined as
RA _RA
nRA-
PRB PR8')ffiel , where the parameter prach-FrequencyOffset ""w` is
expressed as a physical
< ATILT A
resource block number configured by higher layers and fulfilling
,,PRBoffsel Y RD
For frame structure type 2 with preamble format 0-4, there might be multiple
random access resources
in an UL subframe (or UpPTS for preamble format 4) depending on the UL/DL
configuration see table
4.2-2]. Table 5.7.1-3 lists PRACH configurations allowed for frame structure
type 2 where the
configuration index corresponds to a certain combination of preamble format,
PRACH density value,
DRA , and version index, rRA . The parameter prach-Configurationlndex is given
by higher layers. For
frame structure 2 PRACH configuration 0, 1, 2, 20, 21, 22, 30, 31, 32, 40, 41,
42, 48, 49 and 50, the UE
may for intra-EUTRA handover purposes assume an absolute value of the relative
time difference
between radio frame i in the current cell and the target cell is less than
153600 T. For inter-RAT
handover to EUTRA, for PRACH confi.guration 0, 1, 2, 20, 21, 22, 30, 31, 32,
40, 41, 42, 48, 49 and 50,
and if the target E-UTRA cell is synchronized with the source UTRA cell for
handover purposes, the UE
may assume an absolute value of the relative time difference between the start
of an odd (or even)
radio frame in the current UTRA cell and the start of an odd (or even) radio
frame in the target EUTRA
cell of less than 153600 Ts,
[0089] Furthermore, the changes for the matching polarity alternative can
be
incorporated in the procedural description in TS36.331 along with the
synchronization
indicator described below. Following is an example of one of the embodiments,
with
changes shown in italics and underlined:
5.4.2.3 Reception of the RRCConnectionReconfiguration by the UE
23
CA 02808232 2013-02-13
WO 2012/020107
PCT/EP2011/063884
If the UE is able to comply with the configuration included in the
RRCConnectionReconfiguration
message, the UE shall:
1> apply the default physical channel configuration as specified in 9.2.4;
1> apply the default semi-persistent scheduling configuration as specified in
9.2.3;
1> apply the default MAC main configuration as specified in 9.2.2;
1> start timer T304 with the timer value set to t304, as included in the
mobilityControlInfo;
1> consider the target cell to be one on the frequency indicated by the
carrierFreq with a
physical cell identity indicated by the targetPhysCellId;
1> start synchronising to the DL of the target cell;
1> set the C-RNTI to the value of the newUE-Identity;
1> for the target cell, apply the downlink bandwidth indicated by the dl-
Bandwidth;
1> for the target cell, apply the uplink bandwidth indicated by (the absence
or presence of)
the ul-Bandwidth;
1> for the target cell. if synchronisedInterRATHo indicates that the target
cell is synchronized
with the source cell:
2> if the
prach-ConfigurationIndex has one of the following values for FDD: 0, 1, 2,
15, 16, 17, 18, 31, 32, 33, 34, 47, 48, 49, 50 and 63 or one of the following
values
for TDD: 0, 1, 2, 20, 21, 22, 30, 31, 32, 40, 41, 42, 48, 49 and 50:
3> determine the E-UTRA SFN as even or odd as follows: if the LSB of the UTRA
SFN is a the corresponding E-UTRA SFN is an even value. If the LSB of the
UTRA frame number is 1, the corresponding E-UTRA SFN is an odd value.
3> The UE is not required to determine the SFN of the tamet cell by acquiring
system
information from that cell before performing RA CH access in the target cell:
24
CA 02808232 2013-02-13
WO 2012/020107
PCT/EP2011/063884
1> else
2> the UE is required to determine the SFN of the target cell by acquiring
system
information from that cell before performing RACH access in the target cell.
1> perform the radio resource configuration procedure as specified in 5.3.10;
1> forward the nas-SecurityParamToEUTRA to the upper layers;
1> derive the KeNB key, as specified in TS 33.401 [32];
1> derive the KRRGint key associated with the integrityProtAlgorithm, as
specified in TS 33.401
[32];
1> derive the KRRcene key and the KUPenc key associated with the
cipheringAlgorithm, as
specified in TS 33.401 [32];
1> configure lower layers to apply the indicated integrity protection
algorithm and the K.
-
key immediately, i.e. the indicated integrity protection configuration shall
be applied to all
subsequent messages received and sent by the UE, including the message used to
indicate the successful completion of the procedure;
1> configure lower layers to apply the indicated ciphering algorithm, the
KRRcen, key and the
Kupenc key immediately, i.e. the indicated ciphering configuration shall be
applied to all
subsequent messages received and sent by the UE, including the message used to
indicate the successful completion of the procedure;
1> if the RRCConnectionReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> if the RRCConnectionReconfiguration message includes the
reportProximityConfig:
2> perform the proximity indication configuration in accordance with the
received
reportProximityConfig;
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
1> submit the RRCConnectionReconfigurationComplete message to lower layers for
transmission using the new configuration;
1> if the RRCConnectionReconfiguration message does not include the rlf-
TimersAndConstants:
2> use the default values specified in 9.2.5 for timer T310, T311 and constant
N310, N311;
1> if MAC successfully completes the random access procedure:
2> stop timer T304;
2> apply the parts of the Cal reporting configuration, the scheduling request
configuration
and the sounding RS configuration that do not require the UE to know the SFN
of the
target cell, if any;
2> apply the parts of the measurement and the radio resource configuration
that require
the UE to know the SFN of the target cell (e.g. measurement gaps, periodic Cal
reporting, scheduling request configuration, sounding RS configuration), if
any, upon
acquiring the SFN of the target cell;
2> enter E-UTRA RRC_CONNECTED, upon which the procedure ends;
[0090] Furthermore, the changes may be incorporated in the field
description of the
MobilityControlInfo IE in TS36.331 as part of the synchronization indicator
description.
The following example shows one embodiment of a MobilityControlInfo IE for
determining
the LSB of E-UTRAN SFN from the UTRA frame number, with changes shown in
italics
and underlined.
ASN1START
MobilityControlInfo ::= SEQUENCE {
targetPhysCeilld PhysCellId,
26
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
carrierFreq CarrierFreqEUTRA OPTIONAL, -- Cond
HO-toEUTRA
carrierBandwidth CarrierBandwidthEUTRA
OPTIONAL, -- Cond HO-
toEUTRA
additionalSpectrumEmission AdditionalSpectrum Emission OPTIONAL, --
Cond
HO-toEUTRA
1304 ENUMERATED(
ms50, ms100, ms150, ms200, ms500, ms1000,
ms2000, spare1},
newUE-Identity C-RNTI,
radioResourceConfigCommon RadioResourceConfigCommon,
rach-ConfigDedicated RACH-ConfigDedicated OPTIONAL, -- Need
OP
slinchronisedInterRatHo ENUMERATED { TRUE OPTIONAL Cond
SyncHo
CarrierBandwidthEUTRA ::= SEQUENCE {
dl-Bandwidth ENUMERATED {
n6, n15, n25, n50, n75, n100, sparel 0,
spare9, spare8, spare7, spare6, spare5,
spare4, spare3, spare2, sparel},
ul-Bandwidth ENUMERATED {
n6, n15, n25, n50, n75, n100, sparel 0,
spare9, spare8, spare7, spare6, spare5,
spare4, spare3, spare2, sparell OPTIONAL --
Need OP
27
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
CarrierFreqEUTRA ::= SEQUENCE {
dl-CarrierFreq ARFCN-ValueEUTRA,
ul-CarrierFreq ARFCN-ValueEUTRA OPTIONAL -- Cond
FDD
ASN1STOP
[0091] Table 3 below shows exemplary MobilityControlInfo field descriptions
for an IE
according to an embodiment of the present disclosure. Table 3 is for the IE
described
above, with changes in the table shown in italics and underlined.
28
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
MobilityControlinfo field descriptions
t304
Timer T304 as described in section 7.3. ms50 corresponds with 50 ms, ms100
corresponds with 100 ms
and so on.
dl-Bandwidth
Parameter: Downlink bandwidth, see TS 36.101 [42].
ul-Bandwidth
Parameter: Uplink bandwidth, see TS 36.101 [42, table 5.6-'1]. For TDD, the
parameter is absent and it is
equal to downlink bandwidth. If absent for FDD, apply the same value as
applies for the downlink
bandwidth.
rach-ConfigDedicated
The dedicated random access parameters. If absent the UE applies contention
based random access as
specified in TS 36.321 [6].
carrierBandwidth
Provides the parameters Downlink bandwidth, and Uplink bandwidth, see TS
36.101 [42].
synchronisedinterRatHo
Indicates that the source cell is synchronised with the target EUTRA cell
For HO from UTRA the UE may assume that the LSB of E-UTRA SFN = LSB of UTRA
SFN
Conditional presence Explanation
FDD The field is mandatory with default value (the default
duplex distance defined for
the concerned band, as specified in TS 36.101 [42]) in case of "FDD";
otherwise
the field is not present.
HO-toEUTRA The field is mandatory present in case of inter-RAT
handover to E-UTRA;
otherwise the field is optionally present, need ON.
SyncHo The field is present for synchronised inter-RAT handover to E-
UTRA: otherwise
it is not present.
Table 3
[0092] In
another embodiment, if a UTRA cell and an E-UTRA cell are considered to
be frame-synchronized, the ten least significant bits of the 12-bit UTRA frame
number
may be considered to be identical to the 10-bit E-UTRA frame number.
[0093]
Determine the polarity of E-UTRA system frame number when source cell is
GERAN
[0094] In
a GERAN system, a 26-multiframe may have a time length of 120 ms as
defined in 3GPP TS 45.002 V8Ø0. Thus, if the source GERAN cell is specified
to
synchronize the start of each 26-multiframe with an even-numbered radio frame
in the
target E-UTRA system, the UE can derive the polarity of the target E-UTRA cell
based on
29
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
the 26-multiframe number in the source GERAN cell. This procedure allows the
UE to
transmit on the PRACH in the target E-UTRA cell without waiting to decode the
PBCH.
Alternatively, the start of each 26-multifrarne can be specified to be
synchronized with an
odd-numbered radio frame in an E-UTRAN.
[0095] The following is an example of a CR for TS36.211, which may be used
to
describe the changes in the specifications. Changes are shown in italics and
underlined.
Alternatively, this mechanism can be specified in either the procedural text
in TS 36.331
or in the field descriptions of TS 36.331, similar to the examples in the
previous section.
5.7.1 Time and frequency structure
=
For frame structure type 1 with preamble format 0-3, there is at most one
random access resource
per subframe. Table 5.7.1-2 lists the preamble formats according to Table
5.7.1-1 and the
subframes in which random access preamble transmission is allowed for a given
configuration in
frame structure type 1. The parameter prach-Configurationlndex is given by
higher layers. The start
of the random access preamble shall be aligned with the start of the
corresponding uplink subframe
at the UE assuming NTA =0 , where NTA is defined in section 8.1. For PRACH
configurations 0, 1,
2, 15, 16, 17, 18, 31, 32, 33, 34, 47, 48, 49, 50 and 63 the UE may for intra-
EUTRA handover
purposes assume an absolute value of the relative time difference between
radio frame i in the
current cell and the target cell of less than 153600. Ts . For PRACH
configuration O. 1, 2, 15, 16, 17,
18, 31, 32, 33. 34, 47, 48, 49, 50 and 63, and if the target E-UTRA cell is
synchronized with the
source GERAN cell for handover purposes, the UE may assume an absolute value
of the relative
time difference between the start of each 26-multiframe in the current GERAN
cell, where a 26-
multiframe is defined in Section 4.3.3 of 3GPP TS 45.002 V8Ø0, and the start
of an even-
numbered EUTRA frame in the target EUTRA ceIl of less than 153600 T. The first
physical
resource block niVB allocated to the PRACH opportunity considered for preamble
formats 0, 1, 2
and 3 is defined as na
= offset where the parameter prach-FrequencyOffset,
nr¨offiet is
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
expressed as a physical resource block number configured by higher layers and
fulfilling
XJUL
0 < < _ 6.
For frame structure type 2 with preamble formats 0-4, there might be multiple
random access
resources in an UL subframe (or UpPTS for preamble format 4) depending on the
UL/DL
configuration [see table 4.2-2]. Table 5.7.1-3 lists PRACH configurations
allowed for frame structure
type 2 where the configuration index corresponds to a certain combination of
preamble format,
PRACH density value, DRA and version index, rRA . The parameter prach-
Configurationlndex is
given by higher layers. For frame structure type 2 with PRACH configuration 0,
1, 2, 20, 21, 22, 30,
31, 32, 40, 41, 42, 48, 49 or 50, the UE may for intra-EUTRA handover purposes
assume an
absolute value of the relative time difference between radio frame i in the
current cell and the target
cell is less than 153600. Ts . For frame structure 2 PRACH configuration 0, 1,
2, 20, 21, 22, 30, 31,
32, 40, 41, 42, 48, 49 and 50, and if the tartlet E-UTRA cell is synchronized
with the source GERAN
cell for handover purposes, the UE may assume an absolute value of the
relative time difference
between the start of each 26-multiframe in the current GERAN cell (where a 26-
multiframe is
defined in Section 4.3.3 of 3GPP TS 45.002 V8Ø0) and the start of an even-
numbered EUTRA
frame in the target EUTRA cell of less than 153600 Ts,
[0096] Determine the Polarity of E-UTRA SFN when source cell is CDMA2000-
1xRTT
[0097] In a CDMA2000-1xRTT system, the frame length may be 20ms. There may be
at least two ways to determine the frame polarity of the target E-UTRA system
as long as
the CDMA2000-1xRTT frame timing and the E-UTRA radio frame timing are
synchronized.
[0098] In one embodiment, the UE may determine the target E-UTRA frame
boundary
based on the half-frame boundary in the source CDMA2000-1xRTT system. For
example, the UE can assume that the first half of the CDMA2000-1xRTT frame
31
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
corresponds to an odd-numbered radio frame in the target E-UTRA cell and that
the
second half of the CDMA2000-1xRTT frame corresponds to an even-numbered radio
frame in the target E-UTRA cell. Alternatively, the UE can assume that first
half of the
CDMA2000-1xRTT frame corresponds to an even-numbered radio frame in the target
E-
UTRA cell and that the second half of the CDMA2000-1xRTT frame corresponds to
an
odd-numbered radio frame in the target E-UTRA cell.
[0099] In another embodiment, the UE may determine the frame polarity of
the target
E-UTRA system based on the CDMA system time in the source CDMA2000-1xRTT
system. For example, if ceiling (`CDMA system time/10ms) has an odd value,
then the
UE may assume it corresponds to an odd-numbered radio frame in the target E-
UTRA
cell; else if ceiling (`CDMA system time'/10ms) has an even value, then the UE
may
assume it corresponds to an even-numbered radio frame in the target E-UTRA
system.
Other examples include using floor or modular functions.
[00100] For both embodiments described above, the relative time offset between
the
CDMA2000-1xRTT 20nns frame boundary and the E-UTRA radio frame boundary may be
1
I
additionally signaled to the UE. The UE may first adjust the frame boundary or
system
time of the source CDMA2000-1xRTT cell with this relative time offset, and
then use the
adjusted results to determine the polarity of the SFN of the target E-UTRA
cell.
[00101] Determine the polarity of E-UTRA SFN when source cell is CDMA2000-HRPD
[00102] In a CDMA2000-HRPD (i.e., 1xEV-DO) system, the frame length may be
26.667ms, which includes 16 slots where each slot is 1.667ms, Six HRPD slots
may
equal 10ms.
32
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
[00103] In one embodiment, the UE may calculate the HRPD slot number based on
the
CDMA system time using the following formula: (floor ('CDMA system time' /
'slot
duration'). Then the UE may determine the frame polarity (even/odd) of the
target E-
UTRA system based on slot number. For example, if floor ('slot number/ 6) is
an odd
value, then the UE assumes it corresponds to an odd-numbered radio frame in
the target
E-UTRA cell; else if floor ('slot number' / 6) is an even value, then the UE
assumes it
corresponds to an even-numbered radio frame in the target E-UTRA cell.
[00104] In another embodiment, the UE may determine the frame polarity of the
target
E-UTRA system based on the CDMA system time in the source CDMA2000-1xRTT
system as described below. For example, if ceiling ('CDMA system time'/10ms)
is an odd
value, then the UE may assume it corresponds to an odd-numbered radio frame in
the
target E-UTRA cell; else if ceiling ('CDMA system tinneTIOms) is an even
value, then the
UE may assume it corresponds to an even-numbered radio frame in the target E-
UTRA
cell. Other examples include using floor or modular function.
[00105] For both embodiments, the relative time offset between the CDMA2000-
HRPD
10ms system time boundary and the E-UTRA radio frame boundary may be
additionally
signaled to the UE. The UE first may adjust the frame boundary or system time
of the
source CDMA2000-HRPD cell with this relative time offset and then use the
adjusted
results to determine the polarity of the SFN of the target E-UTRA cell.
[00106] Mechanism to determine the polarity of E-UTRA SFN when the source and
target system are not synchronized
[00107] Figure 6 is a flowchart illustrating an exemplary UE procedure during
inter-RAT
handover to determine the radio frame to perform RA, including a timing offset
indication
33
CA 02808232 2013-02-13
WO 2012/020107
PCT/EP2011/063884
for the PRACH configuration, according to an embodiment of the present
disclosure. The
procedure shown in Figure 6 may be implemented by a processor using
instructions
stored on a medium, such as the processor and media shown in Figure 7.
[00108] The process begins as the UE starts a handover procedure to an E-UTRAN
(block 600). The UE obtains the PSS and SSS (block 602). The UE then makes a
determination whether the PRACH config is the same in all frames (block 604).
If "yes,"
i then the UE performs the RA (block 606). The process terminates
thereafter.
[00'109] Returning to block 604, if the PRACH config is not the same in all
radio frames,
then the UE determines if the timing offset is included (block 608). If "yes,"
then the UE
determines the SFN polarity (block 610). The UE then performs the RA in an
appropriate
frame (block 612). The process terminates thereafter.
[00110] Returning to block 608, if the UE determines that the timing offset is
not
included, then the UE obtains the MIB (block 614). The UE then performs the RA
in an
appropriate radio frame (block 616). The process terminates thereafter.
[00111] Note that this embodiment has an optional structure. If a
synchronization
indication is not present, then the handover may be unsynchronized.
If the
synchronization indication is present, then the branch and value of the choice
structure
gives the parameters to determine the alignment of the cells. Thus, in an
embodiment,
there is no separate indicator to signal whether the cells are synchronized or
not.
Accordingly, in addition to the synchronization indication being signaled and
the alignment
being separately signaled, there may be a mechanism to signal both of them in
one
object. Furthermore, if the networks are always synchronized (but not
aligned), then only
the parameters to determine the offset might need to be signaled and no
synchronization
34
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
indicator is needed. Additionally, if source and target cells (in a
synchronized or
unsynchronized system) can determine their timing offset, then parameters
derived from
the offset can be signaled to the UE so that it can determine the target cell
polarity from
the current time value of the source cell.
[00112] In the event that a synchronized network (either intra-RAT or inter-
RAT) is not
being maintained, it may be expected that the frame timing of different base
stations
would gradually drift relative to each other. For example, one base station's
frames may
be slightly shorter than 10 ms, while a second base station's frames may be
slightly
longer than 10 ms. Even if the frame numbering of the two base stations is
aligned at
start-up, their frame numberings may gradually diverge due to the slight
difference in
actual frame lengths. In such a non-synchronized network, it may still be
possible to
initiate an E-UTRA random access prior to acquiring the target cell's MI6 (for
SFN
information) using the following approach.
[00113] First, during the handover negotiation on the network side, the source
cell and
target cell determine their frame numbering and system timing relative to each
other.
This can be performed over the backhaul link or by wirelessly reading the MII3
of the other
cell. This can be performed periodically or upon demand. In another alternate
embodiment, each cell may be provided the SFN and frame timing information of
its
neighbor cells from a network entity, such as a self-organizing network (SON)
manager or
some 0A&M (Operations, Administration & Management) entity.
[00114] Second, as part of the handover command (e.g., as part of the
MobilityControlinfo information element), the UE may be informed of a timing
adjustment
that it should make to the system timing of the source cell (which may be an E-
UTRA or
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
non-E-UTRA cell) in order to obtain sufficient information about the target
cell's system
timing such that the UE can infer the E-UTRA system frame polarity (odd or
even) of the
E-UTRA target cell. This procedure may allow the UE to determine sufficient
information
about the target cell's SFN in order that a random access procedure can be
initiated even
if PRACH resources are not provisioned by the target cell within every radio
frame.
[00116] The system timing adjustment may be signaled using time units based
either
on seconds (e.g., ms) or on the source cell's frame length (e.g., half-frames
or quarter-
frames). The timing unit selected for use could depend on the desired accuracy
of
relative timing synchronization between the two cells after the system timing
adjustment
has been applied. Note that a timing adjustment granularity of T may imply
that a relative
timing synchronization within T/2 can be achieved. For example, if the system
timing
adjustment is signaled in units of 1 ms, then a relative timing
synchronization of 0.5 ms
may be achievable. As another example, if the system timing adjustment is
signaled in
units of quarter-frames (e.g., 2.5 ms for UTRAN and E-UTRAN), then a relative
timing
synchronization of VS of a frame (i.e., 1.25 ms) may be achievable.
(00116] The number of bits required or desired for signaling the system timing
adjustment may depend on the selected signaling granularity and the source
RAT. This
number of bits may be calculated as log2(P/T), where P is the period (in ms)
before an
odd (or even) source cell frame pattern repeats, and T is the selected
signaling
granularity measured in ms. (If the signaling granularity is in units of frame
fractions, then
convert to ms first before applying this formula.)
[00117] For UTRAN and E-UTRAN, P may be 20 ms based on the occurrence of an
odd and even frame pair. For CDMA2000, P may be 20 ms based on the total
length of
36
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
each CDMA2000 frame. For GERAN, P may be 120 ms based on the length of a 26-
multiframe.
[00118] As an example, the selected system timing adjustment signaling
granularity
might be T=2.5 ms, which represents a quarter-frame (for E-UTRA and UTRA).
Timing
adjustments would therefore be signaled in units of quarter-frames (which have
a time
length of 2.5 ms). This signaling allows the compensated timing between the
source and
target cells to be synchronized within 1,25 ms. This signaling may require
three
signaling bits covering a range of 0 to 7 for handover from E-UTRAN, UTRAN,
and
CDMA2000. This signaling may require six signaling bits covering a range of 0
to 47
(units of T=2,5 ms) or 0 to 51 (units of half TDMA frames, Th2.3 ms) for
handover from
GERAN.
[00119] When the UE receives a signaled system timing adjustment in a handover
command, the UE may calculate the target cell's relative system time (for the
purpose of
determining of frame polarity in the target cell) as: (Target cell relative
system time) =
(Source cell system time) + (A x T), where A is the signaled timing adjustment
and T is
the signaling granularity of the timing adjustment. Frame polarity alignment
between the
source and target cells may be defined here as the start of a source cell even
(or odd)
frame being less than 5 ms (less than half an E-UTRA radio frame) away from
the start of
a known even (or odd) target cell frame, as observed at the UE.
[00120] The following is an example of adding the time offset in the IE
MobilityControll nfo, which is transmitted within RRCConnectionReconfiguration
during the
handover procedure. In this example, timing adjustments are signaled in units
of quarter-
frames for E-UTRA and UTRA (a quarter-frame has a time length of 2.5 ms) and
in units
37
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
of half-TDMA-frames for GERAN (a half-TDMA-frame has a time length of ¨2.3
ms). The
following exemplary IE is not meant to be limiting, and other granularity
units for these
timing adjustments may be used. Changes are shown in italics and underlined.
ASN1START
MobilityControllnfo ::= SEQUENCE {
targetPhysCellId PhysCellId,
carrierFreq CarrierFreqEUTRA
OPTIONAL, -- Cond
HO-toEUTRA
carrierBandwidth CarrierBandwidthEUTRA
OPTIONAL, -- Cond HO-
toEUTRA
additionalSpectrumEmission AdditionalSpectrunnErnission
OPTIONAL, -- Cond
HO-toEUTRA
t304 ENUMERATED{
ms50, ms100, ms150, ms200, ms500, ms1000,
ms2000, sparel},
newUE-Identity C-RNTI,
radioResourceConfigCommon RadioResourceConfigComnnon,
rach-Config Dedicated RACH-ConfigDedicated
OPTIONAL, -- Need
OP
timingOffset CHOICE f
deranOffset INTEGER(0..51),
utranOffset INTEGER(0..7),
cdma20000ffset INTEGER(0..7)
OPTIONAL Cond
SyncHo
38
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
CarrierBandwidthEUTRA ::= SEQUENCE {
dl-Bandwidth ENUMERATED {
n6, n15, n25, n50, n75, n100, sparel 0,
spare9, spare8, spare7, spare6, spare5,
spare4, spare3, spare2, spare1},
ul-Bandwidth ENUMERATED {
n6, n15, n25, n50, n75, n100, sparel 0,
spare9, spare8, spare7, spare6, spare5,
spare4, spare3, spare2, sparell OPTIONAL --
Need OP
CarrierFreqEUTRA ::= SEQUENCE {
dl-CarrierFreq ARFCN-ValueEUTRA,
ul-CarrierFreq ARFCN-ValueEUTRA OPTIONAL -- Cond
FDD
ASN1STOP
[001211 Table 4 below shows exemplary MobilityControllnfo field descriptions
for an IE
according to an embodiment of the present disclosure. Table 4 is for the IE
described
above, with changes in the table shown in italics and underlined.
39
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
MobilityControlInfo field descriptions
t304
Timer T304 as described in section 7.3. ms50 corresponds with 50 ms, ms100
corresponds with 100 ms
and so on.
dl-Bandwidth
Parameter: Downlink bandwidth, see TS 36.101 [42].
ul-Bandwidth
Parameter: Uplink bandwidth, see TS 36.101 [42, table 5.6-1]. For TDD, the
parameter is absent and it is
equal to downlink bandwidth. If absent for FDD, apply the same value as
applies for the downlink
bandwidth.
rach-ConfigDedicated
The dedicated random access parameters. If absent the UE applies contention
based random access as
specified in TS 36.321 [6].
carrierBandwidth
Provides the parameters Downlink bandwidth, and Uplink bandwidth, see TS
36.101 [42].
timinuOffset
This field is used to calculate the timing offset between the source and
target cells.
For UTRA and EUTRA, the time offset is in units of quarter radio frame, i.e.,
2.5ms.
For GERAN, the time offset is in units of half-TDMA frame of GERAN.
Conditional presence Explanation
FDD The field is mandatory with default value (the default
duplex distance defined for
the concerned band, as specified in TS 36.101 [42]) in case of "FDD";
otherwise
the field is not present.
HO-toEUTRA The field is mandatory present in case of inter-RAT
handover to E-LITRA;
otherwise the field is optionally present, need ON.
SyncHo The field is present for synchronised inter-RAT handover to
E-UTRA; otherwise
it is not present.
Table 4
[00122] The embodiments described herein provide a number of benefits over the
technical standards mentioned herein. In particular, the embodiments described
herein
reduce the handover to E-UTRA latency and reduce the handover to E-UTRA
interruption
time. Additionally, the embodiments provide a mechanism for determining the
relative
timing offset, or frame polarity, for determining PRACH resource locations in
the target
cell during a handover procedure.
[00123] The UE and other components described above might include processing
and
other components that alone or in combination are capable of executing
instructions or
otherwise able to promote the occurrence .of the actions described above.
Figure 7
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
illustrates an example of a system 1100 that includes a processing component,
such as
processor 1110, suitable for implementing one or more embodiments disclosed
herein.
Accordingly, system 1100 may be employed to execute one or more of the
previously-
described embodiments. In addition to the processor 1110 (which may be
referred to as
a central processor unit or CPU), the system 1100 might include network
connectivity
devices 1120, random access memory (RAM) 1130, read only memory (ROM) 1140,
secondary storage 1150, and input/output (1/0) devices 1160. These components
might
communicate with one another via a bus 1170. In some cases, some of these
components may not be present or may be combined in various combinations with
one
another or with other components not shown. These components might be located
in a
single physical entity or in more than one physical entity. Any actions
described herein as
being taken by the processor 1110 might be taken by the processor 1110 alone
or by the
processor 1110 in conjunction with one or more components shown or not shown
in the
drawing, such as a digital signal processor (DSP) 1180. Although the DSP 1180
is
shown as a separate component, the DSP 1180 might be incorporated into the
processor
1110.
[00124] The processor 1110 executes instructions, codes, computer programs, or
scripts that it might access from the network connectivity devices 1120, RAM
1130, ROM
1140, or secondary storage 1150 (which might include various disk-based
systems such
as hard disk, floppy disk, or optical disk). While only one CPU 1110 is shown,
multiple
processors may be present. Thus, while instructions may be discussed as being
executed by a processor, the instructions may be executed simultaneously,
serially, or
41
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
otherwise by one or multiple processors. The processor 1110 may be implemented
as
one or more CPU chips.
[00125) The network connectivity devices 1120 may take the form of modems,
modem
banks, Ethernet devices, universal serial bus (USB) interface devices, serial
interfaces,
token ring devices, fiber distributed data interface (FDDI) devices, wireless
local area
network (WLAN) devices, radio transceiver devices such as code division
multiple access
(CDMA) devices, global system for mobile communications (GSM) radio
transceiver
devices, universal mobile telecommunications system (UMTS) radio transceiver
devices,
long term evolution (LTE) radio transceiver devices, worldwide
interoperability for
microwave access (WiMAX) devices, and/or other well-known devices for
connecting to
networks. These network connectivity devices 1120 may enable the processor
1110 to
communicate with the Internet or one or more telecommunications networks or
other
networks from which the processor 1110 might receive information or to which
the
processor 1110 might output information. The network connectivity devices 1120
might
also include one or more transceiver components 1125 capable of transmitting
and/or
receiving data wirelessly.
(00126] The RAM 1130 might be used to store volatile data and perhaps to store
instructions that are executed by the processor 1110. The ROM 1140 is a non-
volatile
memory device that typically has a smaller memory capacity than the memory
capacity of
the secondary storage 1150. ROM 1140 might be used to store instructions and
perhaps
data that are read during execution of the instructions. Access to both RAM
1130 and
ROM 1140 is typically faster than to secondary storage 1150. The secondary
storage
1150 is typically comprised of one or more disk drives or tape drives and
might be used
42
CA 02808232 2013-02-13
WO 2012/020107 PCT/EP2011/063884
for non-volatile storage of data or as an over-flow data storage device if RAM
1130 is not
large enough to hold all working data. Secondary storage 1150 may be used to
store
programs that are loaded into RAM 1130 when such programs are selected for
execution.
[00127] The I/0 devices 1160 may include liquid crystal displays (LCDs), touch
screen
displays, keyboards, keypads, switches, dials, mice, track balls, voice
recognizers, card
readers, paper tape readers, printers, video monitors, or other well-known
input/output
devices. Also, the transceiver 1125 might be considered to be a component of
the 1/0
devices 1160 instead of or in addition to being a component of the network
connectivity
devices 1120,
[00128] In an embodiment, a UE is provided, The UE includes a processor
configured
such that the UE receives one or more wireless signals providing handover
synchronization information of a first network component relative to one or
more second
network components. The first network component and the one or more second
network
components are in different radio access networks.
[00129] In another embodiment, a first network component is provided. The
first
network component includes a processor configured to transmit one or more
signals
providing handover synchronization information of the first network component
relative to
one or more second network components. The first network component and the one
or
more second network components are in different radio access networks.
[00130] In another embodiment, a method in a UE is provided. The method
includes
receiving one or more signals providing handover synchronization information
of a first
network component relative to one or more second network components. The first
43
CA 02808232 2015-06-26
,
network component and the one or more second network components are in
different
radio access networks.
[00131] In another embodiment, a method in a first network component is
provided.
The method includes transmitting one or more signals providing handover
synchronization information of the first network component relative to one or
more second
network components. The first network component and the one or more second
network
components are in different radio access networks.
[00132] While several embodiments have been provided in the present
disclosure, it
should be understood that the disclosed systems and methods may be embodied in
many
other specific forms without departing from the scope of the present
disclosure. The
present examples are to be considered as illustrative and not restrictive, and
the intention
is not to be limited to the details given herein. For example, the various
elements or
components may be combined or integrated in another system or certain features
may be
omitted, or not implemented. While the claims below are identified as having
certain
dependencies and relationships, it should be appreciated that it is
contemplated and
should be understood that any of the claims may depend from any other claims
or
combinations of claims.
[00133] Also, techniques, systems, subsystems and methods described and
illustrated
in the various embodiments as discrete or separate may be combined or
integrated with
other systems, modules, techniques, or methods without departing from the
scope of the
present disclosure. Other items shown or discussed as coupled or directly
coupled or
communicating with each other may be indirectly coupled or communicating
through
some interface, device, or intermediate component, whether electrically,
mechanically, or
44
CA 02808232 2015-06-26
,
,
otherwise. Other examples of changes, substitutions, and alterations are
ascertainable
by one skilled in the art and could be made without departing from the scope
of the
present disclosure. The scope of protection being sought is defined by the
following
claims rather than the described embodiments in the foregoing description. The
scope of
the claims should not be limited by the described embodiments set forth in the
examples
but should be given the broadest interpretation consistent with the
description as a whole.
