Skip to content
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

Gnb ID Display for NR and Gnb ID Calculator #42

Open
christianrowlands opened this issue Apr 15, 2024 · 5 comments
Open

Gnb ID Display for NR and Gnb ID Calculator #42

christianrowlands opened this issue Apr 15, 2024 · 5 comments

Comments

@christianrowlands
Copy link
Owner

Originally requested by @high3eam in this comment.

Describe the solution you'd like
From @high3eam :

Since there is no gnb id displayed in NR-SA mode and there are different gnb id lengths defined by 3GPP, I was wondering if it would be possible to implement an option in settings to set the gnb id length for a specific operator.
Like: The user enters a PLMN and can define the appropriate gnb id length (e.g. 24+12). That way, a correct gnb id and sector id could be displayed on the NR dashboard and even logged to csv/geopackage.

Cellmapper does this, too, but not in an elegant way (reports by users to Cellmapper admins -> hardcoded lengths baked into source code).


From @christianrowlands :

As for the gnb id, I have wanted to get that displayed for NR since I added support for it but that variable length has made it hard. There is an issue open with Google to add support in their API to get the number of bits associated with the gnb id, but I doubt they are going to add that: https://issuetracker.google.com/issues/319966463

Where do you typically look up the provider specified gnb id length?

Yes, I could add a setting that takes in a map of PLMNs and corresponding bit length of the gnb id. Let me think through how I want to accomplish this.

I really wish that NR was the same as LTE and it was a fixed length. I am not sure the added complexity is worth it, but 🤷


Additional context
Add any other context or screenshots about the feature request here.

@christianrowlands
Copy link
Owner Author

There is more context here

and here

@high3eam
Copy link
Contributor

@christianrowlands Calculator works well, great addition!

Example screenshots from Cellmapper

@christianrowlands
Copy link
Owner Author

Thanks for the screenshot. I am also working on a mapping feature, and now that I see that I am curious how I can make two towers show up at the same location like Cell mapper does. I bet I could automatically figure out the bit position if two NCIs show up at the same location.

@high3eam
Copy link
Contributor

@christianrowlands Since Cellmapper Android app and server-side backend and frontend are proprietary and not opensource, this is an extremely interesting feature. It would also be a lot easier to report bugs or fix them directly in open source code. So I think there are a lot of people interested in this as well.

Could you elaborate on the "two towers, that show up at the same location" part?

@christianrowlands
Copy link
Owner Author

I am glad to hear that there is interest in the map feature!

What I really mean by "two towers" is two sectors on the same gNodeB. I have exported the database from OpenCelliD and am planning on using that for the tower database. However, I was already worried about how to represent two sectors on the map that show up at exactly the same lat/lon, but I could probably just run through all the different bit combinations on the NCI until I get a gNB ID that matches between the two NCIs, and now I know what mapping the provider uses for the gNB IDs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants