#ricp how to handle E2SM which relies on xapp // RIC-628 + RIC-444 #ricp
generally the RIC platform should not depend on E2SMs. On E2M side we have had an issue that this was not correctly implemented and it is now fixed as solution to https://jira.o-ran-sc.org/browse/RIC-444 (see the gerrit link in the JIRA issue).
As far as I understand there’s a similar issue in subscription manager visible as “e2err_RICEventTriggerDefinitionEmptyDecodeDefaultFail”. The discussion in the development team for this already started, but was on hold for the last two weeks due to ongoing holiday period. For now I also started a JIRA bug case for this: https://jira.o-ran-sc.org/browse/RIC-628 . I am not aware of a good workaround for this.
From: main@... <main@...> On Behalf Of Minhac Lee via lists.o-ran-sc.org
Sent: Wednesday, July 15, 2020 11:19 AM
Subject: [oran-sc] #ricp how to handle E2SM which relies on xapp
Hello, I'm Minha Lee.
As I thought, using different E2SM seems to be a cause of problem.