sinau.fahroe.web.

id

3G Sharing Material

Agenda

sinau.fahroe.web.id

Breakdown Congestion
Understanding of Admission

Control
Understanding of Load
Balance
Understanding of Load
Reshuffle

sinau.fahroe.web.id

Session 1

BREAKDOWN
CONGESTION

sinau.fahroe.web.id

Session 2

UNDERSTANDING OF
ADMISSION CONTROL

sinau.fahroe.web.id

Basic CAC Flowchart

sinau.fahroe.web.id

CAC Policy
The RNC implements differentiated CAC based on
system resources, resource requests, channels, and
service priorities.
System Resources
The system resources involved in CAC are as follows:
NodeB credit resources
Iub transmission resources
Cell code resources
Number of users, including HSDPA/HSUPA and EFACH/E-RACH users
Cell power resources
The RNC implements differentiated CAC based on
system resources requested by users.

sinau.fahroe.web.id

2.1.2Resource

Requests
The resource requests involved in CAC are as
follows:
Cell updates
Service setup: new radio resourcecontrol(RRC)
setup and radio access bearer (RAB) setup
Service change: RAB reconfiguration and
service rate increase or decrease
Handovers: soft handovers, hard handovers,
inter-RAT incoming handovers, and circuit
switched fallback (CSFB)
State transitions: P2D, F2D, and D2D
transitions

2.1.3Channels

sinau.fahroe.web.id

The

amount of consumed resources is channel-specific, and

therefore the RNC implements differentiated CAC based on
channels.
Dedicated Channels
Generally, users consume more resources on dedicated
channels than they do on common channels. Therefore,
CAC focuses on service requests on DCH channels and
HSPA channels, which will be described in the
corresponding chapters.
Common Channels
Users consume relatively smaller amount of resources on
common channels. Therefore, the RNC reserves some
resources for certain common channels and does not
implement CAC for specific requests.
For details about the CAC policy on common channels, see
8 Common ChannelAdmission.
8

sinau.fahroe.web.id

2.1.4Service

Priorities
The RNC implements differentiated CAC for resource requests other than
RRC during NodeB credit resource-based, cell code resource-based, and
power resource-basedadmissions as follows:
The RNC preferentially admits high-priority service requests such as
emergencycalls, detachments, or registrations. For details, see sections
3.2.1AdmissionDecisions on RRC Connection Setup Requestsand
7.2AdmissionControlAlgorithm 1.
The RNC provides differentiatedadmissionthresholds for handovers,
adaptive multirate (AMR) services, non-AMR services, and other services
because these service types have different QoS requirements. A
specialadmissionthreshold is used for handover-related resource requests
and differentiatedadmissionthresholds are used for non-handover-related
resource requests. For details, see the following sections:

3.2.2AdmissionDecisions on Other Resource Requests

5.2AdmissionDecisions on Other Resource Requests
7.2.1 UplinkAdmissionControlAlgorithm 1
7.2.2 DownlinkAdmissionControlAlgorithm 1
7.3.2 UplinkAdmissionControlAlgorithm 2

This

document does not describeadmissioncontrolfor Multimedia

Broadcast Multicast Service (MBMS), which is detailed in
MBMS Feature Parameter Description.

sinau.fahroe.web.id

Session 3

UNDERSTANDING OF
LOAD BALANCE

10

sinau.fahroe.web.id

Session 4

UNDERSTANDING OF
LOAD RESHUFFLE

11

sinau.fahroe.web.id