-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to identify Secondary cells for Carrier aggregation LTE_CA, LTE_CA_NR #28
Comments
That's a bit complicated issue. When it comes to NetMonster there's another layer of data post-processing which brings more light to secondarily serving cells. It utilises cached cells (from log) and attempts to figure out a possibility of aggregation. Since NetMonster Core works just with non-cached data, functionalities are limited. Secondarily serving cells are marked only in NR NSA mode and on select Android versions where PhysicalChannelConfig was accessible. |
thanks |
How can PhysicalChannelConfig be used to identify secondary cell(s)? |
@mroczis If it's okay with you to share, which logs exactly does Netmoster look at to make a guess about the secondary cells? |
#mroczis could you detail please how you get secondary cells? Is it possible to add this feature in netmonster-core? Thanks. [Edit July 10th]: I may understand what mroczis meant about logs and PhysicalChannelConfig... ;) |
I have been searching online for this and didn't find an answer, so I am opening this issue for little guidance.
I am building an application that collects signal information. I ran my application alongside Netmonster and when LTE_CA is discovered Netmonster's UI shows a Primary cell followed by some secondary cells. From Netmonster Core I get the list of cell infos, but how to Identify secondary cells which are being aggregated in LTE_CA or LTE_CA_NR.
Any links or directions will be really helpful.
The text was updated successfully, but these errors were encountered: