paging
Post on 25-Nov-2015
96 Views
Preview:
TRANSCRIPT
-
3G RANOP RU20 3G RANOP RU20 Paging and inter- RNC optimization
1 Nokia Siemens Networks RN31577EN20GLA0
-
Course Content
KPI overviewPerformance monitoringPerformance monitoringAir interface and neighbor optimizationCapacity & traffic optimizationPaging and inter-RNC optimization
2 Nokia Siemens Networks RN31577EN20GLA0
-
Module Objectives
At the end of the module you will be At the end of the module you will be able to:Describe SRNC relocation issuesDescribe Paging Procedure & Performance
3 Nokia Siemens Networks RN31577EN20GLA0
-
Paging and inter-RNC optimization Re-locationRe-location
Paging Performance in 3G- Cell resource states - Cell resource states - Paging capacity improvement RU20
4 Nokia Siemens Networks RN31577EN20GLA0
-
Re-location (1/4)UE Mobility Handling in RAN Limited support of
SRNS relocation SRNC anchoring
UE Mobility Handling in RAN3GPP options to 3GPP options to
use MMuse MM
Limited support ofmulti vendor services
CN
Iu Iu
CN
Iu Iu
CN
Iu Iu
CN
Iu Iu
SRNS relocation SRNC anchoring
RNCRNC Iur RNCRNC
Iu Iu
IurD-RNCS-RNC Iur RNCRNC Iur
Keep serviceas long as possible
SRNC Anchoring which is not as such a standardised mobility method, but which can be implemented by applying an undefined set of standardised
SRNS Relocation, which is a standardised mobility method
anchoring is supported in Nokia
SRNC only for CS RT + PS/NRT services
5 Nokia Siemens Networks RN31577EN20GLA0
undefined set of standardised features
mobility method+ PS/NRT services within Cell_DCH
-
Re-location (2/4)UE Mobility Handling in RAN
3GPP gives two different options to handle inter-RNC mobility in radio network
UE Mobility Handling in RAN
1. SRNS Relocation, 2. 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 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 related to mobility over RNC border between different vendors RNS if the other vendor uses SRNC anchoring
6 Nokia Siemens Networks RN31577EN20GLA0
-
Source and Target RNCRe-location (3/4)Source and Target RNCRelocation 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 RABand RAB In case of failures, Setup and Access failure counters are
incremented both for RRC and RAB
Source RNC: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
RABRAB In case of failures, Active failure counters are incremented both
for RRC and RAB
7 Nokia Siemens Networks RN31577EN20GLA0
-
Failure and Abnormal Release cause at Service LevelRe-location (4/4)Failure and Abnormal Release cause at Service Level
RRC setup and access counters are updated during incoming handovers and incoming handovers and relocations. If the new RRC connection is established or relocated successfully and if there are RAB connections for there are RAB connections for the UE, the RAB setup and access counters are updated as well.
8 Nokia Siemens Networks RN31577EN20GLA0
-
Example of incoming Re-location (1/3)Incoming SRNC Relocation
MSTarget RNCSRNC Relocation DecisionSRNC Relocation Decision
CN
RANAP:Relocation Required
Source RNC
RANAP:Relocation Request
SRNS Relocation,
Incoming SRNC Relocation
Setup phase: RRC_CONN_STP_ATT RRC_CONN_
STP_FAIL_RNCRANAP:Relocation Request Ack
RANAP:Relocation Request CN
Iu IuSTP_FAIL_RNC
Access phase:
User plane set-up
RANAP:Relocation Command
RNSAP:Relocation Commit
DRNCSRNC
Iur
RRC_CONN_STP_CMP RRC_CONN_ACC_FAIL_RNC
SRNC operation started
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
9 Nokia Siemens Networks RN31577EN20GLA0
User plane release
-
Incoming SRNCExample of incoming Re-location (2/3)Incoming SRNCIf 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 and the relative RAB counters
complete
and the relative RAB countersAfter the Iu Relocation Complete message the active phase starts
10 Nokia Siemens Networks RN31577EN20GLA0
-
Incoming SRNC Access PhaseExample 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:Failures are between the Relocation Request and the Relocation Complete:RRC_CONN_STP_FAIL_RNCRRC_CONN_ACC_FAIL_RNC/RADIO
For troubleshooting the M1009 familyCounters is available. The table is called:L3 Relocation signalling measurement.L3 Relocation signalling measurement.
_ATTSSRNC_RELOC_FAILSSRNC_RELOC
__Re =RateFailurelocation Service Level table counters
11 Nokia Siemens Networks RN31577EN20GLA0
-
Outgoing SRNC RelocationExample of outgoing Re-location (1/3)
SRNS Relocation,
Outgoing SRNC Relocation
MSTarget RNCCN
RANAP:Relocation Required
Source RNC
SRNC Relocation DecisionSRNC Relocation DecisionComing
from active and move CN
Iu Iu
RANAP:Relocation Request
RANAP:Relocation Request Ack
and move to release
DRNCSRNC
Iur
SRNC operation
User plane set-up
RANAP:Relocation Command
RNSAP:Relocation CommitActive phase
SRNC operation started
UP switching RRC:UTRAN Mobility Information
RANAP:Relocation Detect
RRC:UTRAN Mobility Information Confirm
From Source RNC point of view the RRC is in the active phase
RANAP:Relocation complete
RRC:UTRAN Mobility Information Confirm
RANAP:Iu Release
RANAP:Iu Release CompleteRelease phase
12 Nokia Siemens Networks RN31577EN20GLA0
active phaseUser plane release
-
Outgoing SRNC RelocationExample of outgoing Re-location (2/3)
Counters for normal release are incremented:
Outgoing SRNC Relocation
RRC_CONN_ACT_REL_SRNCRAB_ACT_REL_xxx_SRNC
13 Nokia Siemens Networks RN31577EN20GLA0
-
From ticket collectionExample of outgoing Re-location (3/3)From ticket collectionRRC Connection Active failuresAs far as Source RNC any failure during the relocation procedure is a failure during the active phase and since it 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 OUT REASON OUT DETAILED REASONfrequency Percentage
Source RNC
STOP WCELL IDOUT FAIL SOURCE OUT REASON OUT DETAILED REASONfrequency Percentage0 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%0 iur_c iur_connection_lost_c default_c 3 0.10%
STOP WCELL IDOUT FAIL SOURCE OUT REASON OUT DETAILED REASONfrequency Percenatge0 rnc_internal_c no_resp_from_rlc_c nok_c 92 3.05%
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%
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%
14 Nokia Siemens Networks RN31577EN20GLA0
0 transmissio_c transport_res_rel_nrm_c default_c 3 0.10%
-
SRNC Relocation failure (1/2)
Impact of SRNC relocation failure in the Setup failure Percentage refers to all the failures in the setup phase Target RNCPercentage refers to all the failures in the setup phase
IN REASON OUT FAIL SOURCE OUT REASON frequency Percentagesrnc_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 RNCSRNC Relocation Decision
CN
RANAP:Relocation RequiredRANAP:Relocation Request
Source RNC
Target RNC
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% User plane set-up
RANAP:Relocation Request Ack
RANAP:Relocation Command
RNSAP:Relocation Commit
Setup phaseRRC_CONN_STP_FAIL_RNC
IN REASON OUT FAIL SOURCE OUT REASON frequency Percentagesrnc_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 operation started
UP switching
RANAP:Relocation complete
RRC:UTRAN Mobility Information
RANAP:Relocation Detect
RRC:UTRAN Mobility Information Confirm
RANAP:Iu Release
Access phase RRC_CONN_ACC_FAIL_RNC
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%
RANAP:Iu Release Complete
User plane release
Active phase
Analysis done using PMI Ticket
15 Nokia Siemens Networks RN31577EN20GLA0
Analysis done using PMI Ticket
-
SRNC Relocation failure (2/2)No response from rlc-nok (017F-191)
Incremented counters in the Source RNCRRC_CONN_ACT_FAIL_RNC
No response from rlc-nok (017F-191)
RRC_CONN_ACT_FAIL_RNCRAB_ACT_FAIL_xxx_RNC
16 Nokia Siemens Networks RN31577EN20GLA0
-
SRNC relocationPaging and inter-RNC optimization SRNC relocation
Thank You !
17 Nokia Siemens Networks RN31577EN20GLA0
-
Paging and inter-RNC optimization Paging Performance in 3GPaging Performance in 3G- Cell resource states - Paging capacity improvement RU20
18 Nokia Siemens Networks RN31577EN20GLA0
-
Paging Performance in 3G - RU10RRC States
UTRA RRC Connected ModeUE in DRX mode
UE in DRX modediscontinous reception
RRC States
URA_PCH CELL_PCHdiscontinous reception
discontinous reception
via Cell Update via Cell Update /
NEW RU10:
CELL_DCH CELL_FACHDedicated resourcesallocated (DCH, HS)
Common resourcesallocated (RACH-FACH)
Tx and Rx mode
via Cell Update Confirm
via Cell Update / Confirm
CELL_DCH CELL_FACHallocated (DCH, HS)Tx and Rx mode
Idle Mode
not implementedCell selection
Cell re-selectionListen to paging
19 Nokia Siemens Networks RN31577EN20GLA0
Idle Mode
-
The packet access procedure in WCDMA should keep the interference caused to other users as small as
Paging Performance in 3G RU10The 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: There are 3 scenarios for WCDMA packet access: infrequent transmission of small packets frequent transmission of small packets and transmission of large packets 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
20 Nokia Siemens Networks RN31577EN20GLA0
(DCH). When the packet data is performed on shared or dedicated channels, the UE is in CELL_DCH state.
-
Paging Performance in 3G RU10Example: 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
Example: Transition from CELL_DCH to CELL_PCH
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.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 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.
CELL_PCH
L3 signaling is RRC: Physical Channel ReconfigurationCELL_DCH
21 Nokia Siemens Networks RN31577EN20GLA0
-
Paging Performance - processing URA reselection
Cell reselection (moving UE)
Periodic cell update (stationary UE)
Paging response (DL
URA reselection Periodic URA update
(stationary UE) Paging response (DL
data / signalling) UL Access (UL data /
Inactivity detection during last 20sec
RNC L2 resources at low level Fast UE with L2 inactivity
Paging response (DL data/ signalling)
UL Access (UL data/signalling)
UL Access (UL data / signalling)
Cell_PCH
Activity supervision Completion of Cell
Update procedureURA_PCH Data in GTP buffer
Inactivity detection of NRT RB
Release of RT RB
PCH
Completion of URA Update procedure
Max. # cell updates in
Cell_FACH
Setup of RT/NRT RB
Max. # cell updates in Cell_FACH / Cell_PCH exceededCell_
DCH
Setup of RT/NRT RB RAB reconfiguration DCH Up or Downgrade Bit rate reduction due to
load reasonsRRC Connection
Release
22 Nokia Siemens Networks RN31577EN20GLA0
IdleMode
load reasons
UL/DL data or signalling
RT RB setup
Release
CN originated paging (MT Call) Random Access (MO Call)
-
Paging lost: cell-PCH not activePaging PerformancePaging lost: cell-PCH not active
incremented only if the mobile is in cell-PCH
(
b
i
t
/
s
)
23 Nokia Siemens Networks RN31577EN20GLA0
-
Paging PerformancePaging Blocking
A terminal, once registered to a network, has been allocated a paging group. For the paging group there are Paging Indicators (PI) which
Paging Blocking
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 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 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 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
this LAC where subscriberB is.
-
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
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 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. 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.maximum paging rate is 100 paging/sec/cell.
25 Nokia Siemens Networks RN31577EN20GLA0
-
Paging buffer Paging Performance in 3G & S-CCPCH config.Paging buffer
Each IMSI belongs to a paging group, according to the formulaEach IMSI belongs to a paging group, according to the formulaPaging group = IMSI mod (DRX cycle length)The paging occasions for each paging group can be
group 1 group 2 group 3 group 4 group 30 group 31 group 32 group 1 group 2
10 ms
group 1served
group 2served
group 3served
group 4served
group 30served
group 31served
group 32served
group 1served
group 2served
10ms * DRX cycle length
In case no buffering is utilized, only 1 paging message related to each paging group would 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 bufferIn the current implementation (RAN04/RAN05), a buffer of 512 places stores the 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 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.
busyplace 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 time is shorter than the repetition time in CN but could be higher than the repetition time in
27 Nokia Siemens Networks RN31577EN20GLA0
time is shorter than the repetition time in CN but could be higher than the repetition time in RNC (when cell-PCH is active).
-
PCH throughput: paging requests blockedPaging Performance in 3GPCH throughput: paging requests blocked
The number of transmitted pagings (on the radio interface) is:paging_requests [pagings/hour] = 3600 * PCH_THROUGHPUT / (80 bits)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 [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 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
paging_requests_blocked [paging/hour] = paging_type_1 - paging_requests
-
PCH Loading Estimation ProcessM1006C25 Paging Type 1 Att CN OrigM1006C25 Paging Type 1 Att CN OrigM1006C26 Paging Type 1 Att RNC Orig all 0 if cell_PCH is not in use
M1000C70 Ave PCH ThroughputM1000C71 PCH Throughput Denom 0M1000C71 PCH Throughput Denom 0
M1001C32,34,36,38,52,56&60 indicate the amount of MTC events in M1001C32,34,36,38,52,56&60 indicate the amount of MTC events in cell basis, which is related to amount of Paging events.
29 Nokia Siemens Networks RN31577EN20GLA0
-
PCH Loading Estimation Process
M1006C25&C26 gives the hourly(or daily) basis number of Paging Air InterfaceM1006C25&C26 gives the hourly(or daily) basis number of Paging Type1 transmitted from CN per cellSince 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
Air Interface
maximum counter value over all the cells in the LA/RA is used in this analysisAverage 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
)max(),max( += LA/RA the in cells among ,M1006C26LA/RA the in cells among M1006C25 e1fPagingTypMaxAmountO
)1(800080][
[sec]36001][[bps]
=
=
=
SCCPCHof # bit izeingRecordSAveragePag
bitizeingRecordSAveragePage1fPagingTypMaxAmountO ughputPagingThro
100][][[%]
)2(24000)1(8000][
=
=
=
=
bps hroughputMaxPagingTbps ughputPagingThro
PagingLoad
SCCPCHof # SCCPCHof # bps hroughputMaxPagingT
30 Nokia Siemens Networks RN31577EN20GLA0
This should on TB level
-
PCH Loading Estimation ProcessStatistically, Paging Type1 is generated in the random manner by a lot of Statistically, Paging Type1 is generated in the random manner by a lot of subscribers, except the special case like Happy New Year callNumber of Paging Type1 generated would form Poisson distributionThrough the below flow Air InterfaceThrough the below flow Air Interface
Target PCH Load
Averaged # of simul. Paging Type1/sec Poisson Distribution
Paging Type1=200bit
Max P.T.1/secMax PCH Throughput
1 SCCPCH 8[kbps] 100 Failure ProbabilityAcceptable? OKNO
YES
Max P.T.1/secMax PCH Throughput
2 SCCPCH 24[kbps] 300 Failure ProbabilityAcceptable?
YES
NO
31 Nokia Siemens Networks RN31577EN20GLA0
Divide LA/RA
NO
-
PCH Loading Cumulative Poisson DistributionAir InterfaceAir Interface
Relation between Probability of Simultaneous "Paging Type1" and PCH LoadingMax PCH Throughput=8[kbps] / Size of Paging Type 1=80[bits]
(Poisson Distribution)
100
C
u
m
u
l
a
t
i
v
e
P
r
o
b
a
b
i
l
i
t
y
[
%
]
2005/Dec/31 23:00 @RNC510No need to have 2 SCCPCH
nor LA/RA division
94
96
98
100
C
u
m
u
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
l
a
t
i
v
e
P
r
o
b
a
b
i
l
i
t
y
[
%
]
PCHLoad=10% PCHLoad=30% PCHLoad=50% PCHLoad=70% PCHLoad=80% max limit (SCCPCH=1)PCHLoad=10% PCHLoad=30% PCHLoad=50% PCHLoad=70% PCHLoad=80% max limit (SCCPCH=1)
When PCH load=80%, ~1.3% of P.T1 fails.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
32 Nokia Siemens Networks RN31577EN20GLA0
NOTE: THIS IS PURELY FROM PCH POINT OF VIEW AND DOES NOT INCLUDE THE PAGING BUFFER HANDLING ASPECT
-
PCH Loading Estimation ResultsPeak hour is 18:00 and the below graph shows the PCH load @ 18:00 (hourly data)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:002005/Jun/01~Dec/31
But still quite difficult to forecast with non-linear approximation.
2005/Jun/01~Dec/31PCH Throughput=8[kbps] / PagingType1=80[bits]
6.0007.0008.0009.000
P
C
H
L
o
a
d
[
%
]
Tenjin Festival
Fireworks@Yodo River
0.67[%/month]
2.0003.0004.0005.0006.000
P
C
H
L
o
a
d
[
%
]
0.0001.000
0
5
/
0
6
/
0
1
0
5
/
0
6
/
0
8
0
5
/
0
6
/
1
5
0
5
/
0
6
/
2
2
0
5
/
0
6
/
2
9
0
5
/
0
7
/
0
6
0
5
/
0
7
/
1
3
0
5
/
0
7
/
2
0
0
5
/
0
7
/
2
7
0
5
/
0
8
/
0
3
0
5
/
0
8
/
1
0
0
5
/
0
8
/
1
7
0
5
/
0
8
/
2
4
0
5
/
0
8
/
3
1
0
5
/
0
9
/
0
7
0
5
/
0
9
/
1
4
0
5
/
0
9
/
2
1
0
5
/
0
9
/
2
8
0
5
/
1
0
/
0
5
0
5
/
1
0
/
1
2
0
5
/
1
0
/
1
9
0
5
/
1
0
/
2
6
0
5
/
1
1
/
0
2
0
5
/
1
1
/
0
9
0
5
/
1
1
/
1
6
0
5
/
1
1
/
2
3
0
5
/
1
1
/
3
0
0
5
/
1
2
/
0
7
0
5
/
1
2
/
1
4
0
5
/
1
2
/
2
1
0
5
/
1
2
/
2
8
33 Nokia Siemens Networks RN31577EN20GLA0
0
5
/
0
6
/
0
1
0
5
/
0
6
/
0
8
0
5
/
0
6
/
1
5
0
5
/
0
6
/
2
2
0
5
/
0
6
/
2
9
0
5
/
0
7
/
0
6
0
5
/
0
7
/
1
3
0
5
/
0
7
/
2
0
0
5
/
0
7
/
2
7
0
5
/
0
8
/
0
3
0
5
/
0
8
/
1
0
0
5
/
0
8
/
1
7
0
5
/
0
8
/
2
4
0
5
/
0
8
/
3
1
0
5
/
0
9
/
0
7
0
5
/
0
9
/
1
4
0
5
/
0
9
/
2
1
0
5
/
0
9
/
2
8
0
5
/
1
0
/
0
5
0
5
/
1
0
/
1
2
0
5
/
1
0
/
1
9
0
5
/
1
0
/
2
6
0
5
/
1
1
/
0
2
0
5
/
1
1
/
0
9
0
5
/
1
1
/
1
6
0
5
/
1
1
/
2
3
0
5
/
1
1
/
3
0
0
5
/
1
2
/
0
7
0
5
/
1
2
/
1
4
0
5
/
1
2
/
2
1
0
5
/
1
2
/
2
8
date
RNC501 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 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 3GPaging Performance in 3G- Paging capacity improvement RU20- Cell resource states - Paging capacity improvement RU20- Paging capacity improvement RU20
35 Nokia Siemens Networks RN31577EN20GLA0
-
Introduction (1/2)24 kbps Paging Channel24 kbps Paging Channel Paging load/activity
- 8 kbps paging channel capacity is implemented for (RU10)
Cch,256,14
E-AGCHimplemented 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,
Cch,128,5
E-AGCH
E-HICH & E-RGCH
Cch,128,6
S-CCPCH with SF128, comparing 8 Kbps/SF256 (more PwR)
- If Paging 24 kbps is used, maximum of available HSDPA codes are only14
Cch,128,4HS-SCCH
Cch,16,0
No HSDPA code freeNo HSDPA code free
only14
AICH
PICHCch,64,1
S-CCPCH 2
Paging Ch with 24 kbps Paging Ch with 24 kbps Bottleneck is PwRBottleneck is PwR
Cch,256,2
Cch,256,3CPICH
P-CCPCH
S-CCPCH 1Pilot coverageS-CCPCHsetup
Bottleneck is PwRBottleneck is PwR Not code tree allocationNot code tree allocation(calculation on next slide)(calculation on next slide)
36 Nokia Siemens Networks RN31577EN20GLA0
WCEL: PtxSCCPCH1It carries a PCH or FACH (mux) or FACH /dedicated). Spreading factor is SF64 (60 kbps) Cch,256,0
Cch,256,1setup
-
Introduction (2/2)8/24 kbps Paging ChannelExample: Power benchmarkExample: Power benchmarkWhat limits first: PwR or Code tree occupation
8/24 kbps Paging Channel
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 Watt60kbps/24kbps, cc. 1/260kbps/24kbps, cc. 1/2
With SF256 PCH (8kbps) needs power 5 dB below CPICH = 28 dBm = 0.63 Watt30kbps/8kbps cc.1/230kbps/8kbps cc.1/2
Power loss = 1.26 W 0.63 W = 0.63 W approx. 600 mW3 % 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
5 % (600 mW) of about 12 W available for user data
-
To support higher paging capacity, the size of transport block for PCH is increased:Concept
24 kbps Paging Channel
PCCH
To support higher paging capacity, the size of transport block for PCH is increased:
Logical channelPCCH
8 kbps = up to 508 kbps = up to 50--75% PCH load75% PCH load
Transport channel8 kbps = 80 Bit / 10ms TTI (default)
PCH
8 kbps = up to 508 kbps = up to 50--75% PCH load75% PCH load
Physical
24 kbps = 240 Bit / 10ms TTI (optional)
Several Several Physical channel
If WCEL: PCH24KbpsEnabled parameter is set to enabled, the PCH transport channel is mapped to a dedicated S-CCPCH physical channel.
SCCPCH
Several Several SS--CCPCH possibleCCPCH possible
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 24 kbps PCH
0: 0x80 bits 0: 0x240 bits very similar
Only difference is the increased transport block
TFS
0: 0x80 bits (0 kbit/s)
1: 1x80 bits(8 kbit/s)
0: 0x240 bits (0 kbit/s)
1: 1x240 bits(24 kbit/s)size
TTI
(8 kbit/s) (24 kbit/s)
10 ms 10 ms
Channelcoding CC 1/2 CC 1/2
CRC 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 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 FACH-c PCHUU-- user datauser data CC-- control datacontrol data
Physical channel SCCPCH 1
40 Nokia Siemens Networks RN31577EN20GLA0
SF 64
-
S-CCPCH Configuration 2a PCH24kbpsEnabled is configured to disabled with this configuration PCH24kbpsEnabled is configured to disabled with this configuration Limits the PCH bit rate to 8 kbps The PCH is allocated its own S-CCPCH
Logical channel DTCH DCCH CCCH BCCH PCCH
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 SCCPCH 2SF 64 SF 256
41 Nokia Siemens Networks RN31577EN20GLA0
SF 64 SF 256
-
S-CCPCH Configuration 2b PCH24kbpsEnabled is configured to enabled with this configuration PCH24kbpsEnabled is configured to enabled with this configuration Increases the PCH bit rate to 24 kbps The PCH is allocated its own S-CCPCH
RU 20RU 20
Logical channel DTCH DCCH CCCH BCCH PCCH
SF128 is allocated to the PCH to support the increased bit rate
Logical channel DTCH DCCH CCCH BCCH PCCH
Transport channel FACH-u FACH-c PCH
Physical channel SCCPCH 1 SCCPCH 2SF 64 SF 128
42 Nokia Siemens Networks RN31577EN20GLA0
SF 64 SF 12824 kbps24 kbps
-
S-CCPCH Configuration 3a PCH24kbpsEnabled is configured to disabled with this configuration 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
Transport channel FACH-u PCHFACH-sFACH-c FACH-c
Physical channel SCCPCH connected
SCCPCH idle
SCCPCH page
SF 64 SF 128 SF 256
43 Nokia Siemens Networks RN31577EN20GLA0
SF 64 SF 128 SF 256
-
S-CCPCH Configuration 3b PCH24kbpsEnabled is configured to enabled with this configuration 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
Transport channel FACH-u PCHFACH-sFACH-c FACH-c
Physical channel SCCPCH connected
SCCPCH idle
SCCPCH page
SF 64 SF 128 SF 128
44 Nokia Siemens Networks RN31577EN20GLA0
SF 64 SF 128 SF 128
-
Code Allocation Cch,256,14
Channelisation code for 24 kbps PCH uses a larger section of the code tree Cch,128,5
E-AGCHCch,128,6
code tree HSDPA cannot use 15 HS-PDSCH
codes when HSUPA 2 ms TTI is enabled with 24 kbps PCH HS-SCCH
E-HICH & E-RGCH
enabled with 24 kbps PCH Requirement for 2nd E-AGCH
code Requirement for F-DPCH code
Cch,128,4
S-CCPCH 2Cch,16,0
Requirement for F-DPCH code
P-CCPCH
AICH
PICHCch,64,1
Cch,256,2
Cch,256,3CPICH
P-CCPCH
S-CCPCH 1
45 Nokia Siemens Networks RN31577EN20GLA0
Cch,256,0
Cch,256,1
-
Paging Performance in 3G RU10
Paging and inter-RNC optimization Paging Performance in 3G RU10
Thank You !
46 Nokia Siemens Networks RN31577EN20GLA0
top related