Note: Descriptions are shown in the official language in which they were submitted.
= CA 03000508 2018-03-28
= WO 2017/066803 PCT/US2016/057420
Control Channel Configuration in Partial and Full Subframes
TECHNICAL FIELD
[0001] This application relates to the field of wireless communication systems
and methods.
Particularly, embodiments described herein relate to aspects of Control
Channel (CC)
Configuration in partial and full subframes, which may be used in 4G (LIE, LIE-
Advanced)
wireless communication systems.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
[0002] Examples of several of the various embodiments of the present invention
are described
herein with reference to the drawings.
[0003] FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per
an aspect of an
embodiment of the present invention.
[0004] FIG. 2 is a diagram depicting an example transmission time and
reception time for two
carriers in a carrier group as per an aspect of an embodiment of the present
invention.
[0005] FIG. 3 is a diagram depicting OFDM radio resources as per an aspect of
an embodiment
of the present invention.
[0006] FIG. 4 is a block diagram of a base station and a wireless device as
per an aspect of an
embodiment of the present invention.
[0007] FIG. 5A, FIG. 58, FIG. 5C and FIG. 5D are example diagrams for uplink
and downlink
signal transmission as per an aspect of an embodiment of the present
invention.
[0008] FIG. 6 is an example diagram for a protocol structure with CA and DC as
per an aspect
of an embodiment of the present invention.
[0009] FIG. 7 is an example diagram for a protocol structure with CA and DC as
per an aspect
of an embodiment of the present invention.
[0010] FIG. 8 shows example TAG configurations as per an aspect of an
embodiment of the
present invention.
[0011] FIG. 9 is an example message flow in a random access process in a
secondary TAG as
per an aspect of an embodiment of the present invention.
[0012] FIG. 10 is an example diagram depicting a downlink burst as per an
aspect of an
embodiment of the present invention.
[0013] FIG. 11 is example diagrams depicting partial subframe and full
subframe as per an
aspect of an embodiment of the present invention.
DETAILED DESCRIPTION OF EMBODIMENTS
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
[0014] Example embodiments of the present invention enable operation of
carrier aggregation.
Embodiments of the technology disclosed herein may be employed in the
technical field of
multicarrier communication systems. More particularly, the embodiments of the
technology
disclosed herein may relate to signal timing in multicarrier communication
systems.
[0015] The following Acronyms are used throughout the present disclosure:
ASIC application-specific integrated circuit
BPSK binary phase shift keying
CA carrier aggregation
CSI channel state information
CDMA code division multiple access
CSS common search space
CPLD complex programmable logic devices
CC component carrier
DL downlink
DCI downlink control information
DC dual connectivity
EPC evolved packet core
E-UTRAN evolved-universal terrestrial radio access network
1-PGA field programmable gate arrays
FDD frequency division multiplexing
HDL hardware description languages
HARQ hybrid automatic repeat request
1E information element
LTE long term evolution
MCG master cell group
MeNB master evolved node B
MIB master information block
MAC media access control
MAC media access control
MME mobility management entity
NAS non-access stratum
OFDM orthogonal frequency division multiplexing
PDCP packet data convergence protocol
PDU packet data unit
CA 03000508 2018-03-28
WO 2017/066803
PCT/US2016/057420
PHY physical
PDCCH physical downlink control channel
PHICH physical HARQ indicator channel
PUCCH physical uplink control channel
PUSCH physical uplink shared channel
PCell primary cell
PCell primary cell
PCC primary component carrier
PSCell primary secondary cell
pTAG primary timing advance group
QAM quadrature amplitude modulation
QPSK quadrature phase shift keying
RBG Resource Block Groups
RLC radio link control
RRC radio resource control
RA random access
RB resource blocks
SCC secondary component carrier
SCell secondary cell
Scell secondary cells
SCG secondary cell group
SeNB secondary evolved node B
sTAGs secondary timing advance group
SDU service data unit
S-GW serving gateway
SRB signaling radio bearer
SC-OFDM single carrier-OFDM
SFN system frame number
SIB system information block
TAI tracking area identifier
TAT time alignment timer
TDD time division duplexing
TDMA time division multiple access
TA timing advance
3
CA 03000508 2018-03-28
WO 2017/066803
PCT/US2016/057420
TAG timing advance group
TB transport block
UL uplink
UE user equipment
VHDL VHSIC hardware description language
[0 0 1 61 Example embodiments of the invention may be implemented using
various physical
layer modulation and transmission mechanisms. Example transmission mechanisms
may
include, but are not limited to: CDMA, OFDM, TDMA, Wavelet technologies,
and/or the like.
Hybrid transmission mechanisms such as TDMA/CDMA, and OFDM/CDMA may also be
employed. Various modulation schemes may be applied for signal transmission in
the physical
layer. Examples of modulation schemes include, but are not limited to: phase,
amplitude, code, a
combination of these, and/or the like. An example radio transmission method
may implement
QAM using BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radio
transmission may be enhanced by dynamically or semi-dynamically changing the
modulation
and coding scheme depending on transmission requirements and radio conditions.
[0 0 17] FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per
an aspect of an
embodiment of the present invention. As illustrated in this example, arrow(s)
in the diagram
may depict a subcarrier in a multicarrier OFDM system. The OFDM system may use
technology
such as OFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. For
example,
arrow 101 shows a subcarrier transmitting information symbols. FIG. 1 is for
illustration
purposes, and a typical multicarrier OFDM system may include more subcarriers
in a carrier.
For example, the number of subcarriers in a carrier may be in the range of 10
to 10,000
subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmission band.
As illustrated in
FIG. 1, guard band 106 is between subcarriers 103 and subcarriers 104. The
example set of
subcarriers A 102 includes subcarriers 103 and subcarriers 104. FIG. 1 also
illustrates an
example set of subcarriers B 105. As illustrated, there is no guard band
between any two
subcarriers in the example set of subcarriers B 105. Carriers in a
multicarrier OFDM
communication system may be contiguous carriers, non-contiguous carriers, or a
combination of
both contiguous and non-contiguous carriers.
[0 0 l 81 FIG. 2 is
a diagram depicting an example transmission time and reception time for two
carriers as per an aspect of an embodiment of the present invention. A
multicarrier OFDM
communication system may include one or more carriers, for example, ranging
from 1 to 10
carriers. Carrier A 204 and carrier B 205 may have the same or different
timing structures.
Although FIG. 2 shows two synchronized carriers, carrier A 204 and carrier B
205 may or may
4
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
not be synchronized with each other. Different radio frame structures may be
supported for FDD
and TDD duplex mechanisms. FIG. 2 shows an example FDD frame timing. Downlink
and
uplink transmissions may be organized into radio frames 201. In this example,
radio frame
duration is 10 msec. Other frame durations, for example, in the range of 1 to
100 msec may also
be supported. In this example, each 10 ms radio frame 201 may be divided into
ten equally sized
subframes 202. Other subframe durations such as including 0.5 msec, 1 msec, 2
msec, and 5
msec may also be supported. Subframe(s) may consist of two or more slots (e.g.
slots 206 and
207). For the example of FDD, 10 subframes may be available for downlink
transmission and
subframes may be available for uplink transmissions in each 10 ms interval.
Uplink and
downlink transmissions may be separated in the frequency domain. Slot(s) may
include a
plurality of OFDM symbols 203. The number of OFDM symbols 203 in a slot 206
may depend
on the cyclic prefix length and subcarrier spacing.
[0019] FIG. 3 is a diagram depicting OFDM radio resources as per an aspect of
an embodiment
of the present invention. The resource grid structure in time 304 and
frequency 305 is illustrated
in FIG. 3. The quantity of downlink subcarriers or RBs (in this example 6
to100 RBs) may
depend, at least in part, on the downlink transmission bandwidth 306
configured in the cell. The
smallest radio resource unit may be called a resource element (e.g. 301).
Resource elements may
be grouped into resource blocks (e.g. 302). Resource blocks may be grouped
into larger radio
resources called Resource Block Groups (RBG) (e.g. 303). The transmitted
signal in slot 206
may be described by one or several resource grids of a plurality of
subcarriers and a plurality of
OFDM symbols. Resource blocks may be used to describe the mapping of certain
physical
channels to resource elements. Other pre-defined groupings of physical
resource elements may
be implemented in the system depending on the radio technology. For example,
24 subcarriers
may be grouped as a radio block for a duration of 5 msec. In an illustrative
example, a resource
block may correspond to one slot in the time domain and 180 kHz in the
frequency domain (for
KHz subcarrier bandwidth and 12 subcarriers).
[0020[ FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplink
and downlink
signal transmission as per an aspect of an embodiment of the present
invention. FIG. 5A shows
an example uplink physical channel. The baseband signal representing the
physical uplink
shared channel may perform the following processes. These functions are
illustrated as
examples and it is anticipated that other mechanisms may be implemented in
various
embodiments. The functions may comprise scrambling, modulation of scrambled
bits to
generate complex-valued symbols, mapping of the complex-valued modulation
symbols onto
one or several transmission layers, transform precocling to generate complex-
valued symbols,
5
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
precoding of the complex-valued symbols, mapping of precoded complex-valued
symbols to
resource elements, generation of complex-valued time-domain DFTS-014DM/SC-FDMA
signal
for each antenna port, and/or the like.
[0021] Example modulation and up-conversion to the carrier frequency of the
complex-valued
DFI __ S-OPDM/SC-PDMA baseband signal for each antenna port and/or the complex-
valued
PRACH baseband signal is shown in FIG. 5B. Filtering may be employed prior to
transmission.
[0022] An example structure for Downlink Transmissions is shown in FIG. 5C.
The baseband
signal representing a downlink physical channel may perform the following
processes. These
functions are illustrated as examples and it is anticipated that other
mechanisms may be
implemented in various embodiments. The functions include scrambling of coded
bits in each of
the codewords to be transmitted on a physical channel; modulation of scrambled
bits to generate
complex-valued modulation symbols; mapping of the complex-valued modulation
symbols onto
one or several transmission layers; precoding of the complex-valued modulation
symbols on
each layer for transmission on the antenna ports; mapping of complex-valued
modulation
symbols for each antenna port to resource elements; generation of complex-
valued time-domain
OFDM signal for each antenna port, and/or the like.
[0023] Example modulation and up-conversion to the carrier frequency of the
complex-valued
OFDM baseband signal for each antenna port is shown in FIG. 5D. Filtering may
be employed
prior to transmission.
[0024] FIG. 4 is an example block diagram of a base station 401 and a wireless
device 406, as
per an aspect of an embodiment of the present invention. A communication
network 400 may
include at least one base station 401 and at least one wireless device 406.
The base station 401
may include at least one communication interface 402, at least one processor
403, and at least
one set of program code instructions 405 stored in non-transitory memory 404
and executable by
the at least one processor 403. The wireless device 406 may include at least
one communication
interface 407, at least one processor 408, and at least one set of program
code instructions 410
stored in non-transitory memory 409 and executable by the at least one
processor 408.
Communication interface 402 in base station 401 may be configured to engage in
communication with communication interface 407 in wireless device 406 via a
communication
path that includes at least one wireless link 411. Wireless link 411 may he a
hi-directional link.
Communication interface 407 in wireless device 406 may also be configured to
engage in a
communication with communication interface 402 in base station 401. Base
station 401 and
wireless device 406 may be configured to send and receive data over wireless
link 411 using
multiple frequency carriers. According to some of the various aspects of
embodiments,
6
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
transceiver(s) may be employed. A transceiver is a device that includes both a
transmitter and
receiver. Transceivers may be employed in devices such as wireless devices,
base stations, relay
nodes, and/or the like. Example embodiments for radio technology implemented
in
communication interface 402, 407 and wireless link 411 are illustrated are
FIG. 1, FIG. 2, FIG.
3, FIG. 5, and associated text.
100251 An interface may be a hardware interface, a firmware interface, a
software interface,
and/or a combination thereof. The hardware interface may include connectors,
wires, electronic
devices such as drivers, amplifiers, and/or the like. A software interface may
include code stored
in a memory device to implement protocol(s), protocol layers, communication
drivers, device
drivers, combinations thereof, and/or the like. A firmware interface may
include a combination
of embedded hardware and code stored in and/or in communication with a memory
device to
implement connections, electronic device operations, protocol(s), protocol
layers,
communication drivers, device drivers, hardware operations, combinations
thereof, and/or the
like.
[0026] The term configured may relate to the capacity of a device whether the
device is in an
operational or non-operational state. Configured may also refer to specific
settings in a device
that effect the operational characteristics of the device whether the device
is in an operational or
non-operational state. In other words, the hardware, software, firmware,
registers, memory
values, and/or the like may be "configured" within a device, whether the
device is in an
operational or nonoperational state, to provide the device with specific
characteristics. Terms
such as "a control message to cause in a device" may mean that a control
message has
parameters that may be used to configure specific characteristics in the
device, whether the
device is in an operational or non-operational state.
[0027] According to some of the various aspects of embodiments, an LTE network
may include
a multitude of base stations, providing a user plane PDCP/RLC/MAC/PHYand
control plane
(RRC) protocol terminations towards the wireless device. The base station(s)
may be
interconnected with other base station(s) (e.g. employing an X2 interface).
The base stations
may also be connected employing, for example, an 51 interface to an EPC. For
example, the
base stations may be interconnected to the MME employing the Sl-MME interface
and to the S-
G) employing the Sl-U interface. The S1 interface may support a many-to-many
relation
between MMEs / Serving Gateways and base stations. A base station may include
many sectors
for example: 1, 2, 3, 4, or 6 sectors. A base station may include many cells,
for example, ranging
from 1 to 50 cells or more. A cell may be categorized, for example, as a
primary cell or
secondary cell. At RRC connection establishment/re-establishment/handover, one
serving cell
7
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
may provide the NAS (non-access stratum) mobility information (e.g. TAI), and
at RRC
connection re-establishment/handover, one serving cell may provide the
security input. This cell
may be referred to as the Primary Cell (PCell). In the downlink, the carrier
corresponding to the
PCell may be the Downlink Primary Component Carrier (DL PCC), while in the
uplink, it may
be the Uplink Primary Component Carrier (UL PCC). Depending on wireless device
capabilities, Secondary Cells (SCells) may be configured to form together with
the PCell a set of
serving cells. In the downlink, the carrier corresponding to an SCell may be a
Downlink
Secondary Component Carrier (DL SCC), while in the uplink, it may be an Uplink
Secondary
Component Carrier (UL SCC). An SCell may or may not have an uplink carrier.
[0028] A cell, comprising a downlink carrier and optionally an uplink carrier,
may be assigned a
physical cell ID and a cell index. A carrier (downlink or uplink) may belong
to only one cell.
The cell ID or Cell index may also identify the downlink carrier or uplink
carrier of the cell
(depending on the context it is used). In the specification, cell ID may be
equally referred to a
carrier ID, and cell index may be referred to carrier index. In
implementation, the physical cell
ID or cell index may be assigned to a cell. A cell ID may be determined using
a synchronization
signal transmitted on a downlink carrier. A cell index may be determined using
RRC messages.
For example, when the specification refers to a first physical cell ID for a
first downlink carrier,
the specification may mean the first physical cell ID is for a cell comprising
the first downlink
carrier. The same concept may apply to, for example, carrier activation. When
the specification
indicates that a first carrier is activated, the specification may equally
mean that the cell
comprising the first carrier is activated.
[0029] Embodiments may be configured to operate as needed. The disclosed
mechanism may
be performed when certain criteria are met, for example, in a wireless device,
a base station, a
radio environment, a network, a combination of the above, and/or the like.
Example criteria may
be based, at least in part, on for example, traffic load, initial system set
up, packet sizes, traffic
characteristics, a combination of the above, and/or the like. When the one or
more criteria are
met, various example embodiments may be applied. Therefore, it may be possible
to implement
example embodiments that selectively implement disclosed protocols.
[0030] A base station may communicate with a mix of wireless devices. Wireless
devices may
support multiple technologies, and/or multiple releases of the same
technology. Wireless
devices may have some specific capability(ies) depending on its wireless
device category and/or
capability(ies). A base station may comprise multiple sectors. When this
disclosure refers to a
base station communicating with a plurality of wireless devices, this
disclosure may refer to a
subset of the total wireless devices in a coverage area. This disclosure may
refer to, for example,
8
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
a plurality of wireless devices of a given LTE release with a given capability
and in a given
sector of the base station. The plurality of wireless devices in this
disclosure may refer to a
selected plurality of wireless devices, and/or a subset of total wireless
devices in a coverage area
which perform according to disclosed methods, and/or the like. There may be a
plurality of
wireless devices in a coverage area that may not comply with the disclosed
methods, for
example, because those wireless devices perform based on older releases of LTE
technology.
[0031] FIG. 6 and FIG. 7 are example diagrams for protocol structure with CA
and DC as per
an aspect of an embodiment of the present invention. E-UTRAN may support Dual
Connectivity
(DC) operation whereby a multiple RX/TX UE in RRC_CONNECTED may be configured
to
utilize radio resources provided by two schedulers located in two eNBs
connected via a non-
ideal backhaul over the X2 interface. eNBs involved in DC for a certain UE may
assume two
different roles: an eNB may either act as an MeNB or as an SeNB. In DC a UE
may be
connected to one MeNB and one SeNB. Mechanisms implemented in DC may be
extended to
cover more than two eNBs. FIG. 7 illustrates one example structure for the UE
side MAC
entities when a Master Cell Group (MCG) and a Secondary Cell Group (SCG) are
configured,
and it may not restrict implementation. Media Broadcast Multicast Service
(MBMS) reception is
not shown in this figure for simplicity.
[0032] In DC, the radio protocol architecture that a particular bearer uses
may depend on how
the bearer is setup. Three alternatives may exist, an MCG bearer, an SCG
bearer and a split
bearer as shown in FIG. 6. RRC may be located in MeNB and SRBs may be
configured as a
MCG bearer type and may use the radio resources of the MeNB. DC may also be
described as
having at least one bearer configured to use radio resources provided by the
SeNB. DC may or
may not be configured/implemented in example embodiments of the invention.
[0033] In the case of DC, the UE may be configured with two MAC entities: one
MAC entity
for MeNB, and one MAC entity for SeNB. In DC, the configured set of serving
cells for a UE
may comprise of two subsets: the Master Cell Group (MCG) containing the
serving cells of the
MeNB, and the Secondary Cell Group (SCG) containing the serving cells of the
SeNB. For a
SCG, one or more of the following may be applied: at least one cell in the SCG
has a configured
UL CC and one of them, named PSCell (or PCell of SCG, or sometimes called
PCell), is
configured with PUCCH resources; when the SCG is configured, there may be at
least one SCG
bearer or one Split bearer; upon detection of a physical layer problem or a
random access
problem on a PSCell, or the maximum number of RLC retransmissions has been
reached
associated with the SCG, or upon detection of an access problem on a PSCell
during a SCG
addition or a SCG change: a RRC connection re-establishment procedure may not
be triggered,
9
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
UL transmissions towards cells of the SCG are stopped, a MeNB may be informed
by the UE of
a SCG failure type, for split bearer, the DL data transfer over the MeNB is
maintained; the RLC
AM bearer may be configured for the split bearer; like PCell, PSCell may not
be de-activated;
PSCell may be changed with a SCG change (e.g. with security key change and a
RACH
procedure); and/or neither a direct bearer type change between a Split bearer
and a SCG bearer
nor simultaneous configuration of a SCG and a Split bearer are supported.
[0034] With respect to the interaction between a MeNB and a SeNB, one or more
of the
following principles may be applied: the MeNB may maintain the RRM measurement
configuration of the UE and may, (e.g, based on received measurement reports
or traffic
conditions or bearer types), decide to ask a SeNB to provide additional
resources (serving cells)
for a UE; upon receiving a request from the MeNB, a SeNB may create a
container that may
result in the configuration of additional serving cells for the UE (or decide
that it has no resource
available to do so); for UE capability coordination, the MeNB may provide
(part of) the AS
configuration and the UE capabilities to the SeNB; the MeNB and the SeNB may
exchange
information about a UE configuration by employing of RRC containers (inter-
node messages)
carried in X2 messages; the SeNB may initiate a reconfiguration of its
existing serving cells
(e.g., PUCCH towards the SeNB); the SeNB may decide which cell is the PSCell
within the
SCG; the MeNB may not change the content of the RRC configuration provided by
the SeNB; in
the case of a SCG addition and a SCG SCell addition, the MeNB may provide the
latest
measurement results for the SCG cell(s); both a MeNB and a SeNB may know the
SFN and
subframe offset of each other by OAM, (e.g., for the purpose of DRX alignment
and
identification of a measurement gap). In an example, when adding a new SCG
SCell, dedicated
RRC signalling may be used for sending required system information of the cell
as for CA,
except for the SFN acquired from a MIB of the PSCell of a SCG.
[0035] In an example, serving cells may be grouped in a TA group (TAG).
Serving cells in one
TAG may use the same timing reference. For a given TAG, user equipment (UE)
may use at
least one downlink carrier as a timing reference. For a given TAG, a UE may
synchronize uplink
subframe and frame transmission timing of uplink carriers belonging to the
same TAG. In an
example, serving cells having an uplink to which the same TA applies may
correspond to serving
cells hosted by the same receiver. A UE supporting multiple TAs may support
two or more TA
groups. One TA group may contain the PCell and may be called a primary TAG
(pTAG). In a
multiple TAG configuration, at least one TA group may not contain the PCell
and may be called
a secondary TAG (sTAG). In an example, carriers within the same TA group may
use the same
TA value and/or the same timing reference. When DC is configured, cells
belonging to a cell
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
group (MCG or SCG) may be grouped into multiple TAGs including a pTAG and one
or more
sTAGs.
[0036] FIG. 8 shows example TAG configurations as per an aspect of an
embodiment of the
present invention. In Example 1, pTAG comprises PCell, and an sTAG comprises
SCe111. In
Example 2, a pTAG comprises a PCell and SCe111, and an sTAG comprises SCe112
and SCe113.
In Example 3, pTAG comprises PCell and SCe111, and an sTAG I includes SCe112
and SCe113,
and sTAG2 comprises SCe114. Up to four TAGs may be supported in a cell group
(MCG or
SCG) and other example TAG configurations may also be provided. In various
examples in this
disclosure, example mechanisms are described for a pTAG and an sTAG. Some of
the example
mechanisms may be applied to configurations with multiple sTAGs.
[0037] In an example, an eNB may initiate an RA procedure via a PDCCH order
for an
activated SCell. This PDCCH order may be sent on a scheduling cell of this
SCell. When cross
carrier scheduling is configured for a cell, the scheduling cell may be
different than the cell that
is employed for preamble transmission, and the PDCCH order may include an
SCell index. At
least a non-contention based RA procedure may be supported for SCell(s)
assigned to sTAG(s).
[0038] FIG. 9 is an example message flow in a random access process in a
secondary TAG as
per an aspect of an embodiment of the present invention. An eNB transmits an
activation
command 600 to activate an SCell. A preamble 602 (Msgl) may be sent by a UE in
response to
a PDCCH order 601 on an SCell belonging to an sTAG. In an example embodiment,
preamble
transmission for SCells may be controlled by the network using PDCCH format
1A. Msg2
message 603 (RAR: random access response) in response to the preamble
transmission on the
SCell may be addressed to RA-RNTI in a PCell common search space (CSS). Uplink
packets
604 may be transmitted on the SCell in which the preamble was transmitted.
[0039] According to some of the various aspects of embodiments, initial timing
alignment may
be achieved through a random access procedure. This may involve a UE
transmitting a random
access preamble and an eNB responding with an initial TA command NTA (amount
of timing
advance) within a random access response window. The start of the random
access preamble
may be aligned with the start of a corresponding uplink subframe at the UE
assuming NTA=0.
The eNB may estimate the uplink timing from the random access preamble
transmitted by the
UE. The TA command may he derived by the eNB based on the estimation of the
difference
between the desired UL timing and the actual UL timing. The UE may determine
the initial
uplink transmission timing relative to the corresponding downlink of the sTAG
on which the
preamble is transmitted.
11
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
[0040] The mapping of a serving cell to a TAG may be configured by a serving
eNB with RRC
signaling. The mechanism for TAG configuration and reconfiguration may be
based on RRC
signaling. According to some of the various aspects of embodiments, when an
eNB performs an
SCell addition configuration, the related TAG configuration may be configured
for the SCell. In
an example embodiment, an eNB may modify the TAG configuration of an SCell by
removing
(releasing) the SCell and adding(configuring) a new SCell (with the same
physical cell ID and
frequency) with an updated TAG ID. The new SCell with the updated TAG ID may
initially be
inactive subsequent to being assigned the updated TAG ID. The eNB may activate
the updated
new SCell and start scheduling packets on the activated SCell. In an example
implementation, it
may not be possible to change the TAG associated with an SCell, but rather,
the SCell may need
to be removed and a new SCell may need to be added with another TAG. For
example, if there
is a need to move an SCell from an sTAG to a pTAG, at least one RRC message,
for example, at
least one RRC reconfiguration message, may be send to the UE to reconfigure
TAG
configurations by releasing the SCell and then configuring the SCell as a part
of the pTAG
(when an SCell is added/configured without a TAG index, the SCell may be
explicitly assigned
to the pTAG). The PCell may not change its TA group and may be a member of the
pTAG.
[0041] The purpose of an RRC connection reconfiguration procedure may be to
modify an RRC
connection, (e.g. to establish, modify and/or release RBs, to perform
handover, to setup, modify,
and/or release measurements, to add, modify, and/or release SCells). If the
received RRC
Connection Reconfiguration message includes the sCellToReleaseList, the UE may
perform an
SCell release. If the received RRC Connection Reconfiguration message includes
the
sCellToAddModList, the UE may perform SCell additions or modification.
[0042] In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on the
PCell
(PSCell) to an eNB. In LTE-Release 12 and earlier, a UE may transmit PUCCH
information on
one cell (PCell or PSCell) to a given eNB.
[0043] As the number of CA capable UEs and also the number of aggregated
carriers increase,
the number of PUCCHs and also the PUCCH payload size may increase.
Accommodating the
PUCCH transmissions on the PCell may lead to a high PUCCH load on the PCell. A
PUCCH on
an SCell may be introduced to offload the PUCCH resource from the PCell. More
than one
PUCCH may he configured for example, a PUCCH on a PCell and another PUCCH on
an SCell.
In the example embodiments, one, two or more cells may be configured with
PUCCH resources
for transmitting CSI/ACK/NACK to a base station. Cells may be grouped into
multiple PUCCH
groups, and one or more cell within a group may be configured with a PUCCH. In
an example
configuration, one SCell may belong to one PUCCH group. SCells with a
configured PUCCH
12
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
transmitted to a base station may be called a PUCCH SCell, and a cell group
with a common
PUCCH resource transmitted to the same base station may be called a PUCCH
group.
[0044] In an example embodiment, a MAC entity may have a configurable timer
timeAlignmentTimer per TAG. The timeAlignmentTimer may be used to control how
long the
MAC entity considers the Serving Cells belonging to the associated TAG to be
uplink time
aligned. The MAC entity may, when a Timing Advance Command MAC control element
is
received, apply the Timing Advance Command for the indicated TAG; start or
restart the
timeAlignmentTimer associated with the indicated TAG. The MAC entity may, when
a Timing
Advance Command is received in a Random Access Response message for a serving
cell
belonging to a TAG and/orif the Random Access Preamble was not selected by the
MAC entity,
apply the Timing Advance Command for this TAG and start or restart the
timeAlignmentTimer
associated with this TAG. Otherwise, if the timeAlignmentTimer associated with
this TAG is
not running, the Timing Advance Command for this TAG may be applied and the
timeAlignmentTimer associated with this TAG started. When the contention
resolution is
considered not successful, a timeAlignmentTimer associated with this TAG may
be stopped.
Otherwise, the MAC entity may ignore the received Timing Advance Command.
[0045] In example embodiments, a timer is running once it is started, until
it is stopped or until
it expires; otherwise it may not be running. A timer can be started if it is
not running or restarted
if it is running. For example, a timer may be started or restarted from its
initial value.
[0046] Example embodiments of the invention may enable operation of multi-
carrier
communications. Other example embodiments may comprise a non-transitory
tangible computer
readable media comprising instructions executable by one or more processors to
cause operation
of multi-carrier communications. Yet other example embodiments may comprise an
article of
manufacture that comprises a non-transitory tangible computer readable machine-
accessible
medium having instructions encoded thereon for enabling programmable hardware
to cause a
device (e.g. wireless communicator, UE, base station, etc.) to enable
operation of multi-carrier
communications. The device may include processors, memory, interfaces, and/or
the like. Other
example embodiments may comprise communication networks comprising devices
such as base
stations, wireless devices (or user equipment: UE), servers, switches,
antennas, and/or the like.
[0047] The amount of data traffic carried over cellular networks is
expected to increase for
many years to come. The number of users/devices is increasing and each
user/device accesses an
increasing number and variety of services, e.g. video delivery, large files,
images. This requires
not only high capacity in the network, but also provisioning very high data
rates to meet
customers' expectations on interactivity and responsiveness. More spectrum is
therefore needed
13
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
for cellular operators to meet the increasing demand. Considering user
expectations of high data
rates along with seamless mobility, it is beneficial that more spectrum be
made available for
deploying macro cells as well as small cells for cellular systems.
[0048] Striving to meet the market demands, there has been increasing
interest from operators
in deploying some complementary access utilizing unlicensed spectrum to meet
the traffic
growth. This is exemplified by the large number of operator-deployed Wi-Fi
networks and the
3GPP standardization of LTE/WLAN interworking solutions. This interest
indicates that
unlicensed spectrum, when present, can be an effective complement to licensed
spectrum for
cellular operators to help addressing the traffic explosion in some scenarios,
such as hotspot
areas. LAA offers an alternative for operators to make use of unlicensed
spectrum while
managing one radio network, thus offering new possibilities for optimizing the
network's
efficiency.
[0049] In an example embodiment, Listen-before-talk (clear channel
assessment) may be
implemented for transmission in an LAA cell. In a listen-before-talk (LBT)
procedure,
equipment may apply a clear channel assessment (CCA) check before using the
channel. For
example, the CCA utilizes at least energy detection to determine the presence
or absence of other
signals on a channel in order to determine if a channel is occupied or clear,
respectively. For
example, European and Japanese regulations mandate the usage of LBT in the
unlicensed bands.
Apart from regulatory requirements, carrier sensing via LBT may be one way for
fair sharing of
the unlicensed spectrum.
[0050] In an example embodiment, discontinuous transmission on an unlicensed
carrier with
limited maximum transmission duration may be enabled. Some of these functions
may be
supported by one or more signals to be transmitted from the beginning of a
discontinuous LAA
downlink transmission. Channel reservation may be enabled by the transmission
of signals, by
an LAA node, after gaining channel access via a successful LBT operation, so
that other nodes
that receive the transmitted signal with energy above a certain threshold
sense the channel to be
occupied. Functions that may need to be supported by one or more signals for
LAA operation
with discontinuous downlink transmission may include one or more of the
following: detection
of the LAA downlink transmission (including cell identification) by UEs; time
& frequency
synchronization of UEs.
[00511 In an example embodiment, DL LAA design may employ subframe boundary
alignment
according to LTE-A carrier aggregation timing relationships across serving
cells aggregated by
CA. This may not imply that the eNB transmissions can start only at the
subframe boundary.
LAA may support transmitting PDSCH when not all OFDM symbols are available for
14
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
transmission in a subframe according to LBT. Delivery of necessary control
information for the
PDSCH may also be supported.
[0052] LBT procedure may be employed for fair and friendly coexistence of LAA
with other
operators and technologies operating in unlicensed spectrum. LBT procedures on
a node
attempting to transmit on a carrier in unlicensed spectrum require the node to
perform a clear
channel assessment to determine if the channel is free for use. An LBT
procedure may involve at
least energy detection to determine if the channel is being used. For example,
regulatory
requirements in some regions, e.g., in Europe, specify an energy detection
threshold such that if
a node receives energy greater than this threshold, the node assumes that the
channel is not free.
While nodes may follow such regulatory requirements, a node may optionally use
a lower
threshold for energy detection than that specified by regulatory requirements.
In an example,
LAA may employ a mechanism to adaptively change the energy detection
threshold, e.g., LAA
may employ a mechanism to adaptively lower the energy detection threshold from
an upper
bound. Adaptation mechanism may not preclude static or semi-static setting of
the threshold. In
an example Category 4 LBT mechanism or other type of LBT mechanisms may be
implemented.
[0053] Various example LBT mechanisms may be implemented. In an example, for
some
signals, in some implementation scenarios, in some situations, and/or in some
frequencies no
LBT procedure may performed by the transmitting entity. In an example,
Category 2 (e.g. LBT
without random back-off) may be implemented. The duration of time that the
channel is sensed
to be idle before the transmitting entity transmits may be deterministic. In
an example, Category
3 (e.g. LBT with random back-off with a contention window of fixed size) may
be implemented.
The LBT procedure may have the following procedure as one of its components.
The
transmitting entity may draw a random number N within a contention window. The
size of the
contention window may be specified by the minimum and maximum value of N. The
size of the
contention window may be fixed or configurable. The random number N may be
employed in
the LBT procedure to determine the duration of time that the channel is sensed
to be idle before
the transmitting entity transmits on the channel. In an example, Category 4
(e.g. LBT with
random back-off with a contention window of variable size) may be implemented.
The
transmitting entity may draw a random number N within a contention window. The
size of
contention window may be specified by the minimum and maximum value of N. The
transmitting entity may vary the size of the contention window when drawing
the random
number N. The random number N is used in the LBT procedure to determine the
duration of
time that the channel is sensed to be idle before the transmitting entity
transmits on the channel.
In an example, an eNB may transmit one or more LBT configuration parameters in
one or more
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
RRC messages and/or one or more PDCCH DCIs. In an example, some of the LBT
parameters
may be configured via RRC message(s) and some other LBT parameters may be
signaled to a
UE via PDCCH DCI (e.g. a DCI including the UL grant).
[0054] LAA may employ uplink LBT at the UE. The UL LBT scheme may be different
from
the DL LBT scheme (e.g. by using different LBT mechanisms or parameters) for
example, since
the LAA UL is based on scheduled access which affects a UE's channel
contention
opportunities. Other considerations motivating a different UL LBT scheme
include, but are not
limited to, multiplexing of multiple UEs in a single subframe.
[0055] In an example, a DL transmission burst may be a continuous transmission
from a DL
transmitting node with no transmission immediately before or after from the
same node on the
same CC. An UL transmission burst from a UE perspective may be a continuous
transmission
from a UE with no transmission immediately before or after from the same UE on
the same CC.
In an example, UL transmission burst is defined from a UE perspective. In an
example, an UL
transmission burst may be defined from an eNB perspective. In an example, in
case of an eNB
operating DL+UL LAA over the same unlicensed carrier, DL transmission burst(s)
and UL
transmission burst(s) on LAA may be scheduled in a TDM manner over the same
unlicensed
carrier. For example, an instant in time may be part of a DL transmission
burst or an UL
transmission burst.
[00561 The following signals or combination of the following signals may
provide functionality
for the UE's time/frequency synchronization for the reception of a DL
transmission burst in
LAA SCell(s): a) serving cell's DRS for RRM measurement (DRS for RRM
measurement may
be used at least for coarse time/frequency synchronization), b) reference
signals embedded
within DL transmission bursts (e.g. CRS and/or DMRS), and/or c)
primary/secondary
synchronization signals. If there is an additional reference signal, this
signal may be used.
Reference signals may be used at least for fine time/frequency
synchronization. Other candidates
(e.g., initial signal, DRS) may be employed for synchronization.
[00571 DRS for RRM may also support functionality for demodulation of
potential broadcast
data multiplexed with DRS transmission. Other mechanism or signals (e.g.,
initial signal, DRS)
for time/frequency synchronization may be needed to support reception of DL
transmission
burst.
[00581 In an example embodiment, DRS may be used at least for coarse
time/frequency
synchronization. Reference signals (e.g., CRS and/or DMRS) within DL
transmission bursts may
be used at least for fine time/frequency synchronization. Once the UE detects
DRS and achieves
coarse time/frequency synchronization based on that, UE may keep tracking on
the
16
CA 03000508 2018-03-28
WO 2017/066803
PCT/US2016/057420
synchronization using reference signals embedded in other DL TX bursts and may
also use DRS.
In an example, a UE may utilize DRS and/or reference signals embedded within
DL
transmission burst targeting the UE. In another example, a UE may utilize DRS
and/or reference
signals embedded within many available DL transmission bursts from the serving
cell (to the UE
and other UEs).
[0059] The discovery signal used for cell discovery/RRM measurement (e.g.
opportunistic
transmission within configured DMTC) may be used for maintaining at least
coarse
synchronization with the LAA cell (e.g. < 31as timing synchronization error
and < 0.1ppm
frequency synchronization error). DRS may be subject to LBT. Inter-DRS latency
generally gets
worse as Wi-Fi traffic load increases. It is noted that the inter-DRS latency
can be rather
significant. In example scenario, there may be 55% probability that the inter-
DRS latency is
40ms and there is 5% probability that inter-DRS latency is > 440ms. The inter-
DRS latency as
seen by the UE may be worse considering the possibility of misdetection by the
UE. Discovery
signal misdetection may be due to actual misdetection or due to UE unavailable
for detection
because of DRX inter-frequency measurement during DMTC occasion.
[0060] Depending on LAA DRS design, OFDM symbol boundary may be obtained by
DRS.
PCell and SCell timing difference may be kept, 30 usec order. The aggregated
cells may be
synchronized to some extent, e.g. aligned frame timing and SFN. Thus, similar
requirement may
be applied to the PCell and LAA cells on the unlicensed band. In an example, a
UE may not
utilize timing and frequency of the PCell for coarse synchronization of LAA
cells since the
timing offset may be up to ¨30us (e.g. non-located) and frequency reference
may not be reliable
due to the band distance between PCell and LAA cell (2GHz Pcell and 5GHz LAA
cell). PCell
timing information also may be used for time synchronization at subframe or
frame level.
SCell(s) may employ the same frame number and subframe number as the PCell.
[0061] PCell timing information may provide some information for symbol
synchronization. By
synchronizing PCell, frequency difference observed by UE between PCell and LAA
Scell may
be up to 0.6 ppm. For example, after 300 ms, the amount of the time drift may
be 0.18 usec at
most. For LAA, path delay may be relatively small as the target coverage is
small. With timing
drift, the multi-path delay may be within cyclic prefix length.
[0062] According
to some of the various aspects of embodiments, a UE may utilize a licensed
band carrier as a reference for time/frequency synchronization for CA of
licensed carrier and
unlicensed carrier, for example when they are in the same group (e.g. co-
located). When non-
collocated eNBs support licensed band PCell and unlicensed band SCell
separately in a CA
scenario, there may exist maximum ¨30 us timing difference between PCell and
unlicensed band
17
CA 03000508 2018-03-28
WO 2017/066803
PCT/US2016/057420
SCell. In an example embodiment, the frequency difference between the UE
synchronized with
PCell and unlicensed band SCell may observe at most 0.6 ppm. An LAA may
provide
functionality for time/frequency synchronization on unlicensed band at least
for non-collocated
CA scenario.
[0063] Example
reasons of frequency difference may be 1) oscillator difference among PCell,
SCell and UE, 2) Doppler shift and 3) fast fading aspect. The oscillator
difference of 0.6 ppm
offset in 5 GHz corresponds to 3 kHz offset. Subcarrier spacing of LTE
numerology is 15 kHz.
This offset may need to be taken into account before FF1 operation. One of the
reasons of
oscillator frequency variation is the temperature. If the frequency difference
is not obtained at the
point of DRS reception, UE may need to buffer subsequent data transmission
until UE obtains
this frequency difference before FFT. The frequency offset caused by this may
be obtained at the
reception of DRS. Doppler shift may be small value for a low mobility UE. Fast
fading and
residual mismatch caused by 1) and 2) may be compensated during demodulation
process similar
to a licensed band. This may not require introducing additional reference
signals for unlicensed
band.
[0064] According to some of the various aspects of embodiments, a UE may be
configured to
perform inter-frequency measurements on the carrier frequency layer using
measurement gaps
for SCells that are not configured yet. SCell receiver may not be turned on
and measurements
may be performed using the Pcell receiver. When a cell is added as Scell but
not activated
("deactivated state"), the UE may receive relevant system information for the
SCell from the
Pcell. UE may be configured to perform measurements on the Scell without
measurement gaps.
SCell receiver may need to be occasionally turned on (e.g. for 5 ms every 160
ms) for RRM
measurements using either CRS or Discovery signals. Cells may be added as
Scell and activated
("activated state"), then the UE may be ready to receive PDSCH on the Scell in
all subframes.
The SCell receiver may perform (E)PDCCH monitoring in every subframe (for self
scheduling
case). SCell receiver may buffer every subframe for potential PDSCH processing
(for both self
and cross-carrier scheduling cases).
[0065] The eNodeB may configure the UE to measure and report RRM measurements
(e.g.
including RSSI) on a set of carrier frequencies. Once a suitable carrier or a
set of suitable carriers
is determined, carrier selected may be added as an SCell by RRC (e.g. with -
15ms configuration
delay), followed by SCell activation (with -24ms delay). If an SCell is
deactivated, the UE may
assume that no signal is transmitted by the LAA cell, except discovery signal
may be transmitted
when configured. If an SCell is activated, the UE is required to monitor
PDCCH/EPDCCH and
perform CSI measurement/reporting for the activated SCell. In a U-cell, a UE
may not assume
18
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
that every subframe of activated LAA SCell contains transmission. For LAA
carriers, channel
access may depend on the LBT procedure outcome. The network may configure and
activate
many carriers for the UE. The scheduler may then dynamically select carrier(s)
for DL
assignment or UL grant transmission.
[0066] According to some of the various aspects of embodiments, the first
stage of cell level
carrier selection may be during initial set up of a cell by an eNB. The eNB
may scan and sense
channels for interference or radar detection. eNB may configure the SCells
accordingly based on
the outcome of its carrier selection algorithm for efficient load balancing
and interference
management. The carrier selection process may be on a different time scale
from the LBT/CCA
procedure prior to transmissions on the carriers in unlicensed spectrum. The
RSSI measurement
report from UE may be used to assist the selection at eNB.
[0067] According to some of the various aspects of embodiments, the second
stage of cell level
carrier selection is after initial set up. The motivation is that eNB may need
to do carrier
(re)selection due to static load and interference change on some carriers,
e.g., a new VVi-Fi AP is
set up and continuously accesses the carrier causing relatively static
interference. Therefore,
semi-static carrier selection may be based on the eNB sensing of the averaged
interference level,
potential presence of radar signals if required, and traffic load on the
carriers over a relatively
longer time scale, as well as RRM measurement from UEs in the cell. Due to the
characteristics
in unlicensed spectrum, RRM measurements on LAA SCells may be enhanced to
support better
carrier selection. For example, the RSSI measurement may be enhanced using
occupancy metric
indicating the percentage of the time when RSSI is above a certain threshold.
It may be noted
that cell level carrier selection may be a long-term (re)selection since the
process may be rather
costly due to the signalling overhead and communication interruptions for UEs
in a cell and it
may also affect the neighbouring cells. Once a suitable set of carriers is
identified, they may be
configured and activated as SCells for UEs. This process may be continuous in
order to keep
reassessing the interference environment. Cell-level carrier selection in
unlicensed spectrum may
be a relatively long-term (re)selection based on eNB sensing and RRM
measurement report from
UE. RRM measurement on LAA SCells may be enhanced to support better carrier
selection.
[0068] Carrier selection from UE perspective may be to support carrier
selection for a UE
among the set of carriers that the eNB has selected at the cell level. Carrier
selection for the UE
in unlicensed spectrum may be achieved by configuring a set of the carriers on
which the UE
supports simultaneous reception and transmission. The UE may perform RRM
measurements on
the configured carriers and report them to the eNB. The eNB may then choose
which of the
carriers to activate and use for transmission when it has pending data for the
UE. The number of
19
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
carriers to activate may then also be chosen based on the data rate needed and
the RRM
measurements for the different carriers. The activation delay for a carrier
before scheduling data
on it may be up to ¨24 ms, assuming that the UE has performed RRM measurement
on this
carrier prior to receiving the activation command within DRX cycle. By
operating the carrier
selection based on activation and deactivation, the selection may also be done
in the order of tens
of ms.
[0069] According to some of the various aspects of embodiments, CRS may not be
transmitted
in an activated subframe when a burst is not scheduled in that subframe. If
there are no
transmissions from the eNB for an extended duration (Toff), UE demodulation
performance may
be impacted due to lack of reference symbols for fine time/frequency tracking.
The extent of
performance impact depends on the amount of time for which there are no eNB
transmissions.
The impact may be mitigated by more frequent transmission of discovery
signals.
[0070] Discovery signals may be transmitted by the eNB even when UEs are not
being
scheduled. Setting discovery signal periodicity based on UE RRM measurement
requirements
(e.g. 160ms) may be more efficient than setting the periodicity based on UE
fine time/frequency
tracking requirement.
[0071] In an example embodiment, Scell deactivation timer for the unlicensed
Scell may be set
to a value closer to (Toff) based on UE fine time/frequency tracking
requirements. This may
result in more frequent transmission of activation commands. Activation
commands may be
needed when the eNB has data to schedule to a UE. From the UE perspective,
after receiving an
activation command in a particular subframe, the UE may receive CRS in a
number (e.g. one or
two) of following subframes. The UEs may receive CRS transmissions for a few
symbols or
subframes, which they may use for settling AGC loop and time-frequency
tracking filters before
PDSCH reception on the SCell. UEs may receive CRS transmission (e.g. in a few
OFDM
symbols) between reception of activation command and reception PDSCH on the
Scell.
[0072] Activating a large number of carriers on dynamic bases may increase the
UE power
consumption, false alarm probability, and processing power requirements.
Improved
mechanisms are needed to improve efficiency in the UE and enable fast and
dynamic carrier
selection/activation in a UE. Novel mechanisms may reduce UE power
consumption, reduce
false alarm probability and reduce processing power requirements. Carrier
selection and
activation may be enhanced to achieve fast dynamic carrier selection (or
switching). A fast
activation procedure for the carrier (e.g. shorter than the currently defined
24 ms) may be defined
to improve efficiency.
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
[0073] Current SCell activation latency may include the MAC CE decoding
latency (-3-6ms)
and SCell activation preparation time (RF preparation, up to -18ms).
Implementation of faster
processes and hardware may reduce these delays. SCell MAC
activation/deactivation signalling
is UE-specific. Signalling overhead may be a concern especially if the cell
used for transmitting
the signal is a macro cell. In an example embodiment, a Ll procedure/indicator
may be
introduced and/or SCell activation signalling may be enhanced.
[0074] Layer one signalling (e.g. PDCCH/EPDCCH from the PCell or another
serving cell)
may be implemented to signal the set of carriers that the UE may monitor for
PDCCH/EPDCCH
and/or measuring/reporting CSI. Control signalling latency may be - 2ms (e.g.
one lms
EPDCCH transmission plus 0.5ms decoding). The DCI format may be of small size
for
transmission reliability and overhead reduction. To reduce control signalling
overhead, the
signalling may be a UE-common signalling. The indication may be sent on a
carrier that the UE
is currently monitoring.
[0075] In an example embodiment, a mechanism based on a Li indication for
starting/stopping
monitoring of up to k activated carriers may be provided. The UE may be
configured with n>=k
CCs. k CCs may be activated via MAC signalling of SCell
activation/deactivation. Then based
on LBT progress over the CCs, a Li indication is sent to inform which of the k
CCs may be
monitored by the UE and which may not. The UE may then receive data burst(s)
on the
monitored CCs. Another Li indication may be sent after the bursts to alter
which CCs may be
monitored since then, and so on. The Li indication may be explicit (e.g.,
based on a signalling)
or implicit (e.g., based on self scheduling and UE detection of scheduling
information on the
SCell). For this example, fast carrier switching is done among at most k CCs.
[0076] In an example embodiment, a mechanism based on a Li signalling for
starting/stopping
monitoring of up to m activated carriers (the number of p configured carriers
may be m or
higher). The activated carriers may be more than n (e.g., there may be more
CCs activated for the
UE than its PDSCH aggregation capability-n). The UE is configured with p CCs,
and there may
be up to m CCs that are activated via MAC signalling of SCell
activation/deactivation. The UE
may not monitor all the activated CCs. The UE may monitor at most n CCs
according a Li
indication. The Li indication needs to be explicit rather than implicit, since
an implicit indication
may require a UE to monitor all the up to m activated carriers at the same
time, exceeding the
UE's capability. For this example, fast carrier switching is done among
possibly more than n
CCs.
[0077] According to some of the various aspects of embodiments, SCell
activation/deactivation
enhancements may be considered for fast carrier switching. SCell
activation/deactivation
21
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
signalling is a MAC signalling. MAC signalling decoding/detection (with or
without
enhancements) may be slower than L 1 signalling decoding/detection. It may
involves
decoding/detection of a Li signalling and furthermore, a PDSCH. If SCell
activation/deactivation is carried by a Li signalling, it may still be
considered for fast carrier
switching. In an example embodiment, a mechanism based on a Ll signalling for
activation/deactivation of the p configured carriers. The UE is configured
with p CCs, but each
time there are at most n CCs are activated via a Li signalling of SCell
activation/deactivation.
For instance, based on LBT progress over the CCs, a Li signalling is sent to
inform which of the
p CCs are activated. The UE may receive data burst(s) on the activated CCs.
Another L
signalling may be sent after the bursts to alter the activated CCs. For this
example, fast carrier
switching is done among possibly more than n CCs.
[00781 The control signalling may be transmitted before the eNB has gained
access to the
carrier via LBT process. An eNB may inform the UE to start (or stop)
monitoring a carrier
(whether the UE would receive a burst or not depends on the presence of PDCCH
scheduling
information for the carrier). An indication for starting monitoring may be
used for more than one
burst, until an indication for stopping monitoring is sent. The indication may
be sent when the
eNB expects the (E) CCA is to complete soon. A purpose of the indication may
be to inform a
UE to start or stop monitoring a carrier.
[0079] Transmitting the control signalling after the eNB has gained access to
the carrier may
incur overhead of the reservation signal (proportional to the control
signalling latency). In an
example, the maximum transmission burst may be 4ms. An eNB may inform the UE
to receive a
burst on a carrier. The eNB may send one indication for a burst. There may be
many short bursts
(e.g., one burst may last up to 4 milliseconds in certain regions). The
indication may be sent after
(E)CCA is completed, consuming some portion of the maximum allowed
transmission duration
for a burst.
[00801 It may still be up to the network to transmit the control signalling
before or after the
channel is occupied. A UE may detect that the burst is from the serving cell
(e.g. by confirming
PCID). The function of the control signalling is to indicate that the UE may
perform DL
transmission burst detection of the serving cell. If a DL burst of the serving
cell is detected, UE
may monitor for possible PDCCH/EPDCCH and/or measuring the CSI on the
indicated SCell.
[0081] In an example embodiment, a UE may be configured with a number of
carriers
potentially exceeding the maximum number of carriers over which the UE may
aggregate
PDSCH. RRM measurements over the configured carriers may be supported. e.g.
RSSI-like
measurement, extension of quasi co-location concept to across collocated intra-
band carriers,
22
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
and/or carrier grouping. Li indication to the UE to start monitoring a
carrier, which is selected
from the configured carriers by the eNB may be supported.
[0082] According to some of the various aspects of embodiments, an eNB may
configure UE
with more component carriers which may potentially exceed the maximum number
of carriers
over which the UE may aggregate PDSCH. Then eNB may activate one or more
carriers among
the configured carriers to UE by the existing signalling, e.g. MAC signalling.
UE may be
scheduled on the one or more activated carriers dynamically based on the LBT
mechanism.
[0083] A UE may switch to receive on any carrier within a set of carriers
selected by the
serving eNB as fast as subframe/symbol-level, while the number of carriers
within the set may
potentially exceed the maximum number of carriers over which the UE may
aggregate PDSCH.
Which carrier(s) the UE may switch to is per eNB indication. When the UE is
indicated with the
carrier(s) it may switch to, the UE may start to monitor the indicated
carrier(s), e.g. within a few
subframes, and may stop monitoring other carriers. By monitoring a carrier it
meant to buffer
and attempt to detect the control channels and other associated channels. The
eNB indication
may instruct the UE to switch to the indicated carrier(s) and monitor the
carrier(s). The eNB may
not instruct the UE to switch to monitor on more carriers than its PDSCH
aggregation capability
in a given subframe. The eNB may not schedule the UE on more carriers than its
PDSCH
aggregation capability. SCell configuration enhancements may allow both semi-
static and fast
carrier switching with reduced transition time. The delay associated with the
SCell configuration
signalling as well as the delay associated with the measurement process may be
decreased.
[0084] In an example embodiment, fast carrier switching may support UE to
switch to any
carrier within a set of carriers selected by the serving eNB as fast as a few
subframes/symbols.
The eNB may send an indication instructing the UE to switch to the indicated
carriers and
monitor the carriers. Then the UE may perform the switching and start
monitoring the indicated
carriers. The UE stops monitoring other carriers. The eNB indication may be
done in Ll. A Li
procedure/indicator, or an enhancements of the SCell activation signalling may
be introduced.
[00851 According to some of the various aspects of embodiments, DRS design may
allow DRS
transmission on an LAA SCell to be subject to LBT. The transmission of DRS
within a DMTC
window if LBT is applied to DRS may consider many factors. Subjected to LBT,
DRS may
transmitted in fixed time position within the configured DMTC. Subject to LBT,
DRS may be
transmitted in at least one of different time positions within the configured
DMTC. The number
of different time positions may be restricted. One possibility is one time
position in the
subframe. DRS transmissions outside of the configured DMTC may be supported.
23
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
[0086] According to some of the various aspects of embodiments, an sensing
interval may allow
the start of a DL transmission burst (which may not start with the DRS)
containing DRS without
PDSCH within the DMTC. Total sensing period may be greater than one sensing
interval.
Whether the above may be used for the case where transmission burst may not
contain PDSCH
but contains DRS, and any other reference signals or channels. The ECCA
counter used for LBT
category 4 for the PDSCH may be frozen during DL transmission burst containing
DRS without
PDSCH
[0 0 87] The RS bandwidth and density/pattern of the DRS design for LAA may
support for
RRM measurement based on a single DRS occasion.
00 881 According to some of the various aspects of embodiments, Discovery
signal may be
transmitted via a successful LBT operation. When the eNB does not have access
to the channel,
the discovery signal burst may not be transmitted. In an example, the
discovery signal periodicity
is configured to be 40 ms, and it may be possible to receive the discovery
signal at least once in
every 160 to 200 ms with a high probability. For example, the probability of
receiving a
discovery signal burst at least once in every 160 ms may greater than 97%. The
UE may adjust
its receiver processing to account for the potential absence of discovery
signals due to lack of
access to the channel. For instance, the UE may detect the presence or absence
of a particular
discovery signal burst using the PSS, SSS and CRS signals.
[0 0 89] According to some of the various aspects of embodiments, the use of
discovery signals
that may be subject to LBT. A discovery signal burst may not be transmitted
when LBT fails.
Data may be transmitted in the intervening subframes. The reference signals
along with control
information may be used to reserve the channel prior to a discovery signal or
data transmission.
[0 0 90] For reception of data on the serving cell, AGC and fine time and
frequency estimation
may employ the discovery signals from the serving cell. In an example, time
and frequency
estimation may be performed using the PSS, SSS and/or CRS inside the discovery
signal
subframes. The use of two or more CRS ports may enhance synchronization
performance. These
signals may provide synchronization estimates that are adequate for the
purpose of RRM
measurements on the serving and neighboring cells. When data is to be received
by the UE in a
subframe that occurs a significant number of subframes after the last
reception of a discovery
signal on the serving cell. Fine tuning of the time and frequency estimates
may be perfon-ned
using the DM-RS and, if present, the CRS within the subframe in which data is
received, and/or
the initial signal. The signal used to reserve the channel before the actual
start of data
transmissions (e.g. reservation signal, initial signal, and/or burst
indicator) may be used to fine
tune time and frequency estimates before the reception of data. When
transmitting data after a
24
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
long absence of any discovery signal or other transmissions, the eNB may
transmit a signal of
longer duration to reserve the channel in order to facilitate the use of such
a signal for timing and
frequency adjustments.
[0091] In an example embodiment, in an unlicensed cell, a downlink burst may
be started in a
subframe. When an eNB accesses the channel it may transmit for a duration of
one or more
subframes. The duration may depend on a maximum configured burst duration in
an eNB, the
data available for transmission, and/or eNB scheduling algorithm. FIG. 10
shows an example
downlink burst in an unlicensed (e.g. licensed assisted access) cell. The
maximum configured
burst duration in the example embodiment may be configured in the eNB. An eNB
may transmit
the maximum configured burst duration to a UE employing an RRC configuration
message.
[0092] The wireless device may receive from a base station at least one
message (e.g. RRC)
comprising configuration parameters of a plurality of cells. The plurality of
cells may comprise
at least one license cell and at least one unlicensed (e.g. LAA cell). The
configuration parameters
of a cell for example may comprise configuration parameters for physical
channels, e.g.
ePDCCH, PDSCH, PUSCH, PUCCH and/or the like. In an example embodiment, IE
epdcch-
Config may indicate the EPDCCH-Configuration for a cell.
[0093] The information element (IE) EPDCCH-Config in the RRC message may
comprise
configuration parameters of an ePDCCH and may configure ePDCCH for a cell. The
IE
EPDCCH-Config may specify the subframes and resource blocks for EPDCCH
monitoring that
E-UTRAN may configure for a serving cell. In an example, ePDCCH-Config may
comprise
subframePatternConfig, startSymbol, setConfigToReleaseList, and
setConfigToAddModList,
and other ePDCCH parameters. In an example, EPDCCH-SetConfigToAddModList may
comprise SEQUENCE (SIZE(1..maxEPDCCH-Set-r11)) OF EPDCCH-SetConfig. In an
example, EPDCCH-SetConfigToReleaseList may comprise SEQUENCE
(SIZE(1..maxEPDCCH-Set-r11)) OF EPDCCH-SetConfigId. In an example, EPDCCH-
SetConfig may comprise setConfigId (an identifier for an ePDCCH set),
transmissionType:
ENUMERATED {localised, distributed}, resourceBlockAssignment:
SEQUENCE{numberPRB-Pairs: ENUMERATED {n2, n4, n8}, resourceBlockAssignment:
BIT
STRING (SIZE(4..38))1, dmrs-ScramblingSequenceInt: INTEGER (0..503), and pucch-
ResourceStartOffset: INTEGER (0..2047), and/or other configuration parameters.
[0094I In an example, the start symbol may indicate the OFDM starting symbol
for any
EPDCCH and PDSCH scheduled by EPDCCH on the same cell in a subframe of a
licensed cell
or a full subframe of an unlicensed (e.g. LAA cell). If not present, the UE
may derive the starting
OFDM symbol of EPDCCH and PDSCH scheduled by EPDCCH from PCFICH. In an
example,
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
values 1. 2, and 3 may be applicable for dl-Bandwidth greater than 10 resource
blocks. Values 2,
3, and 4 may be applicable otherwise. In an example, E-UTRAN may not configure
the field for
UEs configured with transmission mode 10.
[0095] In an example, the IF subframePatternConfig may configure the subframes
which the
UE may monitor the UE-specific search space on EPDCCH, except for pre-defined
rules in the
LTE technology standard. The ePDCCH may be transmitted in one or more
subframes identified
by subframePatternConfig and pre-defined rules, and may not be transmitted in
other subframes.
If the field is not configured when EPDCCH is configured, the UE may monitor
the UE-specific
search space on EPDCCH in subframes except for pre-defined rules in the LTE
technology
standard.
[0096] In an example, IE numberPRB-Pairs may indicate the number of physical
resource-block
pairs used for the EPDCCH set. For example, value n2 may correspond to 2
physical resource-
block pairs; n4 corresponds to 4 physical resource-block pairs and so on.
Value n8 may not be
supported if dl-Bandwidth is set to 6 resource blocks.ln an example, IE
resourceBlockAssignment may indicate the index to a specific combination of
physical resource-
block pair for EPDCCH set that is pre-defined in the technology standard. The
size of
resourceBlockAssignment may be specified in technology standard and based on
numberPRB-
Pairs and the signalled value of dl-Bandwidth.
[0097] The IE dmrs-ScrarnblingSequenceInt may indicate the DMRS scrambling
sequence
initialization parameter. The IE pucch-ResourceStartOffset may indicate PUCCH
format la and
lb resource starting offset for the EPDCCH set. The IE transmissionType may
indicates whether
distributed or localized EPDCCH transmission mode is used.
[0098] In an example embodiment, the wireless device may receive, from a base
station,
downlink control information (DCI) in the ePDCCH resources of a subframe. The
DCI may be
scrambled, by the base station, with the C-RNTI assigned to the wireless
device. The DCI may
comprise an uplink grant or a downlink grant comprising radio resources (e.g.
RBs) for the
wireless device.
[0099] When the DCI of a subframe comprises a downlink grant, the UE may
receive from the
base station one or more transport blocks, in the subframe, in radio resources
indicated in the
downlink grant. The wireless receive may receive the one or more transport
blocks. The wireless
device may transmit to the base station one or more positive or negative
acknowledgement in
response to receiving the one or more transport blocks. The downlink DCI may
further comprise
MCS, MIMO information, HARQ information (HARQ process ID, RV, and/or NDI),
and/or the
like for the one or more transport blocks.
26
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
[00100] When the DCI of a subframe comprises an uplink grant, the UE may
transmit to the
base station one or more transport blocks in a corresponding subframe, in
radio resources
indicated in the uplink grant. The wireless device may transmit to the base
station the one or
more transport blocks. The wireless device may receive front the base station
one or more
positive or negative acknowledgement in response to transmitting the one or
more transport
blocks. The uplink DCI may further comprise MCS, MIMO information, HARQ
information
(harq process ID, RV, NDI), power control command and/or the like for the one
or more
transport blocks.
[00101] In LTE-A release 11 and 12, the information element startSymbol in
epdcch-Config IE
indicates the OFDM starting symbol for any EPDCCH and PDSCH scheduled by
EPDCCH on
the same cell. If startSymbol is not present, the UE may derive the starting
OFDM symbol of
EPDCCH and PDSCH scheduled by EPDCCH from PCFICH. Values 1, 2, and 3 are
applicable
for dl-Bandwidth greater than 10 resource blocks. Values 2. 3, and 4 are
applicable otherwise. E-
UTRAN may not configure the field for UEs configured with transmission mode
10.
[001021 In LTE-A release 11 and 12, EPDCCH starting position may be determined
according
to a mechanism described here. For a given serving cell, if the UE is
configured via higher layer
signaling to receive PDSCH data transmissions according to transmission modes
1-9, if the UE
is configured with a higher layer parameter epdcch-StartSymbol-r11, the
starting OFDM symbol
for EPDCCH given by index /EPDCCHS tat in the first slot in a subframe is
determined from the
higher layer parameter, otherwise: the starting OFDM symbol for EPDCCH given
by index
lEPDCCHStat in the first slot in a subframe is given by the CFI value in the
subframe of the given
NDL 0 , /
serving cell when R and B EPDCCIIStat is given by the CFI value+1 in
the subframe of the
DL
/V <10
given serving cell when RB .
[ 00 1 0 3 ] For a given serving cell, if the UE is configured via higher
layer signalling to receive
PDSCH data transmissions according to transmission mode 10, for each EPDCCH-
PRB-set, the
starting OFDM symbol for monitoring EPDCCH in subframe k is determined from
the higher
layer (RRC) parameter pdsch-Start-r11 as follows. If the value of the
parameter pdsch-Start-rll
belongs to {1,2,3,4}, 5PDCCHStt is given by the higher layer parameter pdsch-
Start-r11. Otherwise
when the value of pdsch-Start-rll is not provided by RRC: 'EPDCCHSS,t is given
by the CFI value
DL
in subframe k of the given serving cell when N >1", and rEPDCCHStart is given
by the CFI
, õ
value+1 in subframe k of the given serving cell when ' If
subframe k is indicated by the
27
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
higher layer parameter mbsfn-SubframeConfigList-r11, 1 EPDCCHStax
EPDCCHStat otherwise
IEPDCCHStart = IEPDCCHStar t
[ 0 0 1 0 4 ] In LTE-A release 11 and 12, ePDCCH starting symbol may be
determined according to
epdcch-StartSymbol-r11, pdsch-Start-r11, CFI value, and/or other parameters
shown above. For
example, when mbsfn-SubframeConfigList-r11 is configured, the starting symbol
may be
determined according to the configuration parameters described above and some
pre-defined
rules.
[00105] In an example embodiment, one or two sets of ePDCCH resources may be
configured
on an LAA cell. In an example embodiment, the mechanisms for determining the
starting symbol
for ePDCCH configured on LAA cell may be determined employing an enhanced
mechanism to
improve radio resource utilization efficiency and reduce signaling overhead.
Example
embodiments provide a mechanism for determining the starting symbol of ePDCCH
on
downlink transmission on partial and full subframes. Example embodiments
improve radio
resource utilization on an LAA cell.
[00106] Transmission of an additional field indicating the ePDCCH starting
symbol of a
subframe via a physical layer channel signaling may increase physical layer
overhead.
Additional physical layer signaling for indicating ePDCCH starting symbol may
increase
downlink signaling overhead. In contrast, transmission of a start symbol field
for ePDCCH in an
RRC message may provide a semi-static method for configuration of ePDCCH
starting symbol
and may reduce downlink signaling overhead and provide the required
flexibility in configuring
the starting symbol of the ePDCCH. In an example embodiment, an eNB may
transmit an RRC
message comprising a start symbol field (1E) employed for determining a
starting symbol of
ePDCCH. In an example embodiment this field may be employed to determine the
starting
symbol in partial and full subframe according to a pre-define rule. When the
start symbol field is
not included in the RRC message, the eNB may employ other signals or fields
(e.g. CFI,
PDSCH-start and/or other paramters) in determining a starting symbol for the
ePDCCH in a
subframe and there may be no need to specify a specific field dedicated for
ePDCCH starting
symbol calculation.
[00107] In an example embodiment, a UE may detect the starting symbol of a
partial subframe
(Offset_Symbol). The starting symbol may be determined employing detection of
a pre-defined
signal, e.g. an initial signal, burst indicator signal/PCFICH, CRS, and/or the
like. A UE may
decode (e.g. blind decode) a known signal pattern (e.g. among many
possibilities) and determine
the starting symbol of a partial subframe. The starting symbol of a subframe
may be named
28
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
Offset_symbol. The Offset_symbol is zero for a full subframe. Example of
beginning partial
subframe (partial subframe), a full subframe, and ending partial subframe is
shown in FIG. 10.
[00108] In an example embodiment, Offset_symbol may be one of one or more
possible values.
The one or more possible values may be predefined, or may be configured by one
or more RRC
message for an LAA cell. In an example embodiment, an eNB may transmit an RRC
message
comprising configuration parameters of a cell. The configuration parameters
may comprise one
or more parameters indicating possible starting symbol values for a subframe.
For example, the
configuration parameters may indicate the possible starting symbol may be
symbol 0 or 7 (at slot
boundaries). For example, the configuration parameters may indicate the
possible starting
symbol may be symbol 0.
[00109] In an example, the Offset_symbol may be 7 for a partial subframe and 0
for a full
subframe. The embodiments provide the needed flexibility in implementing
partial subframes,
wherein the starting symbol of a subframe transmision may not be zero. In an
example
embodiment, symbols in a subframe may be numbered from 0 to 13 (See example
example FIG.
2). For example, the first symbol is symbol 0, the second symbol is symbol 1,
etc. In an example,
symbols in a slot may be numbered from 0 to 6. A subframe may comprise a first
slot and a
second slot (See example example FIG. 2).
[00110] Example embodiments provide mechanisms for determining the starting
symbol for a
partial subframe and a full subframe. Example control channel mapping is
provided below.
Other equivalent mechanisms using different formulas may be implemented, which
result in the
same resource element mapping.
[00111] In an example embodiment, one StartSymbol IE may be configured for
ePDCCH of a
cell. In a full subframe, ePDCCH starting symbol may be the value of
StartSymbol IE. In a
partial subframe, the ePDCCH starting symbol may be the value of StartSymbol
IE +
Offset_symbol. A UE may detect Offset_symbol employing decoding the received
signal (e.g.
blind decoding) and employing RRC signaling (using a field in an RRC message).
In an example
embodiment, up to two sets of ePDCCH may be configured. The same StartSymbol
IE may be
applicable to one or two sets of ePDCCH and the one or two sets may have the
same starting
symbol. The starting symbol applicable to the one or two sets may be
determined depending on
whether ePDCCH is transmitted in a full subframe or a partial subframe. An
example ePDCCH
configuration in a full and partial subframe is shown in FIG. 11. Transmission
of one
StartSymbol IE for determining ePDCCH starting symbol for both partial and
full subframes and
for one or two sets of ePDCCH redcues the size of RRC message (compared with
transmitting
two or more StartSymbol IEs). An example emboidment reduces downlink signaling
overhead.
29
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
[00112] In an example, a parameter in the at least one RRC message may
indicate possible
starting positions of transmission in a subframe of a downlink transmission
burst in an LAA cell.
The starting positions may be applicable to downlink data/control signal
transmission and not to
the reservation signals. For example, a first value of the parameter may
indicate the starting
position is subframe boundary, and a second value of the parameter may
indicate the the starting
position is either subfarme boundary or slot boundary (beginning of the first
or second slot of a
subframe). Reservation signal may start at any point in time depending on the
base station
implementation.
[00113] In an example embodiment, for a given serving cell, if the UE is
configured via higher
layer signaling to receive PDSCH data transmissions according to transmission
modes 1-9, if
the UE is configured with a higher layer parameter epdcch-StartSymbol (in an
RRC message),
the starting OFDM symbol for EPDCCH given by index /EPDCCHStart is determined
from the
higher layer parameter, otherwise the starting 01-DM symbol for EPDCCH given
by index
lEPDCCHStart is given by the CFI (control format indicator) value in the
subframe of the given
serving cell when N RBDL >10 , and / EPDCCHStart is given by the CFI value+1
in the subframe of the
DL
given serving cell when N RB 1 . In an example, in an initial partial
subframe, the 1EPDCCHStart
for the ePDCCH may be offset by Offset_symbol OFDM symbols, e.g. by 7 symbols
(Or equally
the 1EPDCCHStan may be applicable to the second slot.). In a full subframe,
the 1EPDCCHStart for the
ePDCCH may be applicable to the first slot.
[00114] For a given serving cell, if the UE is configured via higher layer
signalling to receive
PDSCH data transmissions according to transmission mode 10, for each EPDCCH-
PRB-set, the
starting OFDM symbol for monitoring EPDCCH in subframe k is determined from
the higher
layer parameter pdsch-Start as follows: if the value of the parameter pdsch-
Start belongs to
(1,2,3,41, EPDCCHStat is given by the higher layer parameter pdsch-Start,
otherwise 1' EPDCCHStart is
RBDL
given by the CFI value in subframe k of the given serving cell when N '1vn
, and 1' EPDCCHSrar is
N DL
given by the CFI value+1 in subframe k of the given serving cell when RB 1 .
In an example,
in an initial partial subframe, the 1EPDCCHStart for the ePDCCH may be offset
by Offset_symbol
OFDM symbols, e.g. by 7 symbols. If subframe k is indicated by the higher
layer parameter
mbsfn-SubframeConfigList, or if subframe k is subframe 1 or 6 for frame
structure type 2,
1 EPDCCHStart Min(2, EPDCCHStart otherwise IEFOCCHStal ¨ I EPOCCHStar In an
example, in an initial partial
subframe, the EPDCCHStart for the ePDCCH may be offset by Offset_symbol OFDM
symbols, e.g.
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
by 7 symbols (Or equally the lEPDCCHStart may be applicable to the second
slot.). In a full
subframe, the 1EPDCCHStart for the ePDCCH may be applicable to the first slot.
The IE pdsch-Start
may indicate the starting OFDM symbol of PDSCH for a cell. In an example,
values 1, 2, 3 may
be applicable when dl-Bandwidth for the concerned SCell is greater than 10
resource blocks,
values 2. 3, 4 may be applicable when dl-Bandwidth for the concerned SCell is
less than or equal
to 10 resource blocks.
[00115] In an example embodiment a wireless device may receive control format
indicator in a
subframe. The wireless device may receive an enhanced physical downlink
control channel
(ePDCCH) signal in the subframe. The ePDCCH may start from an ePDCCH starting
symbol
determined based on the control format indicator, when the subframe is a full
subframe. The
ePDCCH starting symbol is calculated using CFI value and channel bandwidth.
The ePDCCH
starts from the starting symbol plus an offset value when the subframe is a
partial subframe. For
N DL 10
example, the ePDCCH starting symbol may be given by CFI value when " in a
full
subframe. The ePDCCH starting symbol may be given by CFI value +offset_value
when
NRDBL >10
in a partial subframe. When the subframe is an MBSFN subframe, the minimum
ePDCCH starting symbol may be 2 for a full subframe and 2+offset_value for a
partial subframe.
[00116] In an example embodiment, a wireless device (e.g. operating in
transmission mode 10)
may receive at least one radio resource control (RRC) message comprising a
field indicating a
starting symbol for a physical downlink shared channel (PDSCH). The wireless
device may
receive an enhanced physical downlink control channel (ePDCCH) signal in a
subframe. The
ePDCCH may start from an ePDCCH starting symbol determined based on the
starting symbol
for the PDSCH, when the subframe is a full subframe. The ePDCCH may start from
the
ePDCCH starting symbol plus an offset value when the subframe is a partial
subframe. For
example, if the value of the parameter pdsch-Start-r11 belongs to {1,2,3,4},
ePDCCH starting
symbol is given by the higher layer parameter pdsch-Start-r11 for a full
subframe. If the value of
the parameter pdsch-Start-rll belongs to {1,2,3,41, ePDCCH starting symbol is
given by the
higher layer parameter pdsch-Start-r11+Offset value for a partial subframe.
When the subframe
is an MBSFN subframe, the minimum ePDCCH starting symbol may be 2 for a full
subframe
and 2+offset_value for a partial subframe.
[00117] If a serving cell is a LAA Scell, and if the parameter in RRC
indicates subframe Start
Position for a partial subrame may be 7 (Offset symbol), for monitoring EPDCCH
candidates
starting in the first slot of the subframe, the starting OFDM symbol for
EPDCCH is given by
index lEPDCCHStart in the first slot in a subframe, and for monitoring EPDCCH
candidates starting
31
CA 03000508 2018-03-28
WO 2017/066803
PCT/US2016/057420
in the second slot of the subframe, the starting OFDM symbol for EPDCCH is
given by index
/EPDCCHStar Offset_symbol in a subframe (or equally /EPDCCHStait in the
second slot in a
subframe). The starting symbol is offset by Offset_symbol=7 in a partial
subframe.
[00118] In an example, ePDCCH resource mapping (in ePDCCH RBs) may start from
the
ePDCCH starting symbol of the first slot for a full (regular) subframe of an
LAA cell. In an
example, in an initial partial subframe, the ePDCCH start symbol for the
ePDCCH if configured,
may be offset additionally by Offset_symbol OFDM symbols, e.g. by 7 symbols.
In an example,
ePDCCH resource mapping (in ePDCCH RBs) may start from the ePDCCH starting
symbol of
the second slot for a partial subframe of an LAA cell. In an initial partial
subframe, the ePDCCH
start symbol for the ePDCCH if configured, may be start at symbol
Offset_symbol+the starting
symbol of a subframe. In an example, the number of available resource elements
for the
EPDCCH may be an actual number of available REs for the EPDCCH transmission in
the initial
partial subframe.
[ 0 0119] The CFI takes values CFI = 1, 2 or 3. For system bandwidths N ''"n
, the span of the
DCI carried by PDCCH in units of OFDM symbols, 1, 2 or 3, is given by the CFI
(e.g. span 3
NDL < 10
symbols include symbol numbers 0, 1, 2). For system bandwidths RI3 , the
span of the DCI
carried by PDCCH in units of OFDM symbols, 2, 3 or 4, is given by CFI+1.
[00120] For a
given serving cell, if the UE is configured via higher layer signalling to
receive
PDSCH data transmissions according to transmission modes 1-9, and when
StartSymbol IE is
not configured, the starting symbol of ePDCCH may depend on CFI or other
parameters.
[00121] In an example embodiment, in a full subframe, when CFI value is
greater than zero, the
starting OFDM symbol for EPDCCH given by index lEPDCCHStat in the first slot
in a subframe is
DL > 10, and
given by the CFI value in the subframe of the given serving cell when N RIB
lEPDCC HS tat
,DL < in
is given by the CFI value+1 in the subframe of the given serving cell when '
RB . This is for
the case when ePDCCH is transmitted in the full subframe.
[00122] In an example embodiment, in a partial subframe, when CFI value is
greater than zero,
the starting OFDM symbol for EPDCCH given by index F PIX HStat in a subframe
is given by the
, DL
CFI+ Offset_symbol value in the subframe of the given serving cell when ' RB
>10, and
/EPDCCHSLA is given by the CFI value+1+ Offset_symbol in the subframe of the
given serving cell
DL <10
when " RB . PUS is for the case when ePDCCH is configured in the partial
subframe.
32
CA 03000508 2018-03-28
WO 2017/066803 PCT/1JS2016/057420
[00123] In a serving cell, if subframe k is indicated as an MBSFN subframe (by
PHY or RRC
layer signaling), or if subframe k is subframe 1 or 6 for frame structure type
2,
1 EPDCCHSDar = min(2, rEPDCCHStmr) . ePDCCH starting position may not be
smaller than 2.
[00124] In an example embodiment, in an LAA serving cell, if subframe k is
indicated as an
MBSFN subframe (by PHY or RRC layer signaling e.g. by the higher layer
parameter mbsfn-
SubframeConfigList-r1 1) 1LPDCCHStat= min(Offset_syrrbol+ k , rEppcõsnt ),
wherein k =1, or k = 2.
ePDCCH starting position may be Offset symbol +1 or Offset symbol +2. In an
example, the
first one or more symbols may be employed for transmission of physical
signals, such as burst
indicator, initial signal, or other physical layer signals carrying
information about the
subframe/burst configuration. When the starting symbol is Offset_symbol +1,
the symbol
Offset_symbol may be used for transmission physical at least one
signal/channel.
[00125] In an example embodiment, in an LAA serving cell, if subframe k is
subframe 1 or 6,
tEõccõ,,õõ = min(Offset_synbol + k, l'EPDCCHStar)5 wherein k =1, or k = 2. In
an example UE
implementation k may be 1. In another example UE implementation k may be 2.
ePDCCH
starting position may be Offset_symbol +1 or Offset_symbol +2 according to a
UE
implementation. The first one or more symbols may be employed for transmission
of physical
signals, such as burst indicator, initial signal, or other physical layer
signals carriying
information about the subframe/burst configuration.
[00126] In an example embodiment, a wireless device may receive at least one
radio resource
control (RRC) message comprising a field indicating a starting symbol for an
enhanced physical
downlink control channel (ePDCCH). The wireless device may receive ePDCCH
signal in a
subframe. The ePDCCH may start from the starting symbol when the subframe is a
full
subframe. The ePDCCH may start from the starting symbol plus an offset value
when the
subframe is a partial subframe.
[00127] A base station may transmit at least one radio resource control (RRC)
message
comprising a field indicating a starting symbol for an enhanced physical
downlink control
channel (ePDCCH). The base station may transmit ePDCCH signal in a subframe.
The ePDCCH
may start front the starting symbol when the subframe is a full subframe. The
ePDCCH may start
from the starting symbol plus an offset value when the subframe is a partial
subframe.
[00128] The at least one RRC message may further comprise configuration
parameters of a cell.
The cell may be a licensed assisted access (LAA) cell. The at least one RRC
message may
further comprises configuration parameters comprising one or more parameters
indicating
resource blocks (RBs) for the ePDCCH. The at least one or more parameters
indicate one or two
33
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
sets of RB pairs. The field indicating the starting symbol may be applicable
to the one or two
sets of RB pairs. The at least one or more parameters may comprise a first
parameter indicating a
number of RB pairs; and a second parameter indicating an index identifying RB
assignment. The
at least one RRC message may further comprise at least one second parameter
indicating a
subframe pattern comprising one or more subframes, the one or more subframes
comprising the
subframe. The wireless device may receive from the base station one or more
downlink transport
blocks in a PDSCH employing a downlink grant received in the ePDCCH.
[00129] The at least one RRC message may further comprise a parameter
indicating one or
more possible starting positions of transmission in the subframe, the
parameter being employed
by the wireless device to determine the offset value. In an example, the
offset value is seven. The
partial subframe may start from a symbol indicated by the offset value. A
subframe may
comprise two slots in time. A slot comprises a plurality of symbols.
[00130] The wireless device may detect whether the subframe is the full
subframe or the partial
subframe. The wireless device may receive a physical downlink shared channel
(PDSCH) in the
subframe. The starting symbol may be further employed for determining a PDSCH
starting
symbol in the subframe. The PDSCH may start from the starting symbol when the
subframe is
the full subframe. The PDSCH may start from the starting symbol plus the
offset value when the
subframe is the partial subframe.
[00131] In an example emboidment, MBSFN may be configured employing one or
more RRC
messages. IE mbsfn-SubframeConfigList-r11 may comprise
subframeConfigList:MBSFN-
SubframeConfigList.
[00132] In an example, MBSFN-SubframeConfigList may be SEQUENCE (SIZE
(1..maxMBSFN-Allocations)) OF MBSFN-SubframeConfig. The IE MBSFN-
SubframeConfig
may define subframes that are reserved for MBSFN in downlink. For example, IE
MBSFN-
SubframeConfig may be SEQUENCE fradioframeAllocationPeriod: ENUMERATED Inl,
n2,
n4, n8, n16, n321, radioframeAllocationOffset: INTEGER (0..7), subframeAll
cation: CHOICE
toneFrame: BIT STRING (SIZE(6)), fourFrames: BIT STRING(SIZE(24))1.
[00133] In an example, IE fourFrames may be a bit-map indicating MBSFN
subframe
allocation in four consecutive radio frames, "1" may denote that the
corresponding subframe is
allocated for MBSFN. The bitmap may be interpreted as follows: FDD: Starting
from the first
radioframe and from the first/leftmost bit in the bitmap, the allocation may
apply to subframes
#1, #2, #3 , #6, #7, and #8 in the sequence of the four radio-frames. TDD:
Starting from the first
radioframe and from the first/leftmost bit in the bitmap, the allocation may
apply to subframes
34
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
#3, #4, #7, #8, and #9 in the sequence of the four radio-frames. The last four
bits may not be
used. Uplink subframes may not allocated unless the field eimta-MainConfig-r12
is configured.
[00134] In an example, IE oneFrame may may be a bit-map indicating MBSFN
subframe
allocation in one radio frame. "1" may denote that the corresponding subframe
is allocated for
MBSFN. The following mapping may apply: FDD: The first/leftmost bit defines
the MBSFN
allocation for subframe #L the second bit for #2, third bit for #3 , fourth
bit for #6, fifth bit for
#7, sixth bit for #8. TDD: The first/leftmost bit may define the allocation
for subframe #3, the
second bit for #4, third bit for #7, fourth bit for #8, fifth bit for #9.
Uplink subframes may not be
allocated unless the field eimta-MainConfig-r12 is configured. The last bit
may not be used.
[00135] In an example, IE radioFrameAllocationPeriod,
radioFrameAllocationOffset may be
configured. Radio-frames that contain MBSFN subframes may occur when equation
SFN mod
radioFrameAllocationPeriod = radioFrameAllocationOffset is satisfied. Value n1
for
radioframeAllocationPeriod may denote value 1, n2 may denote value 2, and so
on. When
fourFrames is used for subframeAllocation, the equation may define the first
radio frame
referred to in the description below. Values n1 and n2 may not be applicable
when fourFrames is
used.
[00136] In an example, IE subframeAllocation may define the subframes that are
allocated for
MBSFN within the radio frame allocation period defined by the
radioFrameAllocationPeriod and
the radioFrameAllocationOffset.
[00137] In this specification, "a" and "an" and similar phrases are to be
interpreted as "at least
one" and "one or more." In this specification, the term "may" is to be
interpreted as "may, for
example." In other words, the term "may" is indicative that the phrase
following the term "may"
is an example of one of a multitude of suitable possibilities that may, or may
not, be employed to
one or more of the various embodiments. If A and B are sets and every element
of A is also an
element of B, A is called a subset of B. In this specification, only non-empty
sets and subsets are
considered. For example, possible subsets of B = {cell], ce112} are: {cell -
1}, {ce112}, and fce111,
ce1121.
[00138] In this specification, parameters (Information elements: IEs) may
comprise one or
more objects, and each of those objects may comprise one or more other
objects. For example, if
parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises
parameter (1E)
K, and parameter (1E) K comprises parameter (information element) J, then, for
example, N
comprises K, and N comprises J. In an example embodiment, when one or more
messages
comprise a plurality of parameters, it implies that a parameter in the
plurality of parameters is in
CA 03000508 2018-03-28
WO 2017/066803 PCT/US2016/057420
at least one of the one or more messages, but does not have to be in each of
the one or more
messages.
[00139] Many of the elements described in the disclosed embodiments may be
implemented as
modules. A module is defined here as an isolatable element that performs a
defined function and
has a defined interface to other elements. The modules described in this
disclosure may be
implemented in hardware, software in combination with hardware, firmware,
wetware (i.e
hardware with a biological element) or a combination thereof, all of which are
behaviorally
equivalent. For example, modules may be implemented as a software routine
written in a
computer language configured to be executed by a hardware machine (such as C,
C++, Fortran,
Java, Basic, Matlab or the like) or a modeling/simulation program such as
Simulink, Stateflow,
GNU Octave, or LabVIEWMathScript. Additionally, it may be possible to
implement modules
using physical hardware that incorporates discrete or programmable analog,
digital and/or
quantum hardware. Examples of programmable hardware comprise: computers,
microcontrollers, microprocessors, application-specific integrated circuits
(ASICs); field
programmable gate arrays (FPGAs); and complex programmable logic devices
(CPLDs).
Computers, microcontrollers and microprocessors are programmed using languages
such as
assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed
using hardware
description languages (HDL) such as VHSIC hardware description language (VHDL)
or Verilog
that configure connections between internal hardware modules with lesser
functionality on a
programmable device. Finally, it needs to be emphasized that the above
mentioned technologies
are often used in combination to achieve the result of a functional module.
[00140] The disclosure of this patent document incorporates material which is
subject to
copyright protection. The copyright owner has no objection to the facsimile
reproduction by
anyone of the patent document or the patent disclosure, as it appears in the
Patent and Trademark
Office patent file or records, for the limited purposes required by law, but
otherwise reserves all
copyright rights whatsoever.
[00141] While various embodiments have been described above, it should be
understood that
they have been presented by way of example, and not limitation. It will be
apparent to persons
skilled in the relevant art(s) that various changes in form and detail can be
made therein without
departing from the spirit and scope. In fact, after reading the above
description, it will be
apparent to one skilled in the relevant art(s) how to implement alternative
embodiments. Thus,
the present embodiments should not be limited by any of the above described
exemplary
embodiments. In particular, it should be noted that, for example purposes, the
above explanation
has focused on the example(s) using FDD communication systems. However, one
skilled in the
36
= CA 03000508 2018-03-28
=
WO 2017/066803
PCT/US2016/057420
art will recognize that embodiments of the invention may also be implemented
in a system
comprising one or more TDD cells (e.g. frame structure 2 and/or frame
structure 3-licensed
assisted access). The disclosed methods and systems may be implemented in
wireless or
wireline systems. The features of various embodiments presented in this
invention may be
combined. One or many features (method or system) of one embodiment may be
implemented in
other embodiments. Only a limited number of example combinations are shown to
indicate to
one skilled in the art the possibility of features that may be combined in
various embodiments to
create enhanced transmission and reception systems and methods.
[00142] In
addition, it should be understood that any figures which highlight the
functionality
and advantages, are presented for example purposes only. The disclosed
architecture is
sufficiently flexible and configurable, such that it may be utilized in ways
other than that shown.
For example, the actions listed in any flowchart may be re-ordered or only
optionally used in
some embodiments.
[00143]
Further, the purpose of the Abstract of the Disclosure is to enable the U.S.
Patent and
Trademark Office and the public generally, and especially the scientists,
engineers and
practitioners in the art who are not familiar with patent or legal terms or
phraseology, to
determine quickly from a cursory inspection the nature and essence of the
technical disclosure of
the application. The Abstract of the Disclosure is not intended to be limiting
as to the scope in
any way.
37
