paging

7/16/2019 paging

http://slidepdf.com/reader/full/paging-563384e536a43 1/46

3G RANOP RU20

Paging and inter- RNC optimization

1 © Nokia Siemens Networks RN31577EN20GLA0

7/16/2019 paging


Course Content

KPI overview

Air interface and neighbor optimizationCapacity & traffic optimization

Paging and inter-RNC optimization


7/16/2019 paging


Module Objectives

At th n f th m l will

able to:Describe SRNC relocation issues

Describe Paging Procedure & Performance


7/16/2019 paging



-

Paging Performance in 3G -

- Paging capacity improvement RU20


7/16/2019 paging


Re-location (1/4)

Limited su ort of

SRNS relocation “SRNC anchorin ”

3GPP options to 3GPP options to use MM use MM

multi vendor services

CN

Iu Iu

CNCN

Iu Iu

CN

Iu Iu

RNCRNCIur RNCRNC

IurD-RNCS-RNC

IurRNCRNC

Iur

Keep service

as long as possible

”SRNC Anchoring”which is not as such a standardisedmobility method, but which can beimplemented by applying an

SRNS Relocation,

which is a standardised

anchoring issupported in Nokia

SRNC only for CS RT


undefined set of standardisedfeatures

+ PS/NRT serviceswithin Cell_DCH

7/16/2019 paging


Re-location (2/4)

UE Mobilit Handlin in RAN

3GPP gives two different options to handle inter-RNCmobility in radio network

1. SRNS Relocation ,

2. ”SRNC Anchoring”

When neighbouring DRNC or CN do not supportrelocation, anchoring is supported in Nokia SRNC only for

serv ces, ata serv ces an ordata services in CELL_DCH state.

In multivendor cases this will lead to limited functionality

vendors RNS if the other vendor uses ”SRNC anchoring”


7/16/2019 paging


Source and Tar et RNC

Re-location (3/4)

Relocation procedure and failures are detected differently betweenSource 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 RRCand RAB

• In case of failures, Setup and Access failure counters areincremented 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

• In case of failures, Active failure counters are incremented bothfor RRC and RAB


7/16/2019 paging


Failure and Abnormal Release cause at Service Level

Re-location (4/4)

RRC setup and accesscounters are updated during

relocations. If the new RRCconnection is established orrelocated successfully and if

the UE, the RAB setup andaccess counters are updated

as well.


7/16/2019 paging


Example of incoming Re-location (1/3)

Incomin SRNC Relocation

MSTarget RNC

SRNC Relocation DecisionSRNC Relocation Decision

CN

RANAP:Relocation Required

Source RNC

SRNS Relocation ,

Setup phase:• RRC_CONN_STP_ATT

• RRC_CONN_

STP FAIL RNCRANAP:Relocation Request Ack

: e oca on equesCN

Iu Iu _ _

Access phase:

User plane set-up

RANAP:Relocation Command

RNSAP:Relocation Commit

DRNC

SRNC

Iur

• RRC_CONN_STP_CMP

• RRC_CONN_

ACC_FAIL_RNC

SRNC operationstarted

UP switching RRC:UTRAN Mobility Information

RANAP:Relocation Detect

Active phase:

• RRC_CONN_ACC_CMP

RANAP:Relocation complete

RRC:UTRAN Mobility Information Confirm

RANAP:Iu Release

RANAP:Iu Release Complete


User plane release

7/16/2019 paging


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 Attempts• SRNC_RELOC_ATTS

• RRC_CONN_STP_CMP

• RRC_CONN_ACC_CMP

complete

• and the relative RAB counters

After the Iu Relocation Complete message the active phase starts


7/16/2019 paging


Incomin SRNC Access Phase


To evaluate the performance of the incoming SRNC relocation it’s possibleto use the following KPI, both at RNC and cell level.

RRC_CONN_STP_FAIL_RNCRRC_CONN_ACC_FAIL_RNC/RADIO

For troubleshooting the M1009 family

Counters is available. The table is called:“ ” .

_ATTSSRNC_RELOC

