Vous êtes sur la page 1sur 9

WCDMA MAC Project

Problem Formulation

In WCDMA system, the physical channel data rates are fixed for some
spreading factors (from 4 to 256).
However, users may require data rates different from those fixed rates for
different kind of services.

Objective

Our objective is to achieve the Service Rate Mapping of user data from the MAC to
the physical layers.

Specific Topics

In this project, we will consider the following issues:

Channel mapping mapping of transport channel to physical channel.
Multiplexing several transport channels share one physical channel.
QoS control based on environment and service demand.
Scheduling radio resource sharing among users.

System Platform

Single user case


MAC MAC
Transport channel Transport channel
Radio channel


Multiple user case multiplex data of different users to share a single physical
channel



We will first build the system platform by using the RadioLab 3G software by Matlab.
We will also develop the MAC protocol by ourselves and verify the results with the
RadioLab 3G platform.

Demonstration

We will build the system platform on computers for demonstration. We will
demonstrate the whole data flow process from the transmitter to the receiver,
including how data are segmented, mapped to physical channel, scheduled,
transmitted and received.


Data flows through Layer-2 in WCDMA

In this section we study the packet data flow pass through the Layer-2 from higher
layers in the WCDMA system. This can be divided into two parts RLC data flow
and MAC data flow. We begin by study the data flow in each layer with examples,
and then combine the two flows into a complete one through L2.

RLC Layer

The RLC layer architecture is shown below.

Radio channel
MAC MAC
Transport channel Transport channel



RLC layer architecture

When data packets (RLC SDUs) received from RLC-SAPs (Tr-SAP, AM-SAP, or
UM-SAP) enter RLC, they will first be segmented and/or concatenated into
fixed-length PUs (payload units). These PUs are stored in the transmission buffer.
Each RLC PDU is made with a PU by adding the RLC header and the padding or
status in the tail. Before this RLC PDU being transmitted to the logical channel, the
ciphering process is applied.

An example is shown below. It shows a simplified block of the AM-RLC entity. When
the data enter the AM-RLC entity, it is first being segmented/concatenated into PUs
and stored in the transmission buffer. Then each PU is transformed into a RLC PDU
by adding header and padding/status and then send to the DTCH/DCCH logical
channel. The header contains a RLC PDU sequence number (SN, 12 bits for AM-RLC)
and a poll bit P for requesting STATUS. In this diagram we omit the ciphering process.
Also note that in this example, header is needed for AM-RLC. However, for
transparent mode, no protocol overhead is added to the higher layer data.

DTCH / DCCH
Transmitting
transparent
entity
Receiving
transparent
entity
Acknowledged
mode
entity
Transmitting
unacknowl.
entity
Receiving
unacknowl.
entity
Tr-SAP AM-SAP UM-SAP
BCCH / PCCH / CCCH
/ DCCH / DTCH
CCCH / CTCH /
DTC H / DCCH



A simplified data flow in RLC

MAC Layer

When a MAC SDU enters the MAC form the logical channel, itll be added headers
according to the protocol and then send to the transport channel. The MAC
architecture is shown below.

We illustrate the MAC layer data by an example. When a MAC SDU received from
logical channel DTCH/DCCH entering the MAC-d, the first thing is to choose the
type of transport channel. In this example, that data will be mapped to FACH. Then,
the multiplexing unit will add the C/T (4 bits) to the MAC SDU to indicate the logical
channel where the data originates. Then we set the priority of the data. The next step
is to pass the data to MAC-c/sh. In MAC-c/sh, the entity adds the UE-id, UE type and
target channel type field (TCTF) to the data to form a transport block or MAC PDU.
Then this PDU is sent to the transport channel FACH. This process is shown below.

AM-SAP
Segmentation /
Concatenation
Transmission buffer
PU PU PU PU
RLC-SDU
RLC PDU
RLC
SN
P
DTCH / DCCH



MAC layer architecture (UTRAN side)

To summarize the data flow passes through L2 with the aforementioned two examples,
we list them into the several steps:

