Вы находитесь на странице: 1из 46

3G RANOP RU20

Paging and inter- RNC optimization

Nokia Siemens Networks

RN31577EN20GLA0

Course Content
KPI overview Performance monitoring Air interface and neighbor optimization Capacity & traffic optimization Paging and inter-RNC optimization

Nokia Siemens Networks

RN31577EN20GLA0

Module Objectives

At the end of the module you will be able to:


Describe SRNC relocation issues Describe Paging Procedure & Performance

Nokia Siemens Networks

RN31577EN20GLA0

Paging and inter-RNC optimization


Re-location Paging Performance in 3G
- Cell resource states - Paging capacity improvement RU20

Nokia Siemens Networks

RN31577EN20GLA0

Re-location (1/4)
UE Mobility Handling in RAN 3GPP options to use MM
CN

Limited support of multi vendor services

SRNS relocation
CN

SRNC anchoring
CN CN

Iu
RNC

Iu Iur
RNC

Iu
RNC

Iu Iur
RNC S-RNC

Iu Iur

Iu
D-RNC

Iu
RNC

Iu Iur
RNC

Keep service as long as possible

SRNS Relocation, which is a standardised mobility method

anchoring is supported in Nokia SRNC only for CS RT + PS/NRT services within Cell_DCH

SRNC Anchoring which is not as such a standardised mobility method, but which can be implemented by applying an undefined set of standardised features

Nokia Siemens Networks

RN31577EN20GLA0

Re-location (2/4)
UE Mobility Handling in RAN 3GPP gives two different options to handle inter-RNC mobility in radio network

1. 2.

SRNS Relocation, SRNC Anchoring

When neighbouring DRNC or CN do not support relocation, anchoring is supported in Nokia SRNC only for CS RT services, PS RT data services and for PS NRT data services in CELL_DCH state. In multivendor cases this will lead to limited functionality related to mobility over RNC border between different vendors RNS if the other vendor uses SRNC anchoring

Nokia Siemens Networks

RN31577EN20GLA0

Re-location (3/4)
Source and Target RNC
Relocation procedure and failures are detected differently between Source and Target RNC Target RNC: The Target RNC sees the Relocation as incoming RRC SRNC Relocation is an RRC Establishment cause Setup, Access and Active counters are incremented both for RRC and RAB In case of failures, Setup and Access failure counters are incremented both for RRC and RAB Source RNC: The Source RNC starts the Relocation procedure SRNC Relocation is a RRC Release cause RRC Active release counters are incremented both for RRC and RAB In case of failures, Active failure counters are incremented both for RRC and RAB

Nokia Siemens Networks

RN31577EN20GLA0

Re-location (4/4)
Failure and Abnormal Release cause at Service Level
RRC setup and access counters are updated during incoming handovers and relocations. If the new RRC connection is established or relocated successfully and if there are RAB connections for the UE, the RAB setup and access counters are updated as well.

Nokia Siemens Networks

RN31577EN20GLA0

Example of incoming Re-location (1/3)


Incoming SRNC Relocation
Source RNC CN Target RNC RANAP:Relocation Request

SRNC Relocation Decision


RANAP:Relocation Required

MS

SRNS Relocation,
Setup phase:
RRC_CONN_STP_ATT

CN

RANAP:Relocation Request Ack User plane set -up RANAP:Relocation Command RNSAP:Relocation Commit SRNC operation started RANAP:Relocation Detect UP switching

RRC_CONN_ STP_FAIL_RNC

Iu
SRNC

Iu
DRNC

Iur Access phase:


RRC_CONN_STP_CMP RRC_CONN_ ACC_FAIL_RNC

RRC:UTRAN Mobility Information RRC:UTRAN Mobility Information Confirm

RANAP:Relocation complete RANAP:Iu Release RANAP:Iu Release Complete

Active phase:
RRC_CONN_ACC_CMP

User plane release

Nokia Siemens Networks

RN31577EN20GLA0

Example of incoming Re-location (2/3)


Incoming SRNC
If incoming inter-rnc sho is followed by a relocation, the establishment cause in the Target RNC is srnc relocation: The following counters are incremented:

RRC_CONN_STP_ATT SRNC_RELOC_ATTS RRC_CONN_STP_CMP RRC_CONN_ACC_CMP and the relative RAB counters

Attempts complete

