GSD Quality of Service Operation System Performance Group Vienna

PCU logging for field engineers

Author/Editor: Ulrich Gross Ulrich.Gross@motorola.com Motorola GSD - Quality of Service Operation System Performance Group Vienna Date: 07 December 2011 Document ID: UG-01-01-01 Document version: 0.1 Status: draft Find the newest version of this document in: http://compass.mot.com/go/spg

Abstract: Due to lack of official supported statistics and benchmarking tools, it is for specific purposes necessary to log PCU internal messages. This document describes useful commands and procedures solely to benchmark a GPRS system as part of the end-to-end optimization service, including very basic procedures as well as practical tips and tricks. The document does not provide any troubleshooting procedures.

Motorola Confidential Proprietary

This document and the information contained in it is CONFIDENTIAL INFORMATION of Motorola, and shall not be used, published, disclosed, or disseminated outside Motorola in whole or in part without Motorolas consent. This document contains trade secrets of Motorola. Reverse engineering of any or all of the information in this document is prohibited. The copyright notice does not imply publication of the document

End2end optimisation PCU internal stats

SIGN-OFF FORM
Author Revised Revised Ulrich Gross signature signature signature Date Date Date

HISTORY OF REVISIONS
Revision 0.1 0.2 1.0 Date Author Revised by Changes Description draft internal review released

System Performance Group Vienna Motorola Confidential Proprietary

Page 2/18

End2end optimisation PCU internal stats

Table of Content
..................................................................................................................................................2 1. General...................................................................................................................................4 1.1. A peek inside the PCU....................................................................................................4 1.2. How to..........................................................................................................................5 1.2.1. login to a PCU......................................................................................................5 1.2.2. .. display cell to PRP mapping..............................................................................5 1.2.3. .. disable security timeouts ...................................................................................6 1.2.4. .. enable/disable Timestamp.................................................................................6 1.2.5. .. enable/disable filters..........................................................................................6 1.2.6. .. know which PICP terminates which link............................................................7 1.2.7. . Check LCI to CID mapping.................................................................................7 1.2.8. How to set the baud rate of the on board serial interface........................................7 2. BLER & CS.............................................................................................................................8 3. TBF set up and termination....................................................................................................9 3.1. TBF filter..........................................................................................................................9 3.2. Watch TLLI....................................................................................................................10 4. GBL......................................................................................................................................10 4.1. UL/DL traffic...................................................................................................................10 4.2. PCU flow control buffer ................................................................................................11 Appendix A. Short Command reference..................................................................................12 Appendix B. Copy of PCU_Logging_Guide...........................................................................13 Appendix C. Uplink Power Control...........................................................................................14 Collecting logs..........................................................................................................................15 PRM SLLD V3.03.....................................................................................................................15 Section 2.6.1.1 Closed Loop Power Control............................................................................15 ETSI 5.08 10.2.1......................................................................................................................16 MS output power......................................................................................................................16 ETSI 5.05:................................................................................................................................17 4.1.1 Mobile Station.................................................................................................................17 References...............................................................................................................................18

Table of Figures

System Performance Group Vienna Motorola Confidential Proprietary

Page 3/18

End2end optimisation PCU internal stats

1. General
1.1. A peek inside the PCU
P S P ( P P C 7 5 0 b o a rd )
P a g e s fo r C C C H

P R P (P P C 7 5 0 b o a rd )
P a g e s fo r C C C H D L G b s ig n a lin g

CPGM

P I C -G b ( P P C 7 5 0 ) P

GBM CB

GR

D L T est P D U N S T

C ell s ta tu s c h a n g e s U L G b S ig n a lin g R A C H F lo w P a g e s fo r C o n tro l R e q P C C C H /P A C C H

SYM
GW M S ta ts
GSL m e ss a g e s

DB N o tific a tio n s

GSLI

C e ll s ta tu s c h a n g e s S y s in fo (p e r c e ll) C e ll A c tiv a tio n D e a c tiv a tio n

(p e r c e ll, F lo w C o n tro l p e r p a g e b u ffe rs g ro u p ) (p e c e ll, r per Q oS ) F lo w C o n tro l a n d F lu s h s ig n a l

P a g in g b u ffe rs

D L B S S G P fra m es

D L G b fra m e s U L S ta tu s m es sa g e s U L T est P D U

b u ffe rs

L A P D Im m e d ia te A s s ig n F P IC P R A U ra m e -T

PPGM FBM
R LC b lo c k s

FR D LS P F lo w C o n tro l PD Us U L G b fra m e s

To GBM : N o tific a tio n m es sa g e s

