paging

3G RANOP RU20 Paging Paging and interinter- RNC optimizati optimization on

1

© Nokia Siemens Networks

RN31577EN20GLA0

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

2


RN31577EN20GLA0

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

2


RN31577EN20GLA0

Module Objectives

At th n able to:

f th m

l

will

Describe SRNC relocation issues Describe Paging Procedure & Performance

3


RN31577EN20GLA0

Paging and inter-RNC optimization Paging Performance in 3G - Paging Paging capacity capacity improve improvement ment R RU20 U20

4


RN31577EN20GLA0

Re-location (1/4) 3GPP options to use MM

SRNS relocation CN

Iu RNC

“SRNC anchorin ”

Iu RNC

RNC

Iur

RNC

CN

CN

CN

Iu Iur

Limited su ort of multi vendor services

S-RNC

Iu

Iu Iur

D-RNC

RNC

Iu Iur

RNC

Keep service as long as possible

SRNS Relocation, which is a standardised

5


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

RN31577EN20GLA0

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

Re-location (2/4) UE Mobilit Handlin 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 serv ces, ata serv ces an or data services in CELL_DCH state. In multivendor cases this will lead to limited functionality vendors RNS if the other vendor uses ”SRNC anchoring”

6


RN31577EN20GLA0

Re-location (3/4) Source and Tar et 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

•

7

In case of failures, Active failure counters are incremented both for RRC and RAB


RN31577EN20GLA0

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

8


RN31577EN20GLA0

Example of incoming Re-location (1/3) Incomin SRNC Relocation Source RNC

CN

SRNC Relocation Decision

Target RNC

MS

SRNS Relocation ,

RANAP:Relocation Required : e oca on

eques

CN

Setup phase: • RRC_CONN_STP_ATT • RRC_CONN_

RANAP:Relocation Request Ack

Iu

Iu

STP _FAIL_ RNC

SRNC

User plane set -up

Iur

RANAP:Relocation Command RNSAP:Relocation Commit

Access phase: SRNC operation started

• RRC_CONN_STP_CMP • RRC_CONN_

RANAP:Relocation Detect UP switching

ACC_FAIL_RNC

RRC:UTRAN Mobility Information RRC:UTRAN Mobility Information Confirm

RANAP:Relocation complete

Active phase:

RANAP:Iu Release

• RRC_CONN_ACC_CMP RANAP:Iu Release Complete

User plane release

9


RN31577EN20GLA0

DRNC

Example of incoming Re-location (2/3) Incomin 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


RN31577EN20GLA0

Example of incoming Re-location (3/3) Incomin SRNC Access Phase To evaluate the performance of the incoming SRNC relocation it’s possible to use the following KPI, both at RNC and cell level. RRC_CONN_STP_FAIL_RNC RRC_CONN_ACC_FAIL_RNC/RADIO For troubleshooting the M1009 family Counters is available. The table is called: “ ”.

Re location _ Failure _ Rate =

11


SRNC_RELOC_FAILS SRNC_RELOC_ATTS

RN31577EN20GLA0

Service Level table counters

Example of outgoing Re-location (1/3) Out oin SRNC Relocation Coming from active

Source RNC

Target RNC

CN

MS

SRNC Relocation Decision

SRNS Relocation ,

RANAP:Relocation Required

CN

RANAP:Relocation Request

to release

SRNC

User plane set-up

Iur

RANAP:Relocation Command

Active phase

Iu

Iu

RANAP:Relocation Request Ack

DRNC

RNSAP:Relocation Commit

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

User plane release

12


RN31577EN20GLA0

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

Example of outgoing Re-location (2/3) Out oin SRNC Relocation Counters for normal release are incremented: RRC_CONN_ACT_REL_SRNC RAB_ACT_REL_xxx_SRNC

13


RN31577EN20GLA0

Example of outgoing Re-location (3/3) RRC Connection Active failures As far as Source RNC any failure during the relocation rocedure is a failure durin the active hase and since it happens under cells of the target RNC those failures are mapped into Cell id 0 STOP WCELL I 0 0 0 0 STOP WCELL ID 0 0 0 0 0 0

14