After the Iu Relocation Complete message the active phase starts

10

Nokia Siemens Networks

RN31577EN20GLA0

Example of incoming Re-location (3/3)


Incoming SRNC Access Phase
To evaluate the performance of the incoming SRNC relocation its possible to use the following KPI, both at RNC and cell level. Failures are between the Relocation Request and the Relocation Complete: RRC_CONN_STP_FAIL_RNC RRC_CONN_ACC_FAIL_RNC/RADIO For troubleshooting the M1009 family Counters is available. The table is called: L3 Relocation signalling measurement.

Re location _ Failure _ Rate =

SRNC_RELOC_FAILS SRNC_RELOC_ATTS

Service Level table counters

11

Nokia Siemens Networks

RN31577EN20GLA0

Example of outgoing Re-location (1/3)


Outgoing SRNC Relocation
Coming from active and move to release
Source RNC CN Target RNC MS

SRNC Relocation Decision


RANAP:Relocation Required RANAP:Relocation Request

SRNS Relocation,
CN

RANAP:Relocation Request Ack User plane set-up RANAP:Relocation Command

Iu
SRNC

Iu
DRNC

Active phase

Iur

RNSAP:Relocation Commit SRNC operation started RANAP:Relocation Detect UP switching RRC:UTRAN Mobility Information RRC:UTRAN Mobility Information Confirm RANAP:Relocation complete RANAP:Iu Release

Release phase

RANAP:Iu Release Complete

From Source RNC point of view the RRC is in the active phase

User plane release

12

Nokia Siemens Networks

RN31577EN20GLA0

Example of outgoing Re-location (2/3)


Outgoing SRNC Relocation
Counters for normal release are incremented: RRC_CONN_ACT_REL_SRNC RAB_ACT_REL_xxx_SRNC

13

Nokia Siemens Networks

RN31577EN20GLA0

Example of outgoing Re-location (3/3)


From ticket collection
RRC Connection Active failures As far as Source RNC any failure during the relocation procedure is a failure during the active phase and since it happens under cells of the target RNC those failures are mapped into Cell id 0
STOP WCELL IDOUT FAIL SOURCE 0 rnc_internal_c 0 0 0 0 OUT REASON no_resp_from_rlc_c

Source RNC

OUT DETAILED REASON frequency Percentage nok_c 62 2.09% subsystem_down_c default_c default_c radio_conn_lost_c 60 5 3 3

iu_c serv_req_nack_from_iuv_c radio_interface_c no_resp_from_rlc_c iur_c iur_connection_lost_c radio_interface_c radio_link_failure_c

2.02% 0.17% 0.10% 0.10%

STOP WCELL IDOUT FAIL SOURCE OUT REASON OUT DETAILED REASONfrequency Percenatge 0 rnc_internal_c no_resp_from_rlc_c nok_c 92 3.05% 0 iu_c serv_req_nack_from_iuv_c subsystem_down_c 70 2.32% 0 radio_interface_c no_resp_from_rlc_c default_c 9 0.30% 0 radio_interface_c radio_link_failure_c radio_conn_lost_c 4 0.13% 0 radio_interface_c timer_expired_c rrc_dir_sc_re_est_c 3 0.10% 0 transmissio_c transport_res_rel_nrm_c default_c 3 0.10%

14

Nokia Siemens Networks

RN31577EN20GLA0

SRNC Relocation failure (1/2)

Impact of SRNC relocation failure in the Setup failure Percentage refers to all the failures in the setup phase
IN REASON srnc_relocation_c srnc_relocation_c srnc_relocation_c srnc_relocation_c srnc_relocation_c OUT FAIL SOURCE iu_c rnc_internal_c iu_c transmissio_c rnc_internal_c OUT REASON no_resp_from_iuv_c invalid_configuration_c no_resp_from_iuv_c serv_req_nack_from_nrm_c serv_req_nack_from_r_rab_c frequency 79 6 3 2 1

Target RNC
Target RNC MS

Percentage 9.1% 0.7% 0.3% 0.2% 0.1%

Source RNC

CN SRNC Relocation Decision RANAP:Relocation Required

RANAP:Relocation Request

RANAP:Relocation Request Ack User plane -upset RANAP:Relocation Command RNSAP:Relocation Commit SRNC operation started RANAP:Relocation Detect UP switching

Setup phase RRC_CONN_STP_F AIL_RNC