(1 /2 o f a P P C 8 6 0 )
GSL (1 o r m o re 6 4 K L A P D lin k s) PCU CU -C (1 6 K c irc u its on E1) EXEC D LS P

F R A P I m essag es

C C TX

P PRMR M
D o w n lin k T R A U fra m e s

DLS

PPC 860
GTM
U L G b fra m es FR and STR EAM S F R fra m e s HD LC D riv e r

CCRX

R LC b lo c k s

T im in g d a ta , s y n c s ta tu s

TS N (1 /4 o f a P P C 7 5 0 )

U L C U L G b fra m es G b in p u t
U p lin T R A U fra m e s k G blin k s ta tu s ch a ng es b u ffe r (p e r P R P )

E1 lin e E1 lin e

K ey:

E x e c u te s P P C 7 5 0 on

E x e c u te s o n P P C 8 6 0

Pa rt o f a m u ltip ro c e s s fu n c tio n a l u n it b u t is a s e p a ra te p ro c es s
Figure 1: PCU block diagram

As far as performance is related, PRM, FBM, GR and GTM are of interest as they handle directly data blocks. PRM: Packet resource manager Responsible for air interface resources, so if one needs info regarding RLC blocks, TBFs, CS selection and similar stuff, he needs to ask PRM. FBM: Flow buffer manager If anything related to flow control is suspicious (especially when dealing with non Motorola SGSN) its always worth having a look at what FBM has to say. Gives info about the PCU buffer level and leak rate, instantaneous and as reported to the SGSN.

System Performance Group Vienna Motorola Confidential Proprietary

Page 4/18

End2end optimisation PCU internal stats

GR/ GTM: Gb Router /Gb transmit manager, responsible for handling LLC frames coming from and going to the Gb link. Thus, if no Gb link analyser is available, info dumped by those two can be used to count LLC frames, check for throughput peaks on the Gb, etc.

1.2. How to
1.2.1. login to a PCU

There are three ways of logging into a PCU, all of them with different characteristics: 1) Via OMC The most common way in the field, although not the most preferable. Either use the tty_rlogin function from the OMC-R GUI, or the command tty_rlogin <BSS_Name> 2) Via tty over the BSC This is the least preferable option as it has the disadvantage of having to be at the site but still being restricted to 9600 Baud. Simply plug a terminal to the MPROC serial interface. 3) Via tty directly on the processor card of the PCU The best one can do as the serial interface can do 57600 Baud Disadvantage: A special cable is necessary. Want to order a kit of all kinds of cables? This is the ordering number: To login:
MMI-RAM 0114 -> chg_l MMI-RAM 0114 -> set_mmi exec_mon SET_MMI was successful GPROC2_RAM:emon_0114 % GPROC2_RAM:emon_0114 % rl 254 1106h PCU:emon_1106 %

254 points at the PCU and 1106h to the processor board to login. In this case it is a PRP in slot number 6. If you are using a direct terminal connection, set_mmi wont work, use <CTRL> <N> instead. To logout:
<CTRL><D> to log out of the PCU card MMI-RAM 0114 -> !logout to log out of the BSC

******* IMPORTANT NOTE******* Due to the low data rate logs might get corrupted when there are too many messages coming. This means, that one has to consider always the possibility that a particular message might have been lost. ***************************************

1.2.2.

.. display cell to PRP mapping Login to the PSP (must be slot 7 or 9) Chg_l Page 5/18

System Performance Group Vienna Motorola Confidential Proprietary

End2end optimisation PCU internal stats

msg_s 0d0h 9000h 0 0 0 9

Local Cell Ids -------------------------------------------------------------------0xd 0 0x3 0x6 0x8 0x9 0xc 0x11 0x12 0x15 0x17 0x1b 0x1e 0x25 0x3b 0x3c 0x3f 0x45 0x4b 0x4e 0x51 0x1 0x7 0xa 0x13 0x16 0x24 0x26 0x2a 0x2b 0x2c 0x2e 0x34 0x35 0x36 0x38 0x3a 0x3d 0x40 0x43 0x49 0x4c 0x4f 0x14 0x18 0x19 0x1a 0x1d 0x1f 0x20 0x21 0x23 0x27 0x29 0x2d 0x2f 0x30 0x31 0x32 0x33 0x46 0x48 0x52 0x2 0x4 0x5 0xb 0xe 0xf 0x10 0x1c 0x22 0x28 0x37 0x39 0x3e 0x41 0x42 0x44 0x47 0x4a 0x4d 0x50

Example output:
CPU ID -----0x1103 0x1104 0x1105 0x1106