UT FAIL SOURC rnc_internal_c

OUT REASON no_resp_from_rlc_c

Source RNC

UT DETAILED REASO fre uenc nok_c 62

2.09% 2.02% 0.17% . 0.10%

iu_c serv_req_nack_from_iuv_c radio_interface_c no_resp_from_rlc_c _ _ _ _ radio_interface_c radio_link_failure_c

subsystem_down_c default_c _ radio_conn_lost_c

UT FAIL SOURC rnc_internal_c iu_c radio_interface_c radio_interface_c radio_interface_c transmissio_c

UT DETAILED REASO frequency Percenatge nok_c 92 3.05% subsystem_down_c 70 2.32% default_c 9 0.30% radio_conn_lost_c 4 0.13% rrc_dir_sc_re_est_c 3 0.10% default_c 3 0.10%


OUT REASON no_resp_from_rlc_c serv_req_nack_from_iuv_c no_resp_from_rlc_c radio_link_failure_c timer_expired_c transport_res_rel_nrm_c

RN31577EN20GLA0

60 5

Percenta e

3

SRNC Relocation failure (1/2)

Impact of SRNC relocation failure in the Setup failure

IN REASON

OUT FAIL SOURCE

OUT REASON

frequency

Percentage

srnc_relocation_c

iu_c

no_resp_from_iuv_c

79

9.1%

srnc_relocation_c

rnc_internal_c

invalid_conf iguration_c

6

0.7%

srnc_relocation_c

iu_c

no_resp_from_iuv_c

3

0.3%

srnc_relocation_c

transmissio_c

serv_req_nack_from_nrm_c

2

0.2%

srnc_relocation_c

rnc_internal_c

serv_req_nack_from_r_rab_c

1

0.1%

Target RNC

Source RNC

Target RNC

CN

MS

SRNC Relocation Decision RANAP:Relocation Required RANAP:Relocation Request

RANAP:Relocation Request Ack User plane -upset

Setup phaseRRC_CONN_STP_F AIL_RNC

RANAP:Relocation Command RNSAP:Relocation Commit SRNC operation started

Access phase RRC_CONN_ACC_FAIL_ RRC:UTRAN Mobility Information RNC

RANAP:Relocation Detect UP switching

15

IN REASON

OUT FAIL SOURCE

OUT REASON

frequency

Percentage

srnc_relocation_c

iu_c

no_resp_from_iuv_c

76

23.6%

srnc_relocation_c _ _

transmissio_c _

serv_req_nack_from_nrm_c _ _ _ _ _

6

1.9%

srnc_relocation_c

iu_c

no_resp_from_iuv_c

5

1.6%

RANAP:Iu Release Complete

srnc_relocation_c

rnc_internal_c

serv_req_nack_from_r_rab_c

2

0.6%

User plane release

srnc_relocation_c

iu_c

serv_req_nack_from_iuv_c

2

0.6%

srnc_relocation_c

rnc_internal_c

invalid_configuration_c

2

0.6%


RN31577EN20GLA0

RRC:UTRAN Mobility Information Confirm RANAP:Relocation complete RANAP:Iu Release

Active phase

SRNC Relocation failure (2/2) No res onse from rlc-nok 017F-191 Incremented counters in the Source RNC RRC_CONN_ACT_FAIL_RNC RAB_ACT_FAIL_xxx_RNC

16


RN31577EN20GLA0

Paging and inter-RNC optimization

Thank You !

17


RN31577EN20GLA0

Paging and inter-RNC optimization - Cell resource states - Paging capacity improvement RU20

18


RN31577EN20GLA0

Paging Performance in 3G - RU10 UTRA RRC Connected Mode

UE in DRX mode

UE in DRX mode discontinous reception

NEW RU10:

discontinous rece tion

URA_PCH

CELL_PCH

via via Cell Cell UU date date/ Confirm

Common resources allocated (RACH-FACH)

Dedicated resources ,

CELL _ DCH

CELL _ FACH

Tx and Rx mode

Cell selection not implemented

Cell re-selection Listen to paging

19


RN31577EN20GLA0

Tx and Rx mode

