You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for your great work with this project. I'm following your research in this field and I think NG-Scope is a very useful tool for cell allocation analysis.
I'm using the remote UDP socket as an interface to retrieve UE information from NG-Scope. As this interface does only publish the information of the target RNTI/UE, I'm currently developing a procedure to automate the RNTI matching (finding the correct UE RNTI that belongs to my device). Therefore, I would need information (how many bytes sent in a segment) of all captured RNTIs/devices instead of just the target RNTI being published through the remote UDP socket interface.
I've seen in your code, that such a message type might've existed before and I wanted to ask whether you would be interested in discussing such here again?
I would be happy to provide an implementation and contributing it in a PR.
The text was updated successfully, but these errors were encountered:
Hey Bastian- I've reached out to you over email but not sure you've received that message; feel free to reach out to me at [email protected] to discuss further!
Hey NG-Scope team!
First of all, thanks for your great work with this project. I'm following your research in this field and I think NG-Scope is a very useful tool for cell allocation analysis.
I'm using the remote UDP socket as an interface to retrieve UE information from NG-Scope. As this interface does only publish the information of the target RNTI/UE, I'm currently developing a procedure to automate the RNTI matching (finding the correct UE RNTI that belongs to my device). Therefore, I would need information (how many bytes sent in a segment) of all captured RNTIs/devices instead of just the target RNTI being published through the remote UDP socket interface.
I've seen in your code, that such a message type might've existed before and I wanted to ask whether you would be interested in discussing such here again?
I would be happy to provide an implementation and contributing it in a PR.
The text was updated successfully, but these errors were encountered: