TITLE: Basic Multicarrier EVDV operation SOURCE:

illnurturedtownvilleMobile - Wireless

Nov 21, 2013 (3 years and 8 months ago)

64 views

12/6/2004

1




TITLE
:

Basic

Multicarrier

EVDV

operation



SOURCE
:


Srinivasan

Balasubramanian


Srinivasan
.
Balasubramanian@ericsson
.
com


David

Comstock


david
.
comstock@ericsson
.
com



ABSTRACT
:


This

contribution

provides

stage

2

information

for

basic

multicarrier

EVDV

operation
.



RECOMMENDATION
:

Discuss and Adopt.




Ericsson Wireless Communication Incorporated grants a free, irrevocable license to 3GPP2 and its Organizational Partners to i
nco
rporate text or other
copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to
cop
yright and sell in Organizational
Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribu
tio
n; and at the Organizational
Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational

Pa
rtner's standards publication.
Ericsson Wireless Communication Incorporated is also willing to grant licenses under such contributor copyrights to third par
tie
s on reasonable, non
-
discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this co
ntr
ibution.



This document has been prepared by Ericsson Wireless Communication Incorporated to assist the development of specifications b
y 3
GPP2. It is proposed to the
Committee as a basis for discussion and is not to be construed as a binding proposal on Ericsson Wireless Communication Incor
por
ated. Ericsson Wireless
Communication Incorporated specifically reserves the right to amend or modify the material contained herein and to any intell
ect
ual property of Ericsson
Wireless Communication Incorporated other than provided in the copyright statement above
.

12/6/2004

2

EV
-
DV Basic Multicarrier Operation

(NxEV
-
DV)

12/6/2004

3


Simple solution with minimal changes to the
specifications


Specification work done over short time period


Equivalent operation to multiple instances of 1xEV
-
DV


Performance of each carrier same as 1xEV
-
DV


Only changes to Layer 3 Signaling

Objectives for EV
-
DV

basic multicarrier operation

12/6/2004

4

Physical Layer

Layer
Function
Desired
Physical Layer specification
No impacts to Physical Layer specification.
Multiple instances of the TIA-2000 Rev D 1xEVDV Radio
Configurations are used.
F/R-PDCHs on different carriers and associated with the
same call instance operate independently and may have
different configurations.
Common channels
No multicarrier operation for common channels.
Common Channel Layer 3 signaling messages for system
acquisition and access are transmitted on single carriers
only.
Fundicated and Supplemental
channels
No multicarrier operation for Fundicated and Supplemental
channels
A call instance is only associated with an FCH/DCCH/SCHs
on one carrier at any time. The FCH/DCCH/SCH may be
assigned on any carrier assigned to the mobile station.
Number of Forward
link/Reverse Link carriers
Up to 3 (N) carriers for F-PDCH and 3 (M) carriers for R-
PDCH operation may be assigned. N greater than or equal
to M.
For the F-PDCH, the aggregate peak rate would be Nx3.072
Mbps. For the R-PDCH, the aggregate peak rate would be
Mx1.8456Mbps.
MS multicarrier capabilities
indications
MS multicarrier supported indicator.
MS multicarrier contiguous carriers required indicator.
Physical layer
12/6/2004

5

MAC Sublayer

Layer
Function
Desired
MAC specification
No impacts to MAC specification.
Each carrier uses an instance of the TIA-2000 Rev D 1xEVDV MAC
sublayer and shares the assigned dedicated logical channels (f/r-dsch, f/r-
dtch) associated with the call instance.
Logical to Physical channels
mapping
Logical channels mapped to multiple Physical channels on multiple
carriers using Logical to Physical Mapping table.
F/R-PDCCH operation
F/R-PDCCH operation applies only to the F/R-PDCH on the
corresponding carrier.
CQI reporting
CQI reporting applies only to the corresponding carrier.
Cell Selection
Cell Selection for each carrier operates independently. Implementation
specific means can be used to reduce losses when serving sectors for
different carriers belong to different BTSs.
R-REQCH operation
R-REQCH power level reports apply only to the corresponding carrier.
REQCH buffer level reports correspond to the buffer level of the
application (s) associated with a call instance.
F-RCCH operation
F-RCCH operation applies only to the corresponding carrier.
The base station controls the F-RCCH operations on each carrier
independently, i.e., rate assignments are done on a carrier basis.
F-GCH operation
F-GCH operation applies only to the corresponding carrier.
The base station controls the F-GCH operations on each carrier
independently, i.e., rate assignments are done on a carrier basis.
MAC Sublayer
12/6/2004

