radio access network architecture

8/20/2019 RADIO ACCESS NETWORK ARCHITECTURE

1/170

RADIO ACCESS NETWORK

ARCHITECTURE


2/170

5.1 System Architecture

5.2 UTRAN Architecture

5.3 General Protocol Model for UTRAN Terrestrial

Interfaces5.4 Iu, The UTRAN–CN Interface

5.5 UTRAN Internal Interfaces

5.6 UTRAN Enhancements and Evolution

5.7 UTRAN CN Architecture and Evolution


3/170

5.1 SYSTEM ARCHITECTURE

Functional network elementsUser Equipment (UE)

interfaces with user and radio interfaceRadio Access Network (RAN, UMTS Terrestrial RAN

= UTRAN)handles all radio-related functionality

Core Network

switches and routes calls and data connections

to external networks


4/170


5/170

PLMN (Public Land Mobile Network)operated by a single operator

distinguished from each other with unique identities

operational either on their own or together with other

sub-networks

connected to other PLMNs as well as to other types of

network, such as ISDN, PSTN, the Internet, etc.


6/170


7/170

UE consists of two partsMobile Equipment (ME)

the radio terminal used for radio communication

over Uu interfaceUMTS Subscriber Identity Module (USIM)

a smartcard that holds the subscriber identityperforms authentication algorithms

stores authentication and encryption keyssome subscription information that is needed at theterminal


8/170

UTRAN consists of two elementsNode B

converts data flow between Iub and Uu interfacesparticipates in radio resource management

Radio Network Controller (RNC)

owns and controls radio resources in its domainthe service access point (SAP) for all services that

UTRAN provides the CNe.g., management of connections to UE


9/170

Main elements of CN

a) HLR (Home Location Register)

b) MSC/VLR (Mobile Services Switching Centre/VisitorLocation Register)

c) GMSC (Gateway MSC)

d) SGSN (Serving GPRS (General Packet Radio Service)

Support Node)

e) GGSN (Gateway GPRS Support Node)


10/170

(a) HLR (Home Location Register)a database located in user’s home system that stores

the master copy of user’s service profile

service profile consists of, e.g.,

information on allowed services, forbidden

roaming areas

supplementary service information such as

status of call forwarding and the call

forwarding number


11/170

it is created when a new user subscribes to the

system, and remains stored as long as the

subscription is active

for the purpose of routing incoming transactions to

UE (e.g. calls or short messages)HLR also stores the UE location on the level of

MSC/VLR and/or SGSN


12/170

(b) MSC/VLR (Mobile Services SwitchingCentre/Visitor Location Register)◦ the switch (MSC) and database (VLR) that serve theUE in its current location for Circuit Switched (CS)

services◦ the part of the network that is accessed via MSC/VLRis often referred to as CS domain

◦ MSC

used to switch CS transactions

◦ VLR holds a copy of the visiting user’s service

profile, as well as more precise information on

the UE’s location within the serving system


13/170

(c) GMSC (Gateway MSC)the switch at the point where UMTS PLMN is

connected to external CS networks

all incoming and outgoing CS connections go through

GMSC


14/170

(d) SGSN (Serving GPRS (General Packet Radio

Service) Support Node)functionality is similar to that of MSC/VLR but is

typically used for Packet Switched (PS) services

the part of the network that is accessed via SGSN isoften referred to as PS domain

(e) GGSN (Gateway GPRS Support Node)functionality is close to that of GMSC but is in

relation to PS services


15/170

External networks can be divided into two groupsCS networks

provide circuit-switched connections, like the existing telephony

serviceISDN and PSTN are examples of CS networks

PS networksprovide connections for packet data services

Internet is one example of a PS network


16/170

Main open interfacesCu interface

the electrical interface between USIM smartcard

and MEUu interface

the WCDMA radio interface

the interface through which UE accesses the fixed

part of the systemthe most important open interface in UMTS


17/170

Iu interface

connects UTRAN to CN

Iur interface

allows soft handover between RNCsIub interface

connects a Node B and an RNC


18/170

5.2 UTRAN ARCHITECTURE

5.2.1 Radio Network Controller

5.2.2 Node B (Base Station)


19/170


20/170

UTRANconsists of one or more Radio Network Sub-systems (RNS)

RNSa subnetwork within UTRAN

consists of one Radio Network Controller (RNC) and one or

more Node Bs


21/170

RNCsmay be connected to each other via Iur interface

RNCs and Node Bs are connected with Iub interface Main characteristics of UTRAN

support of UTRA and all related functionalitysupport soft handover and WCDMA-specific Radio ResourceManagement algorithms

use of ATM transport as the main transport mechanism inUTRAN

use of IP-based transport as the alternative transportmechanism in UTRAN from Release 5 onwards


22/170

5.2.1 RADIO NETWORK

CONTROLLER

RNC (Radio Network Controller)the network element responsible for radio resources control

of UTRAN

it interfaces CN (normally to one MSC and one SGSN)

terminates RRC (Radio Resource Control) protocol that

defines the messages and procedures between mobile and

UTRANit logically corresponds to the GSM BSC


23/170

註： RADIORESOURCECONTROL

Radio Resource Control (RRC) messagesthe major part of the control signaling between UE and

UTRAN

carry all parameters required to set up, modify and release

Layer 2 and Layer 1 protocol entities

The mobility of user equipment in the connected mode