IN REASON srnc_relocation_c srnc_relocation_c srnc_relocation_c srnc_relocation_c srnc_relocation_c srnc_relocation_c

OUT FAIL SOURCE iu_c transmissio_c iu_c rnc_internal_c iu_c rnc_internal_c

OUT REASON no_resp_from_iuv_c serv_req_nack_from_nrm_c no_resp_from_iuv_c serv_req_nack_from_r_rab_c serv_req_nack_from_iuv_c invalid_configuration_c

frequency 76 6 5 2 2 2

Percentage 23.6% 1.9% 1.6% 0.6% 0.6% 0.6%

Access phase RRC_CONN_ACC_FAIL_ RRC:UTRAN Mobility Information RNC

RRC:UTRAN Mobility Information Confirm RANAP:Relocation complete RANAP:Iu Release RANAP:Iu Release Complete User plane release

Active phase

Analysis done using PMI Ticket

15

Nokia Siemens Networks

RN31577EN20GLA0

SRNC Relocation failure (2/2)


No response from rlc-nok (017F-191)
Incremented counters in the Source RNC RRC_CONN_ACT_FAIL_RNC RAB_ACT_FAIL_xxx_RNC

16

Nokia Siemens Networks

RN31577EN20GLA0

Paging and inter-RNC optimization


SRNC relocation

Thank You !

17

Nokia Siemens Networks

RN31577EN20GLA0

Paging and inter-RNC optimization


Paging Performance in 3G
- Cell resource states - Paging capacity improvement RU20

18

Nokia Siemens Networks

RN31577EN20GLA0

Paging Performance in 3G - RU10


RRC States

UTRA RRC Connected Mode


UE in DRX mode discontinous reception

UE in DRX mode discontinous reception

NEW RU10: via viaCell CellUpdate Update/ Confirm


Dedicated resources allocated (DCH, HS) Tx and Rx mode

URA_PCH

CELL_PCH

Common resources allocated (RACH-FACH)

CELL_DCH

CELL_FACH

Tx and Rx mode

Cell selection Cell re-selection Listen to paging not implemented

Idle Mode
19 Nokia Siemens Networks RN31577EN20GLA0

Paging Performance in 3G RU10


The packet access procedure in WCDMA should keep the interference caused to other users as small as possible. Since there is no connection between the base station and the UE before the access procedure, initial access is not closed loop power controlled and thus the information transmitted during this period should be kept at minimum.

There are 3 scenarios for WCDMA packet access: infrequent transmission of small packets frequent transmission of small packets and transmission of large packets Packet data transfer in WCDMA can be performed using common, shared or dedicated transport channels.
Since the establishment of a dedicated transport channel itself requires signalling and thus consumes radio resources, it is reasonable to transmit infrequent and small NRT user data packets using common transport channels without closed loop power control. Then the random access channel (RACH) in UL and the forward access channel (FACH) in DL are the transport channels used for packet access

When the packet data is transferred on common channels, the UE is in CELL_FACH state. Large or frequent user data blocks are transmitted using shared or dedicated transport channels (DCH). When the packet data is performed on shared or dedicated channels, the UE is in CELL_DCH state.
20 Nokia Siemens Networks RN31577EN20GLA0

Paging Performance in 3G RU10


Example: Transition from CELL_DCH to CELL_PCH
If UE has Multi-RAB allocated (voice call & NRT PS call) & PS data inactivity detected in RNC L2, RNC triggers reconfiguration from Cell_DCH to Cell_PCH on voice call release. UE stays in Cell_PCH until new data is available in UL or DL L2 buffers. As soon as certain traffic volume threshold is met, RNC may reconfigure the connection to Cell_DCH.

Each UE in Cell-DCH or Cell_FACH substate is allocated DMCU resources in RNC. In case of processing shortage in DMCU units, RNC may move UE to Cell_PCH and release all DSP resources in RNC.
L3 signaling is RRC: Physical Channel Reconfiguration

CELL_PCH

CELL_DCH

21

Nokia Siemens Networks

RN31577EN20GLA0

Paging Performance - processing


URA reselection Periodic URA update
(stationary UE)

Paging response (DL


data / signalling) UL Access (UL data / signalling)

Fast UE with L2 inactivity

Inactivity detection during last 20sec RNC L2 resources at low level

