[srsran-users] [srslte-users] "Status"

[Andrea Valori]

Dear Francisco,
the report_json_enable feature is really very handy! Thanks for adding it.

Following up with the discussion, I am now trying to keep track of which
UEs (IMSI) are connected... One option I see is to track the messages in
the srsepc stdout (e.g. 'Attach Complete Message', 'UE Context Release
Completed')... this seems to work, but is there a better or more
straightforward way, in your opinion?

Thanks,

Andrea

On Thu, 6 May 2021 at 23:19, Andrea Valori <avalori at gmail.com> wrote:

> Francisco,
>
> the t option is something I found and used extensively, the problem is how
> to extract the information afterwards. I sent the stdout to a text file and
> then created a Python script to extract the text and parse it... it works
> but definitely is not clean.
> Many thanks for mentioning the "expert json report" that is something I
> was not aware of and I will investigate...
>
> Andrea
>
>
> On Thu, 6 May 2021 at 21:29, Francisco Paisana <
> francisco.paisana at softwareradiosystems.com> wrote:
>
>> Ah, I also forgot the new way to get enb reports via
>> "--expert.report_json_enable=true". That should create a new file in
>> /tmp/enb_report.json with all the enb parameters in json format.
>>
>> Kind Regards,
>> Francisco
>>
>>
>> On Thu, May 6, 2021 at 8:19 PM Francisco Paisana <
>> francisco.paisana at softwareradiosystems.com> wrote:
>>
>>> Ah apologies you mentioned the srsenb traces. You could also "tail" the
>>> enb.log for "PHR" or any other information.
>>>
>>> Kind Regards,
>>> Francisco
>>>
>>>
>>> On Thu, May 6, 2021 at 8:17 PM Francisco Paisana <
>>> francisco.paisana at softwareradiosystems.com> wrote:
>>>
>>>> What about pressing "t" in the srsenb command line to get the traces?
>>>>
>>>> Kind Regards,
>>>> Francisco
>>>>
>>>>
>>>> On Thu, May 6, 2021 at 2:08 PM Andrea Valori <avalori at gmail.com> wrote:
>>>>
>>>>> Dear All,
>>>>>
>>>>> Is there a way to get a "status" of the system?
>>>>> Questions I would like to answer are of the kind
>>>>>
>>>>>    1. "which users are connected?"
>>>>>    2. "which one is their phr?" (to understand if they are moving
>>>>>    away and likely to drop)
>>>>>
>>>>> I seem to understand that this is not something so simple to
>>>>> implement... at the moment I can get the answer to 1. by tracking attach
>>>>> and detach from the stdout of srsepc, and I can get answer 2. from tracking
>>>>> and parsing the trace of srsenb... not really something "straightforward",
>>>>> but maybe I am missing something?
>>>>> Is there a more sensible way to approach this? Or maybe something
>>>>> already implemented in the stack that I am not aware of?
>>>>>
>>>>> Cheers
>>>>> _______________________________________________
>>>>> srslte-users mailing list
>>>>> srslte-users at lists.softwareradiosystems.com
>>>>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>>>>
>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20220216/eb9706b8/attachment.htm>