is controlled by RRC signalingmeasurements, handovers, cell updates, etc.


24/170

3GPP BEARERS FOR SUPPORTING

PACKET-SWITCHED SERVICES

UTRAN CN


25/170

TRAFFIC BEARERS STRUCTURE SUPPORTING

PACKET-SWITCHED SERVICES

3GPP Bearera dedicated path between mobile and its serving GGSN

for a mobile to send or receive packets over a 3GPP PS CN

a 3GPP Bearer in a UMTS network would be a UMTS

Bearer


26/170

Constructed by concatenating

Radio Access Bearer (RAB)

connects a mobile over a RAN to the edge of

CN (i.e., a SGSN)

CN Bearer

carries user traffic between the edge of CN

and a GGSN

SIGNALINGANDTRAFFIC


27/170

SIGNALING AND TRAFFIC

CONNECTIONS BETWEEN MOBILE

AND SGSN


28/170

The signaling connection between mobile and SGSN isconstructed by concatenating

Signaling Radio Bearerbetween mobile and RAN (e.g., the RNC in UTRAN)

Iu Signaling Bearerbetween RAN and SGSN

Signaling and traffic connections between mobile and SGSNRadio Resource Control (RRC) connectionRadio Access Network Application Part (RANAP)connection


29/170

Radio Resource Control (RRC) connectionincludes Signaling Radio Bearers and Traffic Radio

Bearers for the same mobile

used to establish, maintain, and release Radio

Bearersa mobile will use a common RRC connection to carry

signaling and user traffic for both PS and CS services


30/170

Radio Access Network Application Part (RANAP)

connectionincludes I

u Signaling Bearers and I

u Traffic Bearers

for the same mobile

used to establish, maintain, modify, change, andrelease all these I

u Bearers


31/170

5.2.1.1 LOGICAL ROLE OF THE RNC

The RNC controlling one Node B is indicated as

the Controlling RNC (CRNC) of Node B

Controlling RNCresponsible for load and congestion control of its own

cells

executes admission control for new radio links


32/170

In case one mobile–UTRAN connection uses

resources from more than one RNS (due to

handover), the RNCs involved have two separate

logical roles

Serving RNC (SRNC)

Drift RNC (DRNC)


33/170


34/170

Serving RNCSRNC for one mobile is the RNC that terminates boththe Iu link for the transport of user data and thecorresponding RANAP (RAN Application Part)signaling to/from the core network

SRNC also terminates the Radio Resource ControlSignaling, that is the signaling protocol between theUE and UTRAN

it performs L2 processing of the data to/from theradio interface


35/170

basic Radio Resource Management operations are

executed in SRNC

map Radio Access Bearer (RAB) parameters into

air interface transport channel parameters

handover decisionouter loop power control

one UE connected to UTRAN has one and only one

SRNC


36/170

Drift RNCDRNC is any RNC, other than the SRNC, that

controls cells used by the mobile

DRNC does not perform L2 processing of the user

plane data, but routes the data transparentlybetween Iub and Iur interfaces

one UE may have zero, one or more DRNCs


37/170

5.2.2 NODE B (BASE STATION)

Main function of Node B◦ perform the air interface L1 processing, e.g.,

channel coding and interleaving rate adaptation

spreading also performs some basic Radio ResourceManagement operations, e.g.inner loop power control

It logically corresponds to the GSM Base Station


38/170

註：INTERLEAVING

The transmission of pulses from two or more

digital sources in time-division sequence over a

single path

53GENERALPROTOCOLMODEL


39/170

5.3 GENERAL PROTOCOL MODEL

FOR UTRAN TERRESTRIAL

INTERFACES

5.3.1 General

5.3.2 Horizontal Layers

5.3.3 Vertical Planes


40/170

5.3.1 GENERAL

The general protocol model for UTRAN

terrestrial interfacesthe layers and planes are logically independent of

each other

parts of the protocol structure may be changed in thefuture while other parts remain intact


41/170


42/170

5.3.2 HORIZONTAL LAYERS

The protocol structure consists of two main layersRadio network layer

Transport network layer


43/170

5.3.3 VERTICAL PLANES

5.3.3.1 Control Plane

5.3.3.2 User Plane

5.3.3.3 Transport Network Control Plane

5.3.3.4 Transport Network User Plane


44/170

5.3.3.1 CONTROL PLANE

Control Planeused for all UMTS-specific control signalingincludes two parts

application protocol

RANAP (RAN application part) in IuRNSAP (RNS application part) in IurNBAP (Node B application part) in Iub

signaling bearertransport the application protocol messages


45/170

Application protocol is used forsetting up bearers to UE, i.e.

radio access bearer in Iu

radio link in Iur and Iub


46/170

5.3.3.2 USER PLANE

User Plane

transport all information sent and received by the

user, such as

coded voice in a voice call

packets in an Internet connection

includes two parts

data stream(s)

data bearer(s) for data stream(s)


47/170

5.3.3.3 TRANSPORT NETWORK

CONTROL PLANE

Used for all control signaling within transport layer

Does not include any radio network layer information

Includes ALCAP (Access Link Control Application

Part) protocol used to set up the transport bearers(data bearer) for user plane


48/170

Includes signaling bearer needed for ALCAP

Transport network control planeacts between control plane and user plane

makes it possible for application protocol in radio

network control plane to be completely independent of

the technology selected for data bearer in user plane


49/170