1. Data (RLC SDU) enter the RLC layer from the higher layer (AM-SAP)
2. Segment or concatenate data into payload units (PU)
3. Store the PUs in the transmission buffer
4. Transform each PU into a RLC-PDU (add header, tail, ciphering)
5. Send RLC PDU to the logical channel (DTCH/DCCH)
6. Data (MAC SDU) enter MAC-d from logical channel
7. Choose the type of transport channel to be mapped to
8. Multiplexing data and add the C/T (4 bits) tag
9. Set the priority
10. Pass the data to MAC-c/sh
11. Add UE-id (2 bits) and UE type (C-RNTI 16 bits, U-RNTI 32 bits)
12. Add the TFCF (2 bits in the eg.) (transport block/MAC PDU)
MAC-c/sh
PCCH BCCH CCCH CTCH DCCH DTCH
MAC-d
Transport Channel Type Selection
Multiplexing
(CCH)
Multiplexing
(SharedCH)
Multiplexing
(DCH)
DL TFC
selection
Priority setting
Flow control Ciphering
Flow control
Add UE-id and UE-id type
Scheduling / priority handling
Priority setting
DL code
allocation
TCTF mux
DL TF selection
PCH FACH FACH DSCH DCH


13. Scheduling
14. Select TF
15. Send MAC-PDU to the transport channel


MAC data flow from DTCH/DCCH to FACH

In our project, if we assume to process data from RLC in MAC, we need to be more
specific in the system design to decide the following stuff:

Which logical channel to receive data from?
Which transport channel to pass the data to?
C/T field
UE-id and UE type
Target channel type field
TF selection

And for complete MAC functions, we also need to consider multiplexing, priority
setting, and scheduling problems.





MAC SDU
DTCH / DCCH
MAC SDU C/T
MAC SDU C/T
UE
ID
Type
MAC SDU C/T
UE
ID
Type
TCTF
Transport Block (MAC PDU)
FACH
MAC entity
Logical Channel
Transport Channel


RadioLab 3G

There are 6 UMTS/FDD blocksets in the RadioLab 3G software. They are: transport
channel blocks, physical channel blocks, mod/demod blocks, cvm utilities,
miscellaneous, and channel models.

Transport Channel Blocks

Transport channel data source you can generate packet stream, create and select
transport channel format, etc.

Transport channel transforms includes functions of CRC attachment/checking,
channel encoding/decoding, 1
st
and 2
nd
interleaving/deinterleaving, radio frame/PhCH
segmentation/desegmentation, and TrCH multiplexing/demultiplexing.

Rate matching includes the rate matching functions.

Reference channels includes 3GPP defined reference measurement channels of 5
different rates: 12.2, 64, 144, 384, and 768 kbps channels. Encoders and decoders for
uplink and downlink channels are defined.

Physical Channel Blocks

Physical channels primary/secondary SCH, primary CPICH, uplink DPDCH, uplink
DPCCH, downlink DPCH, and uplink pilot code generator.

Random access channels PRACH preamble/preamble decoder/data/control/trigger,
AI generator, AICH, and AICH decoder.

Spreading OVSF spreading/despreading/code generator.

TFCI TFCI encoder/decoder.

IQ mappings serial to parallel/parallel to serial conversion, real-imag to complex,
complex to real-imag.

Scrambling uplink/downlink scrambling/descrambling/code generator.


Other BPSK symbol mapping/demappling and radio slot counter.

Mod/Demod Blocks

Contains pulse shaping, over-sampling, modulate/demodulate, integrate & dump,
Rake receiver, Rake finger, correlator, and peak searcher.

CVM Utilities

Miscellaneous -- contains BER (bit error rate), constellation diagram, gain (a highly
configurable block for different sorts of gain), frame delay, frame resync, etc.

Channel Models AWGN, multipath taps, and multipath.

The RadioLab 3G covers the physical layer functions for UMTS/FDD Layer-1
simulation. However, for a complete simulation including Layer-2, we can add MAC
and RLC layers above the RadioLab 3G platform using Simulink in Matlab.

For a complete demo of our system, we might need to use Simulink in the simulation
for it is easier to show the results dynamically and to collaborate with the RadioLab
3G blocksets.

Meeting with Prof. Su

In the joint project meeting, I found some problems.

1. We will connect our MAC layer system to the physical layer DSP hardware.
However, the physical layer is for cdma2000 system, and the packet format being
transmitted is also cdma2000 format.
2. The system is considered as the uplink case in the receiver side, that is, the base
station. And I am not sure about which case (uplink or downlink) is our proposed
system going to be designed for.
3. Prof. Su said he needs to discuss with other professors involved in this project
about how to combine the different parts of the project of different systems
(WCDMA and cdma2000).




References
3GPP TS 25.301 Radio interface architecture protocol
3GPP TS 25.321 MAC protocol specification
3GPP TS 25.322 RLC protocol specification
3GPP TS 25.211 Physical channels and mapping of transport channels onto
physical channels
WCDMA for UMTS

Vous aimerez peut-être aussi