12.12.2012 Views

UMTS Networks : Architecture, Mobility and Services

UMTS Networks : Architecture, Mobility and Services

UMTS Networks : Architecture, Mobility and Services

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>UMTS</strong> Protocols 325<br />

Figure 10.25 Logical structure of an RRC protocol entity in WCDMA-FDD<br />

also used for frequently repeated messages, like paging, to avoid unnecessary overheads.<br />

Acknowledged mode AM-SAP is used for control signalling that is specific<br />

to one UE whenever reliability of message exchange is required. Unacknowledged<br />

mode UM-SAP, on the other h<strong>and</strong>, is used to avoid the potential delay present in<br />

acknowledged-mode signalling (e.g., when releasing an RRC connection the release<br />

message is repeated many times—quick repeat function—via UM-SAP to increase<br />

the probability of the UE receiving it).<br />

Figure 10.25 also shows the logical structure of an RRC protocol entity. The Dedicated<br />

Control Function Entity (DCFE) is used to h<strong>and</strong>le all signalling specific to one<br />

UE. In the SRNC there is one DCFE entity for each UE having an RRC connection<br />

with this RNC. The Paging <strong>and</strong> Notification Function Entity (PNFE) h<strong>and</strong>les paging<br />

messages sent to idle-mode UEs. In a CRNC there is at least one PNFE entity for each<br />

cell to be controlled. The Broadcast Control Function Entity (BCFE) h<strong>and</strong>les system<br />

information broadcasting on BCCH <strong>and</strong> FACH logical channels. There is at least one<br />

BCFE entity for each cell in a CRNC. Besides these functional entities a special<br />

Routing Function Entity (RFE) is also modelled on top of Figure 10.25. Its task is<br />

to route non-access stratum messages to different MM/CM entities at the UE end <strong>and</strong><br />

to different CN domains at the RNC end.<br />

As key executors of radio resource allocation, the RRC entities in the UE <strong>and</strong> RNC<br />

have control over the L1, MAC <strong>and</strong> RLC entities at their end. In order to execute<br />

control comm<strong>and</strong>s on these lower layer protocol entities, special control SAPs are<br />

available to the RRC protocol entity as shown in Figure 10.25. These control SAPs<br />

are also used for reporting measurements <strong>and</strong> exceptional conditions detected by the<br />

lower layers.<br />

The major function of the RRC protocol is to control the radio bearers, transport<br />

channels <strong>and</strong> physical channels. This is done by set-up, reconfiguration <strong>and</strong> release of<br />

different kinds of radio bearers. Before such actions can take place, RRC protocol<br />

communication must itself be initiated by using a number of (minimum four) signalling<br />

radio bearers. The resulting signalling connection, together with any other subsequently<br />

established bearers, is called RRC connection. During RRC connection, set-up,

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!