_FAILSSRNC_RELOC__Re = RateFailurelocation Service Leveltable counters


7/16/2019 paging


Out oin SRNC Relocation

Example of outgoing Re-location (1/3)

SRNS Relocation ,

MSTarget RNCCN


Source RNC

SRNC Relocation Decision SRNC Relocation Decision Coming

from active

CN

Iu Iu

RANAP:Relocation Request

RANAP:Relocation Request Ack

to release

DRNC

SRNC

Iur

User plane set-up



Active

phase

started

UP switching RRC:UTRAN Mobility Information



From Source RNC pointof view the RRC is in theactive hase


RANAP:Iu Release


Releasephase


User plane release

7/16/2019 paging


Out oin SRNC Relocation


Counters for normal release areincremented:

RRC_CONN_ACT_REL_SRNC

RAB_ACT_REL_xxx_SRNC


7/16/2019 paging



RRC Connection Active failures

As far as Source RNC any failure during the relocationrocedure 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 UT FAIL SOURC OUT REASON UT DETAILED REASO fre uenc Percenta e

Source RNC

0 rnc_internal_c no_resp_from_rlc_c nok_c 62 2.09%

0 iu_c serv_req_nack_from_iuv_c subsystem_down_c 60 2.02%

0 radio_interface_c no_resp_from_rlc_c default_c 5 0.17%

STOP WCELL ID UT FAIL SOURC OUT REASON UT DETAILED REASO frequency Percenatge

0 rnc_internal_c no_resp_from_rlc_c nok_c 92 3.05%

_ _ _ _ _ .

0 radio_interface_c radio_link_failure_c radio_conn_lost_c 3 0.10%

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%

7/16/2019 paging


SRNC Relocation failure (1/2)

Impact of SRNC relocation failure in the Setup failureTarget RNC

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_configuration_c 6 0.7%

MSTarget RNC

SRNC Relocation Decision

CN


RANAP:Relocation Request

Source RNC


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% User plane set-up

RANAP:Relocation Request Ack



SetupphaseRRC_CONN_STP_FAIL_RNC

IN REASON OUT FAIL SOURCE OUT REASON frequency Percentage


srnc_relocation_c transmissio_c serv_req_nack_from_nrm_c 6 1.9%

SRNC operationstarted

UP switching


RRC:UTRAN Mobility Information



RANAP:Iu Release

Access phaseRRC_CONN_ACC_FAIL_ RNC

_ _ _ _ _ _ _ _

srnc_relocation_c iu_c no_resp_from_iuv_c 5 1.6%srnc_relocation_c rnc_internal_c serv_req_nack_from_r_rab_c 2 0.6%

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%


User plane release

Activephase


7/16/2019 paging


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


7/16/2019 paging



Thank You !


7/16/2019 paging



- Cell resource states

- Paging capacity improvement RU20


7/16/2019 paging


Paging Performance in 3G - RU10

UTRA RRC Connected ModeUE in DRX mode

UE in DRX mode

discontinous rece tion

URA_PCH CELL_PCH

discontinous reception

via Cell U datevia Cell U date /

NEW RU10:

CELL DCH CELL FACHDedicated resources

Common resources

allocated (RACH-FACH)

Tx and Rx mode

Confirm

Confirm

_ _ ,

Tx and Rx mode

not implementedCell selection

Cell re-selection

Listen to paging


7/16/2019 paging


The acket access rocedure in WCDMA should kee the interference caused to other users as small as

Paging Performance in 3G RU10

possible. Since there is no connection between the base station and the UE before the access procedure, initialaccess is not closed loop power controlled and thus the information transmitted during this period should be keptat 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 radioresources, it is reasonable to transmit infrequent and small NRT user data packets using common transportchannels without closed loop power control. Then the random access channel (RACH) in UL and the forwardaccess 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.

7/16/2019 paging


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) & PSdata inactivit detected in RNC L2 RNC tri ers reconfi uration

_ _

from Cell_DCH to Cell_PCH on voice call release. UE stays inCell_PCH until new data is available in UL or DL L2 buffers. Assoon as certain traffic volume threshold is met, RNC mayrecon gure e connec on o e _ .