5.3.3.4 TRANSPORT NETWORK USER

PLANE

Transport Network User Planedata bearer(s) in user plane

signaling bearer(s) for application protocol


50/170

5.4 IU, THE UTRAN–CN INTERFACE

5.4.1 Protocol Structure for Iu CS

5.4.2 Protocol Structure for Iu PS

5.4.3 RANAP Protocol

5.4.4 Iu User Plane Protocol5.4.5 Protocol Structure of Iu BC, and the SABP

Protocol


51/170

Iu interfacean open interface that divides the system into radio-

specific UTRAN and CN

handles switching, routing and service control


52/170

Iu can have two main different instances and one

additional instanceIu CS

connect UTRAN to Circuit Switched (CS) CN

Iu PS

connect UTRAN to Packet Switched (PS) CN

Iu BC (Broadcast)

support Cell Broadcast Servicesconnect UTRAN to the Broadcast domain of CN


53/170

5.4.1 PROTOCOL STRUCTURE FOR IU

CS

5.4.1.1 Iu CS Control Plane Protocol Stack

5.4.1.2 Iu CS Transport Network Control Plane

Protocol Stack

5.4.1.3 Iu CS User Plane Protocol Stack


54/170

The following figuredepicts the Iu CS overall protocol structure

the three planes in the Iu interface share a common

ATM (Asynchronous Transfer Mode) transport

physical layer is the interface to physical mediumoptical fiber

radio link

copper cable


55/170


56/170

5.4.1.1 Iu CS CONTROL PLANE

PROTOCOL STACK

Control Plane protocol stack consists of RANAP,

