You are on page 1of 14

Wireless Communication

Inception



























UMTS PLANES
Wireless Communication

Inception

Table of figure


Figure 1: Different domains ............................................................................................................ 3
Figure 2:Functional communication b/w UMTS Domain .............................................................. 5
Figure 3: Different types of stratum ............................................................................................... 6
Figure 4: Acess stratum and Non Access stratum .......................................................................... 6
Figure 5: AS and nas circuit switching ............................................................................................. 7
Figure 6: cicruit switch user plane .................................................................................................. 8
Figure 7:Packet Switched Control Plane Protocol Stack ................................................................. 9
Figure 8: Packet Switched User Plane Protocol Stack .................................................................. 10
Figure 9: user and control plane signalling .................................................................................. 11
Figure 10: protocol state ............................................................................................................... 12
Figure 11: cell dch ......................................................................................................................... 13













Wireless Communication

Inception
UMTS FUNCTION ENTITES : DOMAINS



Figure 1: Different domains
Functions of the UMTS Domains

Infrastructure domain
Access network (AN) domain: functions specific to access technique
Core network (CN) domain: functions independent of access technique


Access network domain

physical entities managing the resources of the access network
provides the user with a mechanism to access the core network domain


Serving network (SN) domain

Wireless Communication

Inception
part of the CN domain to which the AN domain that provides the users access is currently
connected.
responsible for routing calls and transport user data information from source to destination.
provides CN functions that are local to the users access point (i.e. SN changes when the user
moves)

Home network (HN) domain

provides CN functions that are conducted at a permanent location regardless of the location
of the users access point (i.e. does not change due to user mobility)

contains user-specific data and is responsible for management of subscription information

handle home-specific services, not offered by the serving network domain



User Services Identity Module domain (USIM)
related to the home network domain by subscription
Wireless Communication

Inception


Figure 2:Functional communication b/w UMTS Domain (ref specs: 23.101)


Wireless Communication

Inception

Figure 3: Differen types of stratum

Figure 4: Acess stratum and Non Access stratum
Wireless Communication

Inception
UMTS Signaling Protocol Stack

The UMTS signaling protocol stack is divided into Access Stratum (AS) and Non-Access Stratum
(NAS). The Non-Access Stratum architecture evolved from the GSM upper layers and
includes:



Connection Management Handles circuit-switched calls and includes sub layers responsible
for call control (e.g., establish, release), supplementary services (e.g., call forwarding, 3-way
calling), and short message service (SMS).


Session Management Handles packet-switched calls (e.g., establish, release).

Mobility Management Handles location updating and authentication for circuit-switched
calls.

GPRS Mobility Management Handles location updating and authentication for packet-
switched calls.

Because the UMTS Non-Access Stratum layer is essentially the same as GSM, this course
touches only briefly on its functions and service

Circuit Switched (control plane)



Figure 5: as and nas circuit switching
Wireless Communication

Inception

Circuit Switched Control Plane Protocol Stack
The control plane protocol stack illustrates how signaling protocols are terminated. This
example shows a circuit-switched call operating on dedicated physical channels.

Non-Access Stratum (NAS)
Connection Management (CM) protocols are defined between UE and MSC to handle call
setup and release function
Mobility Management (MM) protocols are defined between UE and MSC to handle UE
mobility functions.

Access Stratum (AS)

The Radio Resource Control (RRC) protocol is defined between UE and RNC to handle
establishment, release, and configuration of radio resources.

The Radio Link Control (RLC) protocol is defined between UE and RNC to provide
segmentation, re-assembly, duplicate detection, and other traditional Layer 2 functions.

The Medium Access Control (MAC) protocol is defined between UE and RNC to multiplex user
plane and control plane data.

The Physical Layer protocol is defined between UE and Node B to transfer data over the radio
link. The interface between UE and RNC at the Physical Layer handles macro diversitycombining
and splitting functions.

Circuit Switch User Plane

Figure 6: cicruit switch user plane
Wireless Communication

Inception
Circuit Switched User Plane Protocol Stack
.
Non-Access Stratum (NAS)
An application can consist of several layers. For example, in the case of voice, the topmost
layer corresponds to the actual acoustic signals heard by users on both ends, whereas a
lower layer carries the vocoded bits. In this protocol architecture