Each UE in Cell-DCH or Cell_FACH substate is allocatedDMCU resources in RNC. In case of processing

shortage in DMCU units, RNC may move UE to Cell_PCHand release all DSP resources in RNC.

CELL_PCH

L3 signaling is RRC: Physical Channel Reconfiguration

CELL_DCH


7/16/2019 paging


Paging Performance - processing

• Cell reselection (moving

UE)

• Periodic cell update(stationary UE)

•

• Periodic URA update(stationary UE)

• Paging response (DLdata / signalling)

• Inactivity detectionduring last 20sec

• RNC L2 resources atlow level• Fast UE with L2 inactivity

data/ signalling)

• UL Access (ULdata/signalling)

• ccess a asignalling)

Cell_

• Activity supervision• Completion of Cell

Update procedureURA_ PCH• Data in GTP buffer

• Inactivity detectionof NRT RB

• Release of RT RB

• Completion of URA Update

procedure• Max. # cell u dates in

Cell_ FACH

Cell_FACH / Cell_PCHexceeded

Cell_ DCH

• Setup of RT/NRT RB

• RAB reconfiguration

• DCH Up or Downgrade

• Bit rate reduction due toload reasons

RRC Connection


IdleMode

• UL/DL data orsignalling

• RT RB setup

• CN originated paging (MT Call)

• Random Access (MO Call)

7/16/2019 paging


Pa in lost: cell-PCH not active

Paging Performance

incremented only if the mobileis in cell-PCH

( b i t / s )


7/16/2019 paging


Paging Performance

A terminal, once registered to a network, has been allocated a paginggroup. or t e pag ng group t ere are ag ng n cators w c

appear periodically on the Paging Indicator Channel (PICH) whenthere are paging messages for any of the terminals belonging to thatpaging group. Once a PI has been detected, the terminal decodes the

whether there was a paging message intended for it. The terminalmay also need to decode the PCH in case the PI reception indicateslow reliability of the decision.

procedure will took place. Paging type 1 can happen either due tomobile terminated call or mobile terminated SMS.

First step is to find out where subscriber-B (the called party) is. Thismeans 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 willknow subscriber-B’s location area level. VLR will send pagingcommand to relevant RNC’s (via Iu-CS interface), who are handling


this LAC where subscriber–B is.

7/16/2019 paging


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 intransport 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, themaximum a in rate is 100 a in /sec/cell.


7/16/2019 paging


Pa in buffer

Paging Performance in 3G & S-CCPCH config.

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

served

served

served

group

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 woube served at the end of each period of 10 ms * DRX cycle length.


7/16/2019 paging


Paging Performance - Paging buffer

In the current im lementation RAN04/RAN05 a buffer of 512 laces stores thepaging messages. When a new paging message arrives and the next pagingoccasion is already occupied, the paging message is stored in the first free pagingoccasion 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 lengthWith 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.

busy

place 1 place 2 place 3 place 4 place 5 place 6 place 7 place 8 place 9

busy busy busy

10 ms * DRX cycle length 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).

7/16/2019 paging


PCH throu h ut: a in re uests blocked

Paging Performance in 3G

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 tomobiles 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 pag ng our = pag ng_ ype_ - pag ng_reques s

7/16/2019 paging


PCH Loading – Estimation Process

M1006C26 Paging Type 1 Att RNC Orig all 0 if cell_PCH is not inuse

M1000C70 Ave PCH Throughput

roug pu enom

, , , , ,cell basis, which is related to amount of Paging events.


7/16/2019 paging



M1006C25&C26 gives the hourly(or daily) basis number of “PagingType1” transmitted from CN per cell

Since the counter values are sometimes slightly different on cell basis, the

Air Interface

analysis

Average Paging Record size (=80[bit]) is the figure in RLC level (seems tobe pretty ok currently)