6

RLP and LAC Sublayer

Layer
Function
Desired
RLP
RLP operation
No impacts to RLP specification
A single RLP instance (logical channel/srid) is mapped to
multiple carriers.
Requests for data for the logical channel are made to the RLP
by the MAC sublayer instances based on the current PDCH
resource assignments. Data sequencing is maintained since a
single RLP is used across the multiple carriers.
NAKs may be sent on any carrier.
Retransmissions may be sent on any carrier.
LAC specification
No impacts to LAC specification
LAC operation
A single LAC instance (logical channel/srid) is mapped to
multiple carriers.
Common channel messages (f/r-csch logical channel) are sent
on single carrier channels.
Dedicated signaling messages may be sent on different carriers
but a single message must be sent entirely on 1 carrier to
ensure in order delivery. Requests for data for the logical
channel are made to the LAC sublayer by the MAC sublayer
instances based on the current PDCH resource assignments.
LAC Sublayer
12/6/2004

7

Mux-1
R-PDCH CF-1
Phy Layer-1 (FA-2)
LAC
F-PDCH CF-1
r-pdch-1
f-pdch-1
Mux-0
R-PDCH CF-0
Phy Layer-0 (FA-1)
F-PDCH CF-0
r-pdch-0
R-PDCH-0/
R-PDCCH-0
f-pdch-0
F-PDCH-00/
F-PDCCH-00
F-PDCH-01/
F-PDCCH-01
F-ACKCH-0
R-REQCH-0
F-GCH-0
F-RCCH-0
R-ACKCH-0
R-CQICH-0
RLP_A
f/r-dsch
F/R-FCH/DCCH/SCH
f/r-dtch_rlpa
R-PDCH-1/
R-PDCCH-1
F-ACKCH-1
R-REQCH-1
F-GCH-1
F-RCCH-1
F-PDCH-10/
F-PDCCH-10
F-PDCH-11/
F-PDCCH-11
R-ACKCH-1
R-CQICH-1
Multiple MAC instances share logical channels

12/6/2004

8

RLP Sequence numbers

RLP-A Frame Seq = 1
4096 octets
Frame 1 Segment
1
Frame
Seq 1
Seg
Seq #
Frame 1 Segment
2
Frame
Seq 1
Seg
Seq #
Frame 1 Segment
3
Frame
Seq 1
Seg
Seq #
Octet 1
Octet 45
Octet 4051
Octet 91
Octet 46
Octet 4096
360 bits Frame 1
Frame
Seq 1
360 bits Frame 2
Frame
Seq 2
360 bits Frame 3
Frame
Seq 3
o o
o o
With segmentation frames can be make the maximum size of 4096 octets.
Segmentation can then be used to split it into the 384 size.

With 384 bit packet and no segmentation sequence number,
frame sequence number used by 384 packet

12/6/2004

9

RLP Sequence numbers

Only
Frame Seq #: Maximum 12 bits -
> 4096 packets
Frame Seq # and
Segment Seq #: Maximum 12 bits ->
4096 octets per seq#
Number of outstanding
frames allowed <= 2048
360 bits * 2048 / 8=
92160 octets
384 bits
min
payload
4096 octets * 2048 =
8,388,608 octets
384 bits min
payload
92,160 octets
can be
outstanding
8,388,608 octets
can be outstanding
Number of outstanding
frames allowed <= 2048
12/6/2004

10

Layer 3 Signaling

