Need Assistance with Adding 'Vendor Name' to RIC Indication Header

[mohit4444]

Hello Community,
I’m looking for some guidance on how to add the 'vendor name' to the RIC Indication header. If anyone has experience with this or can point me in the right direction, I would greatly appreciate it.

Thank you in advance for your help!

[pgawlowicz]

You can add it here: https://github.com/srsran/srsRAN_Project/blob/main/lib/e2/e2sm/e2sm_kpm/e2sm_kpm_report_service_impl.cpp#L62

[mohit4444]

Thank you for your assistance. I’ve implemented the suggested changes, and I can confirm that the vendor name is now being received by the OSC RIC. However, it seems that the OSC RIC is unable to decode it, as shown in the attached images. Could this be an issue with the OSC RIC?

[pgawlowicz]

indeed, it is not decoded, you can add it here:
https://github.com/srsran/oran-sc-ric/blob/main/xApps/python/lib/e2sm_kpm_module.py#L60

[mohit4444]

You can ignore the side note in the previous reply. The main issue is that the optional params are not being decoded. Is it possible for you to give me an encoded RIC indication header (with vendor name and sender name)? I'll hardcode it and see if it's being decoded. Thank you for your guidance!

[pgawlowicz]

It seems the header is not correctly decoded in the ricxappframe module:
https://github.com/o-ran-sc/ric-plt-xapp-frame-py/blob/master/ricxappframe/e2ap/asn1.py#L138

The message received from the socket contains the vendor name string, but after decoding RIC Indication in the ricxappframe module it is missing.

[mohit4444]

Exactly! Should we expect a patch release in the near future?

[pgawlowicz]

Unfortunately, we do not plan it.

[mohit4444]

I understand. Thank you! @pgawlowicz