Max Paging Throughput is also in the same layer so that Paging Load canbe calculated with using those values

)max(),max( += LA/RAtheincellsamong , M1006C26 LA/RAtheincellsamong M1006C25e1 fPagingTyp MaxAmountO

80][

[sec]3600

1][[bps]

=

⋅⋅=

bit izeingRecordS AveragePag

bit izeingRecordS AveragePage1 fPagingTyp MaxAmountOughput PagingThro

100][

][[%]

)2(24000][

⋅=

=

==

bpshroughput MaxPagingT

bpsughput PagingThro PagingLoad

SCCPCH of # bpshroughput MaxPagingT


This should on TB level

7/16/2019 paging



Statisticall “Pa in T e1” is enerated in the random manner b a lot ofsubscribers, except the special case like “Happy New Year call”

Number of “Paging Type1” generated would form Poisson distribution

Air Interface

Target PCHLoad

Averaged # of simul. “Paging Type1”/sec Poisson Distribution

“Paging Type1”=200bit

Max “P.T.1”/secMax PCH Throughput

1 SCCPCH 8[kbps] 100Failure Probability

Acceptable?OK

NO

YES

2 SCCPCH 24[kbps] 300Failure Probability

Acceptable?

YES


Divide LA/RA

7/16/2019 paging


PCH Loading – Cumulative Poisson Distribution

Air Interface

Relation between Probability of Simultaneous "Paging Type1" and PCH Loading

Max PCH Throughput=8[kbps] / Size of Paging Type 1=80[bits]

(Poisson Distribution)

100

]

2005/Dec/31 23:00 @RNC510No need to have 2 SCCPCH

nor LA/RA division

94

96

98

l a t i v e P r o b a

b i l i t y [

90

92

0 10 20 30 40 50 60 70 80 90 100 110 120 130 140

# of Simultaneous "PagingType1" [count/sec]

C u m u

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

7/16/2019 paging


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]

7.000

8.000

9.000

] Tenjin Festival

Fireworks@Yodo River

0.67[%/month]

2.000

3.000

4.000

5.000

.

P C H L o a d [

0.0001.000

5 / 0 6 / 0 1

5 / 0 6 / 0 8

5 / 0 6 / 1 5

5 / 0 6 / 2 2

5 / 0 6 / 2 9

5 / 0 7 / 0 6

5 / 0 7 / 1 3

5 / 0 7 / 2 0

5 / 0 7 / 2 7

5 / 0 8 / 0 3

5 / 0 8 / 1 0

5 / 0 8 / 1 7

5 / 0 8 / 2 4

5 / 0 8 / 3 1

5 / 0 9 / 0 7

5 / 0 9 / 1 4

5 / 0 9 / 2 1

5 / 0 9 / 2 8

5 / 1 0 / 0 5

5 / 1 0 / 1 2

5 / 1 0 / 1 9

5 / 1 0 / 2 6

5 / 1 1 / 0 2

5 / 1 1 / 0 9

5 / 1 1 / 1 6

5 / 1 1 / 2 3

5 / 1 1 / 3 0

5 / 1 2 / 0 7

5 / 1 2 / 1 4

5 / 1 2 / 2 1

5 / 1 2 / 2 8


date

RNC501 RNC509 RNC519 RNC510

PCH L di C l i

7/16/2019 paging


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%

er o ca c ec o oa s necessary ut st t

will not reach the max.

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


P i d i t RNC ti i ti

7/16/2019 paging



- Paging capacity improvement RU20- Cell resource states

- ag ng capac y mprovemen


7/16/2019 paging


Introduction (1/2)

Paging load/activity

- 8 kbps paging channel capacity is

Cch,256,14

- 24 kbps can be allocated for RU20 (ASW)

- Transport block size increase

- The stand alone 24kbps PCH is allocated on

Cch,128,5

-

E-HICH & E-RGCH

Cch,128,6

- w ,

comparing 8 Kbps/SF256 (more PwR)

- If Paging 24 kbps is used,

maximum of available HSDPA codes are

Cch,128,4

HS-SCCH

Cch,16,0

No HSDPA code free No HSDPA code free

only14

AICH

PICHCch,64,1

S-CCPCH 2

Paging Ch with 24 kbps Paging Ch with 24 kbps

•• Bottleneck is PwR Bottleneck is PwR

Cch,256,2

Cch,256,3

CPICH

P-CCPCH

S-CCPCH 1Pilot coverage

S-CCPCH

•• Not code tree allocation Not code tree allocation (calculation on next slide) (calculation on next slide)


WCEL: PtxSCCPCH1It carries a PCH or FACH (mux) or FACH

/dedicated). Spreading factor is SF64 (60 kbps)