Layer
Function
Desired Functionality
Layer 3 signaling specification
Minimal impacts to Layer 3 specification
Carriers Active Sets
An independent Active Set is maintained for each carrier.
Context information is maintained for each carrier including a handoff
sequence number.
Multicarrier operation at
channel assignment?
Option 1 (preferred)
: No multicarrier operation at channel
assignment. Additional carrier(s) are added with UHDM on a traffic
channel.
Option 2: Multiple carriers assigned at channel assignment. Multiple
ASSIGN_MODE= '101' records included in ECAM.
UHDM usage
Option 1 (preferred)
: A parameter is added to UHDM to indicate that
when a different CDMA_FREQ is included the MS should not perform
a hard handoff but rather should add the carrier to the current carrier
set. A UHDM is required for each carrier added.
Option 2: Add additional records to UHDM for multiple carriers.
Allows the assignment of multiple carriers with 1 UHDM.
Other Layer 3 messages
Layer 3 messages pertaining to a specific carrier but not including a
CDMA_FREQ parameter must be sent on the relevant carrier;
otherwise, messages may be sent on any carrier.
Layer 3
Signaling
12/6/2004

11

Carrier
Instance 3
...
Service Instanc
e
- srid
- f/r dtch
Call Instance
Carrier
Instance 2
...
Carrier Instance 1
- CDMA_FREQ1,
- active set management
- channel config
- HDM_SEQ1; handoff sequence
number for this carrier
....
Multiple Carrier context records maintained for a call

12/6/2004

12

f-csch:
ECAM
F-PDCH:
Service Connect Msg
(SCR+NNSCR)
R-PDCH:
Service Conn Compl Msg
F-PDCH/R-PDCH:
User Traffic
Traffic Channel Initialization
f-dsch:
UHDM
CDMA_FREQ=Carr2
ADD_CARRIER='1'
HDM_SEQ2 ...

To add carrier, BS
sends UHDM
including Carrier 2
and Additional
Carrier indicator
(ADD_CARRIER)
set to '1'.

Handoff
sequence number
(HDM_SEQ) used
is the one
associated with
carrier 2 so is set
to '0'.
Carrier 2
Carrier 2

Call setup brings
call up on 1 carrier
using existing
procedures.
r-dsch
:
EHOCM
LAST_HDM_SEQ2 ...

Handoff Completion
Message sent on
Carrier 2.

Handoff sequence
number (HDM_SEQ)
used is the one
associated with
carrier 2.
__
MS
__
__
B
S
__
Carrier 1
Carrier 1
r-csch
:
Origination Message/
Page Response Message
Call Setup with

1 carrier

Subsequent

addition of

another carrier

12/6/2004

13

__
MS
__
__B
S
__
Carrier 1
Carrier 1
Carrier 2
[ OR ]
Carrier 2
r-dsch
:
EPSMM
f-dsch:
UHDM
CDMA_FREQ=Carr2
ADD_CARRIER='1'
HDM_SEQ2 ...
f-dsch:
UHDM
CDMA_FREQ=Carr2
ADD_CARRIER='1'
HDM_SEQ2 ...
r-dsch
:
EHOCM
LAST_HDM_SEQ2 ...
r-dsch
:
EHOCM
LAST_HDM_SEQ2 ...

BS receives
EPSMM on Carrier
2, which applies
for Carrier 2.

To do handoff, BS
sends UHDM
including Carrier 2
and "Additional
Carrier Indicator" set
to '1'.

UHDM sent on either
Carrier 1 or Carrier 2.

Handoff sequence
number (HDM_SEQ)
used is the one
associated with
carrier 2.

Handoff Completion
Message sent on
Carrier 2.

Handoff sequence
number (HDM_SEQ)
used is the one
associated with
carrier 2.
Soft Handoff
Carrier 2

12/6/2004

14

F-FCH
RLP
R-PDCH-0
R-PDCH-1
F-PDCH-0
F-PDCH-1
R-FCH
F-SCH-0
F-SCH-1
r-dtch
Carrier 1
Carrier 2
f-dtch
Logical to Physical Mapping

