BASIC TECHNOLOGY FOR MODULATION

UMTS &LTE COMBINE MODULATION

CREATED BY KUMARESAN MURUGAN
SUPPORTING PORTAL FROM FUGENX SITE
 The UMTS Architecture
• A UMTS network can be divided into the
following physical domains:
1. User Domain
2. Radio Access Network
3. Core Network
• The UMTS Core network in Release ’99 is based on the
GSM/GPRS network. Most of the individual elements are
re-used, although they require extensions (e.g. MSC, VLR
etc.)

• The UTRAN elements are completely new. UMTS core

networks must be able to interoperate both this new
UTRAN and the existing GSM BSS access network.

• In order to support more data intensive services, operators

will need to upgrade capacity throughout their networks in
order to cope with the expected increase in traffic, and use
transport protocols which are more efficiently suited to
data and packet transport.
 Upgrades to existing GSM/GPRS elements
• ATM transport
• New speech codec
• Flexibility in connection set-up
• Enhanced charging & billing support
• Interworking with other networks
• Enhanced IP mobility support
 The Two Modes of W-CDMA Access
FDD (Frequency Division Duplex)
This is the name for the UMTS mode which is designed to give
wide area mobile coverage in UMTS. It can support 384kb/s
in a mobile environment and uses a 5Mhz frequency band
for uplink and a separate 5Mhz for downlink.

TDD (Time Division Duplex)

• TDD uses W-CDMA as the modulation scheme, as in FDD,
but shares a single 5Mhz channel for both uplink and
downlink. To do this, the system allocates time slots for
both the uplink and downlink transmissions.
 Elements & Domains in a UMTS network
• A UMTS network can be divided into the
following physical domains:
1. User Domain
2. Radio Access Network
3. Core Network
 THE USER DOMAIN (USIM + ME DOMAINS)
• The user domain describes the equipment needed by the user to
access UMTS services.
• Within this domain are further subdivisions into the Mobile
Equipment (ME) domain and USIM domain. The combined ME and
USIM is sometimes referred to as the Mobile Station (MS) or User
Equipment (UE)
• The USIM domain contains the data and procedures allowing the
ME to securely identify itself, and is linked to the ME by the defined
Cu Interface.
• The ME domain performs radio transmission and contains
applications. It may itself be further subdivided, into the Mobile
Termination MT (radio functions only) and Terminal Equipment TE
(contains end-to-end application, and may be a separate device
from the radio equipment, for example a laptop).
 THE ACCESS NETWORK
• The Access Domain is in direct contact with the User equipment
and the core network. This split is intended to decouple access
functionality from non-access functionality.

• In UMTS, the Access Domain refers to the radio access mechanism,

and is also known as the UTRAN (UMTS Terrestrial Access Network).

• The UTRAN is considered a separate entity to the core network,

with a defined interface connecting them.

• All radio procedures and aspects are fully handled within the
UTRAN, including mobility of the radio connection (soft handover,
relocation of serving entities etc.).
Functions of the UTRAN
UTRAN Architecture – General
 The Node B
• The term Node B refers to the base station equipment
which communicates with the subscriber’s handset via the
radio link.

• It provides radio resources for a UMTS network, and uses

UMTS channel allocation to communicate with the
handset.

• It provides all the RF processing, enabling transmission and

reception information to and from the mobile terminal.

• This information is encoded using the W-CDMA scheme.

Node B tasks
 RNC Terminology
The RNC operates in three main modes
• Controlling RNC
• Serving RNC
• Drift RNC
depending on whether an RRC connection is
established, and how it is configured.
Controlling RNC
• When mobiles are in idle mode, no RRC
connection exists.

• Hence this mode simply describes the

functionality of the RNC which controls the Node
B on which the mobile is camped (i.e. the
selected Node B).

• Any RRC messages relevant to the UE are

terminated at the UE and Node B.
Serving and Drift RNC
• Once a mobile enters the RRC Connected mode, an RRC connection
exists, and RRC messages relevant only to the UE are terminated at
the UE and Serving RNC (SRNC).

• In Soft Handover, the mobile is effectively served by two or more

Node B. In the case where the Node B are connected to different
RNC, the Serving RNC remains as the only Serving RNC, whilst the
new RNC (now called the Drift RNC, or DRNC).

• DRNC Simply provides the radio resources necessary for the added
radio link, and acts to carry the Radio Resource messages and user
data between the SRNC and UE transparently over the Iur and Iub
interfaces on the relevant channels.
 Controlling RNC Functions
• The CRNC controls one or more Node B. In practice,
this is likely to be tens of NodeB.

• It is responsible for loading and congestion of cells,

as well as allocating codes.

• System information broadcasts for mobiles in idle

mode (or packet switched cell or URA paging modes)
are originated from the controlling RNC
 Serving RNC (SRNC)