Cch,256,0

Cch,256,1se up

7/16/2019 paging


Introduction (2/2)

Example: Power benchmark Example: Power benchmark

What limits first: PwR or Code tree occupation

Average HSDPA throughput hardly affected by loss of 1 code, as CQI extremely seldomgood 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/260kbps/24kbps, cc. 1/2

With SF256 PCH (8kbps) needs power 5 dB below CPICH = 28 dBm = 0.63 Watt

30kbps/8kbps cc.1/230kbps/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)


24 kbps Paging Channel

7/16/2019 paging


Concept

24 kbps Paging Channel

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

Logical channel

Transport channel

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

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

SeveralSeveral

channelIf WCEL: PCH24KbpsEnabled parameter is set to “enabled”, the PCH transportchannel is mapped to a dedicated S-CCPCH physical channel.

SCCPCH

SS--CCPCH possibleCCPCH possible


Transport Format Set

7/16/2019 paging


Transport Format Set

• Transport Format Sets for the8 kbps and 24 kbps PCH are

8 kbps PCH 24 kbps PCH

0: 0x240 bitsvery similar

• Only difference is theincreased transport block

TFS

(0 kbit/s)

1: 1x80 bits

(0 kbit/s)

1: 1x240 bits size

TTI

t s

10 ms 10 ms

Channelcoding

CC 1/2 CC 1/2

CRC 16 bit 16 bits


7/16/2019 paging


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 DTCH DCCH CCCH BCCH PCCH

Transport channel FACH-u FACH-c PCH

UU-- user datauser data CC-- control datacontrol data

Physical channel SCCPCH 1


SF 64

7/16/2019 paging


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


Physical channel SCCPCH 1 SCCPCH 2


4

S CCPCH C fi ti 2b

7/16/2019 paging


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

• SF128 is allocated to the PCH to support the increased bit rate

og ca c anne


Physical channel SCCPCH 1 SCCPCH 2


4 1

24 kbps24 kbps

S CCPCH C fi i 3

7/16/2019 paging


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


• SF256 is allocated to the PCH as a result of the low bit rate

Logical channel DTCH DCCH CCCH BCCH CTCH PCCH

Transport channel FACH-u PCHFACH-sFACH-c FACH-c

Physical channel SCCPCHconnected

SCCPCHidle

SCCPCHpage


SF 64 SF 128 SF 256

S CCPCH C fi ti 3b

7/16/2019 paging


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


• SF128 is allocated to the PCH to support the increased bit rate

Logical channel DTCH DCCH CCCH BCCH CTCH PCCH

Transport channel FACH-u PCHFACH-sFACH-c FACH-c

Physical channel SCCPCHconnected

SCCPCHidle

SCCPCHpage


SF 64 SF 128 SF 128

C

7/16/2019 paging


Code Allocation Cch,256,14

• Channelisation code for 24 kbpsPCH uses a larger section of thecode tree Cch,128,5

E-AGCH

Cch,128,6

• HSDPA cannot use 15 HS-PDSCHcodes when HSUPA 2 ms TTI isenabled with 24 kb s PCH HS-SCCH

E-HICH & E-RGCH

• Requirement for 2nd E-AGCHcode

Cch,128,4

S-CCPCH 2

Cch,16,0

-

AICH

PICHCch,64,1

Cch,256,2

Cch,256,3

CPICH

P-CCPCH

S-CCPCH 1

45 © Nokia Siemens Networks RN31577EN20GLA0 Cch,256,0

Cch,256,1


7/16/2019 paging



Thank You !


Documents

paging