UHDM adds a carrier and includes NNSCR containing the mapping from the
logical channels to the newly added PDCHs’ on the new carrier

12/6/2004

15


Mobile Station MAC primitives: R
-
PDCH

R-PDCH
CF-1
R-PDCH
CF-0
Mux-1
(r-pdch-1)
Mux-0
(r-pdch-0)
LAC
(r-dsch)
RLP_A
(r-dtch_rlpa)
Phy Layer-0
(FA-1)
Phy Layer-1
(FA-2)
PHY-RPDCH.Request
(ep, spid, boost, sys_time)
MAC Availability.Indication (channel_type,
max_size, system_time, residual_size)
MAC Data.Request (channel_type,
data, size)
RLP-MAC Availability.Indication (channel_type,
mux_options, max_size, system_time)
RLP-MAC Data.Request (channel_type,
data, size)
RPDCH-Availability.Indication
(mux_sdu_size, sys_time)
RPDCH-Data.Request
(mux_sdu, sys_time)
PHY-RPDCH.Request
(ep, spid, boost, sys_time)
MAC Availability.Indication (channel_type,
max_size, system_time, residual_size)
MAC Data.Request (channel_type,
data, size)
RLP-MAC Availability.Indication (channel_type,
mux_options, max_size, system_time)
RLP-MAC Data.Request (channel_type,
data, size)
RPDCH-Availability.Indication
(mux_sdu_size, sys_time)
RPDCH-Data.Request
(mux_sdu, sys_time)
PHY-RPDCCH.Request (ep_size,
sdu, msib, boost, sys_time)
PHY-RPDCCH.Request (ep_size,
sdu, msib, boost, sys_time)
Note: RLP primitives are not standardized

and are shown only for illustration

12/6/2004

16

F-PDCH CF-0
Mux-1
(f-pdch-1)
Mux-0
(f-pdch-0)
LAC
(f-dsch)
RLP_A
(f-dtch_rlpa)
Phy Layer-0
(FA-1)
Phy Layer-1
(FA-2)
FPDCH-Data.Indication (sdu,
frame_duration, num_bits,
frame_quality)
F-PDCH CF-1
PHY-DecodeFPDCCH.Request (pdcch_id,
pilot_pn, walsh_index, sys_time, num_slots)
PHY-RPDCCH.Indication (sdu, msib,
boost, sys_time)
PHY-DecodeFPDCH.Request (pilot_pn, acid, spid,
ep_size, wci_set, ep_new, sys_time, num_slots)
PHY-DecodeFPDCH.Response (acid,
ep, sys_time, num_slots)
FPDCH-Data.Indication (sdu,
frame_duration, num_bits,
frame_quality)
PHY-DecodeFPDCCH.Request (pdcch_id,
pilot_pn, walsh_index, sys_time, num_slots)
PHY-RPDCCH.Indication (sdu, msib,
boost, sys_time)
PHY-DecodeFPDCH.Request (pilot_pn, acid,
spid, ep_size, wci_set, ep_new, sys_time,
num_slots)
PHY-DecodeFPDCH.Response (acid,
ep, sys_time, num_slots)
RLP-MAC-Data.Indication(channel_id,
channel_type, data, size, system_time)
RLP-MAC-SDUReady.Request (channel_type,
size, scheduling_hint)
RLP-MAC-Data.Indication(channel_id,
channel_type, data, size, system_time)
RLP-MAC-SDUReady.Request (channel_type,
size, scheduling_hint)
MAC-Data.Indication(channel_id, channel_type,
data, size, system_time)
MAC-SDUReady.Request (channel_type, size,
scheduling_hint)
MAC-Data.Indication(channel_id, channel_type,
data, size, system_time)
MAC-SDUReady.Request (channel_type, size,
scheduling_hint)

Mobile Station MAC primitives : F
-
PDCH

Note: RLP primitives are not standardized

and are shown only for illustration