8/10/2019 06_Paging.pdf
1/46
3G RANOP RU20
Soc Classification level
1 Nokia Siemens Networks Presentation / Author / Date
Module 6 Paging and inter- RNC optimization
8/10/2019 06_Paging.pdf
2/46
Course Content
KPI overview
Performance monitoring
Air interface and neighbor optimizationCapacity & traffic optimization
Paging and inter-RNC optimization
Soc Classification level
2 Nokia Siemens Networks Presentation / Author / Date
8/10/2019 06_Paging.pdf
3/46
Module Objectives
At the end of the module you will be
able to:Describe SRNC relocation issues
Describe Paging Procedure & Performance
Soc Classification level
3 Nokia Siemens Networks Presentation / Author / Date
8/10/2019 06_Paging.pdf
4/46
Paging and inter-RNC optimization
Re-location
Paging Performance in 3G- Cell resource states
- Paging capacity improvement RU20
Soc Classification level
4 Nokia Siemens Networks Presentation / Author / Date
8/10/2019 06_Paging.pdf
5/46
CN
RNCRNC
Iu Iu
Iur
CN
RNCRNC
Iu Iu
CN
D-RNCS-RNC
Iu Iu
Iur
CN
RNCRNC
Iu Iu
Iur
SRNS relocation SRNC anchoring
Re-location (1/4)
UE Mobility Handling in RAN3GPP options to3GPP options to
use MMuse MM
Limited support ofmulti vendor services
Soc Classification level
5 Nokia Siemens Networks Presentation / Author / Date
SRNC Anchoring
which is not as such a standardisedmobility method, but which can beimplemented by applying anundefined set of standardised
features
SRNS Relocation,
which is a standardisedmobility method
anchoring issupported in Nokia
SRNC only for CS RT+ PS/NRT services
within Cell_DCH
Keep service
as long as possible
8/10/2019 06_Paging.pdf
6/46
3GPP gives two different options to handle inter-RNCmobility in radio network
1. SRNS Relocation,2. SRNC Anchoring
Re-location (2/4)
UE Mobility Handling in RAN
Soc Classification level
6 Nokia Siemens Networks Presentation / Author / Date
relocation, anchoring is supported in Nokia SRNC only forCS RT services, PS RT data services and for PS NRTdata services in CELL_DCH state.
In multivendor cases this will lead to limited functionality
related to mobility over RNC border between differentvendors RNS if the other vendor uses SRNC anchoring
8/10/2019 06_Paging.pdf
7/46
Source and Target RNCRelocation 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 are
Re-location (3/4)
Soc Classification level
7 Nokia Siemens Networks Presentation / Author / Date
ncremen e o or an
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
8/10/2019 06_Paging.pdf
8/46
Failure and Abnormal Release cause at Service Level
RRC setup and accesscounters are updated duringincoming handovers andrelocations. If the new RRCconnection is established orrelocated successfully and ifthere are RAB connections forthe UE, the RAB setup and
Re-location (4/4)
Soc Classification level
8 Nokia Siemens Networks Presentation / Author / Date
as well.
8/10/2019 06_Paging.pdf
9/46
Setup phase:
RRC_CONN_STP_ATT
RRC_CONN_
STP_FAIL_RNC
MSTarget RNC
SRNC Relocation DecisionSRNC Relocation Decision
CN
User plane set-up
RANAP:Relocation Required
RANAP:Relocation Request Ack
RANAP:Relocation Command
Source RNC
RANAP:Relocation Request
Example of incoming Re-location (1/3)
CN
DRNC
SRNC
Iu Iu
Iur
SRNS Relocation,
Incoming SRNC Relocation
Soc Classification level
9 Nokia Siemens Networks Presentation / Author / Date
Access phase:
RRC_CONN_STP_CMP
RRC_CONN_
ACC_FAIL_RNC
Active phase:
RRC_CONN_ACC_CMP
SRNC operationstarted
UP switching
RANAP:Relocation complete
RRC:UTRAN Mobility Information
RNSAP:Relocation Commit
RANAP:Relocation Detect
RRC:UTRAN Mobility Information Confirm
RANAP:Iu Release
RANAP:Iu Release Complete
User plane release
8/10/2019 06_Paging.pdf
10/46
Incoming SRNCIf incoming inter-rnc sho is followed by a relocation, the establishment cause in theTarget 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
After the Iu Relocation Com lete messa e the active hase starts
Example of incoming Re-location (2/3)
complete
Attempts
Soc Classification level
10 Nokia Siemens Networks Presentation / Author / Date
8/10/2019 06_Paging.pdf
11/46
Incoming SRNC Access PhaseTo evaluate the performance of the incoming SRNC relocation its possibleto use the following KPI, both at RNC and cell level.
Failures are between the Relocation Request and the Relocation Complete:
RRC_CONN_STP_FAIL_RNCRRC_CONN_ACC_FAIL_RNC/RADIO
For troubleshooting the M1009 family
Example of incoming Re-location (3/3)
Soc Classification level
11 Nokia Siemens Networks Presentation / Author / Date
Counters is available. The table is called:L3 Relocation signalling measurement.
_ATTSSRNC_RELOC
_FAILSSRNC_RELOC__Re =RateFailurelocation Service Level
table counters
8/10/2019 06_Paging.pdf
12/46
CN
DRNC
SRNC
Iu Iu
Iur
SRNS Relocation,
Outgoing SRNC Relocation
Example of outgoing Re-location (1/3)
MSTarget RNCCN
User plane set-up
RANAP:Relocation Required
RANAP:Relocation Request
RANAP:Relocation Request Ack
RANAP:Relocation Command
Source RNC
SRNC Relocation DecisionSRNC Relocation DecisionComing
from activeand moveto release
Soc Classification level
12 Nokia Siemens Networks Presentation / Author / Date
From Source RNC pointof view the RRC is in theactive phase
SRNC operationstarted
UP switching
RANAP:Relocation complete
RRC:UTRAN Mobility Information
RNSAP:Relocation Commit
RANAP:Relocation Detect
RRC:UTRAN Mobility Information Confirm
RANAP:Iu Release
RANAP:Iu Release Complete
User plane release
ct ve
phase
Releasephase
8/10/2019 06_Paging.pdf
13/46
Counters for normal release areincremented:
RRC_CONN_ACT_REL_SRNC
RAB_ACT_REL_xxx_SRNC
Outgoing SRNC Relocation
Example of outgoing Re-location (2/3)
Soc Classification level
13 Nokia Siemens Networks Presentation / Author / Date
8/10/2019 06_Paging.pdf
14/46
From ticket collectionRRC Connection Active failures
As far as Source RNC any failure during the relocationprocedure is a failure during the active phase and since ithappens under cells of the target RNC those failures are
mapped into Cell id 0
STOP WCELL ID UT FAIL SOURC OUT REASON UT DETAILED REASO frequency Percentage
0 rnc_internal_c no_resp_from_rlc_c nok_c 62 2.09%
Source RNC
Example of outgoing Re-location (3/3)
Soc Classification level
14 Nokia Siemens Networks Presentation / Author / Date
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 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%
_ _ _ _ _ _ _ _ .
0 radio_interface_c no_resp_from_rlc_c default_c 5 0.17%0 iur_c iur_connection_lost_c default_c 3 0.10%
0 radio_interface_c radio_link_failure_c radio_conn_lost_c 3 0.10%
8/10/2019 06_Paging.pdf
15/46
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 OUT FAIL SOURCE OUT REASON frequency Percentage
srnc_relocation_c iu_c no_resp_from_iuv_c 79 9.1%
srnc_relocat ion_c rnc_internal_c invalid_configuration_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%
MSTarget RNC
SRNC Relocation Decision
CN
RANAP:Relocation Required
RANAP:Relocation Request
RANAP:Relocation Request Ack
Source RNC
SetupphaseRRC_CONN_STP_F
Target RNC
Soc Classification level
15 Nokia Siemens Networks Presentation / Author / Date
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%
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%
srnc_re oca on_c rnc_ n erna_c serv_req_nac _ rom_r_ra _c .
SRNC operationstarted
UP switching
User plane set-up
RANAP:Relocation complete
RRC:UTRAN Mobility Information
RANAP:Relocation Command
RNSAP:Relocation Commit
RANAP:Relocation Detect
RRC:UTRAN Mobility Information Confirm
RANAP:Iu Release
RANAP:Iu Release Complete
User plane release
_
Access phaseRRC_CONN_ACC_FAIL_RNC
Activephase
Analysis done using PMI Ticket
8/10/2019 06_Paging.pdf
16/46
SRNC Relocation failure (2/2)
Incremented counters in the
Source RNC
RRC_CONN_ACT_FAIL_RNC
RAB_ACT_FAIL_xxx_RNC
No response from rlc-nok (017F-191)
Soc Classification level
16 Nokia Siemens Networks Presentation / Author / Date
8/10/2019 06_Paging.pdf
17/46
SRNC relocation
Paging and inter-RNC optimization
Soc Classification level
17 Nokia Siemens Networks Presentation / Author / Date
8/10/2019 06_Paging.pdf
18/46
Paging and inter-RNC optimization
Paging Performance in 3G- Cell resource states
- Paging capacity improvement RU20
Soc Classification level
18 Nokia Siemens Networks Presentation / Author / Date
8/10/2019 06_Paging.pdf
19/46
Paging Performance in 3G - RU10
URA_PCH CELL_PCH
UTRA RRC Connected ModeUE in DRX mode
discontinous reception
UE in DRX mode
discontinous reception
Common resources
via Cell UpdateConfirm
via Cell Update /Confirm
NEW RU10:
RRC States
Soc Classification level
19 Nokia Siemens Networks Presentation / Author / Date
CELL_DCH CELL_FACH
Idle Mode
not implemented
Dedicated resourcesallocated (DCH, HS)
Tx and Rx mode
allocated (RACH-FACH)
Tx and Rx mode
Cell selection
Cell re-selection
Listen to paging
8/10/2019 06_Paging.pdf
20/46
The packet access procedure in WCDMA should keep the interference caused to other users as small aspossible. 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.
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 erformed usin common shared or
Paging Performance in 3G RU10
Soc Classification level
20 Nokia Siemens Networks Presentation / Author / Date
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(DCH). When the packet data is performed on shared or dedicated channels, the UE is inCELL_DCH state.
8/10/2019 06_Paging.pdf
21/46
Paging Performance in 3G RU10
If UE has Multi-RAB allocated (voice call & NRT PS call) & PSdata inactivity detected in RNC L2, RNC triggers reconfigurationfrom 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. Assoon as certain traffic volume threshold is met, RNC mayreconfigure the connection to Cell_DCH.
Example: Transition from CELL_DCH to CELL_PCH
Soc Classification level
21 Nokia Siemens Networks Presentation / Author / Date
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.
L3 signaling is RRC: Physical Channel Reconfiguration
CELL_DCH
CELL_PCH
8/10/2019 06_Paging.pdf
22/46
Paging Performance - processing
Cell reselection (movingUE)
Periodic cell update(stationary UE)
Paging response (DLdata/ signalling)
UL Access (ULdata/signalling)
URA reselection Periodic URA update
(stationary UE)
Paging response (DLdata / signalling)
UL Access (UL data /signalling)
Cell_PCH
Activity supervision Completion of Cell
Update procedureURA_PCH
Inactivity detectionduring last 20sec
RNC L2 resources atlow level Fast UE with L2 inactivity
Data in GTP buffer
Soc Classification level
22 Nokia Siemens Networks Presentation / Author / Date
Idle
Mode
Cell_FACH
of NRT RB
Release of RT RB
Setup of RT/NRT RB RAB reconfiguration
DCH Up or Downgrade
Bit rate reduction due toload reasons
omp e on o p a e
procedure Max. # cell updates in
Cell_FACH / Cell_PCHexceeded
UL/DL data or
signalling RT RB setup
RRC ConnectionRelease
Cell_DCH
CN originated paging (MT Call)
Random Access (MO Call)
8/10/2019 06_Paging.pdf
23/46
Paging lost: cell-PCH not active
(bit/s)
incremented only if the mobileis in cell-PCH
Paging Performance
Soc Classification level
23 Nokia Siemens Networks Presentation / Author / Date
8/10/2019 06_Paging.pdf
24/46
Paging Performance
A terminal, once registered to a network, has been allocated a paginggroup. For the paging group there are Paging Indicators (PI) whichappear 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 thenext PCH frame transmitted on the Secondary CCPCH to seewhether there was a paging message intended for it. The terminalma also need to decode the PCH in case the PI rece tion indicates
Paging Blocking
Soc Classification level
24 Nokia Siemens Networks Presentation / Author / Date
low reliability of the decision.
If network would like to contact into certain user (SIM card) a pagingprocedure 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 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 willknow subscriber-Bs location area level. VLR will send pagingcommand to relevant RNCs (via Iu-CS interface), who are handlingthis LAC where subscriberB is.
8/10/2019 06_Paging.pdf
25/46
Paging Performance in 3G & S-CCPCH config.
In the case that a single S-CCPCH has been configured for a cell, the TTI for the pagingtransport 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
Pa in Channel PCH .
Paging Blocking
Soc Classification level
25 Nokia Siemens Networks Presentation / Author / Date
In the current implementation (see 3GPP 25.331), the PCH has the priority on FACH so thatFACH 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, themaximum paging rate is 100 paging/sec/cell.
8/10/2019 06_Paging.pdf
26/46
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
Paging Performance in 3G & S-CCPCH config.
Soc Classification level
26 Nokia Siemens Networks Presentation / Author / Date
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 wouldbe served at the end of each period of 10 ms * DRX cycle length.
8/10/2019 06_Paging.pdf
27/46
Paging Performance - Paging buffer
In the current implementation (RAN04/RAN05), a buffer of 512 places 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.
Soc Classification level
27 Nokia Siemens Networks Presentation / Author / Date
interested by the paging message.
10 ms * DRX cycle length
busy
place 1 place 2 place 3 place 4 place 5 place 6 place 7 place 8 place 9
busy busy busy
first empty place
NOTE: a paging can be buffered for M * DRX cycle length = 9 * 320 ms = 2.88 sec; thistime is shorter than the repetition time in CN but could be higher than the repetition time inRNC (when cell-PCH is active).
8/10/2019 06_Paging.pdf
28/46
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 Performance in 3G
Soc Classification level
28 Nokia Siemens Networks Presentation / Author / Date
PAGING_TYPE_1_ATT_CN_ORIG- indicates the no.of CN originated paging attempts to mobilesin 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:
paging_requests_blocked [paging/hour] = paging_type_1 - paging_requests
PCH L di E i i P
8/10/2019 06_Paging.pdf
29/46
PCH Loading Estimation Process
M1006C25 Paging Type 1 Att CN OrigM1006C26 Paging Type 1 Att RNC Orig all 0 if cell_PCH is not inuse
M1000C70 Ave PCH Throughput
M1000C71 PCH Throughput Denom 0
Soc Classification level
29 Nokia Siemens Networks Presentation / Author / Date
M1001C32,34,36,38,52,56&60 indicate the amount of MTC events incell basis, which is related to amount of Paging events.
PCH L di E i i P
8/10/2019 06_Paging.pdf
30/46
PCH Loading Estimation Process
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, themaximum counter value over all the cells in the LA/RA is used in thisanalysis
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 usin those values
Air Interface
Soc Classification level
30 Nokia Siemens Networks Presentation / Author / Date
100][
][[%]
)2(24000
)1(8000][
80][
[sec]3600
1][[bps]
)max(),max(
=
=
=
=
=
=
+=
bpshroughputMaxPagingT
bpsughputPagingThroPagingLoad
SCCPCHof#
SCCPCHof#bpshroughputMaxPagingT
bitizeingRecordSAveragePag
bitizeingRecordSAveragePage1fPagingTypMaxAmountOughputPagingThro
LA/RAtheincellsamong,M1006C26LA/RAtheincellsamongM1006C25e1fPagingTypMaxAmountO
This should on TB level
PCH L di E ti ti P
8/10/2019 06_Paging.pdf
31/46
PCH Loading Estimation Process
Statistically, Paging Type1 is generated in the random manner by a lot ofsubscribers, except the special case like Happy New Year call
Number of Paging Type1 generated would form Poisson distribution
Through the below flow
Target PCH Averaged # of simul. Paging Type1/sec Poisson Distribution
Air Interface
Soc Classification level
31 Nokia Siemens Networks Presentation / Author / Date
Max P.T.1/secMax PCH Throughput
2 SCCPCH
1 SCCPCH 8[kbps]
24[kbps]
100
300
Paging Type1=200bit
Failure ProbabilityAcceptable?
Failure ProbabilityAcceptable?
OK
NO
YES
Divide LA/RA
YES
NO
PCH L di C l ti P i Di t ib ti
8/10/2019 06_Paging.pdf
32/46
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)
90
92
94
96
98
100
CumulativeProba
bility[%]
2005/Dec/31 23:00 @RNC510No need to have 2 SCCPCH
nor LA/RA division
Soc Classification level
32 Nokia Siemens Networks Presentation / Author / Date
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)
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 NOTINCLUDE THE PAGING BUFFER HANDLING ASPECT
Practical Max PCH Load = 70%
PCH Loading Estimation Results
8/10/2019 06_Paging.pdf
33/46
PCH Loading Estimation Results
Air Interface
PCH Load @18:00
2005/Jun/01~Dec/31
PCH Throughput=8[kbps] / PagingType1=80[bits]9.000
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.
Fireworks
0.67[%/month]
Soc Classification level
33 Nokia Siemens Networks Presentation / Author / Date
0.0001.000
2.000
3.000
4.000
5.000
6.0007.000
8.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
date
PCHLoad[%]
RNC501 RNC509 RNC519 RNC510
Tenjin Festival
o o ver
PCH Loading Conclusions
8/10/2019 06_Paging.pdf
34/46
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.
Soc Classification level
34 Nokia Siemens Networks Presentation / Author / Date
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.
Paging and inter RNC optimization
8/10/2019 06_Paging.pdf
35/46
Paging and inter-RNC optimization
Paging Performance in 3G- Paging capacity improvement RU20- Cell resource states
- Paging capacity improvement RU20
Soc Classification level
35 Nokia Siemens Networks Presentation / Author / Date
8/10/2019 06_Paging.pdf
36/46
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)
Cch,128,5
Cch,256,14
E-AGCH
HS-SCCH
E-HICH & E-RGCH
Cch,128,6
No HSDPA code freeNo HSDPA code free
Soc Classification level
36 Nokia Siemens Networks Presentation / Author / Date
- If Paging 24 kbps is used,
maximum of available HSDPA codes areonly14
WCEL: PtxSCCPCH1
It carries a PCH or FACH (mux) or FACH/dedicated). Spreading factor is SF64 (60 kbps) Cch,256,0
Cch,256,1
Cch,256,2
Cch,256,3
Cch,128,4
CPICH
P-CCPCH
AICH
PICHCch,64,1
S-CCPCH 1
S-CCPCH 2
Cch,16,0
Pilot coverageS-CCPCHsetup
Paging Ch with 24 kbpsPaging Ch with 24 kbps
Bottleneck is PwRBottleneck is PwR
Not code tree allocationNot code tree allocation
(calculation on next slide)(calculation on next slide)
8/10/2019 06_Paging.pdf
37/46
Introduction (2/2)
Example: Power benchmarkExample: 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 24kb s needs ower 2 dB below CPICH = 31 dBm = 1.26 Watt
8/24 kbps Paging Channel
Soc Classification level
37 Nokia Siemens Networks Presentation / Author / Date
With SF256 PCH (8kbps) needs power 5 dB below CPICH = 28 dBm = 0.63 Watt
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
60kbps/24kbps, cc. 1/260kbps/24kbps, cc. 1/2
30kbps/8kbps cc.1/230kbps/8kbps cc.1/2
24 kbps Paging Channel
8/10/2019 06_Paging.pdf
38/46
Logical channel
PCCH
To support higher paging capacity, the size of transport block for PCH is increased:
8 kb s = 80 Bit / 10ms TTI default
Concept
24 kbps Paging Channel
8 kbps = up to 508 kbps = up to 50--75% PCH load75% PCH load
Soc Classification level
38 Nokia Siemens Networks Presentation / Author / Date
Transport channel
Physicalchannel
If WCEL: PCH24KbpsEnabled parameter is set to enabled, the PCH transportchannel is mapped to a dedicated S-CCPCH physical channel.
PCH
SCCPCH
24 kbps = 240 Bit / 10ms TTI (optional)
SeveralSeveral
SS--CCPCH possibleCCPCH possible
Transport Format Set
8/10/2019 06_Paging.pdf
39/46
Transport Format Set
Transport Format Sets for the8 kbps and 24 kbps PCH arevery similar
Only difference is theincreased transport blocksize
TFS
8 kbps PCH 24 kbps PCH
0: 0x80 bits(0 kbit/s)
1: 1x80 bits(8 kbit/s)
0: 0x240 bits(0 kbit/s)
1: 1x240 bits(24 kbit/s)
Soc Classification level
39 Nokia Siemens Networks Presentation / Author / Date
TTI
Channelcoding
CRC
10 ms
CC 1/2
16 bit
10 ms
CC 1/2
16 bits
S CCPCH C fi ti 1
8/10/2019 06_Paging.pdf
40/46
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
Soc Classification level
40 Nokia Siemens Networks Presentation / Author / Date
Transport channel
Physical channel
FACH-u FACH-c PCH
SCCPCH 1
SF 64
UU-- user datauser data CC-- control datacontrol data
S CCPCH C fi ti 2
8/10/2019 06_Paging.pdf
41/46
S-CCPCH Configuration 2a
Logical channel DTCH DCCH CCCH BCCH PCCH
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
Soc Classification level
41 Nokia Siemens Networks Presentation / Author / Date
Transport channel
Physical channel
FACH-u FACH-c PCH
SCCPCH 1 SCCPCH 2
SF 64 SF 256
S CCPCH Configuration 2b
8/10/2019 06_Paging.pdf
42/46
S-CCPCH Configuration 2b
Logical channel DTCH DCCH CCCH BCCH PCCH
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 20RU 20
Soc Classification level
42 Nokia Siemens Networks Presentation / Author / Date
Transport channel
Physical channel
FACH-u FACH-c PCH
SCCPCH 1 SCCPCH 2
SF 64 SF 128
24 kbps24 kbps
S CCPCH Configuration 3a
8/10/2019 06_Paging.pdf
43/46
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
Logical channel DTCH DCCH CCCH BCCH CTCH PCCH
Soc Classification level
43 Nokia Siemens Networks Presentation / Author / Date
Transport channel
Physical channel
FACH-u PCHFACH-s
SCCPCHconnected
SCCPCHidle
FACH-c FACH-c
SCCPCHpage
SF 64 SF 128 SF 256
S CCPCH Configuration 3b
8/10/2019 06_Paging.pdf
44/46
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
Logical channel DTCH DCCH CCCH BCCH CTCH PCCH
Soc Classification level
44 Nokia Siemens Networks Presentation / Author / Date
Transport channel
Physical channel
FACH-u PCHFACH-s
SCCPCHconnected
SCCPCHidle
FACH-c FACH-c
SCCPCHpage
SF 64 SF 128 SF 128
Code Allocation C
8/10/2019 06_Paging.pdf
45/46
Code Allocation
Channelisation code for 24 kbpsPCH uses a larger section of thecode tree
HSDPA cannot use 15 HS-PDSCHcodes when HSUPA 2 ms TTI isenabled with 24 kbps PCH
Requirement for 2nd E-AGCHCch,128,4
Cch,128,5
Cch,256,14
E-AGCH
HS-SCCH
E-HICH & E-RGCH
Cch,128,6
Soc Classification level
45 Nokia Siemens Networks Presentation / Author / Date
code
Requirement for F-DPCH code
Cch,256,0
Cch,256,1
Cch,256,2
Cch,256,3
CPICH
P-CCPCH
AICH
PICHCch,64,1
S-CCPCH 1
S-CCPCH 2
c , ,
8/10/2019 06_Paging.pdf
46/46
Recommended