NOTE: 0x indicates that these numbers are in hexadecimal format. 1.2.3. PCU .. disable security timeouts Login to the card of desire chg_l msg_s 23 1 0 0 8a04h 1 The DPROC should come back with:
PCU:emon_1105 % Disabling security time out

BSC At the emon prompt: msg_s 112 6 0 0 1c00h 1 No feedback 1.2.4.

.. enable/disable Timestamp

time_stamp on/off 1.2.5. .. enable/disable filters

the command iir_mod <process id> <filter bitmap> instructs the PCU to show debug messages of that specific process. To turn the filter off simply set the filter bitmap to 0. ****** PRACTICAL TIP ****** When a filter dumps a lot of messages, its often hard to issue the commands as its not possible to see the echo or the feedback of it. To make things easier, prepare the commands to use in a text file and just paste them to the terminal. ************ ****** NOTE ****** Filter output might change from BSS software version to another. ************

System Performance Group Vienna Motorola Confidential Proprietary

Page 6/18

End2end optimisation PCU internal stats

1.2.6.

.. know which PICP terminates which link

On the mmi of the BSS type: Disp_proc pcu Example output:

MMI-RAM 0115 -> disp_proc pcu PROCESSOR STATUS INFORMATION FOR LOCATION PCU: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped NC: CPU# ---1107 1101 Not Connected Processor Name ---------------------PSP 0 0 DPROC (PICP) 1 0 State ----B-U B-U Reason ------------------------NO REASON NO REASON Related Device ----------N/A MSI 0 0 GDS 0 0 GSL 0 0 MSI 1 0 GBL 0 0 (GDS 3 0) (GDS 2 0) MSI 2 0 GDS 1 0 GSL 1 0 MSI 3 0 GBL 1 0 (GDS 5 0) (GDS 4 0) MSI 4 0 GDS 2 0 MSI 5 0 GDS 3 0 MSI 6 0 GDS 4 0 MSI 7 0 GDS 5 0 Related Function -------N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A

NE:Not Equipped

1102 DPROC (PICP) 2 0

B-U

NO REASON

1103 DPROC (PRP) 3 0 1104 DPROC (PRP) 4 0 1105 DPROC (PRP) 5 0 1106 DPROC (PRP) 6 0 END OF STATUS REPORT

B-U B-U B-U B-U

NO REASON NO REASON NO REASON NO REASON

This tells you that PRP 3 is physically terminating GDS 2 0, but PICP 1 is handling it. GBL 1 is terminated at PICP 2 so you need to log into this card to trace GBL messages for BVCIs on GBL 1. 1.2.7. . Check LCI to CID mapping

MMI-RAM 0115 -> disp_gsm_cells <site> 1.2.8. How to set the baud rate of the on board serial interface (easy, eh?)

PCU:emon_1106 % baud <baudrate>

System Performance Group Vienna Motorola Confidential Proprietary

Page 7/18

End2end optimisation PCU internal stats

2. BLER & CS
The CS selection algorithm reports a series of information regarding the quality of the air interface. In fact it is the output of the CS selection algorithm containing all the information the algorithm uses to determine which CS to use. NOTE: It reports for each MS in all the cells served by the PRP!! Be careful when using, this means a flood of messages and the probability of losing messages is raised! On the PRP serving the cell under investigation: PCU:emon_1106 % iir_mod 0d9h 4200h
Example filter output
TLLI:e0c492d7 DL CS2=>CS2 BLER:0.000000 ULABN:252201 PIF penalty: 0 PifABN: 4294967295 Score: 0 Stall: 0 Missed DAK: 0 PIF 0 BLER: 0.000000 DLACK: TLLI: e0c492d7 Cell 068 TX Max 043 Adj 043 Min 001 CalcC 041 CalcBL 041 Stal 000 RawC -51 RxQ 000 Bler Calc 0.000 Prev 0.000 PPrev 0.000 DesP 043 AtnC 000 AtnP 000 Plat 10 CAdj -51 CS 001 ts 006 p_redu 000 Poll cs map : 252213 CS: 1 ftype :1 Staying in phase 5 BLER UPDATE: Tot:4 NK:0 BL0.000000=> 0 at ULABN: 252203 Score: 0 Stall: 0 Missed DAK: 0 PIF 0 BLER: 0.000000 calc carrier level is -51, RxQual is 000, New Pwr level (dBm) is:041, Prev DL Pwr level 43 Enforcing SMG29 No Power Control Mode Current dl ts alloc is f0 (Hex) dl attn[0] = 255, [1] = 255, [2] = 255, [3] = 255, [4] = 0, [5] = 0, [6] = 0, [7] = 0