Cell reselection (moving


UE)

Periodic cell update


(stationary UE)

Paging response (DL Activity supervision Completion of Cell Update procedure


data/ signalling) UL Access (UL data/signalling)

Data in GTP buffer

URA_ PCH

Cell_ PCH
Completion of URA Update procedure Max. # cell updates in Cell_FACH / Cell_PCH exceeded

Inactivity detection of NRT RB Release of RT RB

Cell_ DCH
Setup of RT/NRT RB RAB reconfiguration DCH Up or Downgrade Bit rate reduction due to load reasons
CN originated paging (MT Call) Random Access (MO Call)
22 Nokia Siemens Networks RN31577EN20GLA0

Cell_ FACH

RRC Connection Release

Idle Mode

UL/DL data or signalling RT RB setup

Paging Performance
Paging lost: cell-PCH not active
incremented only if the mobile is in cell-PCH
(bit/s) 23 Nokia Siemens Networks RN31577EN20GLA0

Paging Performance
Paging Blocking

A terminal, once registered to a network, has been allocated a paging group. For the paging group there are Paging Indicators (PI) which appear periodically on the Paging Indicator Channel (PICH) when there are paging messages for any of the terminals belonging to that paging group. Once a PI has been detected, the terminal decodes the next PCH frame transmitted on the Secondary CCPCH to see whether there was a paging message intended for it. The terminal may also need to decode the PCH in case the PI reception indicates low reliability of the decision. If network would like to contact into certain user (SIM card) a paging procedure will took place. Paging type 1 can happen either due to mobile terminated call or mobile terminated SMS. First step is to find out where subscriber-B (the called party) is. This means HLR enquiry to subscriber-Bs HLR. HLR will return VLR address where subscriber-B is. VLR will start and act as master to this paging procedure. VLR will know subscriber-Bs location area level. VLR will send paging command to relevant RNCs (via Iu-CS interface), who are handling this LAC where subscriberB is.

24

Nokia Siemens Networks

RN31577EN20GLA0

Paging Performance in 3G & S-CCPCH config.


Paging Blocking

In the case that a single S-CCPCH has been configured for a cell, the TTI for the paging transport channel is 10 ms while the transport block size is 80 bits and the transport block set size is 1. The S-CCPCH can be used to transmit the transport channels: Forward Access Channel (FACH) and Paging Channel (PCH). In the current implementation (see 3GPP 25.331), the PCH has the priority on FACH so that FACH transport blocks can be sent only if the timeslot is not occupied by paging messages. Thus, the maximum PCH throughput is 80 bits / 10 ms = 8 kbit/s. Since the dimension of a paging message (including 1 paging record) is 80 bits, the maximum paging rate is 100 paging/sec/cell.

25

Nokia Siemens Networks

RN31577EN20GLA0

Paging Performance in 3G & S-CCPCH config.


Paging buffer

Each IMSI belongs to a paging group, according to the formula Paging group = IMSI mod (DRX cycle length) The paging occasions for each paging group can be
10 ms

group 1 served

group 2 served

group 3 served

group 4 served

group 30 served

group 31 served

group 32 served

group 1 served

group 2 served

10ms * DRX cycle length

In case no buffering is utilized, only 1 paging message related to each paging group would be served at the end of each period of 10 ms * DRX cycle length.

26

Nokia Siemens Networks

RN31577EN20GLA0

Paging Performance - Paging buffer


In the current implementation (RAN04/RAN05), a buffer of 512 places stores the paging messages. When a new paging message arrives and the next paging occasion is already occupied, the paging message is stored in the first free paging occasion belonging to the paging group. The number of places reserved in the buffer to each paging group depends on a hidden parameter and the DRX cycle length: M = window_size / DRX cycle length With window_size=300 and DRX cycle length=32 M=9; with window_size=300 and DRX cycle length=128 M=2. The following figure shows only the paging occasions belonging to the paging group interested by the paging message.
place 1 place 2 place 3 place 4 place 5 place 6 place 7 place 8 place 9

busy

busy

busy

busy
first empty place

10 ms * DRX cycle length

NOTE: a paging can be buffered for M * DRX cycle length = 9 * 320 ms = 2.88 sec; this time is shorter than the repetition time in CN but could be higher than the repetition time in RNC (when cell-PCH is active).
27 Nokia Siemens Networks RN31577EN20GLA0

