100% found this document useful (1 vote)
624 views5 pages

RRC Connected User License: Re-Balance Between Enodebs

This document discusses rebalancing RRC connected user licenses between enodeBs. It involves querying the maximum historic RRC users and congestion counters for each enodeB, summarizing the current license information, and generating a change request to reduce licenses for some enodeBs and increase them for others. The goal is to equalize the license distribution based on recent usage and congestion levels, avoiding future congestion issues.

Uploaded by

quyphamvan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
624 views5 pages

RRC Connected User License: Re-Balance Between Enodebs

This document discusses rebalancing RRC connected user licenses between enodeBs. It involves querying the maximum historic RRC users and congestion counters for each enodeB, summarizing the current license information, and generating a change request to reduce licenses for some enodeBs and increase them for others. The goal is to equalize the license distribution based on recent usage and congestion levels, avoiding future congestion issues.

Uploaded by

quyphamvan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 5

RRC connected user license

re-balance between enodeBs


1. Query Maximum RRC connected user of enodeBs

 Collect maximum RRC connected user of all enodeB for long-enough time (such as last 30days)
 PRS query enodeB’s maximum RRC connected users and E-RAB congestion counters:
• L.Traffic.eNodeB.FDD.User.Max : maximum RRC connected user of enodeB
• L.E-RAB.FailEst.NoRadioRes.RrcUserLic : number of times E-RAB setup failure due to RRC user congested
2. enodeB License query:

 Query license information of all enodeB and export to excel files.


Network Performance User Experience Terminal

3. License summary

 License name: RRC connected User (FDD)


 Allocated: current amount of license for each enodeB
 License type update:
• Permanent: expiration date is permanent
• Temporary: expiration date is an actual day ( for eg: 2018-12-16)

Only permanent enodeB can be exchanged license


Network Performance User Experience Terminal

4. CR to rebalance license
L.Traffic.eNod
Current congested Target
Date eNodeB Name License type eB.FDD.User. E-RAB SSR Adjust
license times license
Max
Overall TH_SSN_SAM_SON Permanent 29 90 0 100 40 -50
Overall TH_SSN_HAI_BA_TRUNG Permanent 37 115 0 100 55 -60
Overall TH_SSN_HO_XUAN_HUONG Permanent 39 100 0 100 50 -50
Overall NA_CLO_CUA_LO_4 Permanent 42 90 0 100 60 -30
Overall HDG_CLH_CHI_MINH Permanent 45 100 0 100 60 -40
Overall HPG_HAN_DA_NANG_3 Permanent 55 50 35774 71.2103 100 50
Overall HPG_HAN_KDT_SAO_SANG Permanent 55 50 11609 84.3957 80 30
Overall HPG_LCN_QUAN_NAM Permanent 55 50 9951 88.3425 80 30
Overall HPG_TNN_NUI_DEO Permanent 55 50 9889 86.7537 80 30
Overall HPG_NQN_HOANG_DIEU Permanent 55 50 9522 89.049 80 30
Overall HPG_HBG_KS_HUU_NGHI Permanent 110 100 30323 86.0084 130 30
Overall HPG_DKH_HAI_THANH Permanent 110 100 18585 90.1117 130 30

 Evaluate for only “permanent” enodeB based on:


• RRC user max for 30 days
• Current license amount
• E-RAB congestion times
 enodeB candidate for reduction rule to avoid congestion after reduction:
• RRC users max should be at least less than 50% of current license amount.
• Target license should be at least 20% higher than maximum RRC users.
 enodeB for expansion:
• Target license depend on E-RAB setup success rate, E-RAB congestion times
• Total reduction and expansion license amount must be equal.

You might also like