TLLI: Indicates the mobiles TLLI CSX=>CSY: Indicates if the CS changes, or stays the same. BLER: The result of a calculation of the BLER over the last 128 blocks. Note: BLER will stay 0 if the CS changes before the 128 blcok count are reached. In that case there must be missed DAKs or stalls instead. Missed DAKs: Indicates the number of missek DL acknowledge messages. The number displayed represents the actual number of missed DACKs weighted with a factor (5 in 16.20.e1-t5). Stall: Indicates number of RLC window stalls occurred, again weighted with a factor (10 in 16.20.e1-t5). ULABN: UL Absolute Block Number each Block 20ms => accurate timestamp Cell: Indicates the cell by the Local Cell ID RawC: The C value reported by the mobile. Current TS allocation: Refers to the DL and represents a bit pattern in Hex format. E.g.: f0h = 11110000b this would mean TS 7,6,5,4 for DL

****** NOTE ****** If you want to synchronise with a drive tester during logging, keep in mind that there is a buffer for the serial interface. This will effectively delay the messages for a couple of seconds. ********************* Tips for post processing Due to the fact that BLER is calculated on a base of 128 blocks (16.20.e1-t5) it might well be the case, that the number of valid BLER reports is very low, as it will always show 0 if it doesnt have a valid measurement. This implicates, that a BLER distribution taken out of the this filter output cannot come alone, but has to come along preferably in the same chart with missed DAKs, stalls and CS distribution.

System Performance Group Vienna Motorola Confidential Proprietary

Page 8/18

End2end optimisation PCU internal stats

3. TBF set up and termination

3.1. TBF filter
This filter reports messages regarding TBF setup and termination for each TLLI handled by the particular PRP. TBFs are handled by the Packet Resource Manager (PRM) which always has the process id d9h. NOTE: It reports for each MS in all the cells served by the PRP!! Be careful when using, this means a flood of messages and the probability of losing messages is raised! On the PRP serving the cell under investigation: PCU:emon_1106 % iir_mod 0d9h 0c0000000h
Example filter output
TLLI c4861ca8: received PRR on (68,1,4) at ulabn:239962 race=0 Sending TLLI c4861ca8 TFI: 24 PUA ( a) on (68,1,4) at abn = 239971, curr_dl_abn 239971 or 54536370 ms, rrbp = 0 TLLI c4861ca8 UL tfi = 24 starting on (68,1,7) at 239974 TX Watch: Receiving TLLI 0xc4861ca8, cell 68, tx_buffer_index = 0 num_blocks(CS1 ) = 2 Sending TLLI c4861ca8 TFI: 16 PTR( 7) on (68,1,7) at abn = 239987, curr_dl_abn 239987 or 54536690 ms, rrbp = 3 TLLI c4861ca8 DL tfi = 16 starting on (68,1,7) at 239993 TLLI c4861ca8 DL tfi = 16 starting on (68,1,5) at 239993 TLLI c4861ca8 UL tfi = 24 starting on (68,1,6) at 239993 TLLI c4861ca8 DL tfi = 16 starting on (68,1,6) at 239993 54537130 TLLI c4861ca8 UL tfi=24 normal_tbf_release at ulabn=240001 stats(1 1 1 ) DL TBF( 16): uplink requested in DAK for TLLI: c4861ca8 at ulabn = 240003 Sending TLLI c4861ca8 TFI: 25 PUA ( a) on (68,1,6) at abn = 240011, curr_dl_abn 240011 or 54537170 ms, rrbp = 0 TLLI c4861ca8 UL tfi = 25 starting on (68,1,6) at 240014 54537610 TLLI c4861ca8 UL tfi=25 normal_tbf_release at ulabn=240025 stats(1 1 1 ) 54541890 :TLLI c4861ca8 DL tfi=16 normal_tbf_release at ulabn=240239 stats(642 21 0 80 743)

Stats:

PRR Packet Resource Request PTR Packet Timeslot Reconfigure TFI Temporary Flow Indicator PUA Packet UL Assignment Starting on (LCI,carrier id,TS)

for UL total new blocks, total missed blocks, total received blocks. for DL total idle blocks, total new blocks, total NAK blocks, total PAK blocks, sum of all.

TIPS If you want to look at a particular TLLI, be careful to catch the start of the transmission. Otherwise due to supercoattail you might never see the DL assignment.

System Performance Group Vienna Motorola Confidential Proprietary

Page 9/18

End2end optimisation PCU internal stats

3.2. Watch TLLI