Paging Performance in 3G
PCH throughput: paging requests blocked
The number of transmitted pagings (on the radio interface) is: paging_requests [pagings/hour] = 3600 * PCH_THROUGHPUT / (80 bits) The number of paging attempts forwarded to be transmitted on PCH is: paging_type_1 [pagings/hour] = PAGING_TYPE_1_ATT_CN_ORIG + PAGING_TYPE_1_ATT_RNC_ORIG PAGING_TYPE_1_ATT_CN_ORIG- indicates the no.of CN originated paging attempts to mobiles in idle state or PCH/URA substate. PAGING_TYPE_1_ATT_RNC_ORIG-indicates the no.of RNC originated paging attempts to mobiles in PCH/URA substate.

The number of paging attempts not sent on air due to congestion of PCH channel is: paging_requests_blocked [paging/hour] = paging_type_1 - paging_requests

28

Nokia Siemens Networks

RN31577EN20GLA0

PCH Loading Estimation Process


M1006C25 Paging Type 1 Att CN Orig M1006C26 Paging Type 1 Att RNC Orig use M1000C70 Ave PCH Throughput M1000C71 PCH Throughput Denom 0 M1001C32,34,36,38,52,56&60 indicate the amount of MTC events in cell basis, which is related to amount of Paging events. all 0 if cell_PCH is not in

29

Nokia Siemens Networks

RN31577EN20GLA0

PCH Loading Estimation Process


M1006C25&C26 gives the hourly(or daily) basis number of Paging Type1 transmitted from CN per cell Since the counter values are sometimes slightly different on cell basis, the maximum counter value over all the cells in the LA/RA is used in this analysis Average Paging Record size (=80[bit]) is the figure in RLC level (seems to be pretty ok currently) Max Paging Throughput is also in the same layer so that Paging Load can be calculated with using those values
1 3600[sec]

Air Interface