Paging Performance in 3G RU10 The acket access rocedure in WCDMA should kee 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.

• • • •

ere are scenar os or pac et access: infrequent transmission of small packets frequent transmission of small packets and transm ss on o arge pac ets 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 . , CELL_DCH state. 20


RN31577EN20GLA0

Paging Performance in 3G RU10 Exam le: Transition from CELL _ DCH to CELL_ PCH If UE has Multi-RAB allocated (voice call & NRT PS call) & PS data inactivit detected in RNC L2 RNC tri ers reconfi uration 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 recon gure e connec on o e _ .

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_DCH

21


RN31577EN20GLA0

CELL_PCH

Paging Performance - processing • Periodic URA update (stationary UE)

• Paging response (DL data / signalling)

•

ccess

• Fast UE with L2 inactivity

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

UE)

• Periodic cell update (stationary UE)

•

aa

data/ signalling)

signalling)

• Data in GTP buffer

• Cell reselection (moving

URA_ PCH

• Activity supervision • Completion of Cell Update procedure

• UL Access (UL data/signalling)

Cell_

• Inactivity detection of NRT RB • Release of RT RB

• Completion of URA Update procedure • Max. # cell u dates in Cell_FACH / Cell_PCH exceeded

Cell_ DCH

Cell_ FACH

• Setup of RT/NRT RB • RAB reconfiguration • DCH Up or Downgrade • Bit rate reduction due to load reasons

RRC Connection

Idle Mode

• CN originated paging (MT Call) • Random Access (MO Call) 22


RN31577EN20GLA0

• UL/DL data or signalling • RT RB setup

Paging Performance Pa in lost: cell-PCH not active incremented only if the mobile is in cell-PCH ) s / t i b (

23


RN31577EN20GLA0

Paging Performance

A terminal, once registered to a network, has been allocated a paging group. or t e pag ng group t ere are ag ng n cators w c 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 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. 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 en uir to subscriber-B’s 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-B’s location area level. VLR will send paging command to relevant RNC’s (via Iu-CS interface), who are handling this LAC where subscriber–B is.

24


RN31577EN20GLA0

Paging Performance in 3G & S-CCPCH config.

In the case that a sin le S-CCPCH has been confi ured for a cell the TTI for the a in 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: • orwar ccess anne an • Paging Channel (PCH). In the current implementation (see 3GPP 25.331), the PCH has the priority on FACH so that . 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 a in rate is 100 a in /sec/cell.

25


RN31577EN20GLA0

Paging Performance in 3G & S-CCPCH config. Pa in buffer

ac e ongs o a pag ng group, accor ng o e ormu a Paging group = IMSI mod (DRX cycle length) The paging occasions for each paging group can be 10 ms

group served

group

group served

served

served

served

served

served

served

served

10ms * DRX cycle length

n case no u er ng s u ze , on y pag ng message re a e o eac pag ng group wou be served at the end of each period of 10 ms * DRX cycle length.

26


RN31577EN20GLA0

Paging Performance - Paging buffer In the current im lementation RAN04/RAN05 a buffer of 512 laces 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

busy

busy

busy

busy

10 ms * DRX cycle length

place 5

place 6

place 7

place 8

place 9

first empty place

NOTE: a paging can be buffered for M * DRX cycle length = 9 * 320 ms = 2.88 sec; this RNC (when cell-PCH is active). 27


RN31577EN20GLA0

Paging Performance in 3G PCH throu h ut: a in re uests blocked The number of transmitted pagings (on the radio interface) is: pag ng_requests pag ngs our =

_

ts

The number of paging attempts forwarded to be transmitted on PCH is: pag ng_ ype_ pag ngs our = PAGING_TYPE_1_ATT_RNC_ORIG

_

_ _

_

_

+

PAGING _TYPE_1_ATT_CN_ ORIG- indicates the no.of CN ori inated a in attem ts 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: pag ng_reques s_ oc e

28


pag ng our = pag ng_ ype_ - pag ng_reques s

RN31577EN20GLA0

PCH Loading – Estimation Process M1006C26 Paging Type 1 Att RNC Orig  all 0 if cell_PCH is not in use M1000C70 Ave PCH Throughput roug pu enom , , , , , cell basis, which is related to amount of Paging events.

29


RN31577EN20GLA0

PCH Loading – Estimation Process Air Interface

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 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

MaxAmountO fPagingType1 = max( M1006C25, among cells in the LA/RA) + max( M1006C26 , among cells in the LA/RA) PagingThroughput [bps] = MaxAmountO fPagingType1 ⋅ AveragePagingRecordS ize[bit ] ⋅ AveragePagingRecordS ize [bit ] = 80 MaxPagingT hroughput [bps] = 

=

 24000

PagingLoad [%] =

(# of SCCPCH = 2)

PagingThroughput [bps] MaxPagingT hroughput [bps]

This should on TB level 30


RN31577EN20GLA0

⋅

100

1 3600[sec]

PCH Loading – Estimation Process Statisticall “Pa in T e1” is enerated in the random manner b a lot of subscribers, except the special case like “Happy New Year call” Number of “Paging Type1” generated would form Poisson distribution Air Interface

Target PCH Load

Averaged # of simul. “Paging Type1”/sec

Poisson Distribution

“Paging Type1”=200bit

1 SCCPCH

8[kbps] Max PCH Throughput

100 Max “P.T.1”/sec

Failure Probability Acceptable?

YES

NO YES

2 SCCPCH

24[kbps]

300

Failure Probability Acceptable?

Divide LA/RA 31


RN31577EN20GLA0

OK

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" a nd PCH Loading Max PCH Throughput=8[kbps] / Size of Paging Type 1=80[bits] (Poisson Distribution)

] 100 [ y t i l 98 i b a b 96 o r P e v 94 i t a l u m 92 u C

90 0

10

20

30

40

50

60

70

80

90

100

110

120

130

140

# of Simultaneous "PagingType1" [count/sec]

PCHLoad=10%

PCHLoad=30%

PCHLoad=50%

PCHLoad=70%

PCHLoad=80%

max limit (SCCPCH=1)

Practical Max PCH Load = 70% = , . “ . ” . It would be good to have Practical Max PCH Load as 70% so that “simultaneous #P.T1/sec” is practically less than max(=100).

INCLUDE THE PAGING BUFFER HANDLING ASPECT 32


RN31577EN20GLA0

PCH Loading – Estimation Results Friday is the busiest day in the week except special events. Increase : 4[%] in 6[month] from 4[%] to 8[%]  0.67[%/month] . Air Interface PCH Load @18:00 2005/Jun/01~Dec/31 PCH Throughput=8[kbps] / PagingType1=80[bits] 9.000

0.67[%/month]

Fireworks @Yodo River

8.000 7.000

Tenjin Festival

] [ . d a 5.000 o L 4.000 H C 3.000 P

2.000 1.000 0.000 1 0 / 6 0 / 5

8 0 / 6 0 / 5

5 1 / 6 0 / 5

2 2 / 6 0 / 5

9 2 / 6 0 / 5

6 0 / 7 0 / 5

3 1 / 7 0 / 5

0 2 / 7 0 / 5

7 2 / 7 0 / 5

3 0 / 8 0 / 5

0 1 / 8 0 / 5

7 1 / 8 0 / 5

4 2 / 8 0 / 5

1 3 / 8 0 / 5

7 0 / 9 0 / 5

4 1 / 9 0 / 5

1 2 / 9 0 / 5

8 2 / 9 0 / 5

5 0 / 0 1 / 5

2 1 / 0 1 / 5

9 1 / 0 1 / 5

6 2 / 0 1 / 5

date RNC501 33


RN31577EN20GLA0

RNC509

RNC519

RNC510

2 0 / 1 1 / 5

9 0 / 1 1 / 5

6 1 / 1 1 / 5

3 2 / 1 1 / 5

0 3 / 1 1 / 5

7 0 / 2 1 / 5

4 1 / 2 1 / 5

1 2 / 2 1 / 5

8 2 / 2 1 / 5

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% oa s necessary ut st t  er o ca c ec o 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


RN31577EN20GLA0

Paging and inter-RNC optimization - Paging capacity improvement RU20 - Cell resource states - ag ng capac y mprovemen

35


RN31577EN20GLA0

Introduction (1/2) 

Cch,256,14

Paging load/activity

- 8 kbps paging channel capacity is -

- 24 kbps can be allocated for RU20 (ASW) - Transport block size increase - The stand alone 24kbps PCH is allocated on w , comparing 8 Kbps/SF256 (more PwR) - If Paging 24 kbps is used, maximum of available HSDPA codes are only14

Cch,128,6 Cch,128,5 E-HICH & E-RGCH No HSDPA code free

HS-SCCH Cch,128,4

Cch,16,0 S-CCPCH 2 PICH

Cch,64,1

Paging Ch with 24 kbps

AICH

• Bottleneck is PwR • Not code tree allocation Cch,256,3

(calculation on next slide)

S-CCPCH se up

Pilot coverage

S-CCPCH 1

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


RN31577EN20GLA0

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

P-CCPCH CPICH

Introduction (2/2) 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)

37


RN31577EN20GLA0

24 kbps Paging Channel Concept

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

Logical channel

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

Transport channel

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

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


RN31577EN20GLA0

Transport Format Set • Transport Format Sets for the 8 kbps and 24 kbps PCH are very similar

(0 kbit/s)

0: 0x240 bits (0 kbit/s)

1: 1x80 bits

1: 1x240 bits ts

TTI

10 ms

10 ms

Channel coding

CC 1/2

CC 1/2

CRC

16 bit

16 bits

increased transport block size


24 kbps PCH

TFS

• Only difference is the

39

8 kbps PCH

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 alwa s has riorit SF64 is required to transfer the FACH-u and FACH-c bit rates

Logical channel

Transport channel

DTCH

DCCH

FACH-u U- user data

CCCH

FACH-c C- control data

SCCPCH 1

Physical channel

SF 64 40


RN31577EN20GLA0

BCCH

PCCH

PCH

S-CCPCH Configuration 2a ps na e s con gure to sa e w t t s con gurat on • • 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

og ca c anne

Transport channel

FACH-u

FACH-c

SCCPCH 1

Physical channel

4 41


RN31577EN20GLA0

PCH

SCCPCH 2

S-CCPCH Configuration 2b ps na e s con gure to ena e w t t s con gurat on • • Increases the PCH bit rate to 24 kbps RU 20 • The PCH is allocated its own S-CCPCH • SF128 is allocated to the PCH to support the increased bit rate

og ca c anne

Transport channel

FACH-u

FACH-c

SCCPCH 1

Physical channel

4

PCH

SCCPCH 2 1 24 kbps

42


RN31577EN20GLA0

S-CCPCH Configuration 3a ps na e s con gure to sa e w t t s con gurat on • • 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

Transport channel

Physical channel

43


DTCH

DCCH

FACH-u

FACH-c

CCCH

BCCH

CTCH

PCCH

FACH-c

FACH-s

PCH

SCCPCH connected

SCCPCH idle

SCCPCH page

SF 64

SF 128

SF 256

RN31577EN20GLA0

S-CCPCH Configuration 3b ps na e s con gure to ena e w t t s con gurat on • • 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

Logical channel

Transport channel

Physical channel

44


DTCH

DCCH

FACH-u

FACH-c

CCCH

BCCH

CTCH

PCCH

FACH-c

FACH-s

PCH

SCCPCH connected

SCCPCH idle

SCCPCH page

SF 64

SF 128

SF 128

RN31577EN20GLA0

Code Allocation

Cch,256,14

• Channelisation code for 24 kbps

E-AGCH

PCH uses a larger section of the code tree

Cch,128,6 Cch,128,5

• HSDPA cannot use 15 HS-PDSCH

E-HICH & E-RGCH

codes when HSUPA 2 ms TTI is enabled with 24 kb s PCH

• Requirement for 2nd E-AGCH code

HS-SCCH Cch,128,4 Cch,16,0 S-CCPCH 2

-

PICH

Cch,64,1

AICH Cch,256,3 S-CCPCH 1

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

45


RN31577EN20GLA0

P-CCPCH CPICH

paging

Recommend Documents