Suggestions on supporting custom E2 service models and new RAN functions? #272
-
Hello, I was wondering if there was any documentation discussing how to add support for new E2 service models? If there is no existing guidance on this yet then that is OK, but I just wanted to check if there are any high-level pointers before I set off on my own. Particular topics I am wondering about:
Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Hi, You can have a look into the Specifically, adding a new metric would require (Step 1) registering a new metric in the Note that the metric definitions (Step 1) are then checked against the metric definition from ORAN specifications -- here we have structured all ORAN metrics from O-RAN.WG3.E2SM-KPM-R003-v3.00 (that are mainly based on 3GPP TS 28.552). So if you need a custom metric, then you need to add a new metric definition also there. Best, |
Beta Was this translation helpful? Give feedback.
Ah, you actually ask about adding a new E2SM model. Unfortunately, currently, we do not have such guideline. However, we already have E2SM_KPM and E2SM_RC, so only E2SM_CCC is missing. We highly recommend extending those service models as they are the only models defined in ORAN specs.
The ASN.1 code is generated automatically from ASN.1 specification from the related ORAN documents.
If you need your own custom RAN function (service model), you need to define it (together with ASN.1 messages) to be compliant with E2SM speficication (i.e., O-RAN.WG3.E2SM-R003-v03.01)