• Terminates Radio Bearers and Signalling Radio
bearers for the mobile
(ie RRC is terminated here in RRC connected mode).
• Performs Layer 2 processing of data to/from radio
interface.
• Controls handover decisions.
• Outer loop power control.
• SRNC may also be CRNC for Node B(s) used by the
mobile.
• Each connected UE has only one SRNC.
Drift RNC (DRNC)
• Any RNC, other than SRNC which controls cells
used by the mobile.

• No layer 2 processing, unless mobile is using

common or shared transport channel.

• A mobile may have one or more DRNCs.

UMTS ARCHITECTURE
UMTS ARCHITECTURE
Control and user planes
PROTOCOL STACK OF UE
• The Radio Resource Control layer that establishes and controls the
communication link between the base station and the mobile.
• At layer 2 are Broadcast and Multicast Control used for
transmission of cell broadcast messages to all mobiles in the cell.
• Packet Data Convergence Protocol is similar to SNDCP in GPRS. It
transfers user data messages, forwarding each packet in sequence
and provides compression of the (large) packet headers.
• Radio Link Control segments control and user data in to suitably
sized packets for transfer over the lower layers. Backward error
protection may be provided by repetition of packets that are not
acknowledged by the receiver.
• (Medium Access Control transfers data to one of several transport
channels that may have been established.

• The physical layer (layer 1) is responsible for transmitting and

receiving over the Uu (air) interface.
RRC Connection Establishment
• Radio Resource Connection is established to
allow any subsequent signalling exchange
between the mobile and the network.
• It is equivalent to a Channel Assignment phase
in GSM or GPRS.
• Once the channels are assigned, the mobile
can instigate Location Update,GPRS Attach,
call setup, etc.
GMM/SM Uu
Iub
CM RRC PDCP BMC
MM NBAP
RRC PDCP BMC NBAP RLC

RLC MAC MAC

MAC MAC ATM ATM

PHYSICAL PHYSICAL PHYSICAL PHYSICAL

UE NODE-B RNC
 Iu-cs
CM
MM
RANAP RANAP
AAL AAL
ATM ATM
SCCP SCCP
MTP3 MTP3
MTP2 MTP2
MTP1 MTP1
RNC MSC
 Iu-ps
GMM
SM
RANAP RANAP
AAL AAL
ATM ATM
SCCP SCCP
MTP3 MTP3
MTP2 MTP2
MTP1 MTP1
RNC SGSN
 Iur

RNSAP RNSAP
AAL AAL
ATM ATM
SCCP SCCP
MTP3 MTP3
MTP2 MTP2
MTP1 MTP1
RNC RNC
UTRAN PROTOCOLS
Physical Layer
• Multiplexing several Transport Channels onto a Physical Channel

• Coding for error protection

• Channelization to share frequency band

• Scrambling to separate transmissions

• Access control and timing

• Power control
WCDMA Code Types
 Scrambling Codes, Channelisation Codes

Uplink Downlink
Scrambling codes User separation Cell separation

Channelisation Data and Control Users within a

codes channels from the cell
same terminal
Spreading code = Scrambling code x Channelisation code
• Logical Channels define the type of data to be transferred,
for example, traffic, Paging messages, dedicated control
information.

• Transport Channels define how the information will be

carried to the physical layer and define the characteristics
of the data. For example, channel dedicated to a single
mobile, contention based common channel.

• Physical Channels are characterised by their timing and

access protocols(eg random access channels), data rates
(eg traffic channels), and many other parameters.
Channel Availability
• Common Channels
– Available to all mobiles without assignment
• Shared Channels
– A set of mobiles are assigned a channel to
share
– Used only for High Speed channels now
• Dedicated Channels
– The channel is assigned to a single mobile only
• The MAC layer is divided into three logical entities: MAC-b, MAC-
d and MAC-csh.

• MAC-d is responsible for handling dedicated channels (DCH)

allocated to a UE in connected mode.

• Each UE has a MAC-d and each serving RNC has a MAC-d for
each UE.

• MAC-csh is responsible for handling common (and shared

channels).

• Each UE has a MAC-csh and each serving RNC has a MAC-csh for
each cell.
 MAC-b
• The MAC-b entity is responsible for transmission of
system information messages.

• Each UE has a MAC-b and each Node B has a MAC-b.

• The messages are sent from the RRC layer via the
MAC control SAP and the MAC layer is responsible
for scheduling and transmitting them over the BCH
transport channel.
RLC layer
RLC layer
• RLC : Radio link control
– Three modes : Acknowledged, Unacknowledged,
Transparent
– Segmentation and reassembly of higher level
messages
– Backward Error Protection (Acknowledged)
– Ciphering of acknowledged and unacknowledged
mode RLC data
– Padding to fill fixed length PDU