MaxAmountOfPagingType1 = max(M1006C25, among cells in the LA/RA) + max(M1006C26 , among cells in the LA/RA) PagingThroughput [bps] = MaxAmountOfPagingType1 AveragePagingRecordSize[bit ] AveragePagingRecordSize [bit ] = 80 8000 (# of SCCPCH = 1) MaxPagingThroughput [bps ] = 24000 (# of SCCPCH = 2) PagingThroughput [bps ] PagingLoad [%] = 100 MaxPagingThroughput [bps ]

This should on TB level


30 Nokia Siemens Networks RN31577EN20GLA0

PCH Loading Estimation Process


Statistically, Paging Type1 is generated in the random manner by a lot of subscribers, except the special case like Happy New Year call Number of Paging Type1 generated would form Poisson distribution Through the below flow

Air Interface

Target PCH Load

Averaged # of simul. Paging Type1/sec


Paging Type1=200bit

Poisson Distribution

1 SCCPCH

8[kbps]
Max PCH Throughput

100
Max P.T.1/sec

Failure Probability Acceptable? NO YES

YES

OK

2 SCCPCH

24[kbps]

300

Failure Probability Acceptable? NO

Divide LA/RA
31 Nokia Siemens Networks RN31577EN20GLA0

PCH Loading Cumulative Poisson Distribution


Air Interface
2005/Dec/31 23:00 @RNC510 No need to have 2 SCCPCH nor LA/RA division
Relation between Probability of Simultaneous "Paging Type1" and PCH Loading Max PCH Throughput=8[kbps] / Size of Paging Type 1=80[bits] (Poisson Distribution)

Cumulative Probability [%]

100 98 96 94 92 90 0 10 20 30 40 50 60 70 80 90 100 110 120 130 140 # of Sim ultaneous "PagingType1" [count/sec]

PCHLoad=10%

PCHLoad=30%

PCHLoad=50%

PCHLoad=70%

PCHLoad=80%

max limit (SCCPCH=1)

Practical Max PCH Load = 70% When PCH load=80%, ~1.3% of P.T1 fails. It would be good to have Practical Max PCH Load as 70% so that simultaneous #P.T1/sec is practically less than max(=100). NOTE: THIS IS PURELY FROM PCH POINT OF VIEW AND DOES NOT INCLUDE THE PAGING BUFFER HANDLING ASPECT
32 Nokia Siemens Networks RN31577EN20GLA0

PCH Loading Estimation Results


Peak hour is 18:00 and the below graph shows the PCH load @ 18:00 (hourly data) Friday is the busiest day in the week except special events. Increase : 4[%] in 6[month] from 4[%] to 8[%] 0.67[%/month] But still quite difficult to forecast with non-linear approximation.
Air Interface
PCH Load @18:00 2005/Jun/01~Dec/31 PCH Throughput=8[kbps] / PagingType1=80[bits]
9.000 8.000 7.000 PCH Load [%] 6.000 5.000 4.000 3.000 2.000 1.000 0.000 05/06/01 05/06/08 05/06/15 05/06/22 05/06/29 05/07/06 05/07/13 05/07/20 05/07/27 05/08/03 05/08/10 05/08/17 05/08/24 05/08/31 05/09/07 05/09/14 05/09/21 05/09/28 05/10/05 05/10/12 05/10/19 05/10/26 05/11/02 05/11/09 05/11/16 05/11/23 05/11/30 05/12/07 05/12/14 05/12/21 05/12/28

Fireworks @Yodo River Tenjin Festival

0.67[%/month]

date RNC501
33 Nokia Siemens Networks RN31577EN20GLA0

RNC509

RNC519

RNC510

PCH Loading Conclusions


Currently, PCH Load is still only10[%] at most. Only linear trend of PCH Load increase can be seen 4% increase during the past 6 months, from 4% to 8% Periodical check of PCH Load is necessary but still it will not reach the max.

Calculations about PCH load can be used to plan the LA/RA areas BUT it should be noted that the paging buffer handling analysis should be included as well.

34

Nokia Siemens Networks

RN31577EN20GLA0

Paging and inter-RNC optimization Paging Performance in 3G


- Paging capacity improvement RU20
- Cell resource states - Paging capacity improvement RU20

35

Nokia Siemens Networks

RN31577EN20GLA0

Introduction (1/2)
24 kbps Paging Channel
Paging load/activity
- 8 kbps paging channel capacity is implemented for (RU10) - 24 kbps can be allocated for RU20 (ASW) - Transport block size increase - The stand alone 24kbps PCH is allocated on S-CCPCH with SF128, comparing 8 Kbps/SF256 (more PwR) - If Paging 24 kbps is used, maximum of available HSDPA codes are only14
Paging Ch with 24 kbps Bottleneck is PwR Not code tree allocation (calculation on next slide)
Cch,256,3 S-CCPCH 1 Cch,256,2 Cch,256,1 Cch,256,0 Cch,256,14

E-AGCH Cch,128,6 Cch,128,5 E-HICH & E-RGCH

No HSDPA code free


Cch,128,4 Cch,16,0

HS-SCCH

S-CCPCH 2 Cch,64,1 PICH AICH P-CCPCH CPICH

S-CCPCH setup

Pilot coverage

WCEL: PtxSCCPCH1 It carries a PCH or FACH (mux) or FACH /dedicated). Spreading factor is SF64 (60 kbps)
36 Nokia Siemens Networks RN31577EN20GLA0

Introduction (2/2)
8/24 kbps Paging Channel
Example: Power benchmark What limits first: PwR or Code tree occupation Average HSDPA throughput hardly affected by loss of 1 code, as CQI extremely seldom good enough for 15 codes (e.g. probability < 1 : 1000) With SF128 PCH (24kbps) needs power 2 dB below CPICH = 31 dBm = 1.26 Watt 60kbps/24kbps, cc. 1/2 With SF256 PCH (8kbps) needs power 5 dB below CPICH = 28 dBm = 0.63 Watt 30kbps/8kbps cc.1/2 Power loss = 1.26 W 0.63 W = 0.63 W approx. 600 mW 3 % of 20 W max. cell power (1% = 200mW, 3% =600 mW) 5 % (600 mW) of about 12 W available for user data

37

Nokia Siemens Networks

RN31577EN20GLA0

24 kbps Paging Channel


Concept

To support higher paging capacity, the size of transport block for PCH is increased:
PCCH

Logical channel
8 kbps = up to 5050-75% PCH load

8 kbps = 80 Bit / 10ms TTI (default)

Transport channel

PCH 24 kbps = 240 Bit / 10ms TTI (optional)


Several

Physical SCCPC S-CCPCH possible channel H If WCEL: PCH24KbpsEnabled parameter is set to enabled, the PCH transport channel is mapped to a dedicated S-CCPCH physical channel.

