IUB

IUB Issues: Iub limiting, Frames late and Frames lost ratio (REAL CASE)

Slide title minimum 32 pt

(32 pt makes 2 rows

Text and bullet level 1 minimum 24 pt

Bullets level 2-5minimum 20 pt

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–—‘’‚“”„†‡•…‰‹›⁄€™−≤≥fifl

ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș

ΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏ

ЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐәǽẀẁẂẃẄẅỲỳ№

Do not add objects or text in the footer area

Ericsson Internal | 2012-03-14 | Page 2

Iub limiting in a real case

2nd Carrier Launched date

1st recommendation implementation

2nd recommendation implementation

pmCapAllocIubHsLimitingRatioSpi#

Indicates in what degree the HSDPA traffic in downlink for Scheduling Priority Indicator (SPI) # is limited by the Iub/Iur interfaces, between SRNC and RBS. A high value indicates that these interfaces limit the HSDPA traffic in a high degree. When the PM counter indicates a high value, you should consider extending Iub/Iur with higher HSDPA bandwidth.

Counter type: PegCounter is reset after measurement interval: YesCondition: The PM counter is valid for the flow controlled HSDPA flows only. The delay is between SRNC and RBS, that is, both Iub and Iur are included in the delay measurement.

The flow for this SPI has been turned on using the attribute IubDataStreams::schHsFlowControlOnOff.

The number of occurrences when the calculated capacity allocation figure is limited by the Iub high-speed bandwidth every 100 ms compared with the total number of 100 ms periods in the report output period.

Unit: 1%Undefined value: -1 Recommendations are described at the end of the presentation


(32 pt makes 2 rows









Example Issue: Accessibility issues, Iub Limiting and Transmission issues.

› Analysis: When the 2nd Carrier of this site (SXU1041) was launched, Iub limiting appears, the amount of traffic or any configuration issue is the cause, also this site have accessibility issues provoked by a neighbor.

Iub Limiting by hours after 2nd Carrier was

launched.2nd Carrier Launched

date

Recommendations are described at the end of the presentation


(32 pt makes 2 rows









Frames late




pmDchFramesLate

The number of DCH Iub FP frames arrived after ToAWE but before LTOA.

Counter type: PegCounter is reset after measurement interval: YesCondition: Measurement can be started on at least one DBCH device set. That is, state is operational and the device board has correct capability.Undefined value: -1

pmDchFramesTooLate

The number of DCH Iub FP frames discarded owing to too late arrival, that is, after LTOA.

Counter type: PegCounter is reset after measurement interval: YesCondition: Measurement can be started on at least one DBCH device set. That is, state is operational and the device board has correct capability.Undefined value: -1



(32 pt makes 2 rows









Frames lost




PmHsDataFramesLostSpi#

The PM counter counts non-correctly received HS-DSCH data frames in RBS.

Counter type: PegCounter is reset after measurement interval: YesCondition: This PM counter is valid for priority class #, regardless if the HS flow is flow controlled or not. The non-correctly received HS-DSCH data frames counted are the ones with wrong header CRC, wrong payload CRC, destroyed frames (wrong length) and the ones not received at all (which can be detected to a certain degree by the use of the Frame Sequence Number, limited by the FSN length of 15).Measurement can be started on at least one DBCC device set. That is, state is operational and the device board has correct capability.Undefined value: -1

Latest weekend losing frames stopped



(32 pt makes 2 rows









Frames lost ratioThroughput per User

The Traffic Handling Priority (THP) is according to 3GPP an entity that

enables association of a certain relative priority among interactive bearers.

The THP attribute gives the possibility to give traffic different scheduling

priorities in WCDMA RAN, by the use of the Scheduling Priority Indicator

(SPI). This results in a differentiation, based on the user priority, of the data

throughput when the resources are limited. By definition, priority is only

applicable to Interactive traffic class as it is an alternative to the absolute

guarantee of Guaranteed Bit Rate (GBR) traffic classes, and thus these two

attributes types cannot be used together for a single bearer.

The ARP that is sent from the packet core network over the IuPS interface

may be used together with THP to set an SPI in WCDMA RAN. This will give a more granular definition of the SPI configuration.

The Traffic Handling Priority attribute is defined in the HLR as part of the QoS

Profile Subscribed. SAPC may modify the THP attribute, as part of the Quality

Class Identifier (QCI), if 3GPP Gx Rel-7 or later is implemented. Also, SGSN

and GGSN have the possibility to set an updated THP used during the QoS

negotiation.

THP is used by the WCDMA RAN to prioritize traffic, both over the air

interface and in the ATM-based or IP-based transport interfaces to allow

prioritization over the transport network.

Figure shows an example on how a change of THP for a heavy user gives

the normal user a larger part of the available bandwidth in case of cell

congestion. The heavy user may have been identified by measuring the

amount of data that have been consumed during a period of time.


(32 pt makes 2 rows









Frames lost ratio






(32 pt makes 2 rows









Insufficient links (alarms) On October 22 star to have some ALARMS

about IMA Group Insufficient Links

The last of this kind of alarms presented on

NOVEMBER 2nd


(32 pt makes 2 rows









clock synchronization problem

Today is having “clock_synchronisation

_problem” ALARMS


(32 pt makes 2 rows









SXU1041 – Neighbor SXU5159 issues

Neighbor site SXU5159 had some issues that

affects SXU1041 performance.

Neighbor site SXU5159 had some issues that affects SXU1041 performance.


(32 pt makes 2 rows









SXU1041 – KPI´s

TRAFFIC


1st recommendation implementation 2nd recommendation

implementation


(32 pt makes 2 rows









SXU1041 – combined Accessibility

2nd Carrier Launched date 1st recommendation

implementation



(32 pt makes 2 rows









SXU1041 – F1 - KPI´s


(32 pt makes 2 rows









SXU1041 – F1 - KPI´s


(32 pt makes 2 rows









SXU1041

› Note: This Site does not have any lack of Pwr, Hw, DlChanlCode, etc. the issue is only in the Iub, that's why the load sharing parameters to GSM needs to be more aggressive than usual, because we need to start offloading traffic before.

› 1st Recommendation implemented on October 18th in the night: The proposal was to offload UMTS traffic to GSM avoiding Iub limiting.


(32 pt makes 2 rows









SXU1041› 2nd Recommendation implemented on October 29th in the night: The proposal was to

offload more UMTS traffic to GSM avoiding Iub limiting.

Note: pwroffset will still in 10.


(32 pt makes 2 rows









OBSERVATIONS

Sources:

http://cpistore.internal.ericsson.com/alexserv?li=en/lzn7350300r3b&fn=5_1551-lza7016003uen.h.html&ac=linkext

http://gask2web.ericsson.se/service/get?DocNo=7/22102-AOT101057/5&Lang=EN&Rev=C&Format=PDFV1R2&a=b

› This site still having accessibility issues.

› Traffic has offload to GSM.

› The Iub limiting has reduce.

› Lost Frames has stopped, and frames too late has increased.

› The site has Synchronization Issues.


(32 pt makes 2 rows









Documents

IUB