Access Stratum (AS)
The RLC, MAC, and Physical Layer protocols for the user plane are the same as for the control
plane.
RRC does not participate in user plane protocols. It is responsible for setting up the radio
bearers and channels, but does not touch the data.


PACKET SWITCHED CONTROL PLANE


Figure 7:Packet Switched Control Plane Protocol Stack

Non-Access Stratum (NAS)
Session Management (SM) protocols are defined between UE and SGSN to handle packet
session establish and release procedures.

GPRS Mobility Management (GMM) protocols are defined between UE and SGSN to handle
UE mobility functions.

Access Stratum (AS)
The control plane access stratum is identical for packet and circuit switched operations.


Wireless Communication

Inception



PACKETED SWITCHING USER PLANE


Figure 8: Packet Switched User Plane Protocol Stack

Non-Access Stratum (NAS)

The application layer could be Web browsing, FTP, email, etc.

When the Session Management layer activates a Packet Data Protocol (PDP) context, it
identifies the type as Internet Protocol (IP) or Point to Point Protocol (PPP).

Access Stratum (AS)

The Packet Data Convergence Protocol (PDCP) provides protocol transparency for higher layer
protocols, such as IPv4, PPP, and IPv6, and performs protocol control information
compression.

The RLC, MAC, and Physical Layer protocols for the user plane are the same as for the control
plane.


RRC does not participate in user plane protocols.
Wireless Communication

Inception

Figure 9: user and control plane signalling


UE Call States


The UE call processing state is represented by a mode and (optionally) a state within that mode.
The operating modes are:


Idle Mode The UE is receiving messages from the network on a Paging Channel, but does not
transmit anything back to the network. In this mode, the UE may be camped on a
UTRAN cell or a GSM cell, or it may be operating in GPRS Packet Idle Mode. The UE may be
attached (registered for service) to the CS and/or PS core networks.


UTRAN Connected Mode The UE has established an RRC connection for exchange of signaling
messages with UTRAN. The four states of UTRAN connected mode are described in subsequent
slides.




Wireless Communication

Inception





GSM Connected Mode The UE has dedicated GSM channels allocated to it for the purpose of
transferring user data and/or signaling with a GSM network.


GPRS Packet Transfer Mode The UE has dedicated GPRS channels allocated to it for the
purpose of transferring user data and/or signaling with a GPRS network.


Figure 10: protocol state

CELL_DCH
The CELL_DCH state is characterized by:
A dedicated physical channel is allocated to the UE in uplink and downlink.
Wireless Communication

Inception

The UE is known on cell level according to its current active set. In this state, the UE shall


Figure 11: cell dch
Use the connected mode measurement control information received in other states until new
measurement control Information has been assigned to the UE
perform measurements and transmit measurement reports according to the measurement
control information
Depending on UE capabilities, monitor the FACH to receive any broadcast messages.
monitor a DSCH in downlink for user data and signaling messages when instructed by UTRAN.
CELL_FACH
The CELL_FACH state is characterized by:
Neither an uplink nor a downlink dedicated physical channel is allocated to the UE.
The UE the continuously monitors a FACH in the downlink
The UE is assigned a default common or shared transport channel in the uplink (e.g. RACH)
that it can use anytime
Wireless Communication

Inception
according to the access procedure for that transport channel
The UE is known on cell level according to the cell where the UE last made a cell update.
In this state, the UE shall
Use C-RNTI assigned in the current cell as the UE identity on common transport channels
unless when a new cell is
Selected.
monitor a FACH to receive signaling messages or user data addressed to the UE or any
broadcast messages.
acquire system information on the BCH and use the common physical channel and transport
channel configuration.
CELL_PCH
The CELL_PCH state is characterized by:
Neither an uplink nor a downlink dedicated physical channel is allocated to the UE.
The UE uses DRX for monitoring a PCH via an allocated PICH.
No uplink activity is possible [note: if the UE wants to make an uplink access it autonomously
shall enter the CELL_FACH state].
The UE is known on cell level according to the cell where the UE last made a cell update in
CELL_FACH state.
URA_PCH
The URA_PCH state is characterized by:
Neither an uplink nor a downlink dedicated physical channel is allocated to the UE
The UE uses DRX for monitoring a PCH via an allocated PICH.
No uplink activity is possible [note: if the UE wants to make an uplink access it autonomously
enters the CELL_FACH state].
The UE is known on URA level according to the URA assigned to the UE during the last URA
update in CELL_FACH state.

You might also like