38

Nokia Siemens Networks

RN31577EN20GLA0

Transport Format Set


Transport Format Sets for the
8 kbps and 24 kbps PCH are very similar
8 kbps PCH 0: 0x80 bits (0 kbit/s) TFS 1: 1x80 bits (8 kbit/s) TTI Channel coding CRC 10 ms 1: 1x240 bits (24 kbit/s) 10 ms 24 kbps PCH 0: 0x240 bits (0 kbit/s)

Only difference is the


increased transport block size

CC 1/2

CC 1/2

16 bit

16 bits

39

Nokia Siemens Networks

RN31577EN20GLA0

S-CCPCH Configuration 1

This configuration limits the PCH bit rate to 8 kbps The PCH is multiplexed with the FACH-u and FACH-c The PCH always has priority SF64 is required to transfer the FACH-u and FACH-c bit rates

Logical channel

DTCH

DCCH

CCCH

BCCH

PCCH

Transport channel

FACH-u
U- user data

FACH-c
C- control data

PCH

Physical channel

SCCPCH 1 SF 64

40

Nokia Siemens Networks

RN31577EN20GLA0

S-CCPCH Configuration 2a

PCH24kbpsEnabled is configured to disabled with this configuration Limits the PCH bit rate to 8 kbps The PCH is allocated its own S-CCPCH SF256 is allocated to the PCH as a result of the low bit rate

Logical channel

DTCH

DCCH

CCCH

BCCH

PCCH

Transport channel

FACH-u

FACH-c

PCH

Physical channel

SCCPCH 1 SF 64

SCCPCH 2 SF 256

41

Nokia Siemens Networks

RN31577EN20GLA0

S-CCPCH Configuration 2b

PCH24kbpsEnabled is configured to enabled with this configuration Increases the PCH bit rate to 24 kbps The PCH is allocated its own S-CCPCH SF128 is allocated to the PCH to support the increased bit rate
RU 20

Logical channel

DTCH

DCCH

CCCH

BCCH

PCCH

Transport channel

FACH-u

FACH-c

PCH

Physical channel

SCCPCH 1 SF 64

SCCPCH 2 SF 128
24 kbps

42

Nokia Siemens Networks

RN31577EN20GLA0

S-CCPCH Configuration 3a

PCH24kbpsEnabled is configured to disabled with this configuration Limits the PCH bit rate to 8 kbps The PCH is allocated its own S-CCPCH SF256 is allocated to the PCH as a result of the low bit rate DTCH DCCH CCCH BCCH CTCH PCCH

Logical channel

Transport channel

FACH-u

FACH-c

FACH-c

FACH-s

PCH

Physical channel

SCCPCH connected SF 64

SCCPCH idle SF 128

SCCPCH page SF 256

43

Nokia Siemens Networks

RN31577EN20GLA0

S-CCPCH Configuration 3b

PCH24kbpsEnabled is configured to enabled with this configuration Increases the PCH bit rate to 24 kbps The PCH is allocated its own S-CCPCH SF128 is allocated to the PCH to support the increased bit rate DTCH DCCH CCCH BCCH CTCH PCCH

Logical channel

Transport channel

FACH-u

FACH-c

FACH-c

FACH-s

PCH

Physical channel

SCCPCH connected SF 64

SCCPCH idle SF 128

SCCPCH page SF 128

44

Nokia Siemens Networks

RN31577EN20GLA0

Code Allocation
Channelisation code for 24 kbps
PCH uses a larger section of the code tree
Cch,128,6 Cch,128,5

Cch,256,14

E-AGCH

HSDPA cannot use 15 HS-PDSCH


codes when HSUPA 2 ms TTI is enabled with 24 kbps PCH
Cch,128,4 Cch,16,0

E-HICH & E-RGCH HS-SCCH

Requirement for 2nd E-AGCH


code

Requirement for F-DPCH code


Cch,64,1

S-CCPCH 2 PICH AICH Cch,256,3 P-CCPCH CPICH

S-CCPCH 1

Cch,256,2 Cch,256,1 Cch,256,0

45

Nokia Siemens Networks

RN31577EN20GLA0

Paging and inter-RNC optimization


Paging Performance in 3G RU10

Thank You !

46

Nokia Siemens Networks

RN31577EN20GLA0