on top of Broadband (BB) SS7 (Signaling System

#7) protocols

The applicable layers are

Signaling Connection Control Part (SCCP)

Message Transfer Part (MTP3-b)

SAAL-NNI (Signaling ATM Adaptation Layer

for Network to Network Interfaces)


57/170

註： SS7

MTP (Message Transfer Part，訊息轉送部 ) SS7的第一層為信號數據鏈路層 (Signaling Data Link

Level)又稱為實體層 (Phsi!al Level)定義信號鏈路之實體、電氣與功，!"#實體

鏈路$送 SS7信號 SS7的第%層為信號鏈路層 (Signaling Link Level)&' SS7信號訊息(實體層)$送的*+,

SS7的第-層為信號.路層 (Signaling Net"#rkLevel)

/0信號訊息120信號.路 MTP$%&

"#訊息3送、45，6訊789的訊號鏈:20、;


58/170

SCCP：>? ISUP@ABA之C=# ISDN%UP (ISUP)DEABA的信號FG (Signaling

C#nne!ti#n)

#.2、HIJK與LC=M9 (N SP功O )DE信

號FG#PQRS (User)(TUVJK )與LC=M (SPW )9DE信號FG，*XFY送UVZ[，\]R^_送`

a

#PQbcRS部 (User Part)DE信號FGdR


59/170

TCAPCfg (Transa!ti#n Ca'a&ilitiesh TC)i稱CfgjR部 (Transa!ti#n Ca'a&ilities A''li!ati#nParth TCAP)

( SS7.路JklmjR層 (A''li!ati#n Laer)J的一njRoVpq (A''li!ati#n Servi!e EleenthASE)


60/170

r的"# SS7.路J之信號sWB信號sW9t電路FGuv訊息的Y送

為wx之9的LyjR"#一z{oV|T

C=}與C=}9t電路FGuv訊息的C=C=}B.路oVJKZ[~•號€‚ (|T

*oV號€ )ƒ*„ TCAP…"#的oVQ†‡


61/170


62/170

SAAL-NNI is further divided intoService Specific Coordination Function

(SSCF)

Service Specific Connection Oriented

Protocol (SSCOP)

ATM Adaptation Layer 5 (AAL) layers

SSCF and SSCOP layers

designed for signaling transport in ATM

networks

take care of signaling connectionmanagement

AAL5 is used for segmenting the data to

ATM cells


63/170

註：

SSC+ (Servi!e S'e!i,! C##r-inati#n +.n!ti#n)為ˆ定oV>‰功Š‹ UNI (User%t#%Net"#rk Interfa!e)與 NNI

(Net"#rk%t#%Net"#rk Interfa!e)ŒŽ20 (!#nne!ti#n anageent)與鏈:

‘ (link stat.s)’20 SSCOP (Servi!e S'e!i,! C#nne!ti#n Oriente-

Pr#t#!#l)

為ˆ定oVŽ:“”6訊>定，"#*+的訊號Yo

V

Š‹–—˜™、š送}™、Ž˜™與›œž’

Ÿ SSCOPY送Z[，T¡¢Z[£¤›œ，*Ÿš送}™Q¥¦›œh§"#)層6訊>定*+的Y

oV


64/170

註： ATM IN /RIE+


65/170


66/170

註： AAL0 AND AAL1

Above the ATM layer we usually find an ATMadaptation layer (AAL)

AALprocess the data from higher layers for ATMtransmission

segment the data into 48-byte chunks and reassemblethe original data frames on the receiving side


67/170

Five different AALs (0, 1, 2, 3/4, and 5) AAL0

no adaptation is neededthe other adaptation layers have different propertiesbased on three parametersreal-time requirementsconstant or variable bit rateconnection-oriented or connectionless datatransfer


68/170

I. interfa!e .ses t"# AALs AAL0

¨©ˆª為«©DEŽ (!#nne!ti#n%#riente-servi!es)、¬Y (real%tie -ata streas)1

t®定的Y¯° (varia&le &it rate， 2/R)，±²RQY送³´µ的¶·Z[

¸n³´µ的¶·Z[Y¯°¹]®定，º»¼

¸n½¾的¿À,]Á\N…ÂÃ，ÄÅoV«©¬

{Y，±Rm AAL0的YoV

AAL1¨©的ˆª為Æ«DEŽ、t¬Y!1t®定

的Y¯°


69/170


70/170


71/170

5.4.1.2 IU CS TRANSPORT NETWORK

CONTROL PLANE PROTOCOL STACK

Transport Network Control Plane protocol

stack consists of

Signaling Protocol on top of BB SS7

protocols for setting up AAL2 connections (Q.2630.1 [Q.aal2

CS1])

adaptation layer (Q.2150.1 [AAL2

Signaling Transport Converter for

MTP3b])

BB SS7 are those described above

without SCCP layer

5413IUCSUSERPLANE


72/170

5.4.1.3 IU CS USER PLANE

PROTOCOL STACK

A dedicated AAL2 connection is reserved for each

individual CS service

Iu User Plane Protocol residing directly on top of AAL2

542PROTOCOLSTRUCTUREFORIU


73/170

5.4.2 PROTOCOL STRUCTURE FOR IU

PS

5.4.2.1 Iu PS Control Plane Protocol Stack

5.4.2.2 Iu PS Transport Network Control Plane Protocol

Stack

5.4.2.3 Iu PS User Plane Protocol Stack


74/170

The following figuredepicts Iu PS protocol

structure

a common ATM transport is

applied for both User Planeand Control Plane

the physical layer is as

specified for Iu CS


75/170

5421IUPSCONTROLPLANE


76/170

5.4.2.1 IU PS CONTROL PLANE

PROTOCOL STACK

Control Plane protocol stackconsists of

RANAP

signaling bearers

BB SS7-based signaling beareran alternative IP-based

signaling bearer

SCCP layer is used for both

bearer


77/170

IP-based signaling bearer consistsof

M3UA (SS7 MTP3 – User

Adaptation Layer)

SCTP (Stream Control

Transmission Protocol)

designed for signaling

transport in the Internet

ensure reliable, in-sequence

transport of messages withcongestion control

IP (Internet Protocol)

AAL5 (common to both

alternatives)


78/170

註：

SCTP (R+C 034)"#*+的YoV，¨©Ç(m

I.PSÈ¾_•mÉÊ的 IP.路ËÌJ，¹*±Rm IPv5與 IPv4

"#–—˜™、š送}™，!#)層M$UA一nÍ定*+的YÈ¾

M$UAÎm SCTP，"#)層 SCCP訊號Y送}™


79/170

SCCPÏÐ!MTP$•為wÑ層的6訊>定

為ÒÓŸ IPi ATM’6訊>定，(bÑ層"#一nÅÔMTP$的6

訊>定，!ÕÒÓ_•(Ö×6訊>定)

RANAPÐØ¹Æ/0›œgwÙÚ…N送Û的訊息ÜºÝ¦&F$，¬bÑ層6訊>定 (Trans'#rtNet"#rk Laer)«N/0›œg

T SSCOP與 SCTPÞN›œž與Z[š送}™

5422IUPSTRANSPORTNETWORK


80/170

5.4.2.2 IU PS TRANSPORT NETWORK

CONTROL PLANE PROTOCOL STACK

Transport Network Control Plane is not appliedto Iu PS

Setting up of GTP tunnelrequires an identifier for the tunnel and IP addresses

for both directionsthese are already included in RANAP RAB

Assignment messages

5423IUPSUSERPLANE


81/170

5.4.2.3 IU PS USER PLANE

PROTOCOL STACK

Iu PS User Planemultiple packet data flows are

multiplexed on one or several AAL5

PVCs (Permanent Virtual Circuit)

GTP-U (User Plane part of GPRS

Tunneling Protocol) is the

multiplexing layer that provides

identities for individual packet data

flow

each flow uses UDP connectionlesstransport and IP addressing


82/170

5.4.3 RANAP PROTOCOL

RANAPdefines interactions between RNS and CN

the signaling protocol in Iu that contains all the

control information specified for Radio Network Layer

implemented by various RANAP ElementaryProcedures (EP)

each RANAP function may require execution of one or

more EPs


83/170

three classes of EPclass 1 EP

request and response (failure or success)

class 2 EP

request without response

class 3 EP

request and possibility for one or more

responses


84/170

RANAP functionsrelocation

RAB (Radio Access Bearer) management

Iu release

report unsuccessfully transmitted datacommon ID management

paging


85/170

management of tracingUE–CN signaling transfer

security mode control

management of overload

resetlocation reporting


86/170

RANAP FUNCTION--

Relocation：handles both SRNS relocation and

hard handover (including inter-system case

to/from GSM)

SRNS relocationthe serving RNS functionality is relocated

from one RNS to another without changing the

radio resources and without interrupting the

user data flow

prerequisite：all Radio Links are already in

the same DRNC that is the target for the

relocation


87/170

Inter-RNS hard handoverrelocate the serving RNS functionality from

one RNS to another and to change the radio

resources correspondingly by a hard handover

in Uu interfaceprerequisite：UE is at the border of the

source and target cells


88/170

RANAP FUNCTION--

RAB (Radio Access Bearer) management：combinesall RAB handling

RAB set-up

modification of the characteristics of an existing

RABclearing an existing RAB

Iu release

releases all resources (Signaling link and U-Plane)

from a given instance of Iu related to the specifiedUE


89/170

RANAP FUNCTION--

Reporting unsuccessfully transmitted dataallows CN to update its charging records with

information from UTRAN if part of the data sent was

not successfully sent to UE

Common ID managementthe permanent identification of the UE is sent fromCN to UTRAN to allow paging coordination frompossibly two different CN domains


90/170

RANAP FUNCTION--

Pagingused by CN to page an idle UE for a UE terminating

service request, such as a voice call

a paging message is sent from CN to UTRAN with

the UE common identification (permanent Id) andthe paging area

UTRAN will either use an existing signaling

connection, if one exists, to send the page to UE or

broadcast the paging in the requested area


91/170

RANAP FUNCTION--

Management of tracingCN may, for operation and maintenance purposes,

request UTRAN to start recording all activity related

to a specific UE–UTRAN connection


92/170

RANAP FUNCTION--

UE–CN signaling transfertransfer of the first UE message from UE to UTRAN

example

a response to paging

a request of a UE-originated calla registration to a new area

it also initiates the signaling connection for Iu

direct transfer

used for carrying all consecutive signalingmessages over the Iu signaling connection in both

uplink and downlink directions


93/170

RANAP FUNCTION--

Security mode controlused to set the ciphering or integrity checking on or

off

when ciphering is on

the signaling and user data connections in theradio interface are encrypted with a secret key

algorithm


94/170

when integrity checking is onan integrity checksum, further secured with a

secret key, is added to some or all of the Radio

Interface signaling messages

this ensures that the communication partner has not

changed, and the content of the information has not

been altered


95/170

RANAP FUNCTION--

Management of overloadcontrol the load over Iu interface against overload due

example, to process overload at the CN or UTRAN

a simple mechanism is applied that allows

stepwise reduction of the load and its stepwiseresumption6(Jßà的 )šáâã 7, triggered by a timer


96/170

RANAP FUNCTION--

Resetreset the CN or the UTRAN side of Iu interface in

error situations

one end of the Iu may indicate to the other end that it

is recovering from a restart, and the other end canremove all previously established connections


97/170

RANAP FUNCTION--

Location reportingallows CN to receive information on the location of a

given UE

includes two elementary procedures

control the location reporting in RNCsend the actual report to CN


98/170

5.4.4 IU USER PLANE PROTOCOL

Iu User Plane protocolin the Radio Network Layer of Iu User

Plane

defined to be independent of CN

domain

purposecarry user data related to RABs over

Iu interface

the protocol performs either a fully

transparent operation, or framing for

user data segments

the protocol also performs some basic

control signaling to be used for

initialization and online control


99/170

the protocol has two modestransparent mode

ÐØ¹]ºäåæç>定èé，亦即上層所傳送的

通訊協定會直接加上GTP-Uèéà送Û，Iu FPÐ

Ø¹]äåæçZ[

applied for RABs that assume fully transparent

operation

support mode

…"#的Y>定，Šê¯°˜™與9ë™，*

Rmìí real-time的î·Yfor predefined SDU (Service Data Unit) sizes

performs framing of user data into segments of

predefined size


100/170

the SDU sizes typically correspond to AMR (Adaptive Multirate Codec) speechframes, or

the frame sizes derived from the data rate of aCS data call

control procedures for initialization and ratecontrol are defined, and a functionality isspecified for indicating the quality of the framebased, for example, on CRC from radio interface

5.4.5 PROTOCOL STRUCTURE OF IU


101/170

BC, AND THE SABP PROTOCOL

Iu BC interfaceconnects RNC in UTRAN with the broadcast domain

of Core Network, namely with Cell Broadcast Centre

used to define Cell Broadcast information that is

transmitted to mobile user via Cell Broadcast Servicee.g. name of city/region visualized on the mobile

phone display


102/170

Iu BC is a control plane only interfacethe protocol structure of Iu BC is shown as follows


103/170


104/170

SABP (Service Area Broadcast Protocol)provides the capability for Cell Broadcast

Centre in CN to define, modify and

remove cell broadcast messages from RNC

SABP has the following functions

message handling

broadcast of new messages

amendment6¥¦ 7 of existing broadcast

messages

prevention of broadcasting of specific

messages


105/170

load handlingresponsible for determining the loading of the broadcast

channels at any particular point in time

resetpermits CBC to end broadcasting in one or more Service

Areas


106/170

5.5 UTRAN INTERNAL INTERFACES

5.5.1 RNC–RNC Interface (Iur Interface) and theRNSAP Signaling

5.5.2 RNC–Node B Interface and the NBAP

Signaling

5.5.1 RNC–RNC INTERFACE (IUR

INTERFACE)ANDTHERNSAP


107/170

INTERFACE) AND THE RNSAP

SIGNALLING5.5.1.1 Iur1：Support of the Basic Inter-RNCMobility

5.5.1.2 Iur2：Support of Dedicated Channel

Traffic

5.5.1.3 Iur3：Support of Common Channel Traffic

5.5.1.4 Iur4：Support of Global Resource

Management


108/170

The following figure shows the protocol stack of RNCto RNC interface (Iur interface)

Iur interface provides four distinct functions

support of basic inter-RNC mobility (Iur1)

support of dedicated channel traffic (Iur2)support of common channel traffic (Iur3)

support of global resource management (Iur4)


109/170

5.5.1.1 IUR1：SUPPORT OF THE


110/170

BASIC INTER-RNC MOBILITY

This functionality requires the basic module ofRNSAP signalingprovides the functionality needed for the mobility of

the user between two RNCs

does not support the exchange of any user data traffic


111/170

If this module is not implementedthe only way for a user connected to UTRAN via

RNS1 to utilize a cell in RNS2 is to disconnect itself

temporarily from UTRAN (release the RRC

connection)

The functions offered by Iur basic module includesupport of SRNC relocation

support of inter-RNC cell and UTRAN registration

area update

support of inter-RNC packet paging

reporting of protocol errors


112/170

Since this functionality does not involve user datatraffic across IurUser Plane and Transport Network Control Plane

protocols are not needed

5.5.1.2 IUR2：SUPPORT OF


113/170

DEDICATED CHANNEL TRAFFIC

This functionalityrequires dedicated channel module of RNSAP signaling

allows dedicated and shared channel traffic between two

RNCs


114/170

This functionality requires alsoUser Plane Frame Protocol (FP) for dedicated and

shared channel

Transport Network Control Plane protocol (Q.2630.1

[Q.aal2 CS1]) used for the set-up of transport

connections (AAL2 connections)


115/170

Frame Protocol for dedicatedchannels (DCH FP) defines the

structure ofthe data frames carrying the user

data

the control frames used to exchange

measurements and control

information

Frame Protocol for common

channels (CCH FP) describesthe User plane procedure for the

shared channel


116/170

The functions offered by Iur DCH moduleestablishment, modification and release of the dedicated

and shared channel in DRNC due to handovers in dedicated

channel state

set-up and release of dedicated transport connections across

Iur interfacetransfer of DCH Transport Blocks between SRNC and

DRNC

management of the radio links in DRNS via

dedicated measurement report procedurespower setting procedures

compress mode control procedures

5.5.1.3 IUR3：SUPPORT OF


117/170

COMMON CHANNEL TRAFFIC

This functionalityallows the handling of common channel (i.e. RACH, FACH

and CPCH) data streams across Iur interface

Note

CPCH：Common Packet CHannelRACH：Random Access CHannel

FACH：Forward Access CHannel


118/170

It requiresCommon Transport Channel module of RNSAP

protocol

Iur Common Transport Channel Frame Protocol

(CCH FP)

If signaled AAL2 connections are usedQ.2630.1 [Q.aal2 CS1] signaling protocol of the

Transport Network Control Plane is needed


119/170

The functions offered by Iur common transportchannel moduleset-up and release of the transport connection across

Iur for common channel data streams

splitting of the MAC layer between SRNC (MAC-d)and DRNC (MAC-c)

flow control between MAC-d and MAC-c

註


120/170

註：

Œ/0Y6ï的MAC層*ð;為MAC的-nñ層MAC%&

ŒP©òó (&r#a-!ast)的ôõ6ï (l#gi!al !hannel)BjöuB的Y6ï (trans'#rt !hannel)

( UEÜNMAC%&層

( N#-e /)NŒ¸n !ell的MAC%&層


121/170

MAC%-Œ20÷l (-e-i!ate-)6ï( UEÜN一nMAC%-層( SRNC)NŒ¸nUE的MAC%-層

MAC%!8shŒ/0(一z (!##n)與ø< (share-)6ïJ的Z訊

( UE)ÜNMAC%!8sh層( CRNC (C#ntr#lling RNC))NŒ一n !ell的

MAC%!8sh層

5.5.1.4 IUR4：SUPPORT OF GLOBAL

RESOURCEMANAGEMENT


122/170

RESOURCE MANAGEMENT

This provides signaling to support enhancedradio resource management and O&M featuresacross Iur interface

The function is considered optional

This function has been introduced in subsequentreleases for the support ofcommon radio resource management between RNCsadvanced positioning methodsIur optimization


123/170

The functions offered by Iur global resourcemoduletransfer of cell information and measurements

between two RNCs

transfer of positioning parameters between controllertransfer of Node B timing information between two

RNCs

5.5.2 RNC–NODE B INTERFACE

ANDTHENBAPSIGNALING


124/170

AND THE NBAP SIGNALING

5.5.2.1 Common NBAP and the Logical O&M5.5.2.2 Dedicated NBAP


125/170

Figure 5.10 shows the protocol stack of RNC–Node B interface (Iub interface)


126/170


127/170

Figure 5.11 shows the logical model of Node Bseen from the controlling RNC


128/170

Figure 5.11 Logical Model of Node B


129/170

Logical model of Node B includes

the logical resources provided by Node B to UTRAN (via

Controlling RNC) - depicted as "cells" which include the

following physical channel resources

DPCH (Dedicated Physical Channel)

PDSCH (Physical Downlink Shared Channel)

PUSCH (Physical Uplink Shared Channel)

the dedicated channels which have been established on Node

Bthe common transport channels that Node B provides to RNC


130/170

Elements of the logical model1. Node B Communication Contexts for dedicated and

shared channels

corresponds to all the dedicated resources

that are necessary for a user in dedicatedmode and using dedicated and/or shared

channels as restricted to a given Node B


131/170

attributes (not exhaustive)list of Cells where dedicated and/or shared

physical resources are used

list of DCH which are mapped on the

dedicated physical resources for that Node BCommunication Context

list of DSCH and USCH [TDD] which are

used by the respective UE


132/170

the complete DCH characteristics for eachDCH, identified by its DCH-identifier

the complete Transport Channel

characteristics for each DSCH and USCH,

identified by its Shared Channel identifierlist of Iub DCH Data Ports

list of Iub DSCH Data ports and Iub USCH

data ports

FDD – up to one Iub TFCI2 Data Port


133/170

for each Iub DCH Data Port, thecorresponding DCH and cells which are

carried on this data port

for each Iub DSCH and USCH data port, the

corresponding DSCH or USCH and cellswhich serve that DSCH or USCH

physical layer parameters (outer loop power

control, etc)


134/170

2. Common Transport Channel

configured in Node B, on request of CRNC

attributes (not exhaustive) Type (RACH, CPCH [FDD], FACH, DSCH,USCH [TDD], PCH)

Associated Iub RACH Data Port for aRACH, Iub CPCH Data Port for a CPCH

[FDD], Iub FACH Data Port for a FACH, IubPCH Data Port for PCH

Physical parameters


135/170

3. Transport network logical resources

3.1 Node B Control Port

Functionality

exchange the signaling information for

the logical O&M of Node B

the creation of Node B Communication

Contexts


136/170

the configuration of the common transportchannels that Node B provides in a given

cell

PCH and BCH control information

between the RNC and the Node BNode B Control Port corresponds to one

signaling bearer between the controlling

RNC and the Node B

There is one Node B Control Port per Node B


137/170

3.2 Communication Control Portused to send the procedures for controlling theconnections between radio links and Iub DCH

data ports from RNC to Node B for control of NodeB Communication Contexts

one signaling bearer between RNC and Node Bcan at most correspond to one CommunicationControl Port

Node B may have multiple CommunicationControl Ports (one per Traffic Termination Point)


138/170

3.3 Traffic Termination Point

represents DCH, DSCH and USCH [TDD] data

streams belonging to one or more Node B

Communication Contexts (UE contexts), which arecontrolled via one Communication Control Port


139/170

3.4 Iub RACH Data Port3.5 Iub CPCH Data Port [FDD]

3.6 Iub FACH Data Port

3.7 Iub PCH Data Port

3.8 Iub FDD TFCI2 Data Port

3.9 Iub DSCH Data Port

3.10 Iub TDD USCH Data Port

3.11 Iub DCH Data Port

5.5.2.1 COMMON NBAP AND THE

LOGICALO&M


140/170

LOGICAL O&M

Iub interface signaling (NBAP, Node B Application Part) is divided into two essential

componentscommon NBAP

defines the signaling procedures across thecommon signaling link

dedicated NBAP

used in the dedicated signaling link


141/170

User Plane Iub frame protocols

define

the structures of the frames

the basic inband control

procedures for every type of

transport channel (i.e. for

every type of data port of the

model)

Q.2630.1 [Q.aal2 CS1] signaling

used for dynamic

management of AAL2

connections used in User

Plane


142/170

Common NBAP (C-NBAP) proceduresused for the signaling that is not related to one

specific UE context already existing in Node B

defines all the procedures for the logical O&M

(Operation and Maintenance) of Node B

such as configuration and fault management


143/170

Main functions of Common NBAPset-up of the first radio link of one UE, and selectionof the traffic termination point

cell configurationhandling of the RACH/FACH/CPCH and PCH

channelsinitialization and reporting of Cell or Node B specificmeasurement

Location Measurement Unit (LMU) controlfault management

5522DEDICATEDNBAP


144/170

5.5.2.2 DEDICATED NBAP

When the RNC requests the first radio link forone UE via C-NBAP Radio Link Set-up procedureNode B assigns a traffic termination point for the

handling of this UE context

every subsequent signaling related to this mobile is

exchanged with dedicated NBAP (D-NBAP)

procedures across the dedicated control port of the

given Traffic Termination Point


145/170

Main functions of the Dedicated NBAPaddition, release and reconfiguration of radio links

for one UE context

handling of dedicated and shared channels

handling of softer combininginitialization and reporting of radio link specific

measurement

radio link fault management

5.6 UTRAN ENHANCEMENTS

ANDEVOLUTION


146/170

AND EVOLUTION

5.6.1 IP Transport in UTRAN5.6.2 Iu Flex

5.6.3 Stand Alone SMLC and Iupc Interface

5.6.4 Interworking between GERAN and UTRAN,

and the Iur-g Interface


147/170

Release’99 UTRAN architecturedefines the basic set of network elements andinterface protocols for the support of Release ’99WCDMA radio interface

Enhancement of the Release’99 UTRAN

architecturesupport new WCDMA radio interface features toprovide a more efficient, scalable and robust 3GPPsystem architecture

Four most significant additions to the UTRAN

architecture introduced in Release 5 aredescribed in the subsequent sections

5.6.1IPTRANSPORTINUTRAN


148/170

5.6.1 IP TRANSPORT IN UTRAN

ATMthe transport technology used in the first release ofUTRAN

IP transportintroduced in Release 5

In addition to the initially defined option of AAL2/ATM, user plane FP frames can also beconveyedover UDP/IP protocols on Iur/Iub

over RTP/UDP/IP protocols in Iu CS interface

5.6.2IUFLEX


149/170

5.6.2 IU FLEX Release’99 architecture presented

in Figure 5.3

only one MSC and one SGSN

connected to RNC

i.e. only one Iu PS and Iu CS

interface in the RNC

Iu flex (flexible)

allows one RNC to have more

than one Iu PS and Iu CS

interface instances with the

core Main benefits of this feature

possible load sharing between

core network nodes


150/170

5.6.3 STAND ALONE SMLC AND

IUPC INTERFACE


151/170

U C N R C

Location-based servicesexpected to be a very important source of

revenue for mobile operators

a number of different applications are expected

to be available and largely usedUTRAN architecture includes a stand alone

Serving Mobile Location Centre (stand alone

SMLC, or, simply, SAS)

a new network element for handling ofpositioning measurements and calculation of

the mobile station position


152/170

SASconnected to RNC via Iupc interface

Positioning Calculation Application Part (PCAP) is

the L3 protocol used for RNC-SAS signaling

SAS performs the following procedures

provides positioning (GPS related) data to

RNC

performs the position calculation function for

UE assisted GPS


153/170

SAS and Iupc interface are optional elementsIupc

the first version, supported only Assisted GPS

later versions, support for other positioning methods

5.6.4 INTERWORKING BETWEEN

GERAN AND UTRAN, AND THE IUR-G

INTERFACE


154/170

INTERFACE

Iu interfacescheduled to be part of the GSM/EDGE Radio Access

Network (GERAN) in GERAN Release 5

allows reusing 3G Core Network also for GSM/EDGE radio

interface (and frequency band), but also allows a more

optimized interworking between the two radio technologies


155/170

EffectRNSAP basic mobility module is enhanced to allow

the mobility to and from GERAN cells in the target

and the source

RNSAP global module is enhanced in order to allow

GERAN cells measurements to be exchanged betweencontrollers

allows a Common Radio Resource Management

(CRRM) between UTRAN and GERAN radios


156/170

Iur-g interfacerefer to the above-mentioned set of Iur functionalities

that are utilized also by GERAN

5.7 UMTS CORE NETWORK

ARCHITECTURE AND EVOLUTION


157/170

5.7.1 Release’99 Core Network Elements5.7.2 Release 5 Core Network and IP Multimedia

Sub-system


158/170

UMTS radio interface, WCDMAa bigger step in radio access evolution from GSMnetworks

UMTS core networkdid not experience major changes in 3GPP Release’99

specificationRelease’99 structure was inherited from GSMcore networkboth UTRAN and GERAN based radio access networkconnect to the same core network

5.7.1 RELEASE ’99 CORE NETWORK

ELEMENTS


159/170

Two domains of Release’99 core networkCircuit Switched (CS) domainPacket Switched (PS) domain

The division comes from the differentrequirements for datadepending on whether it is real time (circuitswitched) or non-real time (packet data)


160/170

Figure 5.12Release’99 core network

structure with both CS and

PS domains

Registers

HLR, VLR, EIRService Control Point

(SCP)

the link for providing a

particular service to end

user


161/170


162/170

CS domain has the following elementsMobile Switching Centre (MSC), including Visitor

Location Register (VLR)

Gateway MSC (GMSC)


163/170

PS domain has the following

elementsServing GPRS Support

Node (SGSN)

covers similar functions

as MSC for packet data,

including VLR typefunctionality

Gateway GPRS Support

Node (GGSN)

connects PS core

network to othernetworks, e.g. to the

Internet


164/170

In addition to the two domains, the networkneeds various registers for proper operationHome Location Register (HLR)

Equipment Identity Register (EIR)

contains the information related to theterminal equipment

can be used to, e.g., prevent a specific terminal

from accessing the network

5.7.2 RELEASE 5 CORE NETWORK

AND IP MULTIMEDIA SUB-SYSTEM


165/170

Release 4 included the change in core network CSdomainMSC was divided into MSC server and MediaGateway (MGW)

GMSC was divided into GMSC server and MGW

Release 5contains the first phase of IP Multimedia Sub-system(IMS)

this will enable a standardized approach for IP-basedservice provision via PS domain

l


166/170

Release 6

enhance IMS to allow theprovision of services similar to CS

domain services from PS domain

Release 5 architecture is presented

in Figure 5.13

Home Subscriber Server (HSS)

shown as an independent item

Session Initiation Protocol (SIP)

the key protocol between

terminal and IMS

the basis for IMS-related

signaling


167/170


168/170

MSC or GMSC server

takes care of the control functionality asMSC or GMSC, respectively

user data goes via Media Gateway (MGW) one MSC/GMCS server can control multipleMGWsthis allows better scalability of the network

when data rates increase with new dataservices

in this case, only the number of MGWsneeds to be increased

MGW performs actual switching for user data

and network interworking processing

e.g., echo cancellation or speech decoding/

encoding


169/170

IMS includes the following key

elementsMedia Resource Function (MRF)

controls media stream resourcesor mixes different mediastreams

Call Session Control Function(CSCF)the first contact point toterminal in the IMS (as a proxy)

handling of session statesacting as a firewall towardsother operator’s networks


170/170

Media Gateway Control Function

(MGCF)handle protocol conversions

control a service coming via CS

domain and perform processing in

an MGW, e.g. for echo cancellation

radio access network architecture

Documents