This function is useful if you need detailed information about a specific mobile, e.g. to enhance the information given by MDTT with the PCU info. NOTE: It`s not recommended to enable it globally outside a lab system. In the field it can be very useful, but only if its enabled for the TLLI under investigation.
msg_s 0d9h 9000h 0 0 7404 4 34 1 <tlli_byte3> <tlli_byte2> <tlli_byte1> <tlli_byte0> Example: msg_s 0d9h 9000h 0 0 7404 4 34 1 0ch 0 0c3h 0f8h

will enable watch tlli for tlli = c00c3f8h

msg_s 0d9h 9000h 0 0 7404 4 34 0 will turn it off, msg_s 0d9h 9000h 0 0 7404 4 34 0ffh will turn it on

globally.

Example output
TLLI c886894e ul request in new cell 28 from old cell 71 tlli = c886894e, ms class = 4. freq_type 1 Picking tfi index:0:rx buff index:0:old_index_in the map:35 for TFI:13 Created TFI:13, tfi index: 0, rx buff index:0 UL TBF( 13) starting at frame= 479015, abn= 110542, rbn= 10, num_dl_msg = 1 Sending TLLI c886894e TFI: 13 PUA ( a) on (28,1,4) at abn = 110539, curr_dl_abn 110539 or 51650802 ms, rrbp = 0 Sending TLLI c886894e TFI: 13 PUA ( a) on (28,1,4) at abn = 110560, curr_dl_abn 110560 or 51651223 ms, rrbp = 0 tlli c886894e ul_tfi 13 resend PUA with no PCA at (28,1,7) missed 6 data blocks Sending TLLI c886894e TFI: 13 PUA ( a) on (28,1,4) at abn = 110575, curr_dl_abn 110575 or 51651523 ms, rrbp = 0 tlli c886894e ul_tfi 13 resend PUA with no PCA at (28,1,7) missed 18 data blocks No UD received (25 blocks): TLLI: c886894e TFI: 13 No UD received (25 blocks): TLLI: c886894e TFI: 13 No UD received (25 blocks): TLLI: c886894e TFI: 13 TLLI c886894e ul_tfi 13 1st uplink data block at (28,1,7) ul_state TRANSFER mc_state TRANSFER ulabn 110663 TLLI c886894e bsn at countdown 0 = 0 ulabn = 110663 TLLI c886894e final bsn 0, ulct_end = 110688, ulabn = 110663

TLLI Packet UL Assignment Packet Control Acknowledge (LCI, carrier id, TS) relative reserved block period block sequence number

4. GBL
4.1. UL/DL traffic
The GBL is terminated at the PICP. The processes handling incoming/outgoing traffic are Gb router (GR), process id 0d7h for DL and GTM process id 0d3h for UL.
PCU:emon_1101 % iir_mod 0d7h 0f8h iir_mod: iir_mask for process 0xd7 changed to 0x000000f8. PCU:emon_1101 % iir_mod 0d3h 0fch iir_mod: iir_mask for process 0xd3 changed to 0x000000fc.

System Performance Group Vienna Motorola Confidential Proprietary

Page 10/18

End2end optimisation PCU internal stats

052432535ms: FLOW_CONTROL_BVC_ACK PDU received on BVCI 22714 52435943ms: DL_UNITDATA PDU received. BVCI 30104, LLC len: 25, SUSPEND_ACK PDU received for TLLI C0860ABC 52442165ms : UL_UNITDATA PDU sent. BVCI 30104, PDU len: 1611, 0x1106 52442213ms: DL_UNITDATA PDU received. BVCI 30104, LLC len: 25, SUSPEND_ACK PDU received for TLLI C4835B04 FLOW_CONTROL_BVC_ACK PDU received on BVCI 22714 FLOW_CONTROL_BVC_ACK PDU received on BVCI 22714 52457641ms : UL_UNITDATA PDU sent. BVCI 23704, PDU len: 1611, 0x1104

TLLI: 0xc4835a8a TLLI: 0xc4835b04, PRP: TLLI: 0xc4835a8a

TLLI: 0xf1031774, PRP:

BVCI identifies also the cell LLC len: length of the LLC frame TLLI PDU len: reports always 1611, this is a bug.

4.2. PCU flow control buffer

The PCU buffer, (the leaky bucket) is handled by the Flow Buffer Manager (FBM). Especially when the SGSN is non Motorola and the track leads to a flow control issue this filter will give valuable info additionally to Gb logs as it not only reports what the PCU sends to SGSN, but also the real situation in the PCU buffer. To activate: iir_mod 0d5h 0f000h Example output
53872703 53877975 53882220 53882220 53887460 53910137 53997059 53999710 53999710 54002699 CELL CELL CELL CELL CELL CELL CELL CELL CELL CELL 5 5 28 28 28 83 83 14 14 83 CBL: FBM is CBL: CBL: FBM is FBM is FBM is CBL: CBL: FBM is 0 BMAX: 140625 R: 450 initializing the rate buffer 18 BMAX: 151875 R: 486 0 BMAX: 151875 R: 486 initializing the rate buffer sending fc with Bmax= 103700 sending fc with Bmax= 120000 18 BMAX: 145000 R: 464 0 BMAX: 145000 R: 464 sending fc with Bmax= 145300 decr incr decr and R= 332 and R= 384 incr decr and R= 465

Current Buffer Level BMAX maximum allowed buffer level. This is dynamically allocated by the PCU, depending on the number of cells handled by the PRP fc actual flow control message sent to the SGSN timestamp in milliseconds

System Performance Group Vienna Motorola Confidential Proprietary

Page 11/18

End2end optimisation PCU internal stats

Appendix A. Short Command reference

To set watch tlli globally (PRP)
msg_s 0d9h 9000h 0 0 7404 4 34 0ffh

To set watch tlli fro a specific tlli

msg_s 0d9h 9000h 0 0 7404 4 34 1 <tlli_byte3> <tlli_byte2> <tlli_byte1> <tlli_byte0> example msg_s 0d9h 9000h 0 0 7404 4 34 1 0ch 0 0c3h 0f8h * should produce * watch tlli enabled for tlli = c00c3f8h

To turn watch tlli off

msg_s 0d9h 9000h 0 0 7404 4 34 0

To print DL BLER and CS used on PRP.

iir_mod 0d9h 04200h

To force CS on the PCU (PRP):

msg_send 0d9h 9000h 0 0 7404h 4 47 <downlink_fake_flag> <uplink_fake_flag> Where <downlink_fake_flag> is: 0 = force CS1, 1 = force CS2, If allow_32_k_trau=yes 2 = force CS3, 3 = force CS4 255 = algorithm select Where <uplink_fake_flag> is: 0 = force CS1, 1 = force CS2, If allow_32_k_trau=yes 2 = force CS3, 3 = force CS4 255 = algorithm select

To print CS flags (PRP):

msg_send 0d9h 9000h 0 0 7404h 4 48

To print DL LLC frame info of PICP:

iir_mod 0d7h 0f8h

To print UL LLC info of PICP:

iir_mod 0d3h 0fch

To print filters:
iir_dis

To print TBF information of PRP:

iir_mod 0d9h 0c0000000h

To print PCU buffer information of PRP:

iir_mod 0d5h

System Performance Group Vienna Motorola Confidential Proprietary

Page 12/18

End2end optimisation PCU internal stats

Appendix B. Copy of PCU_Logging_Guide

Enable logging on the PCU via OMC-R remote access to the proper PCU card
To Do: 1. disable security timeout value on OMC-R or take care that it doesnt time out (30 minutes) 2. remote login to BSC MMI 3. look up local cell id: enter disp_gsm_cell <location of the cell> 4. change to security level 3 5. set_mmi exec_mon (go to GPROC) or Cntrl-N 6. disable security timeout on GPROC: msg_send 112 6 0 0 1c00h 1 7. rlogin to PCU MPROC: rl 254 1107h 8. to figure out the port hosting cell with local cell id from above: route logical 14 9. go back to the GPROC with Cntrl-D 10. rl 254 11<PCU slot got from thanks to step 8> 11. change to security level 3 12. disable secutiry timeout on DPROC: msg_s 23 1 0 0 8a04h 1 13. time_stamp on 14. dump the information reported after entering: iir_m 0d9h 0c0004000h ... CS and TBF information 15. to disable the logging and close the session: iir_m 0d9h 0 16. 17.
Result Step 8: OFFSET CPU MBOX OFFSET CPU MBOX OFFSET CPU MBOX ---------------------- ---------------------- ---------------------1 0x1106 ------........1 is our local cell id and it is hosted on card 1106

System Performance Group Vienna Motorola Confidential Proprietary

Page 13/18

End2end optimisation PCU internal stats

Appendix C. Uplink Power Control

V1.0 RAN 2/11/03 Updated to reference other docs.

See PRM LLD, ETSI 5.05, ETSI 5.08 for further detail. Closed Loop Power Control: Calculation of ms_pwr_offset fudge factor.
We want to vary the MS power offset according to how far away the BTS RxLev is from the power box mean. Pbm = pwr_box_mean Pbm_rxlev_diff = rxlev_bts pwr_box_mean. CH = rxlev_bts pwr_box_mean ms_pwr_offset CH = pbm_rxlev_diff ms_pwr_offset CH can vary in the range of gamma_0_offset (6) max_gamma (62) max_gamma will always = 62. Therefore ms_pwr_offset can range between 0 CH pbm_rxlev_diff i.e. 0 62 pbm_rxlev_diff This variation is CH should correspond to mobiles transmit capability variation i.e. max_ms_tx_pwr (33) min_ms_tx_pwr (5) = ms_tx_pwr_range (28) Setting ms_pwr_offset to max will then correspond to incrementing/decrementing the ms_tx_power by max of ms_tx_pwr_range (28). ms_txpwr_range won't be 28 always. The value depends on the min_tx_power and max_tx_power. Former depends on the freq band (GSM900, DCS1800) and later depends on the freq band and MSRA capability of the mobile. So the range would depend on which mobile you are using in which freq band.

[62 pbm_rxlev_diff] max_tx_pwr_range Therefore, Ms_pwr_offset = (pbm_rxlev_diff * max_tx_pwr_range) [max_gamma pbm_rxlev_diff] Need to kick mobile harder if pathloss doesnt vary and RxLev is still outside the power box. Example of Field Log: Out of Pwr Box, TLLI:c0000e88:ul_abn:202008:PrevGamma:6:NewGamma:6:ul_rxlev:82: ms_pwr_offset:5:ts:3:multiplier:-1 TLLI:0xc0000e88:ul_gamma sent in PCTA:3:TS:3 TLLI:0xc0000e88:ul_gamma sent in PCTA:14:TS:7 Out of Pwr Box, TLLI:c0000e88:ul_abn:202014:PrevGamma:6:NewGamma:6:ul_rxlev:84:

System Performance Group Vienna Motorola Confidential Proprietary

Page 14/18

End2end optimisation PCU internal stats

ms_pwr_offset:4:ts:3:multiplier:-1 Explanation: The value that is actually sent to the MS is in the ul_gamma sent line and it indicates which message it was sent in. It also indicates which timeslot the ul_gamma was sent for. In this case, the POWER BOX (ie where we want to keep the mobile) is set to: l_rxlev_ul_p = 30 (-80 dbm) u_rxlev_ul_p = 40 (-70 dbm) so we want to try to keep the MS transmitting at a power such that our RXLEV that we receive is ~-75dbm gprs_pc_alpha = 0 in this example (Close loop which is recommended). With this setting, we tell the MS which absolute power to transmit at. In GSM900, the max power that the MS can transmit is 39dbm see below. For a 2W mobile, the MS is capable of transmitting at a maximum of 33dbm. Therefore with the power control formula below, if the PCU wants the 2W MS to transmit at maximum power, it will send a gamma = 3 for the timeslot which tells the MS to transmit at 6dbs below 39dbm (or 33dbm). In GSR5x the PCU might send a gamma for two separate timeslots even in the case where only a UL single timeslot is active. This could happen when mobile just ended an UL (on TS 7) and started a new UL (on TS 3). We retain gamma for TS 7 if the previous UL were released normally. So we will have gamma values for two TS's available and we would send both to mobile in the PUA assignment. In PUAN however we send it only for the TS assigned for current UL TBF. In 1650 the PCU sends gamma only for the TS assigned on current TBF for PUA as well as PUAN. For PCTR we never send an altered gamma value. We always tell the mobile to go full power on the new TS assigned. GAMMA_TN (5 bit field) The GAMMA_TN field is the binary representation of the parameter CH for MS output power control in units of 2 dB, see 3GPP TS 05.08. The GAMMA_TN field is coded according to the following table: Bit 54321 00000 00001 :::: 11110 11111

CH = 0 dB CH = 2 dB CH = 60 dB CH = 62 dB

Collecting logs
- UL RXLEV should be between the cell parameters u_rxlev_ul_p and l_rxlev_ul_p for the majority of the run if all is working well and you should see In Power Box and not Out of Power Box: - iir_m 0d9h 0c0000000h - TLLI watch - msg_send 0d9h 9000h 0 0 7404h 4 255 1 00 00 01 00 (power control)

PRM SLLD V3.03 Section 2.6.1.1 Closed Loop Power Control

Closed loop power control can be achieved by setting to zero and becomes an algorithm very similar to that used in circuit switched power control. When this algorithm is used, the PCU effectively sends the mobile station the actual attenuation off maximum power, (CH) to transmit at. The mobile station uses the following equation to determine the power level to transmit at:

System Performance Group Vienna Motorola Confidential Proprietary

Page 15/18

End2end optimisation PCU internal stats

Where 0 is a constant that depends on the frequency band that the mobile is operating within. 0 = 39 dBm for GSM900 0 = 36 dBm for DCS1800 0 = 33 dBm for PCS 1900 0 = 39 dBm for GSM850 The base station then uses the receive level of the base station on each channel (SSb) in conjunction with the power box mean to determine the new attenuation level to be used. If the mobile is within the power box, no adjustment is necessary. If the mobile is outside of the power box then CH is adjusted accordingly and stored in the mobile context for the next opportunity to send power control information to the mobile. The Following Equations are used:

P = 0 CH

If ((SSb +18) > U_RXLEV_UL_P)

V V U _ R X L E_ U L_ P L _ R X L E_ U L_ P P w r B o x M e a n = 2
CH Re duction =

( SS b + 18 ) PwrBoxMean
2

If ((SSb +18) < L_RXLEV_UL_P)

CH Increase =
SSb:

PwrBoxMean ( SS b + 18 ) 2
L_RXLEV_UL_P: and U_RXLEV_UL_P 0 = -110 dBm 1 = -109 dBm 63 = -47 dBm

0 = -128dBm 1 = -127 dBm 127 = -1 dBm Open Loop Power Control

ETSI 5.08 10.2.1 MS output power

The RF output power, PCH , to be employed by the MS on each individual uplink PDCH shall be: PCH = min(0 - CH - * (C + 48), PMAX), (1) where CH is an MS and channel specific power control parameter, sent to the MS in an RLC control message (see 3GPP TS 04.60). For those uplink PDCHs, for which CH has not been defined, value 0 shall be used. = 39 dBm for GSM 400, GSM900, GSM850 = 36 dBm for DCS1 800 and PCS 1900 is a system parameter, broadcast on PBCCH or optionally sent to MS in an RLC control message (see 3GPP TS 04.18 and 3GPP TS 04.60). is the normalised received signal level at the MS as defined in 10.2.3.1. is the maximum allowed output power in the cell = GPRS_MS_TXPWR_MAX_CCH if PBCCH or CPBCCH exist MS_TXPWR_MAX_CCH otherwise

0 C PMAX

All power values are expressed in dBm. When the MS receives new CH or values, the MS shall use the new value to update PCH according to equation (1) 2 radio blocks after the end of the frame containing the last timeslot of the message block

System Performance Group Vienna Motorola Confidential Proprietary

Page 16/18

End2end optimisation PCU internal stats

containing the new value, which ensures 2 blocks time for processing even in case of timeslot reconfiguration. The MS may round the calculated output power to the nearest nominal output power value (see 3GPP TS 05.05) although a higher resolution is preferred. The output power actually transmitted by the MS shall fulfil the absolute accuracy as specified in 05.05. In addition, the transmitted power shall be a monotonic function of the calculated output power and any change of 2 dB in the calculated value shall correspond to a change of 2 1.5 dB in the transmitted value. The MS shall use the same output power on all four bursts within one radio block. When accessing a cell on the PRACH or RACH (random access) and before receiving the first power control parameters during packet transfer on PDCH, the MS shall use the output power defined by PMAX. MS_TXPWR_MAX_CCH is broadcast on the BCCH of the cell. A class 3 DCS1 800 MS shall add to it the value POWER OFFSET broadcast on the BCCH. GPRS_MS_TXPWR_MAX_CCH is broadcast on PBCCH or CPBCCH of the serving cell. If the MS accesses a cell on the PRACH before receiving GPRS_MS_TXPWR_MAX_CCH on PBCCH, the MS shall determine PMAX using MS_TXPWR_MAX_CCH as default. If a calculated output power is not supported by the MS, the MS shall use the supported output power which is closest to the calculated output power.

ETSI 5.05: 4.1.1 Mobile Station

The MS maximum output power and lowest power control level shall be, according to its class, as defined in the following tables (see also 3GPP TS 02.06). For GMSK modulation
Power class 1 2 3 4 5 GSM 400 & GSM 900 & GSM 850 Nominal Maximum output power -----8 W (39 dBm) 5 W (37 dBm) 2 W (33 dBm) 0,8 W (29 dBm) DCS 1 800 Nominal Maximum output power 1 W (30 dBm) 0,25 W (24 dBm) 4 W (36 dBm) PCS 1 900 Nominal Maximum output power 1 W (30 dBm) 0,25 W (24 dBm) 2 W (33 dBm) Tolerance (dB) for conditions normal 2 2 2 2 2 extreme 2,5 2,5 2,5 2,5 2,5

System Performance Group Vienna Motorola Confidential Proprietary

Page 17/18

End2end optimisation PCU internal stats

References
[1] PRM_Low_level_design [2] ETSI GSM05.03

System Performance Group Vienna Motorola Confidential Proprietary

Page 18/18